QA of BTOW + ETOW peds + status tables in DB , pp 500
Updated on Wed, 2009-04-22 15:57. Originally created by balewski on 2009-04-22 15:30.
This blog keeps track of incremental improvement of BTOW +ETOW peds & status tables. All available data for days 76-103 are processed (sampled).
- Iteration #4, April 22. Justin produced peds & status tables based on minB events. Matt uploaded them. Jan accumulated pedestal residua for the first 3K L2W events in every fill, discard towers w/ status!=1 for both ped & status. Attachments A), B) show file-by-fill 2D spectra for BTOW & ETOW , respectively.
- Conclusion 1: all pedestals are reasonable, very good.
- Conclusion 2: the following blocks of BTOW towers should be masked as bad in DB
Table 1, Problems w/ BTOW status tables page fill remarks p9 F10415 kill 1 tower, ID~595 p12-14 F10439, 448, 449 kill 80 towers, ID~600 p21,22 F10471, 476 as above p23 F10478 kill 80 towers, ID~1550 p29-37 F10507- 532 kill 8 bands x ~8? towers, ID~500-600 p38,39 F1035,536 as above +kill 4 bands x ~8? towers, ID~750 - Conclusion 3: the following blocks of ETOW towers should be masked as bad in DB
Table 2, Problems w/ ETOW status tables page fill remarks p5 F10403 all ADCs are stuck at one value, full ETOW needs masking p8 F10412 mixture of as above and good data - mask bad time intervals p14-16 F10449-454 kill 4 blocks of ~6 towers for X=200,260,320,380 p17,24,34,36,38 F10445,482,527,531,535 mixture of problem on page 5 and good data - mask bad time intervals p28 F10505 all ADCs are stuck at one value, full ETOW needs masking p5 F10403 can you mask this one tower
- Conclusion 1: all pedestals are reasonable, very good.
»
- balewski's blog
- Login or register to post comments