1 / 13

RPC & LVL1 Mu Barrel Online Monitoring during LS1

RPC & LVL1 Mu Barrel Online Monitoring during LS1. M. Della Pietra. Overview. Status of ATLAS DataFlow changes during LS1 Changes for gnam based monitoring Monitoring @ SFI not more possible: future? Trigger and readout extension in feet region Noisy and dead channel mapping campaign.

ashley
Download Presentation

RPC & LVL1 Mu Barrel Online Monitoring during LS1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RPC & LVL1 Mu Barrel Online Monitoring during LS1 M. Della Pietra

  2. Overview • Status of ATLAS DataFlow changes during LS1 • Changes for gnam based monitoring • Monitoring @ SFI not more possible: future? • Trigger and readout extension in feet region • Noisy and dead channel mapping campaign M. Della Pietra

  3. Changes in Atlas DF FROM S. KOLOS M. Della Pietra

  4. Changes in Atlas DF FROM S. KOLOS M. Della Pietra

  5. Changes in Atlas DF FROM S. KOLOS M. Della Pietra

  6. Changes in gnam code? • No changes has to be done in gnam code about sampling • We have just to reconfigure gnam application in OKS attaching them to a new event sampler (new DCMs in TDAQ dataflow) or to a specific output stream. • We can monitor on many sources (many streams) • Also there should be no modification in gnam API foreseen, but no decision have been taken up to now. • I will ask again for naming the file saved by gnam with something more the the file number to have more than on file for each run M. Della Pietra

  7. What about monitoring at SFI? • At tree level, is fine for us to monitor a full event after the HLT chain instead of before it. • We started to monitor at SFI only because it was the first (and actually only) place where we can sample a complete event to compare many RODs • But there is a second order problem • Are we interested in monitoring events discarded by HLT chain? • Up to now is not clear how it can be possible: • Full rejected events by HLT can be monitored easily • If we want to sample only MUON HLT discarded events we have to agree a change of trigger configuration with Trigger Group M. Della Pietra

  8. Changes in Atlas DQMF FROM S. KOLOS M. Della Pietra

  9. Changes in Atlas DQMF FROM S. KOLOS M. Della Pietra

  10. Changes in Atlas DQMF FROM S. KOLOS M. Della Pietra

  11. DQM & OHP • Do we have request to be forward to the MWG? • New functionalities? • Do we think to still use both displays? • I think so… M. Della Pietra

  12. Feet extensions • We have to add the readout of the new trigger chambers in feet region • Add some more histos accordingly (1 day work) • Write the new mapping file (a couple of week) M. Della Pietra

  13. Noisy and dead channels • At the restart I suggest to start a campaign in finding (by scratch) dead and noisy channels • Now we have a tool (not available during commissioning, never used in the last period) to run a macro (even automatically) on online histograms • Work done by Arturo Sanchez • We need to debug also the automatic storage in DB of dead/noisy channels M. Della Pietra

More Related