Difference between revisions of "SCT DQshift"

From Atlas Wiki
Jump to navigation Jump to search
 
(35 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
The [https://twiki.cern.ch/twiki/bin/viewauth/Atlas/SCTOfflineMonitoringShifts  Official SCT DQ shift twiki]
 
The [https://twiki.cern.ch/twiki/bin/viewauth/Atlas/SCTOfflineMonitoringShifts  Official SCT DQ shift twiki]
  
The [http://atlasdqm.web.cern.ch/atlasdqm/ ATLAS data quality] portal
+
The [http://atlasdqm.web.cern.ch/atlasdqm/ ATLAS DQ homepage]
 +
 
 +
The [http://atlas-runquery.cern.ch/ ATLAS run query]
  
 
The [https://atlasop.cern.ch/operation.php  ATLAS detector operations] page
 
The [https://atlasop.cern.ch/operation.php  ATLAS detector operations] page
Line 27: Line 29:
 
''' 1] Check the ATLAs e-Log page for (SCT-specific) information on the run'''
 
''' 1] Check the ATLAs e-Log page for (SCT-specific) information on the run'''
  
Use search form on the  [http://muondoc.home.cern.ch/muondoc/Software/Database/  ATLAS e-Log] page
+
Use search form on the  [https://atlasop.cern.ch/elog/ATLAS/ATLAS/  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  [https://atlasdqm.web.cern.ch/atlasdqm 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.
  
  
'''2] Check the '''known''' defects in the database for this run:'''
+
b) click on defect database to check known defects:
  
Use the [https://atlasdqm.cern.ch/defectentry/ defect entry] page
+
Use 'filter SCT' and look for defects.  
  
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)]
+
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: ([https://twiki.cern.ch/twiki/bin/viewauth/Atlas/SCTOfflineMonitoringShifts#DQ_Defects 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.
  
  
'''3]  Look at the histogram-summary from Tier-0 processing and sign-off the run:'''
+
c) From Tier-0 startpage click on entire run to check all histograms
  
Look at the ES1 (express stream pass 1) of the Tier-0 processing and check the [https://atlasdqm.cern.ch/webdisplay/tier0/ histogram-summary].
+
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.
  
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:''' 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 defect ?
 +
 
 +
From Tier-0 start page click on defect database and upload new entry
 +
 
 +
Send a mail to the expert. Get the name of the shifter from the ATALS OTP page (<font color="red">xxx missing xxx</font>)
  
Note:
 
*check box UNCHECKED (to indicated you have actually looked at the run)
 
*password to sign-off the run: SctDq
 
  
 +
d) sign of run
  
<font color="red">what to do when you discover a new defect:</font>
+
From Tier-0 start page select defect database and then 'sign off the run'. Make sure to make a comment and submit
  
Send a mail to the expert. Get the name of the shifter from the ATALS OTP page (xxx missing xxx)
+
'''Note:''' password to sign-off the run: SctDq
  
  
 
'''4]  Obtain information for run-summary'''
 
'''4]  Obtain information for run-summary'''
  
Get the run summary (report, lumi and efficiencies) from the [https://atlasdqm.cern.ch/atlaswebdq/ SCT DQ webtool]
 
  
Use SCT-standard and use the run-number
+
4a) Get the run summary (report, lumi and efficiencies) from the [https://atlasdqm.cern.ch/atlaswebdq/ 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 this information in the ATLAS e-Log at step 5]
 +
 
 +
 
 +
4b) get luminosity (if step 4a failed)
 +
 
 +
Go to the [https://atlasdqm.cern.ch/webdisplay/tier0/ ATLAS tier-0 histogram page]. When you move your mouse over the run you are interested in (left side of the screen) you get the summary of the run. With Luminosity information.
 +
 
 +
Another way is through the  [http://atlas-runquery.cern.ch/ ATLAS run query]
 +
 
 +
search string (lumi): 'find run 12345 / show all'
 +
 
 +
search string (dq): 'find run 12345 / show dq'
 +
 
 +
 
 +
'''Note:''' you also get this summary information through automatic SCT mail
 +
 
 +
 
 +
'''5]  Finish up: make an entry in the ATLAS DQ logbook and e-Log'''
 +
 
 +
Start at the  [https://atlasdqm.web.cern.ch/atlasdqm ATLAS DQ homepage]
 +
 
 +
 
 +
a) ATLAS DQ logbook
 +
 
 +
Enter 1-line comment in [https://atlasdqm.cern.ch/dqsignoff/ DQ logbook]  (also available through the [https://atlasdqm.web.cern.ch/atlasdqm ATLAS DQ homepage])
 +
 
 +
'''Note:''' you might need to click on 'expand' at bottom of the page if your run is not visible.
 +
 
 +
 
 +
b) ATLAS e-Log (the real thing)
 +
 
 +
Enter the run summary you got at step 4] and additional comments in the [https://atlasop.cern.ch/elog/ATLAS/ATLAS/  ATLAS e-Log] page.
  
 +
enter 'SCT'
  
'''5]  Make an entry in the ATLAS e-Log'''
+
title: SCT DQ report run <>
  
Enter the run summary and additional comments in the e-Log on the [https://atlasop.cern.ch/operation.php ATLAS operations page]
+
copy in the comment lines:
 +
- the 'report' you got from step 4]
 +
- the efficiencies you got from step 2]
  
  
 
''done''
 
''done''

Latest revision as of 07:31, 11 June 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 DQ homepage

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) From Tier-0 startpage 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 defect ?

From Tier-0 start page click on defect database and upload new entry

Send a mail to the expert. Get the name of the shifter from the ATALS OTP page (xxx missing xxx)


d) sign of run

From Tier-0 start page select defect database and then 'sign off the run'. Make sure to make a 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 this information in the ATLAS e-Log at step 5]


4b) get luminosity (if step 4a failed)

Go to the ATLAS tier-0 histogram page. When you move your mouse over the run you are interested in (left side of the screen) you get the summary of the run. With Luminosity information.

Another way is through the ATLAS run query

search string (lumi): 'find run 12345 / show all'

search string (dq): 'find run 12345 / show dq'


Note: you also get this summary information through automatic SCT mail


5] Finish up: make an entry in the ATLAS DQ logbook and e-Log

Start at the ATLAS DQ homepage


a) ATLAS DQ logbook

Enter 1-line comment in DQ logbook (also available through the ATLAS DQ homepage)

Note: you might need to click on 'expand' at bottom of the page if your run is not visible.


b) ATLAS e-Log (the real thing)

Enter the run summary you got at step 4] and additional comments in the ATLAS e-Log page.

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