- BEMC
- BTOF
- DAQ
- Detector Upgrades
- EEMC
- EPD
- ETOF
- FCS
- FGT
- FPD & FMS & FPS
- FTPC
- FTT
- HFT
- HLT
- L3
- MTD
- MTD NPS Maps
- PMD
- PP2PP
- RICH
- Roman Pot Phase II*
- Run-18 calibrations
- SSD
- SVT
- Slow Controls
- TPC
- TRG
- Trigger Detectors
- VPD
- test
d ped-monitor (Jan)
Updated on Tue, 2009-03-10 09:52. Originally created by balewski on 2008-01-31 19:13.
Under:
L2-pedestal monitor-Algo ( 100% accept)
- Goal: accumulate pedestals for all towers of ETOW & BTOW.
- RTS params:
par_pedSubtr =rc_ints[0]!=0; par_speedFact =rc_ints[1]; par_saveBinary=rc_ints[2]!=0; par_dbg =rc_ints[3]; par_prescAccept=rc_ints[4];
- Meaning of speed
time spent in L2-ped is proportional to # of towers processed per event. speed=1 means for every event process all 4800+720 towers, takes 1mSec speed=2 means for the first event process tower 1,2, 5,6, 9,10,...., takes 500 uSec for the second event process tower 3,4, 7,8, 11,12,...., takes 500 uSec repeat So L2ped runs 2x faster but effectively you get 1/2 of stats for all towers. speed=4 means : 1st eve works with towers: 1,2,3,4, 17,18,19,20,... takes 250 uSec 2nd eve works with towers: 5,6,7,8, 21,22,23,24,... 3rd ... 4th eve ... repeat You got the pattern. Allowed 'speeds' are common divider of 4800 & 768. Allowed speed values: 1,2,4,8,16,32,64,192 But even if you type sth absurd L2ped will correct it to the closest correct value.
»
- Printer-friendly version
- Login or register to post comments