SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 1/7 SVAC 8 tower testing+ACD Anders and Eduardo

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 2/7 The rationale for SVAC Data Taking Assumptions behind today’s proposal –Tests of 8 tower testing + ACD will be the last opportunity to take SVAC data before LAT is assembled –Remaining 8 towers will be delivered in “one bunch” »Most likely limited testing time: mostly LPT and CPT Reasons behind SVAC data taking requests –Study ACD before we use it to assess performance –ACD is a substitute for the muon telescope »discussions with Mike Huffer –Tests that address quality of data and can not easily be done in a testbed should have priority –Offline issues can be assigned lower priority »Even if Eduardo is freaking out… –Some tests are needed to address issues that have been presented in the Instrument Analysis Workshops –Some test are viewed as preparation for 45(?) days of system testing –After LAT Is fully assembled

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 3/7 ACD performance and TKR readout redundancy (2 in 1 to save time) Objective –Verify that TKR readout redundancy does not affect hit/cluster multiplicity Method –Trigger on ACD –Not sure how much to prescale yet –Define a MIP in the CAL –Select muons –Compare TKR variables under different readout configurations Flight configuration for all registers –Just ACD_ROI1 allowed to trigger –ROI1: topological »ACD tiles shadow the towers underneath. »Configure the test for 8 towers »Side tiles are also allowed to trigger »May need to prescale »Need to sharpen the definition of ROI after discussions today –We need to look at MC right now Data Taking Runs –Read TKR from both sides –Read TKR from LEFT side only –Read TKR from RIGHT side only –Read TKR from RIGH, LEFT, RIGHT, LEFT,.... Data Taking Time –2 hours per run –need to verify that with MC muon For the time being avoid CAL_LE as a trigger but do not dismiss it, it is just to expedite the test CAL re-triggering needs to be understood if we want to use CAL_LE as a trigger E. Grove is writing a test plan (STR) for that Mike asked us to consider placing a muon telescope paddle underneath to use as a cross check

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 4/7 Multiple Trigger Engine Test Objective –Verify functionality required for on- orbit operations Trigger Engine –Configure one trigger engine to Flight settings –Configure another trigger engine to CAL 4 range readout –autorange ACD –Should ACD participate in the trigger? –If so, need to prescale Data Taking Time –4 hours –If ACD does not trigger need to verify estimates based on existing data –If we decide ACD should trigger we need to verify time estimates with MC Snapshot of SVAC Config Report for current test runs Mike has already checked to some level that the digital functionality actually works (GEM tester) We recommend to still do that test but with lower priority compared to the ACD tests

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 5/7 ACD “Inefficiency” test Objective –Verify what are the “holes” when the ACD is in VETO mode Register configuration –Flight –To study ACD performance ACD is set to VETO Data Taking Time –2 hours –It is a functionality test –Do we need a longer run? Muon to probe ACD inefficiency

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 6/7 CAL runs (after discussions with E. Grove) Short runs –Full Mode High Energy Muon gain (10 min), similar to B13 (minus TEM diag.) –4 range, auto range –Unsuppressed –FLE ~ 100 MeV –FHE ~ 1 GeV –LE gain = 5 –HE gain = 0 –TEM Diagnostics disabled –Full Mode Flight Gain (10 min) –1 range, auto range –Unsuppressed –FLE ~ 100 MeV –FHE ~ 1 GeV –LE gain = 5 –HE gain = 15 (this is new) –TEM Diagnostics disabled This is to be compared to the solicited trigger tests which now is part of the CPT for pararellized tests done right before! If online is not ready we still want this test “Long” runs –Flight (1 h): Will become the new B2 –1 range, auto-range –Zero suppression (LAC=2 MeV) –FLE ~ 100 MeV –FHE ~ 1 GeV –LE gain = 5 –HE gain = 15 (this is new) –TEM Diagnostics disabled –Muon Calibration auto-range (15 h): Same as current B10 runs –4 range, auto-range –Zero suppression (LAC=2 MeV) –FLE ~ 100 MeV –FHE ~ 1 GeV –LE gain = 5 –HE gain = 0 –TEM Diagnostics enabled HE gain = 13 (saturates at 50 GeV) HE gain = 15 (saturates at 20% higher value) Level III(?) Spec now requires saturation >60 GeV

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 7/7 Definition of ROIs ROI has to be adapted to 8 towers. –Some of the regions will have to be made much larger than for 16 towers: –To account for the fact that all the towers on the right side of the grid are not present. –Will also need special ROI: –Shadow the towers in the grid for TKR Right/Left readout test. –Coincidence between tiles on the sides (also for TKR Right/Left readout test).

SVAC Instrument Analysis Meeting Aug 5, 2005 E. do Couto e Silva and Anders W. Borgland 8/7 Summary 8 towers: –We will calibrate all the CALs with parallelized scripts –That is the plan –We will take the usual B2, B10 and B13 SVAC data runs. 8 towers + ACD: –We have proposed a certain number of runs: –They replace the usual B2, B10 and B13 SVAC runs. –Are there additional test runs you would like to see? Runs done differently? –This is the time to tell us!