1. Usually, the shift last for a week and starts from Thursday end on next Wednesday.
2. You will receive from atlasdqm@cernNOSPAMPLEASE.ch the email about run that's missing DQ signoff. MS, MS_BULK, MCP, MCP_BULK are your duties.
3. You can check run information and check what's the run you need to sign before the next Wednesday, DQ convener will send out request to hn-atlas-DataQuality@cernNOSPAMPLEASE.ch, and you can also consult your experts.
4. When express stream is ready, you can look at plots for ES stream, "express_express", which is a limited sampling over the whole run, to find some issue early and record it on whiteboard. Usually do this for all the run before next Wednesday.
5. Later when the tag is ready, you can try to look at plots for BULK stream, "physics_main". Remember to look at the correct f tag and htag, they will sometimes be summarized by DQ convener. Pay attention. Sometimes BULK stream will be reprocessed, and you need to wait for new tag to finish to check the plots.
6. In the case the express stream are sign-off by previous shifters, you might need to sign-off BULK stream for those. Just do the same procedure, but check the issue that's recorded on the Whiteboard, then take care with those issues when you're checking BULK. If an issue is not seen on ES1, you'd better report it to expert ASAP.
7. At the end of the shift, you need to make a report.

• Infos:
  • MuonDataQuality
• Plots to look at:
  • AtlasDqm : Tier-0 plots. MuonDetectors and MuonTracking
  • Digging deeper into what happened: CR shifter elog
• Keep track of what's happening:
  • MuonOfflineDQShiftWhiteboard: You can go to Sign-off Defect at second tab and enter run number to quickly copy the run information.
• How to sign-off:
  • Sign-off Defect: In first tab, you can see unchecked means not signed off. In third tab, you can do: MS/MS_BULK sign off with password "Muons", MCP/MCP_BULK sign off with password "McpDq". Here's a list of defects.
    • Generally impact need to be ~ 10% to be assigned any defect. For example, MDT has 250 chambers in each crate. Always talk to expert.
    • Defect have the form of <which system>_(<subdetector>_<detailed region>/<which performance>)_<problem description>
  • Sign-off in ELisA: Search/Advanced search for the run number, reply ES when you sign off ES stream, reply BLK when you sign off BLK stream. Don't forget to modify the system affected, and assign a run number if not there. Basically copy what's written on whiteboard here. Can simplify the text. Still need advice?
• Plots that are reference:
  • Manual
  • Case Study
• About the Report
  • Indico: Data Quality meeting for every sub-system, every Wednesday.
  • Temlate Report
• How to find the source of the problem?
  • If you're interested, or want to advanced your skill, or go a bit further. You can find the reason of chamber drop, etc, etc on the shift summary of Control Room ELisA.
• Experience During Shift
  • 2018-04-23 DCS(Detector Control System) can sometime automatically generate RPC HV_STANDBY error for the whole run. While the histograms shows ok. This needs to be recorded on whiteboard for experts to take notice and investigate.
  • Do not sign off a run until any related issue is resolved with expert's help.
  • 2017-09-16 Some tag could have problem, like f863, the clusters in B-layer are significantly fewer.. but in updated tag f867, it's not there.
  • 2017-09-13 TRT issue can appear in many other systems, like MCP reconstruction. It's usually magnified in reco Z. When reco Z distribution has zip or gap, might check MuonTracking, CBMuons plots, and you might find what happened there.

-- RongkunWang - 2018-05-06