Difference between revisions of "SCT DQshift"
| Line 1: | Line 1: | ||
The minimal path through all documentation necessary for an SCT DQ shift | The minimal path through all documentation necessary for an SCT DQ shift | ||
| − | |||
{| border="1" cellpadding="2" cellspacing="0" | {| border="1" cellpadding="2" cellspacing="0" | ||
|- | |- | ||
! style="background:#ffba00;" | General information | ! style="background:#ffba00;" | General information | ||
| − | |||
|} | |} | ||
Revision as of 12:58, 22 March 2012
The minimal path through all documentation necessary for an SCT DQ shift
| General information |
|---|
The Official SCT DQ shift twiki
The ATLAS data quality portal
The ATLAS detector operations page
| The shift itself |
|---|
1] Check the ATLAs e-Log page for (SCT-specific) information on the run
Use search form on the ATLAS e-Log page
2] Check the known defects in the database for this run:
Use the defect entry page
There is a finite number of defects defined for the SCT (twiki SCT DQ defect list)
3] Look at the histogram-summary from Tier-0 processing and sign-off the run:
Look at the ES1 (express stream pass 1) of the Tier-0 processing and check the histogram-summary.
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.
Note:
- check box UNCHECKED (to indicated you have actually looked at the run)
- password to sign-off the run: SctDq
what to do when you discover a new defect:
Send a mail to the expert. Get the name of the shifter from the ATALS OTP page (xxx missing xxx)
4] Obtain information for run-summary
Get the run summary (report, lumi and efficiencies) from the SCT DQ webtool
Use SCT-standard and use the run-number
5] Make an entry in the ATLAS e-Log
Enter the run summary and additional comments in the e-Log on the ATLAS operations page
done