Difference: LArMonitoringPenseBete (1 vs. 19)

Revision 192014-01-22 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 20 to 20
 The larmonitoring package is checked out on larmon account in ~larmon/public/LArCalorimeter/LArMonitoring. All scripts are supposed to be moved here and then deleted from their former location
Added:
>
>
The documentation on the server stuff can be found here
 

Crucial facilities to be preserved

Facility Current location in larmon account Storage in LArMonitoring Dev Migration Status AOB

Revision 182013-06-21 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 25 to 25
 
Facility Current location in larmon account Storage in LArMonitoring Dev Migration Status AOB
WeeklyReport : extract all inefficiencies from defect useful for weekly/yearly report Removed python/LADIeS Benjamin Done  
WDE : WebdisplayExtractor     Christopher    
Added:
>
>
LArIDTranslator public/LArIdTranslator python/LArIdTranslator ??    
 
HV Trip database public/HVTripsDB?? python/HVTripsDB Operation team   3 dir exists today in public : nothing, _new, _test - Is the public/TripVizualizer directory related?
UPDTools: extarction of nb of channels flagged public/script/LADIeS python/LADIeS/UPDTools.exe Pavol / Walter   New linux exe that execute python script stored in larcalib
Changed:
<
<
LArPage 1 public/LArPage1 python LArPage1 Olivier D. Dir simply copied - No change yet  
>
>
LArPage 1 public/LArPage1 python LArPage1 Olivier D. Dir simply copied - No change yet  
LCE infrastructure        
 
Changed:
<
<
Important note for services using xmlrpc communication (WDE, Page1, WeeklyReport...): the new password generated for 1 year is now hidden in ~larmon/passfile.txt
>
>
Important note for services using xmlrpc communication (WDE, LArPage1, WeeklyReport...): the new password generated for 1 year is now hidden in ~larmon/passfile.txt
  To retrieve it, one should use the following typical sequence:

Revision 172013-06-21 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 17 to 17
 This page is meant to collect all informations to clean the messy larmon account during LS1.

Ideally, one would like to have all relevant scripts in the LArMonitoring package and not widespread in all the account as it is now.

Added:
>
>
The larmonitoring package is checked out on larmon account in ~larmon/public/LArCalorimeter/LArMonitoring. All scripts are supposed to be moved here and then deleted from their former location
 

Crucial facilities to be preserved

Changed:
<
<
Facility Current location in larmon account Storage in LArMonitoring Dev Migration Status
WeeklyReport : extract all inefficiencies from defect useful for weekly/yearly report     Benjamin  
WDE : WebdisplayExtractor     Christopher  
HV Trip database     Operation team  
>
>
Facility Current location in larmon account Storage in LArMonitoring Dev Migration Status AOB
WeeklyReport : extract all inefficiencies from defect useful for weekly/yearly report Removed python/LADIeS Benjamin Done  
WDE : WebdisplayExtractor     Christopher    
HV Trip database public/HVTripsDB?? python/HVTripsDB Operation team   3 dir exists today in public : nothing, _new, _test - Is the public/TripVizualizer directory related?
UPDTools: extarction of nb of channels flagged public/script/LADIeS python/LADIeS/UPDTools.exe Pavol / Walter   New linux exe that execute python script stored in larcalib
LArPage 1 public/LArPage1 python LArPage1 Olivier D. Dir simply copied - No change yet  
 
Added:
>
>
Important note for services using xmlrpc communication (WDE, Page1, WeeklyReport...): the new password generated for 1 year is now hidden in ~larmon/passfile.txt
 
Added:
>
>
To retrieve it, one should use the following typical sequence:

passfile = open("/afs/cern.ch/user/l/larmon/passfile.txt"); passwd = passfile.read().strip(); passfile.close(); s = xmlrpclib.ServerProxy('https://%s@atlasdqm.cern.ch'%(passwd))

I tried to update it for LAr Page 1. Not for WDE.

 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->

Revision 162013-06-21 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 10 to 10
 
<!-- if you want to modify it to something more meaningful, just replace LArMonitoringPenseBete below with i.e "My Topic"!-->
<!---------------------------------------------------------  snip snip ----------------------------------------------------------------->
Changed:
<
<

LArMonitoringPenseBete

>
>

larmon account cleaning

 
<!--optional-->
Changed:
<
<
<!-- Add an introduction here, describing the purpose of this topic. !-->
>
>
This page is meant to collect all informations to clean the messy larmon account during LS1.
 
Changed:
<
<
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!
>
>
Ideally, one would like to have all relevant scripts in the LArMonitoring package and not widespread in all the account as it is now.
 
Changed:
<
<
Urgent matters are spotted with a Orange led.
>
>

Crucial facilities to be preserved

 
Changed:
<
<

Algorithms

>
>
Facility Current location in larmon account Storage in LArMonitoring Dev Migration Status
WeeklyReport : extract all inefficiencies from defect useful for weekly/yearly report     Benjamin  
WDE : WebdisplayExtractor     Christopher  
HV Trip database     Operation team  
 
Deleted:
<
<
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:
    • https://pcatdwww.cern.ch/elog/ATLAS_W/ATLAS/21076
    • 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.

Offline

  • 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).
 

<!--***********************************************************-->

Revision 152009-03-25 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 54 to 54
 
  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
    • Algorithm stable, documentation done, DQMF available.
Changed:
<
<
    • To be done : Orange led correct error computation for histo dynamicaly booked for faulty FEBs (cf pb of 100% yield).
>
>
    • 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)
Changed:
<
<
    • Pending problem : is HEC geometry really correct? use the right method (cf discussion with Guillaume Unal). Is it done?
>
>
    • Pending problem : nice FCAL geometry by E.Wulf to be implemented for coverage.
 
  • LArOddCells [MIS_CH]:
    • Concerned runs : PEDESTAL mainly. (PHYSIC? to be determined)
Line: 82 to 82
 
  • 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.
