Warning : this page is NOT a summary of different DQ activities in LAr. This is not exhaustive and does NOT reflect all the work done by different involved persons. This is just a personal biased view of the current problems and wonders, that sometimes only exists in authors mind!

Urgent matters are spotted with a Orange led.


Last update : 20 February 2009

Subgroups :

  • [DCS] : DCS only
  • [DAQ] : all quantities related to data integrity, data flow, enabled readout...
  • [MIS_CH] : monitoring of misbehaving channels. The monitoring is performed at several levels: LArDigit, LArRawChannel, CaloCells
  • [SIG] : monitoring of signal (mainly at digit levels)
  • [PHYS] : monitoring of "physical" quantities (in connection with e gamma group)

  • DCS status calculator [DCS]:
    • Concerned runs : PHYSIC (CALIB?)
    • Status/State now stored in COOL with common IOVs for global LAr and DCS sub partitions. "Worst case" algorithm used to extract a flag. Analysis done on reprocessed runs : all GREEN except 3 runs for which the data was bad by written. Flags to be written in DCS database (only private processing up to now). Logic to be tested during cosmic runs.
    • Followed by Samir Arfaoui.

  • Monitoring at the ROD level [DAQ][MIS_CH]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
    • Current available plots : GLink temperature (to be removed from DQ - this is not really DQ), sample 0 pedestal monitoring, number of discarded events, busy status (tbc).
    • Main software already implemented. Not sure that the problem relative to sbc stability is fixed. To be investigated.
    • Then once it is fixed, have to do summary plots and DQMF checks. Rémi (and LAPP students) agreed to work on this.

  • Monitoring of the DSP computation [DAQ]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
    • Comparison of energy extracted by DSP and the one computed from digits (extracted just for cells with signal above a given threshold).
    • Implemented online. Almost perfect, except some patholigical channels with very low error yield to be understood. Under study by online experts (problem coming from high rate runs??).
    • Code also includes time/chi2 computation. Basically works (few pathologies still be understood)
    • Implementation of offline processing at CAF under study : M.Aurousseau in contact with N.Berger : should be rather straightforward. To be done : protection in code to avoid useless processing when these are raw data (implementation by M.Aurousseau).

  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
    • Algorithm stable, documentation done, DQMF available.
    • To be done : Orange led correct error computation for histo dynamicaly booked for faulty FEBs (cf pb of 100% yield). L.Helary is investigating this.
    • Current maintenance and analysis : Benjamin Trocmé

  • LArCoverage [DAQ]:
    • Concerned runs : PHYSIC only for the moment (LArRawChannel).
    • Current maintenance and further development : Jessica Leveque. The larcoverage should be refined to provide a more precise view of different pathologies : "Serious" (very high noise, dead), "Minor" (noise slightly high), "intermittent" (Noise burst)
    • Pending problem : nice FCAL geometry by E.Wulf to be implemented for coverage.

  • LArOddCells [MIS_CH]:
    • Concerned runs : PEDESTAL mainly. (PHYSIC? to be determined)
    • Algorithm stable, documentation almost done, DQMF available.
    • Mainly minor developments on request.
    • Current maintenance and analysis : Benjamin Trocmé.
    • Orange led Have to understand what are the few events with a yield greater than 1%. Related to noise bursts studied elsewhere?

  • LArNoiseMonToolBase suite [MIS_CH]:
    • Concerned runs : PEDESTAL.
    • Tool mainly used for commissioning and debugging with a lot of clever plots. Still integrated (in its basic version) in automatic monitoring of calibration runs.
    • Long time development by Victoria Team.

  • LArRawChannel monitoring [MIS_CH] :
    • Development by Michel Lefebre and Franck Berghaus
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold), average energy per cell, noise per cell, proportion of events in negative tails (3 x noise à la LArOddCells).
    • Treatment of quality factor now implemented. To be tuned

  • Basic digits monitoring (for cells with signal only) [SIG]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
    • Plot for each FEB the number of cells with sample of the maximum signal outside a time window, the number of saturated cells and with digits == 0, the mean time of the maximum signal. Basic pulse shape reconstruction per partition (à la LArCosmics), variation of peak position vs time.
    • Orange led Merging not properly done for case of bin with 0% or 100%. Pending problem L.Helary is investigating this.

  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
    • Fine monitoring of the shape stability by using the digits extracted (for cells with signal only).
    • Objective : detect varying shape within a short time scale (i.e faster the delay runs frequency). Question of available statistic to be clarified : by processing the bulk, one would require typically 2-3 days of data. May be interesting in stable running but perhaps not at the LHC start.
    • Required deep infrastructure modifications (especially : partial event building in a dedicated calibration stream, while keeping the main physic stream). Now available in tdaq-1-09-01
    • Development by Nicolas Berger

  • Orange led Monitoring of quality word of LArRAwChannel [SIG]:
    • Concerned runs : ALL.
    • Potentially interesting to detect HV spike (cf much faster rising signal) spotted by Laurent Serin et al.
    • For the moment, quality word not computed routinely(cf problem of memory consumption, as the pulse shape is needed to extract it). Since 14.2.0, however possible to compute it privately.
    • Some interests by Laurent Serin and Laurent Duflot. See talk by Adam Gibson on 1/9 LAr weekly meeting and Bin Guo presentation at 24/9 analysis meeting. How to convert this in a monitoring tool?
    • Preliminary implementation in LArRawChannelMonTool

  • CaloCells monitoring [MIS_CH][PHYS]:
    • Bad channels masking to be tested to see one gets plot easier to interpret. Create 2 plots : with and without masking.
    • Remove useless plots (cell rate without threshold? just 2 thresholds?)

  • Caloclusters monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.

