Trigger Test Plan

 The original proposals for ACD STRs:

• STR21c: ACD channel uniformity tests
  1. Use charge injection to verify GEM veto list channel map & check ROI arrival time uniformity.
  2. Max charge injection to check CNO trigger tile by tile and record arrival time.
  3. Redo test 1 with redundant side of GASU.
• STR21a: ACD TREQ scan
  1. Treq test for a few tile against the muon telescope to get an initial mean delay, and check ACD trigger timing resolution. (A slight modification we would like is to add some tests with muon telescope covering some tiles on the side, in addition to the nominal central ACD tiles on the top).
  2. Treq test for all ACD tiles using tower data and TKR trigger as timing reference. 
• STR21b: ACD TACK scan
  1. Scan ACD hit map latching delay and stretch parameters.
  2. ACD TACK delay scan with all towers using TKR trigger. (This test with a slight variation of using ACD itself as trigger can be performed in the tent, which is highly desirable to exercise the script and using the time available to accumulate large statistics which may be more difficult later due to full LAT schedule constraint)
• STR24: ACD trigger efficiency
  • Muon data taking using towers and TKR trigger.
• STRyy: ACD veto test
  1. ACD veto test with CAL LE as base trigger and activating TKR+ROI veto for muon data collection.
  2. ACD trigger rate test using ACD ROI as triggers to map out individual tile trigger rates.  

Given the change of plan to perform ACD tests after all towers are installed for the full LAT, we can take advantage of the interim time while ACD is in the tent to split the ACD tests into early tests with ACD in the tent, and others merged into standard LAT level tests. A possible split is reflected in the color marked on the above tests: Red items can be performed with ACD in the tent (some needs the muon telescope); the Dark Blue items will be included as part of the standard LAT level tests.    

LAT Level Tests:

The current draft of the LAT level test plan