Changed:
<
<
    • Possibility to mask bad channels.
>
>
    • 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.
Line: 114 to 114
 
  • Stateless (plain) Athena :
    • Functional. Tested and documented
Changed:
<
<
    • Orange led Migration to be done for online monitoring (cf Benedetto talk at DQ workshop).
>
>
    • 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 :
Changed:
<
<
    • LArFEBMon : right strict cut (no FEB in error?).
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning? Zero weight to be applied to get right online DQMF check.
>
>
    • 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 :
Changed:
<
<
    • Display to be tested at P1. No showstopper to test this.
    • DQM configurator : allows to have a better geometry view of LAr. Under study by Franck Berghaus.
>
>
    • 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
Line: 143 to 143
 
    • Standalone QT application developed by P.A. Delsart. Now documented.
    • Next step : development of plugin in OHP nexus.
Added:
>
>
  • 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.
Deleted:
<
<
  • Orange led Interaction with LVL1 calo:
    • New dedicated tab in OHP?
    • How to improve misbehaving channels flagging to allow shifters to give quick feedback to LVL1 calo persons? Have first to revive automatic extraction of misbehaving channels from DQMF (in a text file). LArOddCells seems to be a good candidate as a starting point.
    • Problem also related to how to store infromations on "non permanently unhappy channels" (should they be stored in DB?).
 

Offline

  • Root macros :
Line: 164 to 164
 
  • Orange led Followup of DQ along time :
    • Basic quantities to be integrated in ATLAS tool (nb of events, proportion of muons candidates...)
Changed:
<
<
>
>
    • 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

Revision 142009-02-23 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 22 to 22
 

Algorithms

Changed:
<
<
Last update : 20 January 2008
>
>
Last update : 20 February 2009
  Subgroups :
Line: 35 to 35
 
  • DCS status calculator [DCS]:
    • Concerned runs : PHYSIC (CALIB?)
Changed:
<
<
    • Status/State now stored in COOL with common IOVs for global LAr and DCS sub partitions.
    • Waiting for an implementation of algorithm "Worst case summary" by K.Leney. Followed by Samir Arfaoui.
>
>
    • 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
Line: 48 to 48
 
    • 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??).
Changed:
<
<
    • Code also includes time/chi2 computation. To be debugged (see minutes of 22 september DQ meeting).
>
>
    • 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]:
Line: 58 to 58
 
    • Current maintenance and analysis : Benjamin Trocmé

  • LArCoverage [DAQ]:
Changed:
<
<
    • Concerned runs : PHYSIC only for the moment (LArRawChannel). CALIB to be determined when we have better experience of the tool.
    • Current maintenance and further development : Jessica Leveque.
>
>
    • 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 : is HEC geometry really correct? use the right method (cf discussion with Guillaume Unal). Is it done?

  • LArOddCells [MIS_CH]:
Line: 76 to 76
 
  • LArRawChannel monitoring [MIS_CH] :
    • Development by Michel Lefebre and Franck Berghaus
Changed:
<
<
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold), average energy per cell, noise per cell, proportion of events with sigma above 3 x noise (à la LArOddCells).
    • Proposed new quantity : rms of negative tails : computed in TProfile by filling in the same time a mirrored distribution (therefore <> always equal to 0 but rms extracted).
>
>
    • 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
Changed:
<
<
    • Plot for each FEB the number of cells with sample of the maximum signal outside a time window, the number of saturated cells, the mean time of the maximum signal. Possibility to mask bad channels. Basic pulse shape reconstruction per partition (à la LArCosmics), variation of peak position vs time.
    • To be done : monitoring of cells with digits = 0. May be useful to correlate things with weird behaviour observed in DSP monitoring (to be confirmed...).
>
>
    • 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.
    • Possibility to mask bad channels.
 
  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
Line: 96 to 96
 
    • 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?
Added:
>
>
 
  • CaloCells monitoring [MIS_CH][PHYS]:
Deleted:
<
<
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
 
    • Bad channels masking to be tested to see one gets plot easier to interpret. Create 2 plots : with and without masking.
Deleted:
<
<
    • HEC binning to be fixed
 
    • Remove useless plots (cell rate without threshold? just 2 thresholds?)
Deleted:
<
<
 
  • Caloclusters monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
Deleted:
<
<
    • Are bad channels masked? Not yet on purpose!
 

Online / P1 environment

Line: 136 to 132
 
    • Have to think how to include DQMF

  • Orange led LArGatherer :
Changed:
<
<
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.
    • Have to test the possibility to choose the avergaing mode by use the name convention (_AVG or _SUM) and check this fullfill our possibilities. Under discussion with Peter Renkel and Serguei Kolos.
>
>
    • 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.
Line: 173 to 168
 
    • Followup of problems can not be handled by such tools : see next point on a dynamic history tool.

  • History tool developed by Sheffield group
Added:
>
>
    • 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).
 
Deleted:
<
<

Roadmap to have a better handling of misbehaving channels

It was especially spotted many times the difficulty to give a reliable diagnostic online to our LVL1 colleagues. Several things can be done to improve things

  • Provide a tool (GUI? script?) that provides a correspondance between FT/slot, eta/phi and trigger towers in a friendly way; this is expecially useful to use LArOddCells and LarRawChannels where all plots are made in FT/slot contexts. This tool is generally needed for a lot of aspects and is awaited for a long time and it was not clear how to implement this. The recent release of OHP Nexus may be a nice way to get this working. Feasibility investigated by P.A.Delsart.

  • Store in bad channels DB the known FEB subject to noise bursts. Action : ask teddy to add a single flag "IntermittentBurst" (BT). The database can first be stored with Stefan et al list (+ input from Savannah subject submitted on 8/10 - to be followed). Then, we'll need to get somebody to keep tracks of all misbehaving channels observed in physic runs in interaction with list provided by Manuella. Candidate : canadian post doc arriving in early october? 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) (JL)

  • Mask bad channels in different algorithms. 2 options here :
    • mask the bad channels in job options as done right now but this is subject to definition how what should be masked. Only "Serious", or also "Minor" and "Intermittent". For detecting new problems, one should mask everything but we lose information. To be discussed. Can be implemented soon (except perhaps for CaloCells- to be investigated).
    • develop a new plugin that do a dynamic merging of LArCoverage plots and all kind of 2D plots. This is the most elegant and flexible method but is it technically feasible? This is more for long term plans.

