Difference between revisions of "SCT DQshift"
| Line 28: | Line 28: | ||
Use search form on the [https://atlasop.cern.ch/elog/ATLAS/ATLAS/ ATLAS e-Log] page | Use search form on the [https://atlasop.cern.ch/elog/ATLAS/ATLAS/ ATLAS e-Log] page | ||
| + | |||
| + | System effected SCT ald look for run. | ||
| Line 33: | Line 35: | ||
Use the [https://atlasdqm.cern.ch/defectentry/ defect entry] page | Use the [https://atlasdqm.cern.ch/defectentry/ defect entry] page | ||
| + | |||
| + | Look for Tier-0 offline | ||
There is a finite number of defects defined for the SCT ([https://twiki.cern.ch/twiki/bin/viewauth/Atlas/SCTOfflineMonitoringShifts#DQ_Defects twiki SCT DQ defect list)] | There is a finite number of defects defined for the SCT ([https://twiki.cern.ch/twiki/bin/viewauth/Atlas/SCTOfflineMonitoringShifts#DQ_Defects twiki SCT DQ defect list)] | ||
| Line 39: | Line 43: | ||
'''3] Look at the histogram-summary from Tier-0 processing and sign-off the run:''' | '''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 [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. |
| + | |||
| + | a) look for known defects: | ||
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. | 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. | ||
| Line 46: | Line 52: | ||
*check box UNCHECKED (to indicated you have actually looked at the run) | *check box UNCHECKED (to indicated you have actually looked at the run) | ||
*password to sign-off the run: SctDq | *password to sign-off the run: SctDq | ||
| + | |||
| + | |||
| + | b) | ||
| + | |||
| + | c) sign of the run | ||
Revision as of 08:46, 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] Check the known defects in the database for this run:
Use the defect entry page
Look for Tier-0 offline
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 express stream pass 1) of the Tier-0 processing and check the atlasdqmhistogram-summary.
a) look for known defects:
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
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