Online / P1 environment

  • PT receiving no event or very few events:
    • Things seems to have improved since early september.
    • Interaction with TDAQ experts would be appreciated to have a better understanding of how PT are connected to SFIs (especially when no KeyValue is specified) and if debugging tools are available in case of problems.

  • Stateless (plain) Athena :
    • Functional. Tested and documented
    • Migration now done for online monitoring (cf Benedetto talk at DQ workshop).

  • Test the decoupling of HLT release with release used for LArPT
    • Done?

  • Orange led Online DQMF configuration :
    • LArFEBMon : right strict cut (no FEB in error?).
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning? Zero weight now applied to get right online DQMF check. Usefullness of this test to be understood. Do we want to monitor misbehaving channels online.

  • New DQMF display :
    • Now available for data integrity checks.
    • DQM configurator : allows to have a better geometry view of LAr. Under study by Franck Berghaus. Usefullness of this to be understood (OHP Nexus may be much more useful for our purposes).

  • Shifter documentation :
    • Preliminary OHP version satisfactory
    • Have to think how to include DQMF

  • Orange led LArGatherer :
    • Under discussion with Peter Renkel and Serguei Kolos.

  • Setup a simple tool to get the difference between current runs and conditions loaded for a cells :
    • Beta version by Walter Lampl works nicely. Need an additinal layer to get cell in term of FT/slot/channel instead of COOL channel. Then write a small pyroot script to be executed by shifter.
    • Done by Jean Francois MArchand. Documented.
    • Implementation at P1 to be done. Jean Francois in contact with Hans Von Der Schmid.

  • Orange led Find a way to provide a graphical mapping between FT/Slot and Eta/Phi for shifters :
    • Standalone QT application developed by P.A. Delsart. Now documented.
    • Next step : development of plugin in OHP nexus.

  • Orange led Interaction with HLT/LVL1 calo:
    • New dedicated tab in OHP? How to improve misbehaving channels flagging to allow shifters to give quick feedback to LVL1 calo persons?.
    • Ongoing development by P.A.Delsart in contact with D.Damazio.
    • Problem also related to how to store informations on "non permanently unhappy channels" (should they be stored in DB?).

  • Orange led "Quasi online" monitoring of data integrity of calibration runs :
    • Many problems seen in september with missing events in results (hopefully mainly empty events).
    • Need to monitor all events to check that nothing is missing.
    • Concrete implementation to be clarified.


  • Root macros :
    • Develop an interface to display ramp/wave coefficient (computed from automatic processed) stored in an ntuple.
    • Action : Ilya Orlov.
    • Already done : routine that create a new root file with all adequate histos; pros : fast access to all histos once the file is created. Cons : memory consuming!
    • Also done : plugin in root macro to produce on request the wished pulse shape; pros : no new file; cons : slow if a lot of request are sent (ex : all pulse shape of a FT!).
    • To be done : ramp treatment + test + CVS commit.

  • Orange led Followup of DQ along time :
    • Basic quantities to be integrated in ATLAS tool (nb of events, proportion of muons candidates...)
    • New TRT webdisplay to be tested.
    • Followup of problems can not be handled by such tools : see next point on a dynamic history tool.

  • History tool developed by Sheffield group
    • Migration to CERN server (contact with RTT people)
    • Include more streams (RNDM trigger?)
    • Include more algorithms : LArDigit ? LArRawChannel?
    • Analysis of FEBMon error yield in interaction with DO/DP people (N.Kerschen working on this).

Major updates:
-- BenjaminTrocme - 02 Sep 2008

%RESPONSIBLE% BenjaminTrocme
%REVIEW% Never reviewed

Edit | Attach | Watch | Print version | History: r19 | r17 < r16 < r15 < r14 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r15 - 2009-03-25 - BenjaminTrocme
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback