Difference between revisions of "SCT DQshift"
| Line 32: | Line 32: | ||
| − | '''2] | + | '''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 [https://atlasdqm.web.cern.ch/atlasdqm ATLAS DQ homepage ] | Start at the [https://atlasdqm.web.cern.ch/atlasdqm ATLAS DQ homepage ] | ||
| Line 54: | Line 56: | ||
Check SCT and things that are not ok. | Check SCT and things that are not ok. | ||
| − | |||
Look at the ES1 (express express stream pass 1) of the Tier-0 processing and check the [https://atlasdqm.cern.ch/ atlasdqm]histogram-summary. | Look at the ES1 (express express stream pass 1) of the Tier-0 processing and check the [https://atlasdqm.cern.ch/ atlasdqm]histogram-summary. | ||
| − | |||
| − | |||
| − | |||
Note: | Note: | ||
Revision as of 08:53, 13 April 2012
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 data quality portal
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
System effected SCT ald 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
b) Select run you want
Click on 'exp[ress express' (Note if *** run is still processing)
b1) click on defect database
filter SCT and look for defects
There is a finite number of defects defined for the SCT (twiki SCT DQ defect list)
Now, check in the histograms if you understand the defects and if there are more/less than in the 'known database' database/Check if the defects are
b2) click on entire run
Check SCT and things that are not ok.
Look at the ES1 (express express stream pass 1) of the Tier-0 processing and check the atlasdqmhistogram-summary.
Note:
- check box UNCHECKED (to indicated you have actually looked at the run)
- password to sign-off the run: SctDq
b)
c) sign of the run
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] Finish up: 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