*** DRAFT *** Trigger Test Plan       Update  Oct/11/04


 Tower level Trigger tests         
 -------------------------

 The trigger test will heavily rely on the external scintillator cosmic muon 
 trigger as a reference for timing, unbiased source for efficiency checks, 
 as we move in different towers under the muon telescope. The Muon trigger 
 rate is ~5 Hz. It would be potentially beneficial to add the MiniACD in
the towere test as it gives an independent fast timing signals matching
the tower fiducial.       

 1) CAL trigger frontend setup check
    Purpose: Check channel uniformity for noise/threshold, pulse height, 
             relative timing. Check CAL-Hi threshold behavior and difference 
             vs CAL LE for same threshold.   
    Setup:   Charge injection triggers on CAL alone. 
    Test Time:      4 hours ? 
    Analysis Time:  8 hours 

 2) TRK trigger frontend setup check
    Purpose: Check channel uniformity for noise/threshold, relative timing.
    Setup:   Using the Cal strobe, but details to be defined after our 
    first play with a tracker. 
    Test Time:      To be defined.
    Analysis Time:  To be defined. 
    (This may well be longer than the CAL because the more significant 
     nonuniformity concerns.)    

 3) GEM Timing alignment:
    Purpose: Check time alignment of each GEM trigger input vs the external 
             muon trigger to verify the time alignment and jitter for each 
             Trigger Input. 
    Setup:   Trigger on Ext-mu and one Trigger Input to be tested to scan 
             over a range of GEM input delays for this Trigger Input. 
             Examine the fraction of Ext-Mu events with GEM condition 
             summary also showing the Trigger Input being on. Because the 
             limitation of current GEM logic and DAQ data, this has to be 
             done for each Trigger Input separately at present.The timing 
             scan also has to step over the full 16 tick delay range to 
             see the overlap falling edges on each side to fit for center 
             time and jitter. Each scan point needs ~5000 events to get a 
             reasonable precision.       
    Test Time:  Total 9 hours 
       a) CAL LE vs Ext-Mu    16*5000 events ~ 16000 sec   4.5 hours    
       b) TKR vs Ext-Mu             "           "           "
       Note: at single tower level, there is no CNO/ROI.
             CAL Hi not explictly tested here. Rely on test 1) to ensure 
             relative timing between CAL Hi and CAL Lo.    
    Analysis Time:  2 hours  

    Note: If we can modify the GEM window turn logic, we can potentially 
          do all inputs simultaneously, to save testing time by a factor 
          of 2 at tower level. It has a larger benefit factor when including 
          ROI,CNO from ACD in the LAT level test, where time is more 
          critical. If we can get additional timing DAQ data from GEM, we 
          probably won't need a timing delay scan. Just one or two tests 
          of 5000 events, total <1 hour for the whole test. The result 
          will also be more direct and reliable than the scan fits, with 
          a simpler analysis. The possible additional DAQ timing data will 
          also allow continued monitoring of trigger timing during any 
          kind of data taking so that repeated dedicated tests on the 
          would not be necessary.  

 4) Subsystem TACK delay test:
    Purpose: Check the trigger output delay timing for latching subsystem 
             data is optimal.
    Setup:   Trigger on Ext-mu only, scan the TACK delays for all subsystems 
             simultaneously, then analyze data MIP pulse heights to find 
             the optimal TACK delay. 
    Test time: 8 point scan total (5 hours ?)              
    Analysis time:  4 hours

 5) Main efficiency test run:
    Purpose: Running all triggers on cosmic muons to cross check efficiency
             to eaxmine overall efficiency as well as uniformity.
    Setup:   Trigger on Ext-mu, CAL, TRK, for a large data sample. 
    Test Time:      4 hours ? 
    Analysis time:  4 hours ?      

Note: 
a) Tests need to be performed in sequence (except 1 & 2 are independent).
b) The analysis time is an interesting issue: how long does it take to
   process the data ? The test sequence depends on the analysis result 
   from the previous test before can proceed to the next test in many 
   cases so that the total real time should include analysis time in the 
   chain.
c) There is no suitable particle test for CAL Hi. Have to rely on the 
   charge injection tests to establish threshold and timing vs CAL Lo.
d) ACD triggers can only be formally tested at LAT level (but we are 
   using mini ACD to set up the test procedure).        
e) GASU/GEM is nominally tested by Mike. Do we also need to add a formal
   Q/A test procedure for GEM as part of trigger tests ? This could be 
   potentially quite complicated to cover allthe corners.   
f) Many tests above have obvious overlaps with other subsystem tests.
   How to integrate the tests ?  
    
LAT Level tests
===============

LAT level test details still to be defined.

Some basic principles: 
We believe the tower level tests are the most important to validate the 
CAL/TKR triggers in detail. Once ensured the internal integrity of the 
CAL/TKR triggers. The LAT level tests can potentially use just the 
CAL/TKR triggers to cross check each other and checking the ACD triggers.