BCAL Action Items and Working Tasks

From GlueXWiki
Revision as of 18:37, 9 April 2015 by Zisis (Talk | contribs) (Created page with "= Finalize Spring running conditions = = Detector and Analysis Action Items = #Take LED runs to check system (Elton and Noemi) #Investigate pedestal parameters for differen...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Finalize Spring running conditions

Detector and Analysis Action Items

  1. Take LED runs to check system (Elton and Noemi)
  2. Investigate pedestal parameters for different temperatures (Tegan)
  3. Pedestal-threshold fluctuation effect: fluctuating atten lengths, etc
  4. mod7 vs mod8 running (Mark?)
  5. Analyze runs at different overbias for efficiency/noise (Ahmed)
  6. Think about how best to use BCAL-triggered runs to study calibrations (Andrei and Zisis)
  7. Investigate how to check efficiency vs DAQ thresholds (Elton)
  8. Determine effective velocity for each channel (George)
  9. Determine time-walk corrections (George)
  10. Determine time offsets (?)
  11. Cosmics at Regina to check reflections (Noemi, Laura) - Elton’s scripts
  12. Cosmics with BCAL self-triggering (?) - CDC people are included, Beni’s data (A+Z)
  13. Long-term LED pulser running to validate relative monitoring (?)
  14. TDCs from pulsers, cosmics, data (?) - Occupancy plots- GV’s stuff
  15. One-ended hits (Andrei, Zisis)

Simulation & Reconstruction Action Items

  1. Rerun cosmics with lower threshold (Irina, Andrei)
  2. Check new dark hits code after David's adjustments (Tegan)
  3. Shower curvature tables: compare KLOE to IU codes (Tegan, Andrei)
  4. Software benchmark hangup: BCAL code (mcsmear) - not multithreaded?
  5. z-coordinate determination from up/down amplitude ratio (Tegan, Andrei)
  6. Cleanup: (Tegan, Will L.)
    1. Set variable “failures” to a number other than zero (e.g. -9999 or similar)
    2. Comb code for constants to be pulled out into a database
  7. Sampling fraction tables
  8. Charged particle simulations (Andrei, Irina)

Note on sensor temperatures

The +5C temp is our planned operation for when the SiPMs have sustained radiation damage, so we may be good to run higher in the beginning.  We should look at the data we took and see if the 24C->18C->12C shows an effect somewhere.  Eugene expressed a desire to run at a temperature and other settings that we think we would want to run in the fall, and possible set those for our upcoming spring run.  Going to lower temps now would a) test the system to make sure we can work with chillers at +5C (SiPMs at 7-8 C) for long periods, and b) give us a bigger lever arm on data.  We should come up with a plan of how to decrease the temps over the years/months, perhaps based on accumulated neutron fluence, or something similar, with a possible goal of trying to keep the resolution constant as noise increases due to degradation.