- BEMC
- BTOF
- DAQ
- Detector Upgrades
- EEMC
- 2007 run, hardware changes
- 2008 run preparation
- Calibrations
- 2007 EEMC Tower Gains
- Calculating EEMC pedestal and status tables
- Calculating EEMC tower ideal gains and expected MIP response
- EEMC Calibration Docs
- EEMC Tower Swaps
- Overview for generating EEMC pedestals and status tables
- Producing ADC distributions for the EMCs from raw DAQ files
- Run 10 EEMC Calibrations
- Run 11 EEMC Calibrations
- Run 12 EEMC Calibrations
- Run 13 EEMC Calibrations
- Run 15 EEMC Calibrations
- Run 17 EEMC Calibrations
- Run 8 EEMC calibrations
- Run 9 EEMC calibrations
- Uploading EEMC Pedestal, Status and Gain Calibrations to the DB
- EEMC Detector Operator Manual
- EEMC Maintenance/Operations Documents
- Endcap Geometry
- Endcap Geometry update (2009)
- Log of tower base and fee issues
- eemc as-built info and proto tests
- emc2-hn minutes (by Jan)
- how-to by Jan
- slow controls archive viewer
- trash
- 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
Status and Pedestal Tables
Updated on Fri, 2017-06-30 08:53. Originally created by tinglin on 2017-06-09 10:55.
Under:
RunList Selection:
Use one good emc-check run with at least 50k events for each fill from pp510. Some fills did not have good emc-check run.
For pp510, total emc_check run list has 227 runs, some problematic (?) runs:
18065063, only has 1 event;
18066002, second emc_check run in same fill, Shift Leader comment: 18065001 rate too high?
The final list has 210 runs and is available: runList_2017_emc_check_final
Summary of tower:
tower status by fill
a01TA05: masked out on April 26th by Will
a01TC05: failed for part of the run
a02TA01: dead entire run
a02TC04: bad entire run
a02TC06: failed for part of the run
a12TC05: bad entire run
Summary of MAPMT:
MAPMT status by fill
MAPMT Pedestal Width
Use one good emc-check run with at least 50k events for each fill from pp510. Some fills did not have good emc-check run.
For pp510, total emc_check run list has 227 runs, some problematic (?) runs:
18065063, only has 1 event;
18066002, second emc_check run in same fill, Shift Leader comment: 18065001 rate too high?
18087034, only has 1 event;
18092096, emc_check run pp energy < 500GeV
18108002, second emc_check run in same fill.
18108043, emc_check run pp energy < 500GeV
18109051, emc_check run pp energy < 500GeV
18111048, emc_check run pp energy < 500GeV
18111052, emc_check run pp energy < 500GeV
18112046, emc_check run pp energy < 500GeV
18113047, emc_check run pp energy < 500GeV
18113047, emc_check run pp energy < 500GeV
18115037, emc_check run pp energy < 500GeV
18115043, emc_check run pp energy < 500GeV
18115047, emc_check run pp energy < 500GeV
18115051, emc_check run pp energy, Blue 253.798GeV, Yellow 253.797GeV, smaller than normal value 254.867GeV.
18115051, emc_check run pp energy, Blue 253.798GeV, Yellow 253.797GeV, smaller than normal value 254.867GeV.
18115055, emc_check run pp energy < 500GeV
18119001, Shift Leader Marked as Junk
18143047, second emc_check run in same fill.
Summary of tower:
tower status by fill
a01TA05: masked out on April 26th by Will
a01TC05: failed for part of the run
a02TA01: dead entire run
a02TC04: bad entire run
a02TC06: failed for part of the run
a03TE03: dead for one run
a03TE11: failed for two runs
a04TB07: stuck bit entire run
a04TC01: dead entire run
a05TA12: stuck bit entire run
a05TC12: dead entire run
a06TA03: failed entire run
a06TA07: stuck bit entire run
a07TB12: failed for one run
a07TC05: failed entire run
a08TB07: stuck bit entire run
a09TC04: dead for part of the run
a11TA08: dead entire run
a11TB07: failed for part of the run
a11TB07: failed for part of the run
a11TD01 dead for part of the run
a11TD02
a11TD03
a11TD04
a11TD05
a11TD06
a11TD07
a11TD08
a11TD09
a11TD10
a11TD11
a11TD12
a12TC05: bad entire run
a12TD01: failed for part of the run
a12TD09: failed for part of the run
Summary of MAPMT:
MAPMT status by fill
MAPMT Pedestal Width
»
- Printer-friendly version
- Login or register to post comments