1 / 7

Athena LAr Noise Monitoring Software Brief Status Report

Athena LAr Noise Monitoring Software Brief Status Report. Michel Lefebvre University of Victoria 02 Nov 2005. Following discussions with Remi Lafaye, the design is evolving Try to avoid computing the pedestal and rms in different places in the code

mimir
Télécharger la présentation

Athena LAr Noise Monitoring Software Brief Status Report

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. Athena LAr Noise Monitoring Software Brief Status Report Michel Lefebvre University of Victoria 02 Nov 2005 • Following discussions with Remi Lafaye, the design is evolving • Try to avoid computing the pedestal and rms in different places in the code • Pedestal and their rms are to be computed in dedicated algorithms and, optionally, loaded in the database • LArDigit: LArPedestalMaker produces LArPedestal • needs improvements (Kai) • LArRawChannel: a similar algorithm perhaps to be written • One way to monitor the pedestals and their rms is to take info from these objects • LArDigit: from LArPedestal • LArNoiseMonToolBase design (Rolf, Michel) still good • Continue implementation!

  2. simple design idea • implements common code • implemented MonitorToolBase LArNoiseMonToolBase • handles specifics • handles loop over relevant objects LArDigitNoiseMonTool LArRawChannelNoiseMonTool LArPedestalMonTool (not yet) • First implementation working well • Expect the design to be stable • implementation will evolve with profiling info LAr noise monitoring status report

  3. a few histograms (Phase1 run 18720) FebID, LAr partition and gain • sample 0 (ADC) per channel for a given FEB LAr noise monitoring status report

  4. a few histograms (Phase1 run 18720) Feedthrough ID and gain • sample 0 (ADC) per FEB for a given feedthrough LAr noise monitoring status report

  5. a few histograms (Phase1 run 18720) FebID, LAr partition and gain • LArRawChannel signal (GeV) per channel for a given FEB LAr noise monitoring status report

  6. a few histograms (Phase1 run 18720) FebID, LAr partition and gain • LArRawChannel signal (GeV) per FEB for a given feedthrough LAr noise monitoring status report

  7. coherent/incoherent noise • Consider implementing (relative) coherent noise monitoring • the issue was discussed with Petr Gorbanov and Remi Lafaye and a good solution exist • difficulty is free gain • speed is an issue • Histogram checking to be tried very soon • root macros implementation (Tayfun, Michel) stating NOW LAr noise monitoring status report

More Related