The above 3 points are mainly meant to improve things for LAr shifters. Concerning offline, the way to report things right now is efficient only if someone is following things on a long term basis (canadian post doc?). We should try to find a way to get FT/slot vs eta/phi correspondance offline (if the above solution in OHP is approved).

 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->

Revision 132009-01-20 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 22 to 22
 

Algorithms

Changed:
<
<
Last update : 23 september 2008
>
>
Last update : 20 January 2008
  Subgroups :
Line: 47 to 47
 
  • 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).
Added:
>
>
    • 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. To be debugged (see minutes of 22 september DQ meeting).
Changed:
<
<
    • Routine processing offline under study (CAF).
    • Now working online. Still waiting for last DSP version for debugging of precisions problems (obvious in HEC / FCAL)
>
>
    • 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.
Changed:
<
<
    • Monitoring of number of results block now available. To be done : Orange led dynamic histo booking for faulty FEBs + checksum error to be reported.
>
>
    • To be done : Orange led correct error computation for histo dynamicaly booked for faulty FEBs (cf pb of 100% yield).
 
    • Current maintenance and analysis : Benjamin Trocmé

  • LArCoverage [DAQ]:
Line: 71 to 71
 
  • LArNoiseMonToolBase suite [MIS_CH]:
    • Concerned runs : PEDESTAL.
Changed:
<
<
    • Tool mainly used for commissioning and debugging with a lot of clever plots. Still integrated (in its basic version) in automatic monitoring.
>
>
    • 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] :
Deleted:
<
<
    • Lightened version of NoiseMonToolBase suite to monitor LArRAwChannel
 
    • Development by Michel Lefebre and Franck Berghaus
Changed:
<
<
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold) and average energy per cell.
>
>
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold), average energy per cell, noise per cell, proportion of events with sigma above 3 x noise (à la LArOddCells).
 
    • Proposed new quantity : rms of negative tails : computed in TProfile by filling in the same time a mirrored distribution (therefore <> always equal to 0 but rms extracted).
Deleted:
<
<
    • Orange led To be done : integration of LArRawChannels plots from LArCosmicsMonTool.
    • Will also be considered : yield per event of cells above a given threshold (possibility to detect noise bursts).
 
  • Basic digits monitoring (for cells with signal only) [SIG]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
Changed:
<
<
    • Plot for each FEB the number of cells with sample of the maximum signal outside a time window, the number of saturated cells, the mean time of the maximum signal. Possibility to mask bad channels. Basic pulse shape reconstruction per partition (à la LArCosmics).
    • Orange led To be done : variation of peak position vs time.
>
>
    • Plot for each FEB the number of cells with sample of the maximum signal outside a time window, the number of saturated cells, the mean time of the maximum signal. Possibility to mask bad channels. Basic pulse shape reconstruction per partition (à la LArCosmics), variation of peak position vs time.
    • To be done : monitoring of cells with digits = 0. May be useful to correlate things with weird behaviour observed in DSP monitoring (to be confirmed...).
 
  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
Line: 114 to 111
 

Online / P1 environment

Deleted:
<
<
 
Line: 130 to 123
 
  • Test the decoupling of HLT release with release used for LArPT
    • Done?
Deleted:
<
<
  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
    • Now implemented in PT. Summary content to be understood.
 
  • 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 to be applied to get right online DQMF check.
Line: 147 to 137
 
  • Orange led LArGatherer :
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.
Changed:
<
<
    • Have to test the possibility to choose the avergaing mode by use the name convention (_AVG or _SUM) and check this fullfill our possibilities. Under discussion with Peter Renkel and Serguei Kolos
>
>
    • Have to test the possibility to choose the avergaing mode by use the name convention (_AVG or _SUM) and check this fullfill our possibilities. 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.
Line: 155 to 145
 
    • 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 :
Changed:
<
<
    • QT application developed by P.A. Delsart. To be integrated in OHP Nexus.
>
>
    • Standalone QT application developed by P.A. Delsart. Now documented.
    • Next step : development of plugin in OHP nexus.
 
  • 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).
Line: 169 to 160
 

Offline

Deleted:
<
<
  • Follow CPU/Memory consumption
    • Orange led Checks new performances when switching LArDigits (in physic mode) and removing LArCosmicsMonTool (last LArRawChannel plots to be moved to adequate algo).
    • Action : Damir Lelas (in coordination with tool developers).

  • LArRodMonitoring :
    • Which infrastructure to check systematically the computation in DSP?
    • Not recommanded at Tier0 to limit memory consumption. At CAF? On which timescale?

  • Offline DQMF configuration :
    • Orange led Update of LArGlobal plots (type, nb of samples, 2D LArFEBMon plots...) + use of log scale...
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).
 
  • Root macros :
    • Develop an interface to display ramp/wave coefficient (computed from automatic processed) stored in an ntuple.
    • Action : Ilya Orlov.
Line: 189 to 168
 
    • To be done : ramp treatment + test + CVS commit.

  • Orange led Followup of DQ along time :
Added:
>
>
    • Basic quantities to be integrated in ATLAS tool (nb of events, proportion of muons candidates...)
 
Changed:
<
<
    • First trial of automatic DQ check with extraction of problems with time : http://trocme.web.cern.ch/trocme/
    • More automatic, fancy framework : under study by Sheffield group.
>
>
    • Followup of problems can not be handled by such tools : see next point on a dynamic history tool.

  • History tool developed by Sheffield group
 

Roadmap to have a better handling of misbehaving channels

Revision 122008-11-25 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.

Revision 112008-11-14 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 102 to 102
 
  • CaloCells monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
Changed:
<
<
    • Bad channels masking to be tested to see one gets plot easier to interpret.
>
>
    • Bad channels masking to be tested to see one gets plot easier to interpret. Create 2 plots : with and without masking.
    • HEC binning to be fixed
    • 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.

Revision 102008-11-13 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 36 to 36
 
  • DCS status calculator [DCS]:
    • Concerned runs : PHYSIC (CALIB?)
    • Status/State now stored in COOL with common IOVs for global LAr and DCS sub partitions.
Changed:
<
<
    • Have now to interact with Katarine Leney to have it implemented in DCS status flag calculator. Followed by Samir Arfaoui.
>
>
    • Waiting for an implementation of algorithm "Worst case summary" by K.Leney. Followed by Samir Arfaoui.
 
  • Monitoring at the ROD level [DAQ][MIS_CH]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
Line: 48 to 48
 
    • 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).
    • Code also includes time/chi2 computation. To be debugged (see minutes of 22 september DQ meeting).
Changed:
<
<
    • Routine processing offline under study (CAF). Now working online.
>
>
    • Routine processing offline under study (CAF).
    • Now working online. Still waiting for last DSP version for debugging of precisions problems (obvious in HEC / FCAL)
 
  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
    • Algorithm stable, documentation done, DQMF available.
Changed:
<
<
    • Monitoring of number of results block available. Commited when new LArByteStream and LArRawEvent available.
    • Apart from this, mainly minor developments on request.
>
>
    • Monitoring of number of results block now available. To be done : Orange led dynamic histo booking for faulty FEBs + checksum error to be reported.
 
    • Current maintenance and analysis : Benjamin Trocmé

  • LArCoverage [DAQ]:
Line: 79 to 79
 
    • Development by Michel Lefebre and Franck Berghaus
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold) and average energy per cell.
    • Proposed new quantity : rms of negative tails : computed in TProfile by filling in the same time a mirrored distribution (therefore <> always equal to 0 but rms extracted).
Changed:
<
<
    • Orange led To be done : masking of bad channels. Have to understand how to perform DQMF check on this.
>
>
 
    • Will also be considered : yield per event of cells above a given threshold (possibility to detect noise bursts).

  • 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, the mean time of the maximum signal. Possibility to mask bad channels. Basic pulse shape reconstruction per partition (à la LArCosmics).
Added:
>
>
    • Orange led To be done : variation of peak position vs time.
 
  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
Line: 119 to 120
 
    • 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.
Changed:
<
<
  • Stateless Athena :
>
>
  • Stateless (plain) Athena :
 
    • Functional. Tested and documented
Changed:
<
<
    • What about MDA and histogram saving in this framework, if one decides to switch to Stateless for routine monitoring?
>
>
    • Orange led Migration to be done for online monitoring (cf Benedetto talk at DQ workshop).
 
  • Test the decoupling of HLT release with release used for LArPT
Added:
>
>
    • Done?
 
  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
    • Now implemented in PT. Summary content to be understood.

  • Orange led Online DQMF configuration :
Changed:
<
<
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition and especially for HEC/FCAL.
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning?
>
>
    • LArFEBMon : right strict cut (no FEB in error?).
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning? Zero weight to be applied to get right online DQMF check.
 
  • New DQMF display :
    • Display to be tested at P1. No showstopper to test this.
    • DQM configurator : allows to have a better geometry view of LAr. Under study by Franck Berghaus.
Deleted:
<
<
  • New OHP Nexus :
    • Expected to become the new standard. Very promising (more friendly GUI, faster, more flexible!).
    • Configuration file currently updated by Jessica Leveque.

  • Online DQMF configuration :
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).
 
  • Shifter documentation :
    • Preliminary OHP version satisfactory
    • Have to think how to include DQMF

  • Orange led LArGatherer :
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.
Changed:
<
<
    • Have to test the possibility to choose the avergaing mode by use the name convention (_AVG or _SUM) and check this fullfill our possibilities.
>
>
    • Have to test the possibility to choose the avergaing mode by use the name convention (_AVG or _SUM) and check this fullfill our possibilities. 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.
Line: 157 to 152
 
    • 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 :
Changed:
<
<
    • Superimposed plot in OHP?
    • First contact with Sabine Elles to see whether her little python/athena script can be used as a base.
>
>
    • QT application developed by P.A. Delsart. To be integrated in OHP Nexus.
 
  • 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).
Line: 173 to 167
 

Offline

  • Follow CPU/Memory consumption
Added:
>
>
* Orange led Checks new performances when switching LArDigits (in physic mode) and removing LArCosmicsMonTool (last LArRawChannel plots to be moved to adequate algo).
 
    • Action : Damir Lelas (in coordination with tool developers).

  • LArRodMonitoring :
Line: 180 to 175
 
    • Not recommanded at Tier0 to limit memory consumption. At CAF? On which timescale?

  • Offline DQMF configuration :
Added:
>
>
    • Orange led Update of LArGlobal plots (type, nb of samples, 2D LArFEBMon plots...) + use of log scale...
 
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).

  • Root macros :
Line: 191 to 187
 
Changed:
<
<
    • First trial of an implementation with FEBMon (nb of FEB per event to start - then nb of FEBMon errors).
    • Action : Benjamin Trocmé then Julien Labbé
>
>
    • First trial of automatic DQ check with extraction of problems with time : http://trocme.web.cern.ch/trocme/
    • More automatic, fancy framework : under study by Sheffield group.
 

Roadmap to have a better handling of misbehaving channels

Revision 92008-10-13 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 194 to 194
 
    • First trial of an implementation with FEBMon (nb of FEB per event to start - then nb of FEBMon errors).
    • Action : Benjamin Trocmé then Julien Labbé
Added:
>
>

Roadmap to have a better handling of misbehaving channels

It was especially spotted many times the difficulty to give a reliable diagnostic online to our LVL1 colleagues. Several things can be done to improve things

  • Provide a tool (GUI? script?) that provides a correspondance between FT/slot, eta/phi and trigger towers in a friendly way; this is expecially useful to use LArOddCells and LarRawChannels where all plots are made in FT/slot contexts. This tool is generally needed for a lot of aspects and is awaited for a long time and it was not clear how to implement this. The recent release of OHP Nexus may be a nice way to get this working. Feasibility investigated by P.A.Delsart.

  • Store in bad channels DB the known FEB subject to noise bursts. Action : ask teddy to add a single flag "IntermittentBurst" (BT). The database can first be stored with Stefan et al list (+ input from Savannah subject submitted on 8/10 - to be followed). Then, we'll need to get somebody to keep tracks of all misbehaving channels observed in physic runs in interaction with list provided by Manuella. Candidate : canadian post doc arriving in early october? 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) (JL)

  • Mask bad channels in different algorithms. 2 options here :
    • mask the bad channels in job options as done right now but this is subject to definition how what should be masked. Only "Serious", or also "Minor" and "Intermittent". For detecting new problems, one should mask everything but we lose information. To be discussed. Can be implemented soon (except perhaps for CaloCells- to be investigated).
    • develop a new plugin that do a dynamic merging of LArCoverage plots and all kind of 2D plots. This is the most elegant and flexible method but is it technically feasible? This is more for long term plans.

The above 3 points are mainly meant to improve things for LAr shifters. Concerning offline, the way to report things right now is efficient only if someone is following things on a long term basis (canadian post doc?). We should try to find a way to get FT/slot vs eta/phi correspondance offline (if the above solution in OHP is approved).

 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->

Revision 82008-09-25 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 22 to 22
 

Algorithms

Changed:
<
<
Last update : 11 july 2008
>
>
Last update : 23 september 2008
  Subgroups :
Line: 35 to 35
 
  • DCS status calculator [DCS]:
    • Concerned runs : PHYSIC (CALIB?)
Changed:
<
<
    • For the moment, Status/State stored separatly in COOL with different IOVs. Waiting to have stored in a single folder to implement a status flag for LAr based on these 2 quantities.
    • When implementation is done, go back to Katarine Leney for whom it should be rather easy to assess a flag from these status/state stored in COOL (xml configuration file : flexible and easy!).
>
>
    • Status/State now stored in COOL with common IOVs for global LAr and DCS sub partitions.
    • Have now to interact with Katarine Leney to have it implemented in DCS status flag calculator. Followed by Samir Arfaoui.
 
  • Monitoring at the ROD level [DAQ][MIS_CH]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
Line: 47 to 47
 
  • 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).
Changed:
<
<
    • Tool functionnal. Implementation in online/offline world to be clarified (see relevant sections).
    • To de done : similar tool with time computation.
>
>
    • Code also includes time/chi2 computation. To be debugged (see minutes of 22 september DQ meeting).
    • Routine processing offline under study (CAF). Now working online.
 
  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
    • Algorithm stable, documentation done, DQMF available.
Changed:
<
<
    • To be done : monitoring of number of results block (new LArRawEvent needed)
>
>
 
    • Apart from this, mainly minor developments on request.
    • Current maintenance and analysis : Benjamin Trocmé
Line: 67 to 67
 
    • Algorithm stable, documentation almost done, DQMF available.
    • Mainly minor developments on request.
    • Current maintenance and analysis : Benjamin Trocmé.
Added:
>
>
    • 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.
Line: 78 to 79
 
    • Development by Michel Lefebre and Franck Berghaus
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold) and average energy per cell.
    • Proposed new quantity : rms of negative tails : computed in TProfile by filling in the same time a mirrored distribution (therefore <> always equal to 0 but rms extracted).
Changed:
<
<
    • Orange led To be done : masking of bad channels + BCID dependance (example : nb of cells above a given threshold vs BCID)
>
>
    • Orange led To be done : masking of bad channels. Have to understand how to perform DQMF check on this.
 
    • Will also be considered : yield per event of cells above a given threshold (possibility to detect noise bursts).

  • Basic digits monitoring (for cells with signal only) [SIG]:
    • Concerned runs : PHYSIC mainly. CALIB for debugging
Changed:
<
<
    • Plot for each FEB the number of cells with sample of the maximum signal outside a time window, the number of saturated cells, the mean time of the maximum signal. Possibility to mask bad channels.
    • To be done : basic pulse shape reconstruction per partition (à la LArCosmics).
>
>
    • Plot for each FEB the number of cells with sample of the maximum signal outside a time window, the number of saturated cells, the mean time of the maximum signal. Possibility to mask bad channels. Basic pulse shape reconstruction per partition (à la LArCosmics).
 
  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
Line: 97 to 97
 
    • 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.
Changed:
<
<
    • Some interests by Laurent Serin and Laurent Duflot. See talk by Adam Gibson on 1/9 LAr weekly meeting. How to convert this in a monitoring tool?
>
>
    • 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?
 
  • CaloCells monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
Changed:
<
<
    • Are bad channels masked? Not yet on purpose.
>
>
    • Bad channels masking to be tested to see one gets plot easier to interpret.
 
  • Caloclusters monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
Line: 114 to 114
 
Changed:
<
<
  • Orange led PT receiving no event :
>
>
  • PT receiving no event or very few events:
 
Changed:
<
<
    • Problem of event sampler?
    • To be investigated with TDAQ experts.

  • CaloMonitoring switched off in LArPT-Cosmics since mid August :
    • Experts working on it.
    • Fixed on 14 september.
>
>
    • 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 Athena :
    • Functional. Tested and documented
Changed:
<
<
    • What about MDA and histogram saving in this framework?
>
>
    • What about MDA and histogram saving in this framework, if one decides to switch to Stateless for routine monitoring?
 
  • Test the decoupling of HLT release with release used for LArPT

  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
Changed:
<
<
    • Functional in Stateless. To be implemented in LArPT
>
>
    • Now implemented in PT. Summary content to be understood.
 
  • Orange led Online DQMF configuration :
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition and especially for HEC/FCAL.
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning?
Added:
>
>
  • New DQMF display :
    • Display to be tested at P1. No showstopper to test this.
    • DQM configurator : allows to have a better geometry view of LAr. Under study by Franck Berghaus.

  • New OHP Nexus :
    • Expected to become the new standard. Very promising (more friendly GUI, faster, more flexible!).
    • Configuration file currently updated by Jessica Leveque.
 
  • Online DQMF configuration :
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).
Line: 143 to 147
 
    • Preliminary OHP version satisfactory
    • Have to think how to include DQMF
Deleted:
<
<
  • New DQMF display development (C++ / qt / root):
    • to be used online, more user friendly and flexible than the current implementation with JAIDA.
    • 1st beta bersion by end of june
    • To be tested by Franck Berghaus.
 
  • Orange led LArGatherer :
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.
Added:
>
>
    • Have to test the possibility to choose the avergaing mode by use the name convention (_AVG or _SUM) and check this fullfill our possibilities.
 
  • 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.
Changed:
<
<
    • Implementation at P1 to be tested.
>
>
    • 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 :
    • Superimposed plot in OHP?
Added:
>
>
    • First contact with Sabine Elles to see whether her little python/athena script can be used as a base.

  • 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.

  • Orange led Interaction with LVL1 calo:
    • New dedicated tab in OHP?
    • How to improve misbehaving channels flagging to allow shifters to give quick feedback to LVL1 calo persons? Have first to revive automatic extraction of misbehaving channels from DQMF (in a text file). LArOddCells seems to be a good candidate as a starting point.
    • Problem also related to how to store infromations on "non permanently unhappy channels" (should they be stored in DB?).
 

Offline

Line: 171 to 182
 
  • Offline DQMF configuration :
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).
Changed:
<
<
  • Orange led Root macros :
>
>
  • 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!
Changed:
<
<
    • To be 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!).
>
>
    • 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.
 
Changed:
<
<
  • Followup of DQ along time :
>
>
  • Orange led Followup of DQ along time :
 

Revision 72008-09-22 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 127 to 127
 
    • Functional. Tested and documented
    • What about MDA and histogram saving in this framework?
Changed:
<
<
  • Test the decoupling of HLT release with release used for PT
>
>
  • Test the decoupling of HLT release with release used for LArPT
 
  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
Changed:
<
<
    • Functional in Stateless. To be implemented in LArPT
>
>
    • Functional in Stateless. To be implemented in LArPT
 
Changed:
<
<
  • Online DQMF configuration :
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition.
>
>
  • Orange led Online DQMF configuration :
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition and especially for HEC/FCAL.
 
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning?

  • Online DQMF configuration :
Line: 154 to 154
 
  • 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.
Added:
>
>
    • Implementation at P1 to be tested.
 
  • Orange led Find a way to provide a graphical mapping between FT/Slot and Eta/Phi for shifters :
    • Superimposed plot in OHP?

Revision 62008-09-17 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 110 to 110
 

Online / P1 environment

Changed:
<
<
  • Orange led PT crashes :
>
>
  • PT crashes :
 
Changed:
<
<
    • Suspicion of a memory leak (cf post by Luca Fiorini)
    • To be investigated
>
>
    • Fixed - Was due to a rebooking of histo
 

Revision 52008-09-16 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 53 to 53
 
  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
    • Algorithm stable, documentation done, DQMF available.
Changed:
<
<
    • Have to implement the check of data block size in order to find empty data block also in result mode.
>
>
    • To be done : monitoring of number of results block (new LArRawEvent needed)
 
    • Apart from this, mainly minor developments on request.
    • Current maintenance and analysis : Benjamin Trocmé
Line: 84 to 84
 
  • 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, the mean time of the maximum signal. Possibility to mask bad channels.
Changed:
<
<
    • To be done : better determination of signal window (on the fly?) + treatment of different gains + basic pulse shape reconstruction per partition (à la LArCosmics).
>
>
    • To be done : basic pulse shape reconstruction per partition (à la LArCosmics).
 
  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
Line: 120 to 120
 
    • Problem of event sampler?
    • To be investigated with TDAQ experts.
Changed:
<
<
  • Orange led CaloMonitoring switched off in LArPT-Cosmics since mid August :
>
>
  • CaloMonitoring switched off in LArPT-Cosmics since mid August :
 
    • Experts working on it.
Added:
>
>
    • Fixed on 14 september.
 
Changed:
<
<
  • Orange led Stateless Athena :
    • Test started.
    • Looks promising with HelloWorld but problem of Athena configuration for LAr example.
>
>
  • Stateless Athena :
    • Functional. Tested and documented
 
    • What about MDA and histogram saving in this framework?

  • Test the decoupling of HLT release with release used for PT
Changed:
<
<
  • Orange led Implementation of LArRodMonitoring (comparison DSP vs reco) :
    • In a specific task (LArPT-ROD) with a specific reco.
    • To be done by Mathieu Aurousseau when stateless Athena monitoring works.
>
>
  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
    • Functional in Stateless. To be implemented in LArPT
 
  • Online DQMF configuration :
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition.
Line: 148 to 147
 
  • New DQMF display development (C++ / qt / root):
    • to be used online, more user friendly and flexible than the current implementation with JAIDA.
    • 1st beta bersion by end of june
Changed:
<
<
    • Status?
>
>
    • To be tested by Franck Berghaus.
 
  • Orange led LArGatherer :
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.

  • 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.
Added:
>
>
    • Done by Jean Francois MArchand. Documented.
 
  • Orange led Find a way to provide a graphical mapping between FT/Slot and Eta/Phi for shifters :
    • Superimposed plot in OHP?

Revision 42008-09-03 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 96 to 96
 
  • 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.
