CALICE Test Beams at DESY/CERN in 2006 - ECAL Task List

Modified at CALICE ECAL meeting at UCL, 6-Mar-2006

This is a first attempt to define specific tasks - mainly for ECAL - for the CALICE test beams at DESY and CERN in 2006. The list was compiled from discussions in the UK, therefore at present only includes names of people in the UK and where they are interested in contributing in the short term.

We know there is much activity in these and other areas outside the UK, but we do not have a complete list of this and did not try to guess. Both the list and the names will evolve with feedback.

The aim is to ensure that all the necessary tasks have been identified and that someone is committed to producing results in every area. There is a sigfnificant amount of code already existing (Calice-SW; Goetz G.; George M.), and people are needed to use this to carry out the studies. Could groups (or individual people) please contact us to say which areas they are interested in working on, or to add additional items to the list? We can then produce a revised list which can be discussed further at the next Calice ECAL meeting at UCL on 6-March.

Paul Dauncey, David Ward, Nigel Watson - 09-Feb-2006

CTA (Chris Targett-Adams), FS (Fabrizio Salvatore), MFG (Michele Faucci-Gianelli), MG (Mike Green), GM (George Mavromanolakis), DRW (David Ward), WY (Wenbiao Yan), PD (Paul Dauncey), AM (Anne-Marie Magnan), HY (Hakan Yilmaz), YM (Yoshi Mikami), NKW (Nigel Watson).
MR (Manqui Ruan, LAL), EG (Erika Garutti), BB (Bernard Bouquet), DB (Dave Bailey), RP (Roman Poeschl), GG (Goetz Gaycken), MGroll (Marius Groll), SK (Sven Karstensen)

Data/Model comprisons
  1. Energy resolution vs. energy, angle - YM/NKW + MR
    Can only be meaningful when shower fully contained/detector complete
  2. Position resolution vs. energy, angle - AM/PD/HY + GM + MR
    Individual hit resolution in each layer
  3. Angular resolution vs. energy, angle - AM/PD/HY + NKW/YM + MR
  4. Comparision and tuning of simulation to data - CTA + DRW + MR
  5. Comparision of calibrations in cosmics vs. real data - MR
  6. Efficiency, dead space between pads and wafers - GM + MR
    Estimates of individual sensor response, and accuracy of modelling of geometric inefficiency
Electronics/DAQ understanding
(This could be done either in LCIO/with Marlin or, for very fast turnaround before LCIO conversion, using the binary files themselves.)
  1. Coherent noise - CTA + GG
    Study of sources of noise in the system, why they vary between configurations, how we minimise the noise using the VFE timing sequence.
  2. Crosstalk - CTA + BB
    In VFE calibrations runs, pulse one channel, look at others. Will same cross-talk be present in beam data?
  3. Shaping times - CTA
    Measure for each preamplifier using both VFE calibration runs and cosmics (or beam) HOLD scans. Determine channel-by-channel correction to the gain if all channels not the same.
  4. HOLD timing setting - CTA + DB
    Urgent - needed immediately! Determines the HOLD delay to actually run the system - current cosmic run may not have optimal setting!
  1. Tracker calibration - MFG, EG, MGroll. (MFG to travel to DESY for this)
    Includes survey/alignment of drift chambers relative to detector stage, mapping of material upstream of ECAL front face and track fitting itself. Determination of drift velocity (+its stability), chamber efficiency with modified gas mixing fractions (non-flammable, but less efficient).
  2. Pedestals vs. time, noise vs. time - CTA
    Determination of stability
  3. Pedestals vs. temperature, noise vs. temperature - CTA
    Determination of stability with ambient conditions, and precision with which temperature should be recorded during running.
  4. Cosmics data compatibility - GM
    Compare gain calibration from early 2005 cosmic running with most recent data, understand any changes.
  5. VFE calibration - GM
    Compare with gain calibrations determined from cosmics and/or beam data. If useful/compatible, then see "Run Planning, 2".
  6. Electron beam calibration - NKW/YM
    Is it possible to select a subset of reconstructed electron events to extract cleaner MIP peak? If so, then see "Run Planning, 3".
  7. Production data reconstruction - GM
    Systematic production of reconstructed data files for all runs using appropriate mappings, conditions, etc.. Output LCIO files with reconstructed objects, available to collaboration.
Run planning
  1. Optimisation of missing slab positions - DRW + AM/PD/HY
    Study where to place inactive slabs if insufficient wafers are produced in time to fill 30 layers at 6 wafers/layer
  2. Need for electronics calibration; how often? - CTA + RP
    Determine frequency required based on stability study
  3. Need for electron beam calibration - YM/NKW
    If "Reconstruction 6." possible, define data required (spatial distribution into ECAL, no. good events/beam position, hence time estimate for programme).
Run monitoring
  1. Immediate online monitoring - PD
    Timescale of few seconds: simple, always available, predefined histograms, real time.
  2. Semi-online bin file monitoring - GM
    Timescale few min. - 30 mins.: operate on binary files from DAQ, not LCIO, present histograms (hits, energy, ..., per layer, event, DAQ rate, aerage pedestal, etc), event display (can be configured different frequency to histograms). Includes diagnostic test programs which can be modified/run on shift to study individual channels.
  3. (Near-offline)
    (a)LCIO conversion (could use output of 2, above)
    (b)LCIO monitoring
    - GG + RP
    Timescale ~1 day: offline job which can include any contributed Marlin processor, allows more thorough study of data without having to access dCache - needs appropriate mapping file to be used, so some delays likely if configuration changed during running - PC and LCIO installation for this possibly to be provided by HCAL people?
    Read whatever LCIO files are available on 3TB NFS disk, expect these files will be deleted after 1-2 days (and not written to dCache)
  4. Book keeping during shifts - EK -> SK
    Electronic logbook (must be available to read outside testbeam lab.), tabular summary of each run configuration/angle/energy/total events/mapping files, etc.)... Expect to use common logbook with HCAL (c/o DESY)? Temperature also to record.
    Profit from GANMVL/EUDET effort c/o Sven K.
  5. Recording test beam conditions - EK -> SK
    From accelerator: at DESY (manual input magnet current to define beam energy - limited information), at CERN (perhaps H2/4 + H6 beamline, beam parameters available electronically? Perhaps into conditions data?)
    Ask SK to liase with CERN.
  6. Recording physical configuration - EK -> SK
    Need survey of drift chambers/scintillators/position of detector on stage, plus many photographs of experimental area.
    CERN Survey Group should be aware of CALICE requirements before installation.
  1. DONE: Digitisation of tracking hits - FS
    Drift chambers currently record all individual energy deposits, need to remove low energy simulated hits at appropriate level, store as tracker hits
  2. DONE: Truth particle information - FS
    Positions (and ideally momentum) at tracking chambers and also immediately in front of ECAL front face should be stored
  3. Digitisation of ECAL - CTA, AM
    Add noise (channel-by-channel), threshold, time-dependence due to preamp shaper, crosstalk, coherent noise. This should be implemented as a Marlin processor, build on existing work.
  4. Production MC simulation - FS + DB
    Systematic mokka production of standard MC samples of 100k events for each angle/energy/stage position and detector configuration, based on initial schedule of measurements to be made with beam. Output LCIO files available to collaboration.
  5. Production MC reconstruction - MFG/FS + DB
    Systematic event reconstruction, application of any default digitisation, and making samples publically available. Output LCIO files with reconstructed objects available to collaboration.
  6. Simulation of Cerenkov chambers - ??
    These will be part of the beamline instrumentation for the CERN runs, and need to be simulated