SCT DQshift
The minimal path through all documentation necessary for an SCT DQ shift
Goal of the shift: make sure all flags related to SCT operation are correctly stored in the database before the run is processed at the Tier-1's
| General information |
|---|
The Official SCT DQ shift twiki
The ATLAS run query
The ATLAS detector operations page
| The DQ shift |
|---|
The shifter checks if the known problems are indeed present, checks for potential new ones, signs off the run and makes a summary following these steps:
1] Check the ATLAs e-Log page for (SCT-specific) information on the run
Use search form on the ATLAS e-Log page
Check on button next to 'system affected', select SCT and look for run
2] Look at the histogram-summary from Tier-0 processing
This is the step where the real work is done: see if you can identify the known defects, look for potential new problems and 'sign off' the run.
Start at the ATLAS DQ homepage
a) Click on Tier-0 offline and select run you want and click on 'express express' stream.
Note: if the run has *** , the run is still processing. You'll have to wait.
b) click on defect database to check known defects:
Use 'filter SCT' and look for defects.
In the next steps you will need to confirm these and look for new ones. There is a finite number of defects defined for the SCT. A full list can be found here: (twiki SCT DQ defect list). Each defect has a fatality-level attached to it. Fatal warnings will flag the run as not useful for physics.
c) go back to Tier-0 page and click on entire run to check all histograms
Select ID -> SCT and check the histograms to see if you understand the defects and if there are others present that are not in the 'known database' database. Note that problams are detected automatically and good/maybe/bad histograms appear as green/orange/red.
Note: write down efficiencies for later use (endcap-A, Barrel and endcap-C). You get the efficiencies by clicking on the efficiency-summary histogram for each of the 3 subsystems separately.
c) new things: upload new entry in database
Send a mail to the expert. Get the name of the shifter from the ATALS OTP page (xxx missing xxx)
d) sign off the run
make comment and submit
Note: password to sign-off the run: SctDq
4] Obtain information for run-summary
4a) Get the run summary (report, lumi and efficiencies) from the ATLAS DQ website
Click on 'SCT', select 'standard' and then on 'report' to get the full summary for your run.
Note: you need to copy-paste in the ATLAS e-Log at step 5]
4b) get luminosity (if step 4a failed)
Get information through the ATLAS run query
search string for runs:
http://atlas-runquery.cern.ch/query.py?q=find+run+201350%2C201351+/+show+dqsum
5] Finish up: make an entry in the ATLAS DQ logbook and e-Log
Start at the ATLAS DQ homepage
a) ATLAS DQ logbook
Click on DQ logbook (also available through the ATLAS DQ homepage) Not too clear who reads this, but is the summary in case you are not present during Wednesday's meeting
b) ATLAS e-Log (the real thing)
Enter the run summary you got at step 4] and additional comments in the e-Log. Follow link from the ATLAS DQ homepage
enter 'SCT'
title: SCT DQ report run <>
copy in the comment lines: - the 'report' you got from step 4] - the efficiencies you got from step 2]
done