Changed:
<
<
    • For the moment, quality word not implemented (cf problem of memory consumption, as the pulse shape is needed to extract it). Should be solved with 14.2.0 where a pulse shape binned by 3ns is used.
>
>
    • 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. How to convert this in a monitoring tool?

  • CaloCells monitoring [MIS_CH][PHYS]:

Revision 32008-09-03 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 156 to 156
 
  • 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.
Added:
>
>
  • Orange led Find a way to provide a graphical mapping between FT/Slot and Eta/Phi for shifters :
    • Superimposed plot in OHP?
 

Offline

  • Follow CPU/Memory consumption

Revision 22008-09-03 - BenjaminTrocme

Line: 1 to 1
 
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
Line: 18 to 18
  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!
Added:
>
>
Urgent matters are spotted with a Orange led.
 

Algorithms

Line: 34 to 35
 
  • DCS status calculator [DCS]:
    • Concerned runs : PHYSIC (CALIB?)
Changed:
<
<
    • For the moment, Status/State stored separatly in COOL with different IOV. Waiting to have stored in a single folder to implement a status flag for LAr based on these 2 quantities.
>
>
    • For the moment, Status/State stored separatly in COOL with different IOVs. Waiting to have stored in a single folder to implement a status flag for LAr based on these 2 quantities.
 
    • When implementation is done, go back to Katarine Leney for whom it should be rather easy to assess a flag from these status/state stored in COOL (xml configuration file : flexible and easy!).

  • 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).
Changed:
<
<
    • Main software already implemented. Stability (especially wrt regular sbc crash) to be proven.
>
>
    • 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).
    • Tool functionnal. Implementation in online/offline world to be clarified (see relevant sections).
Added:
>
>
    • To de done : similar tool with time computation.
 
  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
Line: 56 to 58
 
    • Current maintenance and analysis : Benjamin Trocmé

  • LArCoverage [DAQ]:
Changed:
<
<
    • Concerned runs : PHYSIC only for the moment (LArRawChannel). CALIB to be determined when we have better experience of the tool.
    • Current maintenance and further development : Jessica Leveque and Francesco Spano.
>
>
    • Concerned runs : PHYSIC only for the moment (LArRawChannel). CALIB to be determined when we have better experience of the tool.
    • Current maintenance and further development : Jessica Leveque.
 
    • Pending problem : is HEC geometry really correct? use the right method (cf discussion with Guillaume Unal). Is it done?

  • LArOddCells [MIS_CH]:
Line: 67 to 69
 
    • Current maintenance and analysis : Benjamin Trocmé.

  • LArNoiseMonToolBase suite [MIS_CH]:
Changed:
<
<
    • Concerned runs : PEDESTAL + PHYSIC
    • Main facility used up to now : digits with especially some specific
>
>
    • 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.
 
    • Long time development by Victoria Team.

  • LArRawChannel monitoring [MIS_CH]:
Changed:
<
<
>
>
    • Lightened version of NoiseMonToolBase suite to monitor LArRAwChannel
 
    • Development by Michel Lefebre and Franck Berghaus
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold) and average energy per cell.
    • Proposed new quantity : rms of negative tails : computed in TProfile by filling in the same time a mirrored distribution (therefore <> always equal to 0 but rms extracted).
Changed:
<
<
    • To be done : masking of bad channels + BCID dependance (example : nb of cells above a given threshold vs BCID)
>
>
    • Orange led To be done : masking of bad channels + BCID dependance (example : nb of cells above a given threshold vs BCID)
 
    • Will also be considered : yield per event of cells above a given threshold (possibility to detect noise bursts).

  • 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, the mean time of the maximum signal. Possibility to mask bad channels.
Changed:
<
<
    • To be done : better determination of signal window (on the fly?) + treatment of different gains.
>
>
    • To be done : better determination of signal window (on the fly?) + treatment of different gains + basic pulse shape reconstruction per partition (à la LArCosmics).
 
  • Refined digits monitoring [SIG]:
    • Concerned runs : PHYSIC only.
Line: 91 to 93
 
    • 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
Changed:
<
<
>
>
  • 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 implemented (cf problem of memory consumption, as the pulse shape is needed to extract it). Should be solved with 14.2.0 where a pulse shape binned by 3ns is used.
Changed:
<
<
    • Some interests by Laurent Serin and Laurent Duflot.
>
>
    • Some interests by Laurent Serin and Laurent Duflot. See talk by Adam Gibson on 1/9 LAr weekly meeting. How to convert this in a monitoring tool?
 
  • CaloCells monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
Line: 108 to 110
 

Online / P1 environment

Changed:
<
<
  • PT crashes :
>
>
  • Orange led PT crashes :
 
Changed:
<
<
  • PT receiving no event :
>
>
  • Orange led PT receiving no event :
 
Changed:
<
<
    • Problem of event sampler
>
>
    • Problem of event sampler?
 
    • To be investigated with TDAQ experts.
Changed:
<
<
>
>
  • Orange led CaloMonitoring switched off in LArPT-Cosmics since mid August :
 
    • Experts working on it.
Changed:
<
<
  • Stateless Athena :
    • To be tested
>
>
  • Orange led Stateless Athena :
    • Test started.
    • Looks promising with HelloWorld but problem of Athena configuration for LAr example.
 
    • What about MDA and histogram saving in this framework?
Changed:
<
<
  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
>
>
  • Test the decoupling of HLT release with release used for PT

  • Orange led Implementation of LArRodMonitoring (comparison DSP vs reco) :
 
    • In a specific task (LArPT-ROD) with a specific reco.
Changed:
<
<
    • To be done by Mathieu Aurousseau
>
>
    • To be done by Mathieu Aurousseau when stateless Athena monitoring works.
 
  • Online DQMF configuration :
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition.
Line: 145 to 150
 
    • 1st beta bersion by end of june
    • Status?
