- 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
EEMC Gains - corrected for mis-set TCD phase
Updated on Tue, 2009-09-01 09:04. Originally created by stevens4 on 2009-08-31 15:45.
Under:
EEMC TCD Phase and Effective Gains
During Run 9 the TCD phase was set incorrectly for ETOW (run < 10114054) and ESMD (run < 10140030). A study (shown here) found the slope ratio for the 2 TCD phases which was used to calculate new gain tables for ETOW and ESMD. These "mis-set" TCD phase timing settings are not optimal for the vast majority of channels, thus the data taken during these periods are more suspect to issues such as timing jitter, vertex position dependencies, etc. To account for these issues, we have set gain=-1 for these time periods for the standard "ofl" flavor of the DB. The new gains (calculated with the slope ratios) have been uploaded to the DB for the same timestamps but with a flavor of "missetTCD", so that this data is permanently flagged as having issues that data taken with optimal timing (hopefully) do not.
As a reminder, here are a few lines of code for how to read these "missetTCD" flavor tables from the DB instead of the default "ofl" tables:
stDb = new St_db_Maker("StarDb", "MySQL:StarDb");
stDb->SetFlavor("missetTCD","eemcPMTcal"); //sets flavor for ETOW gains
stDb->SetFlavor("missetTCD","eemcPIXcal"); //sets flavor for ESMD (mampt) gains
Note: the "missetTCD" flavor is valid only for Run 9 during the time periods given above, so it will return gain<0 for any other times.
»
- Printer-friendly version
- Login or register to post comments