Transcript ppt

SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
LAT Data Is Here!
Anders W. Borgland
Science
Verification,
Analysis and
Calibrations
/
Physics
Verification and
Optimization
Anders W. Borgland
1
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
LAT SVAC Muon Runs
• SVAC muon runs are done!
• Three run types:
– B13:
– Non-zero suppressed, 4-range readout in CAL, high
energy muon gain
– 3 runs, each 5 minutes
– B2:
– Flight configuration
– 23 runs, each 15 minutes (470k events, 500 Hz)
– B30:
– Uh?
– Like B10 i.e. 4-range readout of CAL and high energy
muon gain
– Except CAL LO and CAL HI not allowed to open the trigger
window!
– 60 runs, each 15 minutes (470k events, 500 Hz)
• Why B30?
Anders W. Borgland
2
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
CAL Configuration Problems
• We had problems with:
– CAL Configuration
– LAC (zero-suppression) thresholds
– Trigger thresholds
– See Eric Grove's talk!
• Retriggering!
– Real retriggering i.e. Not just discarded events.
– Only in B10 runs!
– Only in Bay 2 (FM117)!
– See next page for plots:
– CAL HI and CAL LO seem to 'retrigger' at the same time.
• Decided to:
– Not allow CAL HI/LO to open the trigger window
– This is called B30 (otherwise identical to B10)
• Still retriggered events:
– Coincidence between a real event and a retriggered event.
– To remove them:
– Require no CAL HI trigger in Bay 2
– Use SVAC ntuple variable: GemCalHeVector[2]==0
– About 0.08% of the total event sample
Anders W. Borgland
3
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
B10: Retriggering In Bay 2
Bay 2 CAL LO
Bay 2 CAL HI
GemDelta Event Time
Retriggered
events
Anders W. Borgland
4
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
Retriggering And Increased
CAL
Occupancy
Number of CAL xtals
in Bay 2 for CAL HI triggers.
Number of CAL xtals
in Bay 2 when no CAL HI
trigger
Anders W. Borgland
5
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
'Hot LAC'
• Second problem:
– Six hot crystals:
– Always read out:
» Tower 0, Layer 1, Column 8
» Tower 2, Layer 0, Column 3
» Tower 3, Layer 3, Column 5
» Tower 8, Layer 0, Column 5
» Tower 10, Layer 1, Column 5
» Tower 11, Layer 5, Column 10
– Only hot for readout, not trigger!
– “Hot LAC”
– Some of them make it into Recon:
– But they have low energy consistent with these LAC
thresholds being a little too low.
Anders W. Borgland
6
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
'Hot LAC': Cal Digi
Anders W. Borgland
7
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
'Hot LAC': Cal Recon
Neighbouring xtal
Anders W. Borgland
8
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
Trigger Configuration
• Allowed to open the trigger:
– TKR
– CAL LO and CAL HI: Only for B2 and B13 runs!
– CNO:
– Threshold set to ~8 MIPs
– Periodic: 10 Hz
• In addition:
– ROI bit:
– Not allowed to open the trigger window!
– Worked as a trigger
– One Region of Interest defined:
» Included all the tiles
– (Remember you also have the GEM ACD tile bits)
– Not entirely planned, but a nice feature :-)
– Veto threshold:
– Set to 0.2 MIP
– But see Eric's talk.
Anders W. Borgland
9
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
Saturated TOT
B2 run
B30 run
More strips with saturated
TOT in B2 runs than in
B30 runs:
Trigger timing?
Somebody should look
into this!
Anders W. Borgland
10
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
Near Future
• TKR calibrations done!
• CAL calibrations:
– Verification underway with NRL
• ACD calibrations:
– Done!
– But:
– AcdRecon can not read in calibration constants!
– Code under development!
– No calibrated ACD quantities in the ntuples and root files:
– They still use the ideal calibrations
– No time estimate for when this will be ready.
• New EngineeringModel:
– Hope to have a new release today.
• Reprocessing:
– Will start as soon as:
– CAL calibration verified
– EM ready
– Hopefully this weekend!
• MC follows when reprocessing starts.
Anders W. Borgland
11
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
List Of Runs
• As soon as the data is reprocessed:
– List of runs with event rates, event sizes etc
• For the curious:
– What happened to run 1355494?
– Status: FAILED
– Known VHDL bug:
– Gives GTCC phasing error – we got one!
– Very low rate – only once before in an SVAC run
– We have to live with this problem!
– Only allowed failure in an SVAC run:
– TKR FIFO full
– Fail 440k events because of one bad event .... hum hum
– Run quality under investigation.
Anders W. Borgland
12
SVAC/PVO
Instrument Analysis Meeting, January 20, 2006
Instrument Analysis Workshop
• Instrument Analysis Workshop
– February 27 and 28!
– Just before the DC2 kickoff
– Analysis:
– You will have plenty of time to analyse this weekend's
data!
• Email will be sent out soon.
Anders W. Borgland
13