SVAC 8 tower testing with ACD

1
SVAC 8 tower testing with ACD

• Anders and Eduardo

2
The Rationale For SVAC Data Taking

• Assumptions behind todays 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
• 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 Instrument Analysis Workshops
• Some test are viewed as preparation for 45(?)
  days of system testing
• After LAT Is fully assembled

Reminder!
3
TKR Readout Redundancy

• Objective
• Verify that the TKR readout redundancy does not
  affect hit/cluster multiplicity
• Method
• Trigger on the ACD
• Define ROI with 15/25 top tiles that shadow the 8
  towers see next page
• 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 top tiles that shadow the 8 towers
  underneath.
• Use three out of five rows of ACD top tiles
  See next page 000,001,002,010,011,012,020,021,022
  ,030,031,032,040,041,042
• Need two identical ROI for triggering on
  coincidence (GEM logic)
• ROI2 ROI1
• Rate will be a maximum of 1.5 kHz
• Assuming 100 Hz/tile

Trigger on ACD top tiles
Look at TKR quantities
4
ACD Tile MAP
ROI 15/25 top tiles
5
ACD Veto

• Objective
• Verify the ROI VETO logic
• Find the 'holes' in the ACD coverage when the ACD
  is in VETO mode
• Register configuration
• Flight
• ACD is set to VETO
• ROI for 8 towers defined by SVAC
• From MC studies
• Nearly complete.
• Data Taking Time
• 4 hours

Muon to probe ACD inefficiency
6
Multiple Trigger Engine Test

• Objective
• Verify functionality required for on-orbit
  operations
• Trigger Engine
• Configure one trigger engine to Flight settings
• All triggers except the periodic trigger goes
  into this engine
• Normal readout
• Configure another trigger engine to non-zero
  suppressed, 4 range readout of the CAL
• Use a 1 Hz periodic trigger
• Does not use the ACD
• But when will we do this test if not now?
• Data Taking Time
• 1h

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