Changed:
<
<
>
>
  • Orange led LArGatherer :
 
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.
Added:
>
>
  • 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.
 

Offline

  • Follow CPU/Memory consumption
    • Action : Damir Lelas (in coordination with tool developers).
Changed:
<
<
>
>
  • LArRodMonitoring :
 
    • Which infrastructure to check systematically the computation in DSP?
    • Not recommanded at Tier0 to limit memory consumption. At CAF? On which timescale?

  • Offline DQMF configuration :
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).
Changed:
<
<
  • Root macros :
>
>
  • Orange led 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!

Revision 12008-09-02 - BenjaminTrocme

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="BenjaminTrocme"
<!-- This is the default ATLAS template. 
Please modify it in the sections indicated to create your topic! In particular, notice that at the bottom there are some sections that must be filled for publicly accessible pages.
If you have any comments/complaints about this template, then please email : Stephen Haywood (Computing Documentation Coordinator)
S.Haywood at rl.ac.uk (or failing that, edward.moyse at cern.ch)
-->

<!-- By default the title is the WikiWord used to create this topic !-->
<!-- if you want to modify it to something more meaningful, just replace LArMonitoringPenseBete below with i.e "My Topic"!-->
<!---------------------------------------------------------  snip snip ----------------------------------------------------------------->

LArMonitoringPenseBete

<!--optional-->

<!-- Add an introduction here, describing the purpose of this topic. !-->

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!

Algorithms

Last update : 11 july 2008

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?)
    • For the moment, Status/State stored separatly in COOL with different IOV. Waiting to have stored in a single folder to implement a status flag for LAr based on these 2 quantities.
    • When implementation is done, go back to Katarine Leney for whom it should be rather easy to assess a flag from these status/state stored in COOL (xml configuration file : flexible and easy!).

  • 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. Stability (especially wrt regular sbc crash) to be proven.
    • 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).
    • Tool functionnal. Implementation in online/offline world to be clarified (see relevant sections).

  • LArFEBMon [DAQ]:
    • Concerned runs : ALL
    • Algorithm stable, documentation done, DQMF available.
    • Have to implement the check of data block size in order to find empty data block also in result mode.
    • Apart from this, mainly minor developments on request.
    • Current maintenance and analysis : Benjamin Trocmé

  • LArCoverage [DAQ]:
    • Concerned runs : PHYSIC only for the moment (LArRawChannel). CALIB to be determined when we have better experience of the tool.
    • Current maintenance and further development : Jessica Leveque and Francesco Spano.
    • Pending problem : is HEC geometry really correct? use the right method (cf discussion with Guillaume Unal). Is it done?

  • 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é.

  • LArNoiseMonToolBase suite [MIS_CH]:
    • Concerned runs : PEDESTAL + PHYSIC
    • Main facility used up to now : digits with especially some specific
    • Long time development by Victoria Team.

  • LArRawChannel monitoring [MIS_CH]:
    • Lightened version of NoiseMonToolBase suite to monitor LArRAwChannel
    • Development by Michel Lefebre and Franck Berghaus
    • Quantities currently computed : occupancy (nb of events per cell above a given threshold) and average energy per cell.
    • Proposed new quantity : rms of negative tails : computed in TProfile by filling in the same time a mirrored distribution (therefore <> always equal to 0 but rms extracted).
    • To be done : masking of bad channels + BCID dependance (example : nb of cells above a given threshold vs BCID)
    • Will also be considered : yield per event of cells above a given threshold (possibility to detect noise bursts).

  • 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, the mean time of the maximum signal. Possibility to mask bad channels.
    • To be done : better determination of signal window (on the fly?) + treatment of different gains.

  • 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

  • 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 implemented (cf problem of memory consumption, as the pulse shape is needed to extract it). Should be solved with 14.2.0 where a pulse shape binned by 3ns is used.
    • Some interests by Laurent Serin and Laurent Duflot.

  • CaloCells monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
    • Are bad channels masked? Not yet on purpose.

  • Caloclusters monitoring [MIS_CH][PHYS]:
    • Ongoing work to produce compact summary plots, tune DQMF thresholds.
    • Are bad channels masked? Not yet on purpose!

Online / P1 environment

  • Stateless Athena :
    • To be tested
    • What about MDA and histogram saving in this framework?

  • Implementation of LArRodMonitoring (comparison DSP vs reco) :
    • In a specific task (LArPT-ROD) with a specific reco.
    • To be done by Mathieu Aurousseau

  • Online DQMF configuration :
    • LArFEBMon : configuration file to be updated with the right histo ("Nb of errors per FEB") for all partition.
    • CaloCells : tuning of threshold - is it the right test? really needed at the beginning?

  • Online DQMF configuration :
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).

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

  • New DQMF display development (C++ / qt / root):
    • to be used online, more user friendly and flexible than the current implementation with JAIDA.
    • 1st beta bersion by end of june
    • Status?

  • LArGatherer :
    • Review needed to check if gathering is correctly done : if yes, check that the OHP file is correctly set; if not, contact Peter Renkel with a complete list of problems to fix.

Offline

  • Follow CPU/Memory consumption
    • Action : Damir Lelas (in coordination with tool developers).

  • LArRodMonitoring :
    • Which infrastructure to check systematically the computation in DSP?
    • Not recommanded at Tier0 to limit memory consumption. At CAF? On which timescale?

  • Offline DQMF configuration :
    • Decision tree to be discussed (for the moment only worst case summary but not satisfactory).

  • 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!
    • To be 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!).

<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
<!--***********************************************************-->


<!--For significant updates to the topic, consider adding your 'signature' (beneath this editing box)-->
Major updates:
-- BenjaminTrocme - 02 Sep 2008

<!--Please add the name of someone who is responsible for this page so that he/she can be contacted if changes are needed.
The creator's name will be added by default, but this can be replaced if appropriate.
Put the name first, without dashes.-->
%RESPONSIBLE% BenjaminTrocme
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
%REVIEW% Never reviewed
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback