Last Update: Sep/27/05

The proposed early ACD trigger tests we to be performed in the tent: 

All tests are intented to be run with LATTE 4, with only ACD+GASU 
and some with muon telescope. 
The GASU for this test has to be a new version that includes conditions 
arrival times and ACD LRS counters.

1) ACD channel uniformity map
   This test is a prerequisit for establishing the ACD channel connectivity 
   and uniformity before the other trigger tests related to ACD. 
   a) Charge injection tests are first performed at muon signal level for 
      one tile at a time to check GEM veto list channle mapping and record 
      ROI trigger arrival time. 
   b) Similar test with maximum charge injection and lowered HLD threshold 
      to verify the CNO trigger and check GEM CNO arrival time for each tile. 
   c) Given the extensive ACD control logic in the GASU, repeat test a) 
      using the GASU redundant side. This test only requires the ACD 
      detector and a GASU teststand. 
   Test procedure:     Performance & ops doc test 6.4.2.9
   Expected duration:  30min

2) ACD TREQ timing resolution test
   This test is aimed at an early timing test for the ACD ROI trigger to 
   establish the typical timing parameters, which are essential for defining
   the setup of many other LAT level trigger tests which will be using the 
   ACD as a trigger. The existing I&T muon telescope will be place over 
   a few chosen tiles on the top plane as well as some side tiles in turn
   and the standard tower level TREQ test will be executed using the muon
   telescope as a timing reference to determine the mean arrival time for 
   the ACD ROI trigger and measure the timing resolution for the few 
   chosen tiles.

   Test procedure:     Part of Performance & ops doc test 6.4.2.1
   Expected duration:  5 hours

3) ACD hit latching control parameter tuning
   This test is aimed at verifying the optimal settings of ACD hit delay 
   and stretch parameters for data latching. Taking the preliminary TREQ 
   alignment for ACD ROI trigger and the standard GEM window width, verify 
   the ACD data latching for various combinations of delay and stretch 
   parameters using ACD ROI as trigger to collect small amount of cosmic 
   muon data at each point. This is mainly to ensure the data latching 
   parameters not too close to the data buffer edge.          

   Test procedure:     Part of Performance & ops doc test 6.4.2.2
   Expected duration:  30min

4) Early ACD standalone TACK scan
   This test is aimed at an early tests on the ACD TACK optimization, with
   a similar procedure as the eventual LAT level TACK scan, except this 
   test will use the ACD ROI itself as the trigger and can be performed 
   with just ACD and a GASU. This will allow accumulation of large 
   statistics while waiting for the LAT integration, while the LAT test 
   later will be more constrained in time by the overall schedule.    

   Test procedure:     Part of Performance & ops doc test 6.4.2.2
                       (except using ACD to trigger instead)  
   Expected duration:  8 hours

5) ACD trigger rate test
   This test is aimed at identifying potentially hot ACD trigger tiles.
   By grouping the ACD tiles into ROI triggers and take cosmic muon data,
   the GEM veto list can be checked to see if a particular tile is 
   generating abnormally high rate of triggers. This test will be part of 
   the LAT level test later, but the other tests using ACD will need to 
   know the hot channels in advance. 
      
   Test procedure:     Performance & ops doc test 6.4.2.6
   Expected duration:  30min