Difference: RichDataQuality (1 vs. 49)

Revision 492018-09-23 - MarcoCattaneo

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="DataQuality"
>
>
META TOPICPARENT name="LHCbInternal.DataQuality"
 

LHCb RICH Data Quality

This page summarises the efforts of the RICH Data Quality with instructions for the RICH and the RICH DQ piquet.

Line: 106 to 106
 
  • RICH Operations: Wednesdays, 10:35 (CERN time) in the Rich section of Indico. All operational aspects of the RICH detector, as well as longer term planning is discussed here.
  • RICH Software: Fridays 15:00 (CERN time) in the Rich section of Indico. All RICH aspects related to software issues are discussed (e.g. Data-Quality, alignment, reconstruction, ...)
  • LHCb Data-Quality meeting, Weekdays 13:30 (CERN time), EVO link
Changed:
<
<
  • Online Data-Quality task-force: Wednesdays 10:00 (CERN time) DataQuality section of Indico
>
>
 

Previous Trainings, etc.

Several old training slides are available. Please have a look at them as most information is still valid.
Line: 310 to 310
 Presenter_HistoryFile.png

  • A dialog window will open, choose the merged histogram file from Brunel or DaVinci
Changed:
<
<
  • The Pages relevant for data-quality checks are in the DataQuality section of the list:
>
>
  • The Pages relevant for data-quality checks are in the LHCbInternal.DataQuality section of the list:
  Presenter_OfflineDQPages.png
Line: 504 to 504
 
  • Trackless ring radii and photon yield - Brunel:
    Presenter_Brunel_TracklessRings.png
Changed:
<
<
>
>
  PIDMonitoring_DStar.png
Changed:
<
<
>
>
  PIDMonitoring_JPsi.png

  • UKL1 with truncated data:

Revision 482010-08-03 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 58 to 58
 The status of the reconstruction of the latest runs (Express and Full stream), as well as the re-processing or stripping, etc can be monitored from the Production Monitoring Dirac page.

Some remarks:

Added:
>
>
  • You need to be logged into the PCs in the Offline Control Room to be able to connect to the database. The machines are called pclbocr0N with 0<n<5
 
  • The instructions for the general LHCb DQ shifter can be found here: Shift Instructions. They include the instructions how to merge histograms (which should be done by the general DQ shifter) and where the relevant histogram files can be found.
  • We don't expect any quick changes, hence it should be sufficient to look only at high-statistics runs unless there are indications of potential issues (e.g. errors from the online monitoring in CAMERA, "odd" features in the online Presenter pages, etc). Low statistics runs will probably not allow much definite statements....
  • The Express stream is currently being validated, i.e. it is quite likely that this part is not yet fully operational
Line: 181 to 182
 files by the central DQ shifter. Alternatively, use the hadd tool provided by ROOT and merge the histograms yourself. Newly downloaded histogram files are announced on =lhcb-dataquality-shifters@cern.ch =.
Changed:
<
<
To start the Presenter (e.g. on lxplus) do the following:
>
>
To start the Presenter (e.g. on the PCs in the offline control room) do the following:
  SetupProject Online

Revision 472010-07-12 - StephenWotton

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 245 to 245
 Presenter_HPDnHIt1DReference.png

UKL1 with truncated events

Changed:
<
<
The UKL1 boards truncate events if the occupancy gets too hight. This means that for the Ingress (and all following in this event) of the UKL1, the actual data is discarded (while the header information in the data is retained). In normal running conditions, this should not happen. If the monitoring plot shows any entry, make an entry (with screen-shot) to the eLog, note the machine running condition (e.g. MD, injection, physics data taking) and send an email to the RICH Data-Quality mailing list.
>
>
The UKL1 boards truncate events if the occupancy gets too high in order to keep the multi-event packet (MEP) below the maximum allowed size required by the readout. The part of the RICH event data that is handled by the affected L1 board may be either partially or wholly truncated. This means that data corresponding to blocks of individual HPDs are dropped while the HPD header information in the data is retained. Once truncation is activated for an event, all remaining data for that event and for any events following in the MEP are discarded for the affected L1 board.

In normal running conditions, this is expected to happen only sporadically when there is a burst of pathologically large events. During injection, however, it appears to be rather common. If the monitoring plot shows any entry, make an entry (with screen-shot) to the eLog, note the machine running condition (e.g. MD, injection, physics data taking) and send an email to the RICH Data-Quality mailing list.

 UKL1TruncatedData.png

HPD Efficiency

Revision 462010-07-11 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 244 to 244
 This 1D plot contains the same information and shows the number of hits (from the fast moving average) per HPD. The 1D representation has been added as it is easier to compare to a reference plot. The HPDs are arranged as columnNr*NrOfColums+NrOfHPDInColum. Presenter_HPDnHIt1DReference.png
Added:
>
>

UKL1 with truncated events

The UKL1 boards truncate events if the occupancy gets too hight. This means that for the Ingress (and all following in this event) of the UKL1, the actual data is discarded (while the header information in the data is retained). In normal running conditions, this should not happen. If the monitoring plot shows any entry, make an entry (with screen-shot) to the eLog, note the machine running condition (e.g. MD, injection, physics data taking) and send an email to the RICH Data-Quality mailing list. UKL1TruncatedData.png
 

HPD Efficiency

During the long abort gap between the bunch trains the 4 corner pixels of the HPD silicon chip is activated. This special data is recorded and analysed on the Calibration Farm. Ideally, each pixel activated should be seen in the monitoring process. One might
Line: 502 to 506
 
Added:
>
>
  • UKL1 with truncated data:
    UKL1TruncatedData.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 527 to 534
 
META FILEATTACHMENT attachment="Presenter_Brunel_TracklessRings.png" attr="" comment="Trackless ring radii and photon yield - Brunel" date="1274202198" name="Presenter_Brunel_TracklessRings.png" path="Presenter_Brunel_TracklessRings.png" size="153258" stream="Presenter_Brunel_TracklessRings.png" tmpFilename="/usr/tmp/CGItemp28907" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="PIDMonitoring_DStar.png" attr="" comment="PID Offline DataQuality D*->D pi" date="1277119007" name="PIDMonitoring_DStar.png" path="PIDMonitoring_DStar.png" size="159807" stream="PIDMonitoring_DStar.png" tmpFilename="/usr/tmp/CGItemp40690" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="PIDMonitoring_JPsi.png" attr="" comment="PID Offline DataQuality J/psi -> mu mu" date="1277119031" name="PIDMonitoring_JPsi.png" path="PIDMonitoring_JPsi.png" size="141909" stream="PIDMonitoring_JPsi.png" tmpFilename="/usr/tmp/CGItemp40456" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="UKL1TruncatedData.png" attr="" comment="UKL1 with truncated data" date="1278842178" name="UKL1TruncatedData.png" path="UKL1TruncatedData.png" size="123557" stream="UKL1TruncatedData.png" tmpFilename="/usr/tmp/CGItemp46370" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 452010-06-25 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 48 to 48
 
    • Regularly look at the various online Presenter pages
    • Keep an eye on the messages in Camera. During a normal run only (green) information messages should appear. Occasionally some (yellow) warning messages could occour, however, they should not persist. No (red) error messages should be on the screen.
  • Keep an eye on the =MonitoringMon= and check that the RichDAQMon and RichRingMon keep analysing events
Added:
>
>
  • If necessary, look at a specific run Checking the output of the online monitoring. For example, this should be done for a run taken in unusual conditions (e.g. high number of average collisions) or when a specific run is suspected to be problematic (several disabled HPDs, etc)
 

Offline checks

This part is based on the Brunel on DaVinci histograms obtained from the reconstruction of the raw data ("production"). An email should be automatically sent to the mailing list lhcb-dataquality-shifters when new histograms are available. The following should be done for both the FULL and the Express stream:
  • If not already done by the central DQ shifter, merge the Brunel and DaVinci histograms from the individual reconstruction jobs into one file with the full statistics (place them in your area to avoid confusion)
  • Look at the provided Presenter pages (for the offline DQ part)
  • Run the global alignment monitor
Added:
>
>
The status of the reconstruction of the latest runs (Express and Full stream), as well as the re-processing or stripping, etc can be monitored from the Production Monitoring Dirac page.
  Some remarks:
  • The instructions for the general LHCb DQ shifter can be found here: Shift Instructions. They include the instructions how to merge histograms (which should be done by the general DQ shifter) and where the relevant histogram files can be found.
Line: 139 to 141
 
Added:
>
>
 

CAMERA

The CAMERA error reporting tool is used to display all information gathered by the online monitoring. The user-interface showing these messages can be started via startCameraGui.
Line: 258 to 262
  Presenter_OnlineBrunel_Alignment.png
Added:
>
>

Checking the Online-Monitoring plots offline for a specific run

All histograms produced by the online monitoring are saved which allows to check the output e.g. for a specific run. The histograms are saved to /hist/SaveSets which is accessible from the plus cluster in IP8. Below this directory, the structure is organised by

  • year / partition / Monitoring-Task / Month / Day
  • ByRun / Monitoring - Task / run-number (1st digit) / run-number (2nd digit)

where again the RICH tasks are RichDAQMon, RichRingMon and RichCalibMon.

The histograms are saved at regular intervals (currently every 10 minutes) which allows to look at a specific part of the run. If you want to look at the whole run, the following command is helpful (e.g. to look at run 74286 for the trackless rings)

cd /hist/Savesets/2010/LHCb/RichRingMon
hadd ~/MergedHistos_TracklessRings_run74286.root `find . -name RichRingMon*74286*.root`
where
  • cd will bring you to the directory containing all histograms for the trackless ring monitor (if you know the day when the run was taken this will shorten the search for all files)
  • hadd is from the ROOT package and merges a set of files. The syntax is: hadd output.root list-of-input.root
  • find will start from the current directory (.) and return a list of all files matching the search criteria.
  • note the special quotation marks around the find command which returns the output of the command in a way that it can be used as input to hadd
You can then look at the merged histograms in the same way as the Offline DQ pages described below. Note that you need to load separate files if you want to look at the output of the trackless ring-finder, the low-level checks (e.g. hit-maps and disabled HPDs) or the HPD efficiency (measured by the calibration farm).
 

Offline Data-Quality pages

The histograms from the reconstruction (Brunel and DaVinci) should already have been downloaded by the central DQ shifter as detailed in the Offline DQ Procedures. All files should be below /afs/cern.ch/lhcb/group/dataquality/ROOT/Collision10 organised by

Revision 442010-06-23 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 137 to 137
 
  • HistogramDB. For completeness - it is unlikely you will need to edit the display properties of any histogram. However, here is where you can...
Added:
>
>
 

CAMERA

The CAMERA error reporting tool is used to display all information gathered by the online monitoring. The user-interface showing these messages can be started via startCameraGui.

Revision 432010-06-21 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 313 to 313
 Presenter_PID_Lambda.png

RICH Data-Quality Page 7: PID Monitoring with D* (DaVinci)

Added:
>
>
PIDMonitoring_DStar.png
 

RICH Data-Quality Page 8: PID Monitoring with J/psi (DaVinci)

Added:
>
>
PIDMonitoring_JPsi.png
 

Alignment monitoring (offline)

Line: 464 to 467
 
  • Trackless ring radii and photon yield - Brunel:
    Presenter_Brunel_TracklessRings.png
Added:
>
>

 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 487 to 496
 
META FILEATTACHMENT attachment="Presenter_PID_Lambda.png" attr="" comment="Lambda PID monitoring plot, express stream run 71487" date="1274201819" name="Presenter_PID_Lambda.png" path="Presenter_PID_Lambda.png" size="156645" stream="Presenter_PID_Lambda.png" tmpFilename="/usr/tmp/CGItemp29168" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_PID_KShort.png" attr="" comment="Ks PID monitoring plot, express stream run 71487" date="1274201848" name="Presenter_PID_KShort.png" path="Presenter_PID_KShort.png" size="155215" stream="Presenter_PID_KShort.png" tmpFilename="/usr/tmp/CGItemp29025" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_Brunel_TracklessRings.png" attr="" comment="Trackless ring radii and photon yield - Brunel" date="1274202198" name="Presenter_Brunel_TracklessRings.png" path="Presenter_Brunel_TracklessRings.png" size="153258" stream="Presenter_Brunel_TracklessRings.png" tmpFilename="/usr/tmp/CGItemp28907" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="PIDMonitoring_DStar.png" attr="" comment="PID Offline DataQuality D*->D pi" date="1277119007" name="PIDMonitoring_DStar.png" path="PIDMonitoring_DStar.png" size="159807" stream="PIDMonitoring_DStar.png" tmpFilename="/usr/tmp/CGItemp40690" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="PIDMonitoring_JPsi.png" attr="" comment="PID Offline DataQuality J/psi -> mu mu" date="1277119031" name="PIDMonitoring_JPsi.png" path="PIDMonitoring_JPsi.png" size="141909" stream="PIDMonitoring_JPsi.png" tmpFilename="/usr/tmp/CGItemp40456" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 422010-06-17 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 16 to 16
 

Before you start

  • Subscribe to the relevant mailing lists
  • Make sure you're aware of all meetings detailed below
Added:
>
>
  • You need a valid Grid certificate to access the book-keeping database
 
Changed:
<
<
  • make sure that you execute the script /group/rich/scripts/rich_login.sh in your login script on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser
>
>
  • make sure that you execute the script /group/rich/sw/scripts/setup.sh in your login script (e.g. add the line . /group/rich/sw/scripts/setup.sh to your ~/.bashrc) on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser
 

Duties

Line: 46 to 47
 
  • Log into the online systems at IP8 and keep a Presenter and CAMERA window open
    • Regularly look at the various online Presenter pages
    • Keep an eye on the messages in Camera. During a normal run only (green) information messages should appear. Occasionally some (yellow) warning messages could occour, however, they should not persist. No (red) error messages should be on the screen.
Changed:
<
<
  • Keep an eye on the MonitoringMon and check that the RichDAQMon and RichRingMon keep analysing events
>
>
  • Keep an eye on the =MonitoringMon= and check that the RichDAQMon and RichRingMon keep analysing events
 

Offline checks

This part is based on the Brunel on DaVinci histograms obtained from the reconstruction of the raw data ("production"). An email should be automatically sent to the mailing list lhcb-dataquality-shifters when new histograms are available. The following should be done for both the FULL and the Express stream:
Line: 55 to 56
 
  • Run the global alignment monitor

Some remarks:

Added:
>
>
  • The instructions for the general LHCb DQ shifter can be found here: Shift Instructions. They include the instructions how to merge histograms (which should be done by the general DQ shifter) and where the relevant histogram files can be found.
 
  • We don't expect any quick changes, hence it should be sufficient to look only at high-statistics runs unless there are indications of potential issues (e.g. errors from the online monitoring in CAMERA, "odd" features in the online Presenter pages, etc). Low statistics runs will probably not allow much definite statements....
  • The Express stream is currently being validated, i.e. it is quite likely that this part is not yet fully operational
  • The instructions will evolve with time and we need to gain experience with the detector behaviour in realistic running conditions.
Line: 149 to 151
 

In case of issues with CAMERA

If you don't see any info message coming to camera in more than one minute do the following checks:
Changed:
<
<
  • Check in MonitoringMon that the RICH monitoring algorithms are running and processing data.
>
>
  • Check in MonitoringMon that the RICH monitoring algorithms are running and processing data.
 
  • Check in the logviewer whether or not you get messages like:
    • May27-235252[WARN] mona0806: Gaudi.exe(LHCb_MONA0806_RichDAQMon_00): CameraTool: Could not connect to any camera server!  -> Aborting message 'CentralTrigger4NHitMonitorLHCb/1/Initialized
    • May27-235252[WARN] mona0806: Gaudi.exe(LHCb_MONA0806_RichDAQMon_00): CameraTool: Above message repeated 5 > times. Aborting further messaging of this type. An issue with the PC hist01 is possible.
Line: 355 to 357
 

Log files

The log files preserving the messages shown in the error logger are written to /clusterlogs/partitions/< partition >/daq where < partition > is the partition of interest such as LHCb or RICH
Added:
>
>

Useful hints

Get information about a specific run

kerzel@pchy 0 $ SetupProject LHCbDirac
kerzel@pchy 0 $ dirac-bookkeeping-run-informations 70768
Run  Informations: 
Run Start:                                         2010-04-26 17:56:00
Run End:                                           2010-04-26 17:57:00
  Configuration Name:                              VELO
  Configuration Version:                           NZS
  FillNumber:                                      0
  Data taking description:                         BeamOff-VeloOpen-MagOff
  Processing pass:                                 Real Data
  Stream:                                          [90000001]
  FullStat:                                       [9671]                                             Total:   9671
  Number of events:                               [9671]                                             Total:   9671
  Number of file:                                 [3]                                                Total:   3
  File size:                                      [2929765916]                                       Total:   2929765916
 

Per-event display of RICH hits

  • Can be done using Panoramix
  • Instructions from Thomas Ruf:

Revision 412010-06-16 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 30 to 30
 
  • Follow data-quality related issues for the RICH, contact experts if necessary, liaise with general LHCb DQ shifter
  • Attend the general DQ meeting at 2pm (CERN time, weekdays only)
Added:
>
>

If we're not running in "global"

The duties of the LHCb RICH Data-Quality piquet are aimed towards taking physics data, i.e. the RICH detectors are included in global running under the LHCb partition.
  • If the RICH detectors are in "local" mode, experts are usually testing or making dedicated measurements (e.g. ion feedback). In this case, not much needs to be done - but it helps to keep an eye on Camera and the Presenter just to make sure everything looks OK.
  • If the RICH detectors are in "global" mode (included in the LHCb partition) but there is no beam, the detectors are usually run to "exercise the system" and keep everything alive. Again, not much needs to be done in this case - but keep an eye on CAMERA and the Presenter to spot any issue which might occur as early as possible
 

Online checks

This part is aimed at assisting the RICH piquet by keeping an eye on the overall detector behaviour during data taking. These duties only need to be performed if the RICH detectors are running in "global", i.e. the LHCb partition.

Revision 402010-06-14 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 101 to 101
 Several old training slides are available. Please have a look at them as most information is still valid.
Added:
>
>
 

More detailed TWiki pages, web-links etc.

Revision 392010-06-11 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 94 to 94
  In this meeting the current plan for the day will be discussed by the Run Chief and the sub-detector experts. The News slides usually give a good overview of the plan for the LHC and LHCb for the day or longer term.
  • RICH Operations: Wednesdays, 10:35 (CERN time) in the Rich section of Indico. All operational aspects of the RICH detector, as well as longer term planning is discussed here.
  • RICH Software: Fridays 15:00 (CERN time) in the Rich section of Indico. All RICH aspects related to software issues are discussed (e.g. Data-Quality, alignment, reconstruction, ...)
Changed:
<
<
>
>
 
  • Online Data-Quality task-force: Wednesdays 10:00 (CERN time) DataQuality section of Indico

Previous Trainings, etc.

Revision 382010-06-07 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 24 to 24
 
  • make sure that you execute the script /group/rich/scripts/rich_login.sh in your login script on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser
Changed:
<
<

Duites

>
>

Duties

 

General

  • Follow data-quality related issues for the RICH, contact experts if necessary, liaise with general LHCb DQ shifter

Revision 372010-06-02 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 141 to 141
 CameraGui_WithRing.png

In case of issues with CAMERA

Changed:
<
<
>
>
If you don't see any info message coming to camera in more than one minute do the following checks:
  • Check in MonitoringMon that the RICH monitoring algorithms are running and processing data.
  • Check in the logviewer whether or not you get messages like:
    • May27-235252[WARN] mona0806: Gaudi.exe(LHCb_MONA0806_RichDAQMon_00): CameraTool: Could not connect to any camera server!  -> Aborting message 'CentralTrigger4NHitMonitorLHCb/1/Initialized
    • May27-235252[WARN] mona0806: Gaudi.exe(LHCb_MONA0806_RichDAQMon_00): CameraTool: Above message repeated 5 > times. Aborting further messaging of this type. An issue with the PC hist01 is possible.
  • Read the line at the very bottom left of the CAMERA Gui. It must show: Connected to hist01:45124 , / NOT Connected to . If instead it shows Connected to , / NOT Connected to: hist01:45124 the Gui lost the connection with the Server. Try starting another Gui.
  • If RICH monitoring algorithms are running and processing data, check that the PC hist01 is active by typing: ssh -X hist01. If the system hangs without giving back the shell prompt, it means that hist01 is not responding. hist01 is the PC on which the CAMERA servers physically run (together with many other tasks). It happened in the past that it crashed and it has been restarted by hand. CAMERA will be back as soon as hist01 is back, although you need to open a new CAMERA Gui when hist01 resurrect. To make sure the LHCb Online team knows about the unavailability of hist01, call the Online piquet (or the shift leader in case you don't get any answer from the first).
  • If RICH monitoring algorithms are running and processing data AND hist01 is up then send an email at nicola.mangiafave@gmail.com_NO_SPAM_ with the details of the checks previously made.
 

Presenter

Revision 362010-05-27 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 140 to 140
 The example below shows the GUI with an hitmap where two isolated rings have been identified by the trackless ring-finding algorithm. CameraGui_WithRing.png
Added:
>
>

In case of issues with CAMERA

 

Presenter

Revision 352010-05-19 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 26 to 26
 

Duites

Added:
>
>

General

  • Follow data-quality related issues for the RICH, contact experts if necessary, liaise with general LHCb DQ shifter
  • Attend the general DQ meeting at 2pm (CERN time, weekdays only)
 

Online checks

This part is aimed at assisting the RICH piquet by keeping an eye on the overall detector behaviour during data taking. These duties only need to be performed if the RICH detectors are running in "global", i.e. the LHCb partition.
Line: 90 to 94
  In this meeting the current plan for the day will be discussed by the Run Chief and the sub-detector experts. The News slides usually give a good overview of the plan for the LHC and LHCb for the day or longer term.
  • RICH Operations: Wednesdays, 10:35 (CERN time) in the Rich section of Indico. All operational aspects of the RICH detector, as well as longer term planning is discussed here.
  • RICH Software: Fridays 15:00 (CERN time) in the Rich section of Indico. All RICH aspects related to software issues are discussed (e.g. Data-Quality, alignment, reconstruction, ...)
Changed:
<
<
>
>
 

Previous Trainings, etc.

Several old training slides are available. Please have a look at them as most information is still valid.

Revision 342010-05-18 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 96 to 96
 

Previous Trainings, etc.

Several old training slides are available. Please have a look at them as most information is still valid.
Added:
>
>
 

More detailed TWiki pages, web-links etc.

Line: 276 to 277
 Presenter_RichDQ_Page2.png

RICH Data-Quality Page 3: Trackless rings (Brunel)

Changed:
<
<
Should look similar to the trackless ring-finding from online monitoring. (currently no plot due to a bug in the software configuration)
>
>
Presenter_Brunel_TracklessRings.png
 

RICH Data-Quality Page 4: Photon reconstruction with tracks (Brunel)

Line: 285 to 285
 

RICH Data-Quality Page 5: PID Monitoring with Ks0 (DaVinci)

Added:
>
>
Presenter_PID_KShort.png
 

RICH Data-Quality Page 6: PID Monitoring with Lambdas (DaVinci)

Added:
>
>
Presenter_PID_Lambda.png
 

RICH Data-Quality Page 7: PID Monitoring with D* (DaVinci)

Line: 410 to 412
  Presenter_RichDQPage4.png
/>
Added:
>
>
  • Lambda PID monitoring plot, express stream run 71487:
    Presenter_PID_Lambda.png

  • Ks PID monitoring plot, express stream run 71487:
    Presenter_PID_KShort.png

  • Trackless ring radii and photon yield - Brunel:
    Presenter_Brunel_TracklessRings.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 430 to 441
 
META FILEATTACHMENT attachment="Presenter_RichDQ_Page1.png" attr="" comment="Presenter: Rich DQ Page 1" date="1273160049" name="Presenter_RichDQ_Page1.png" path="Presenter_RichDQ_Page1.png" size="149978" stream="Presenter_RichDQ_Page1.png" tmpFilename="/usr/tmp/CGItemp31902" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RichDQ_Page2.png" attr="" comment="Presenter: Rich DQ Page 2" date="1273160074" name="Presenter_RichDQ_Page2.png" path="Presenter_RichDQ_Page2.png" size="128113" stream="Presenter_RichDQ_Page2.png" tmpFilename="/usr/tmp/CGItemp31836" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RichDQPage4.png" attr="" comment="Presenter: Rich DQ Page 4" date="1273160095" name="Presenter_RichDQPage4.png" path="Presenter_RichDQPage4.png" size="171761" stream="Presenter_RichDQPage4.png" tmpFilename="/usr/tmp/CGItemp31882" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Presenter_PID_Lambda.png" attr="" comment="Lambda PID monitoring plot, express stream run 71487" date="1274201819" name="Presenter_PID_Lambda.png" path="Presenter_PID_Lambda.png" size="156645" stream="Presenter_PID_Lambda.png" tmpFilename="/usr/tmp/CGItemp29168" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_PID_KShort.png" attr="" comment="Ks PID monitoring plot, express stream run 71487" date="1274201848" name="Presenter_PID_KShort.png" path="Presenter_PID_KShort.png" size="155215" stream="Presenter_PID_KShort.png" tmpFilename="/usr/tmp/CGItemp29025" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_Brunel_TracklessRings.png" attr="" comment="Trackless ring radii and photon yield - Brunel" date="1274202198" name="Presenter_Brunel_TracklessRings.png" path="Presenter_Brunel_TracklessRings.png" size="153258" stream="Presenter_Brunel_TracklessRings.png" tmpFilename="/usr/tmp/CGItemp28907" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 332010-05-10 - ChristopherRJones

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 16 to 16
 

Before you start

  • Subscribe to the relevant mailing lists
  • Make sure you're aware of all meetings detailed below
Changed:
<
<
  • Get accounts for the ShiftDB, eLogs, ticket- and Savannah systems, as well as the online cluster
  • If you're working from remove, set-up your ssh links and NX clients to log into the online systems
>
>
 

Revision 322010-05-08 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 53 to 53
 
  • Make an entry to the RICH eLog with as many details as possible (e.g. the warning messages from Camera, a screen-shot, etc).
  • Send an email to lhcb-rich-dataquality AT cern.ch and lhcb-rich-operations AT cern.ch
  • In case of a severe issue affecting the operations and on-going data-taking, try to contact the RICH piquet (e.g. when several HPDs are being disabled, an "odd" stripe-pattern appears in the hitmap displays, etc)
Added:
>
>
 

Mailing list

Subscribe to the mailing lists (... @cern.ch):

Revision 312010-05-07 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 24 to 24
 
  • make sure that you execute the script /group/rich/scripts/rich_login.sh in your login script on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser
Added:
>
>

Duites

Online checks

This part is aimed at assisting the RICH piquet by keeping an eye on the overall detector behaviour during data taking. These duties only need to be performed if the RICH detectors are running in "global", i.e. the LHCb partition. If the detectors are taken into "local" control (i.e. partitions RICH, RICH1 or RICH2) experts are usually working with them.

  • Familiarise yourself with the LHC(b) plans for the day by attending the daily run meeting or reading the minutes, looking at the entries in the General Shift eLog and the RICH eLog
  • Log into the online systems at IP8 and keep a Presenter and CAMERA window open
    • Regularly look at the various online Presenter pages
    • Keep an eye on the messages in Camera. During a normal run only (green) information messages should appear. Occasionally some (yellow) warning messages could occour, however, they should not persist. No (red) error messages should be on the screen.
  • Keep an eye on the MonitoringMon and check that the RichDAQMon and RichRingMon keep analysing events

Offline checks

This part is based on the Brunel on DaVinci histograms obtained from the reconstruction of the raw data ("production"). An email should be automatically sent to the mailing list lhcb-dataquality-shifters when new histograms are available. The following should be done for both the FULL and the Express stream:
  • If not already done by the central DQ shifter, merge the Brunel and DaVinci histograms from the individual reconstruction jobs into one file with the full statistics (place them in your area to avoid confusion)
  • Look at the provided Presenter pages (for the offline DQ part)
  • Run the global alignment monitor

Some remarks:

  • We don't expect any quick changes, hence it should be sufficient to look only at high-statistics runs unless there are indications of potential issues (e.g. errors from the online monitoring in CAMERA, "odd" features in the online Presenter pages, etc). Low statistics runs will probably not allow much definite statements....
  • The Express stream is currently being validated, i.e. it is quite likely that this part is not yet fully operational
  • The instructions will evolve with time and we need to gain experience with the detector behaviour in realistic running conditions.

In case of issues:

  • Make an entry to the RICH eLog with as many details as possible (e.g. the warning messages from Camera, a screen-shot, etc).
  • Send an email to lhcb-rich-dataquality AT cern.ch and lhcb-rich-operations AT cern.ch
  • In case of a severe issue affecting the operations and on-going data-taking, try to contact the RICH piquet (e.g. when several HPDs are being disabled, an "odd" stripe-pattern appears in the hitmap displays, etc)
 

Mailing list

Subscribe to the mailing lists (... @cern.ch):
  • lhcb-rich-dataquality
Line: 194 to 224
  TestpatternEffi_run70681.png
Changed:
<
<

Alignment monitoring

>
>

Alignment monitoring (online)

 The alignment of each of the 4 HPD panels monitored online using OnlineBrunel. The page shown below shows the output of the monitoring - in the next step, automated fits and alerts will be added.
Added:
>
>
(N.B. This plot is based on a n old version of the data-base which does not reflect the latest alignment)
 Presenter_OnlineBrunel_Alignment.png

Offline Data-Quality pages

Line: 259 to 291
 

RICH Data-Quality Page 8: PID Monitoring with J/psi (DaVinci)

Changed:
<
<

Alignment monitoring

>
>

Alignment monitoring (offline)

  The procedure to verify the global RICH alignment is described in detail in the Alignment TWiki The global alignment should be verified regularly for both RICH1 and RICH2. We don't expect the alignment that the alignment will change quickly or often. Therefore it should not be necessary to verify it for each run. Furthermore, analysing low statistics run will probably not be beneficial. As a first step (until we have more experience) it should be sufficient to analyse a high statistics run every day or every other day.
Line: 268 to 300
 
  • Identify a high-statistics run to analyse
  • If not already available, merge all Brunel histogram files from this run using hadd (from the ROOT package) and place it into your area
  • Follow the TWiki to download and run the latest version of the alignment check for both RICH1 and RICH2
Changed:
<
<
  • If either of the fit parameters SinAmp or CosAmp exceeds 0.001 rad
>
>
  • If either of the fit parameters SinAmp or CosAmp (significantly) exceeds 0.001 rad, do the following:
    • post a comment to the RICH eLog
    • send an email to the email lists lhcb-rich-dataquality AT cern.ch and lhcb-rich-operations AT cern.ch
    • add an entry to the Online ProblemDB
 
Line: 318 to 353
 

-- UlrichKerzel - 11 Jul 2008

Added:
>
>
<!-----
 
  • Presenter page: HPD hit pull:
    Presenter_HPDHitPull.png
Line: 371 to 407
 
  • Presenter: Rich DQ Page 4:
    Presenter_RichDQPage4.png
Added:
>
>

/>
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 302010-05-07 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 259 to 259
 

RICH Data-Quality Page 8: PID Monitoring with J/psi (DaVinci)

Added:
>
>

Alignment monitoring

 
Added:
>
>
The procedure to verify the global RICH alignment is described in detail in the Alignment TWiki The global alignment should be verified regularly for both RICH1 and RICH2. We don't expect the alignment that the alignment will change quickly or often. Therefore it should not be necessary to verify it for each run. Furthermore, analysing low statistics run will probably not be beneficial. As a first step (until we have more experience) it should be sufficient to analyse a high statistics run every day or every other day.
 
Changed:
<
<
>
>
Follow the following steps:
  • Identify a high-statistics run to analyse
  • If not already available, merge all Brunel histogram files from this run using hadd (from the ROOT package) and place it into your area
  • Follow the TWiki to download and run the latest version of the alignment check for both RICH1 and RICH2
  • If either of the fit parameters SinAmp or CosAmp exceeds 0.001 rad
 

Revision 292010-05-07 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 30 to 30
 
  • lhcb-rich-operations
  • lhcb-rich-software
  • lhcb-data-quality
Added:
>
>
  • lhcb-dataquality-shifters
 
  • lhcb-online-users
  • lhcb-online
  • lhcb-run-news
Line: 115 to 116
 

For Offline checks

Follow Step 5 of the offline-DQ procedures.
Changed:
<
<
N.B. The current Twiki is a bit out of date ....
>
>
N.B. Currently the histogram files from the reconstruction jobs (Brunel and DaVinci) are downloaded and merged manually by the central DQ shifter. Hence the RICH DQ Piquet can only act once pointed to the relevant files by the central DQ shifter. Alternatively, use the hadd tool provided by ROOT and merge the histograms yourself. Newly downloaded histogram files are announced on =lhcb-dataquality-shifters@cern.ch =.
 
Changed:
<
<
E.g. do the following
>
>
To start the Presenter (e.g. on lxplus) do the following:
  SetupProject Online
Line: 217 to 221
  Presenter_OfflineDQPages.png
Changed:
<
<
The screen-shots below show what the pages look like for a typical run
>
>
The screen-shots below show what the pages look like for a typical run for the Brunel based histograms. The pages based on DaVinci will be added soon (as there is currently a new version being deployed).
 
Changed:
<
<
N.B. Reference plots are currently being prepared and the pages will likely be updated in this early phase of running.
>
>
The same procedure can of course be used for the individual reconstruction jobs (i.e. prior to the histogram merging) with the caveat that the files will only contain a fraction of the events recorded in the run.

Note:

  • As histograms are booked on demand, some plots may not be available due to low statistics. In this case the message Error missing source... appears in the histogram title.
  • Reference plots are currently being prepared and the pages will likely be updated in this early phase of running.
 

Revision 282010-05-07 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 18 to 18
 
  • Make sure you're aware of all meetings detailed below
  • Get accounts for the ShiftDB, eLogs, ticket- and Savannah systems, as well as the online cluster
  • If you're working from remove, set-up your ssh links and NX clients to log into the online systems
Changed:
<
<
  • Familiarise yourself with the Presenter, Camera and how to run Panoptes offline on raw data in IP8
>
>
 
  • make sure that you execute the script /group/rich/scripts/rich_login.sh in your login script on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser

Mailing list

Revision 272010-05-06 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 110 to 110
 in the online system and the Presenter can be started with startOfficialMonitor. Normally, this alias points to the official script, however, at times it may be better to use an updated version...
Changed:
<
<

Offline in the offline control room

>
>

For Offline checks

 Follow Step 5 of the offline-DQ procedures.
Deleted:
<
<
 N.B. The current Twiki is a bit out of date ....
Added:
>
>
E.g. do the following

SetupProject Online

presenter.exe -C /afs/cern.ch/lhcb/group/dataquality/ROOT/presenter_1.cfg &

and ignore the warning message about DIM_DNS_NODE.

 N.B. There is no NX server available offline at the moment. To log in from remote, use the procedures to log into the online cluster and then log back into lxplus

Reference plots

Line: 191 to 201
 
  • processing, e.g. Real_Data_RecoStripping-01
  • stream, e.g. 90000000
Added:
>
>
The central DQ shifter will merge all histogram files into one file covering the whole run. Once this is done, the Presenter pages can be looked at in the following way:

  • If not already done, change the Presenter to History mode from Tools -> History mode.
  • Then use the drop-down list to select a histogram file to investigate:

Presenter_HistoryFile.png

  • A dialog window will open, choose the merged histogram file from Brunel or DaVinci
  • The Pages relevant for data-quality checks are in the DataQuality section of the list:

Presenter_OfflineDQPages.png

The screen-shots below show what the pages look like for a typical run

N.B. Reference plots are currently being prepared and the pages will likely be updated in this early phase of running.

RICH Data-Quality Page 1: Occupancy and Decoding (Brunel)

Presenter_RichDQ_Page1.png

RICH Data-Quality Page 2: Long tracks selection efficiency (Brunel)

Presenter_RichDQ_Page2.png

RICH Data-Quality Page 3: Trackless rings (Brunel)

Should look similar to the trackless ring-finding from online monitoring. (currently no plot due to a bug in the software configuration)

RICH Data-Quality Page 4: Photon reconstruction with tracks (Brunel)

Presenter_RichDQPage4.png

RICH Data-Quality Page 5: PID Monitoring with Ks0 (DaVinci)

RICH Data-Quality Page 6: PID Monitoring with Lambdas (DaVinci)

RICH Data-Quality Page 7: PID Monitoring with D* (DaVinci)

RICH Data-Quality Page 8: PID Monitoring with J/psi (DaVinci)

 

Tools in the online environment

Several tools exist to check that the online monitoring is working
Line: 276 to 337
 
  • RICH eLog:
    eLog_Rich.png
Added:
>
>
  • Presenter: History file selection dialog:
    Presenter_HistoryFile.png

  • Presenter: Offline DQ page selection:
    Presenter_OfflineDQPages.png

  • Presenter: Rich DQ Page 1:
    Presenter_RichDQ_Page1.png

  • Presenter: Rich DQ Page 2:
    Presenter_RichDQ_Page2.png

  • Presenter: Rich DQ Page 4:
    Presenter_RichDQPage4.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 291 to 367
 
META FILEATTACHMENT attachment="Presenter_DisabledHPDs.png" attr="" comment="Presenter page indicating disabled HPDs" date="1272884747" name="Presenter_DisabledHPDs.png" path="Presenter_DisabledHPDs.png" size="107363" stream="Presenter_DisabledHPDs.png" tmpFilename="/usr/tmp/CGItemp31540" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RefIcon.png" attr="h" comment="Icon for reference plots in presenter" date="1272901099" name="Presenter_RefIcon.png" path="Presenter_RefIcon.png" size="6332" stream="Presenter_RefIcon.png" tmpFilename="/usr/tmp/CGItemp31971" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="eLog_Rich.png" attr="" comment="RICH eLog" date="1272968103" name="eLog_Rich.png" path="eLog_Rich.png" size="318433" stream="eLog_Rich.png" tmpFilename="/usr/tmp/CGItemp32243" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Presenter_HistoryFile.png" attr="" comment="Presenter: History file selection dialog" date="1273155216" name="Presenter_HistoryFile.png" path="Presenter_HistoryFile.png" size="8694" stream="Presenter_HistoryFile.png" tmpFilename="/usr/tmp/CGItemp31618" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_OfflineDQPages.png" attr="" comment="Presenter: Offline DQ page selection" date="1273156723" name="Presenter_OfflineDQPages.png" path="Presenter_OfflineDQPages.png" size="28096" stream="Presenter_OfflineDQPages.png" tmpFilename="/usr/tmp/CGItemp31803" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RichDQ_Page1.png" attr="" comment="Presenter: Rich DQ Page 1" date="1273160049" name="Presenter_RichDQ_Page1.png" path="Presenter_RichDQ_Page1.png" size="149978" stream="Presenter_RichDQ_Page1.png" tmpFilename="/usr/tmp/CGItemp31902" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RichDQ_Page2.png" attr="" comment="Presenter: Rich DQ Page 2" date="1273160074" name="Presenter_RichDQ_Page2.png" path="Presenter_RichDQ_Page2.png" size="128113" stream="Presenter_RichDQ_Page2.png" tmpFilename="/usr/tmp/CGItemp31836" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RichDQPage4.png" attr="" comment="Presenter: Rich DQ Page 4" date="1273160095" name="Presenter_RichDQPage4.png" path="Presenter_RichDQPage4.png" size="171761" stream="Presenter_RichDQPage4.png" tmpFilename="/usr/tmp/CGItemp31882" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 262010-05-04 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 44 to 44
 

ELog

Several electronic log-books are used to keep track of any information relevant to operational issues
Added:
>
>
eLog_Rich.png
 
Line: 270 to 273
 
  • Icon for reference plots in presenter:
    Presenter_RefIcon.png
Added:
>
>
  • RICH eLog:
    eLog_Rich.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 284 to 290
 
META FILEATTACHMENT attachment="ErrorLogger.png" attr="" comment="Error logger" date="1272878269" name="ErrorLogger.png" path="ErrorLogger.png" size="108741" stream="ErrorLogger.png" tmpFilename="/usr/tmp/CGItemp31768" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_DisabledHPDs.png" attr="" comment="Presenter page indicating disabled HPDs" date="1272884747" name="Presenter_DisabledHPDs.png" path="Presenter_DisabledHPDs.png" size="107363" stream="Presenter_DisabledHPDs.png" tmpFilename="/usr/tmp/CGItemp31540" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_RefIcon.png" attr="h" comment="Icon for reference plots in presenter" date="1272901099" name="Presenter_RefIcon.png" path="Presenter_RefIcon.png" size="6332" stream="Presenter_RefIcon.png" tmpFilename="/usr/tmp/CGItemp31971" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="eLog_Rich.png" attr="" comment="RICH eLog" date="1272968103" name="eLog_Rich.png" path="eLog_Rich.png" size="318433" stream="eLog_Rich.png" tmpFilename="/usr/tmp/CGItemp32243" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 252010-05-03 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 13 to 13
 

As a RICH DQ piquet

Changed:
<
<

Preparations

>
>

Before you start

 
  • Subscribe to the relevant mailing lists
Changed:
<
<
  • Get accounts for the ShiftDB, eLogs, ticket- and Savannah systems
>
>
  • Make sure you're aware of all meetings detailed below
  • Get accounts for the ShiftDB, eLogs, ticket- and Savannah systems, as well as the online cluster
 
  • If you're working from remove, set-up your ssh links and NX clients to log into the online systems
  • Familiarise yourself with the Presenter, Camera and how to run Panoptes offline on raw data in IP8
  • make sure that you execute the script /group/rich/scripts/rich_login.sh in your login script on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser
Line: 47 to 48
 

Meetings

Changed:
<
<
  • Daily run meeting at IP8, 9am (CERN time)
  • RICH Operations: Wednesdays, 10:35 (CERN time)
>
>
  • Daily run meeting at IP8, 9am (CERN time) In this meeting the current plan for the day will be discussed by the Run Chief and the sub-detector experts. The News slides usually give a good overview of the plan for the LHC and LHCb for the day or longer term.
  • RICH Operations: Wednesdays, 10:35 (CERN time) in the Rich section of Indico. All operational aspects of the RICH detector, as well as longer term planning is discussed here.
  • RICH Software: Fridays 15:00 (CERN time) in the Rich section of Indico. All RICH aspects related to software issues are discussed (e.g. Data-Quality, alignment, reconstruction, ...)
  • LHCb Data-Quality meeting
  • Online Data-Quality task-force: A new task force lead by O. Callot. More details soon.
 

Previous Trainings, etc.

Several old training slides are available. Please have a look at them as most information is still valid.
Line: 74 to 79
 
Changed:
<
<
  • Detailed overview of the [https://lbtwiki.cern.ch/bin/view/Online/MonitoringExpertGuide][Monitoring for Experts]]
>
>
 
  • When working from remote, logging into the online systems can be very slow as the X protocol forwarding e.g. the Presenter or Camera window is very slow. Follow the instructions at Log into online systems to use the NX client. The NX client software can be obtained from NoMachine
Line: 94 to 99
 

Presenter

Added:
>
>

Starting the Presenter

Online in the control room

 The Presenter is the official LHCb tool to look at histograms produced by the various online and offline monitoring algorithms.
Changed:
<
<
In the online system, the Presenter can be started with startOfficialMonitor
>
>
The official script to start the presenter is /group/online/presenter/run_presenter.sh. We have provided an alias to this in the online system and the Presenter can be started with startOfficialMonitor. Normally, this alias points to the official script, however, at times it may be better to use an updated version...

Offline in the offline control room

Follow Step 5 of the offline-DQ procedures.

N.B. The current Twiki is a bit out of date ....

N.B. There is no NX server available offline at the moment. To log in from remote, use the procedures to log into the online cluster and then log back into lxplus

 
Changed:
<
<

DataManager pages

>
>

Reference plots

Several of the Presenter pages can be shown together with a reference plot. This allows some judgement whether the current situation is regarded as "normal". The reference plots can be switched on by clicking on the icon Presenter_RefIcon.png in the top right part of the Presenter (if available). N.B. As we're in the early phase of the start-up of the LHCb experiment, we still need some experience what should be regarded as "good" or "bad". Hence the reference plots are taken from some run at 3.5 TeV which didn't show any obvious "oddities" - but judgement should be taken with a grain of salt. Futhermore, the presenter doesn't currently support different running conditions (yet), e.g. as the reference plot is taken from a 3.5 TeV run, the average hit occupancy might differ at a different beam energy or lower/higher beam intensity.

Online in IP8

The following pages are used in the control room (or remotely) to monitor the current state of the RICH detectors.

DataManager pages

 Several pages are (being) added to the Shift section of the list of available Presenter pages. These pages are mainly for the central Data-Manager shift crew but should also be monitored on a regular basis by the RICH crew.

The two screen-shots below show the overview pages for RICH1 and RICH2. In nominal conditions both pages should look

Line: 117 to 143
 Presenter_ShiftRich2.png
Changed:
<
<

Disabled HPDs

>
>

Disabled HPDs

 In order to prevent any loss time in global data-taking, individual HPDs becoming "upset" (e.g. because of synchronisation issues or other hick-ups) can be disabled by the online monitoring. These "upset" HPDs may e.g. show a large number of HPD pixels permanently on or the data recorded by them may be inconsistent with the rest of the event, etc. A detailed warning message is sent to CAMERA why a particular HPD has been disabled and the location of these HPDs is shown in a dedicated page in the Presenter. All 4 histograms (one per detector panel) are empty in normal conditions as shown in the example below.

Presenter_DisabledHPDs.png

Changed:
<
<

Trackless Rings

>
>

Trackless Rings

 A trackless ring finding algorithm runs on the Monitoring Farm based on an Elastic Neural Network. This approach does not rely on input of any other sub-detector and gives a rough performance estimate of the RICH. The presenter page shows the distribution of ring radii (sensitive to refractive index, and hence to temperature and pressure) and the photon yield for rings found in the gas radiators of RICH1 and RICH2.

(N.B. the second peak in the radii distribution in the top left plot is likely an artifact from the cut off of the maximum allowed ring size)

Presenter_TracklessRings_RefOverlay.png

Changed:
<
<

Hits per HPD

>
>

Hits per HPD

 Several pages are available in the presenter to cross-check the current occupancy.

This page shows the pull of the expected vs actual number of hits per HPD in each RICH panel. The expected number of hits is calculated from a slowly moving average (over many events) whereas the actual number of hits is given by a fast moving average (over few events). Any large outliers indicate that an HPD does not see the expected number of events consistent with the current luminosity.

Line: 139 to 165
 This 1D plot contains the same information and shows the number of hits (from the fast moving average) per HPD. The 1D representation has been added as it is easier to compare to a reference plot. The HPDs are arranged as columnNr*NrOfColums+NrOfHPDInColum. Presenter_HPDnHIt1DReference.png
Changed:
<
<

HPD Efficiency

>
>

HPD Efficiency

 During the long abort gap between the bunch trains the 4 corner pixels of the HPD silicon chip is activated. This special data is recorded and analysed on the Calibration Farm. Ideally, each pixel activated should be seen in the monitoring process. One might expect that not each pixel is read out with 100% efficiency at all times - but in general the HPD efficiency should be close to 100%.
Line: 149 to 175
  TestpatternEffi_run70681.png
Changed:
<
<

Alignment monitoring

>
>

Alignment monitoring

 The alignment of each of the 4 HPD panels monitored online using OnlineBrunel. The page shown below shows the output of the monitoring - in the next step, automated fits and alerts will be added.

Presenter_OnlineBrunel_Alignment.png

Added:
>
>

Offline Data-Quality pages

The histograms from the reconstruction (Brunel and DaVinci) should already have been downloaded by the central DQ shifter as detailed in the Offline DQ Procedures. All files should be below /afs/cern.ch/lhcb/group/dataquality/ROOT/Collision10 organised by
  • run type, e.g. Beam3500GeV-VeloClosed-MagDown
  • run number, e.g. 70732
  • processing, e.g. Real_Data_RecoStripping-01
  • stream, e.g. 90000000
 

Tools in the online environment

Several tools exist to check that the online monitoring is working
Line: 234 to 267
 
  • Presenter page indicating disabled HPDs:
    Presenter_DisabledHPDs.png
Added:
>
>
  • Icon for reference plots in presenter:
    Presenter_RefIcon.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 247 to 283
 
META FILEATTACHMENT attachment="Presenter_ShiftRich2.png" attr="" comment="Presenter page: Shift manager page for Rich2" date="1272877265" name="Presenter_ShiftRich2.png" path="Presenter_ShiftRich2.png" size="205232" stream="Presenter_ShiftRich2.png" tmpFilename="/usr/tmp/CGItemp31609" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="ErrorLogger.png" attr="" comment="Error logger" date="1272878269" name="ErrorLogger.png" path="ErrorLogger.png" size="108741" stream="ErrorLogger.png" tmpFilename="/usr/tmp/CGItemp31768" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_DisabledHPDs.png" attr="" comment="Presenter page indicating disabled HPDs" date="1272884747" name="Presenter_DisabledHPDs.png" path="Presenter_DisabledHPDs.png" size="107363" stream="Presenter_DisabledHPDs.png" tmpFilename="/usr/tmp/CGItemp31540" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Presenter_RefIcon.png" attr="h" comment="Icon for reference plots in presenter" date="1272901099" name="Presenter_RefIcon.png" path="Presenter_RefIcon.png" size="6332" stream="Presenter_RefIcon.png" tmpFilename="/usr/tmp/CGItemp31971" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 242010-05-03 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 81 to 81
 
  • HistogramDB. For completeness - it is unlikely you will need to edit the display properties of any histogram. However, here is where you can...

CAMERA

Changed:
<
<
The CAMERA error reporting tool is used to display all information gathered by the online monitoring. Information is shown in green
>
>
The CAMERA error reporting tool is used to display all information gathered by the online monitoring. The user-interface showing these messages can be started via startCameraGui. Messages showing some detailed information are presented in green
 (e.g. monitoring algorithm started, found a ring , etc), warnings are shown in yellow and errors in red. By clicking on a particular message, more information (if available) is shown. The monitoring algorithms announce themselves at the end of the initialisation (during the Configure phase when a new run is started) and most of them report that they have seen the first event as well. This indicates that they are correctly set up and also receive events from the central buffer of the monitoring farm.
Line: 96 to 98
 In the online system, the Presenter can be started with startOfficialMonitor

DataManager pages

Added:
>
>
Several pages are (being) added to the Shift section of the list of available Presenter pages. These pages are mainly for the central Data-Manager shift crew but should also be monitored on a regular basis by the RICH crew.

The two screen-shots below show the overview pages for RICH1 and RICH2. In nominal conditions both pages should look similar to these examples. The page contains two 2D histograms (one per detector panel) showing a integrated hitmap of the light detected by the HPDs. Some of the central HPDs have a higher hit-count than the others as they receive more light from the denser environment in the collision. A 1D histogram shows the inclusive distribution of the number of hits in the recorded events. The remaining 2D histograms (again, one per detector panel) indicate which HPD (if any) has been disabled by the online monitoring software due to some issue. These histograms are empty in nominal conditions - if any entry is found, at least one HPD shows "odd" behaviour which needs to be investigated.

For RICH1:

Presenter_ShiftRich1.png

For RICH2:

Presenter_ShiftRich2.png

Disabled HPDs

In order to prevent any loss time in global data-taking, individual HPDs becoming "upset" (e.g. because of synchronisation issues or other hick-ups) can be disabled by the online monitoring. These "upset" HPDs may e.g. show a large number of HPD pixels permanently on or the data recorded by them may be inconsistent with the rest of the event, etc. A detailed warning message is sent to CAMERA why a particular HPD has been disabled and the location of these HPDs is shown in a dedicated page in the Presenter. All 4 histograms (one per detector panel) are empty in normal conditions as shown in the example below.

Presenter_DisabledHPDs.png

 

Trackless Rings

A trackless ring finding algorithm runs on the Monitoring Farm based on an Elastic Neural Network. This approach does not rely on input of any other sub-detector and gives a rough performance estimate of the RICH. The presenter page shows the distribution of ring radii (sensitive to refractive index, and hence to temperature and pressure) and the photon yield for rings found in the gas radiators of RICH1 and RICH2.
Line: 151 to 177
  ErrorLogger.png
Added:
>
>

Log files

The log files preserving the messages shown in the error logger are written to /clusterlogs/partitions//daq where is the partition of interest such as LHCb or RICH
 

Per-event display of RICH hits

  • Can be done using Panoramix
  • Instructions from Thomas Ruf:
Line: 202 to 231
 
  • Error logger:
    ErrorLogger.png
Added:
>
>
  • Presenter page indicating disabled HPDs:
    Presenter_DisabledHPDs.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Line: 214 to 246
 
META FILEATTACHMENT attachment="Presenter_ShiftRich1.png" attr="" comment="Presenter page: Shift manager page for Rich1" date="1272877248" name="Presenter_ShiftRich1.png" path="Presenter_ShiftRich1.png" size="204342" stream="Presenter_ShiftRich1.png" tmpFilename="/usr/tmp/CGItemp31579" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_ShiftRich2.png" attr="" comment="Presenter page: Shift manager page for Rich2" date="1272877265" name="Presenter_ShiftRich2.png" path="Presenter_ShiftRich2.png" size="205232" stream="Presenter_ShiftRich2.png" tmpFilename="/usr/tmp/CGItemp31609" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="ErrorLogger.png" attr="" comment="Error logger" date="1272878269" name="ErrorLogger.png" path="ErrorLogger.png" size="108741" stream="ErrorLogger.png" tmpFilename="/usr/tmp/CGItemp31768" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Presenter_DisabledHPDs.png" attr="" comment="Presenter page indicating disabled HPDs" date="1272884747" name="Presenter_DisabledHPDs.png" path="Presenter_DisabledHPDs.png" size="107363" stream="Presenter_DisabledHPDs.png" tmpFilename="/usr/tmp/CGItemp31540" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 232010-05-03 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 82 to 82
 

CAMERA

The CAMERA error reporting tool is used to display all information gathered by the online monitoring. Information is shown in green
Changed:
<
<
(e.g. monitoring algorithm started, found a ring , etc), warnings are shown in yellow and errors in red. By clicking on a particular message, more information (if available) is shown. The example below shows the GUI with an hitmap where two isolated rings have been identified by the trackless ring-finding algorithm.
>
>
(e.g. monitoring algorithm started, found a ring , etc), warnings are shown in yellow and errors in red. By clicking on a particular message, more information (if available) is shown. The monitoring algorithms announce themselves at the end of the initialisation (during the Configure phase when a new run is started) and most of them report that they have seen the first event as well. This indicates that they are correctly set up and also receive events from the central buffer of the monitoring farm. Camera_AlgInitialise.png

The example below shows the GUI with an hitmap where two isolated rings have been identified by the trackless ring-finding algorithm.

 CameraGui_WithRing.png
Changed:
<
<

Presenter Pages

>
>

Presenter

 The Presenter is the official LHCb tool to look at histograms produced by the various online and offline monitoring algorithms. In the online system, the Presenter can be started with startOfficialMonitor
Line: 95 to 100
 

Trackless Rings

A trackless ring finding algorithm runs on the Monitoring Farm based on an Elastic Neural Network. This approach does not rely on input of any other sub-detector and gives a rough performance estimate of the RICH. The presenter page shows the distribution of ring radii (sensitive to refractive index, and hence to temperature and pressure) and the photon yield for rings found in the gas radiators of RICH1 and RICH2.
Changed:
<
<
(N.B. the second peak in the radii distribution in the top left plot is not yet understood)
>
>
(N.B. the second peak in the radii distribution in the top left plot is likely an artifact from the cut off of the maximum allowed ring size)
  Presenter_TracklessRings_RefOverlay.png
Line: 124 to 129
  Presenter_OnlineBrunel_Alignment.png
Added:
>
>

Tools in the online environment

Several tools exist to check that the online monitoring is working

MonitoringMon

The MonitoringMon monitors the event buffers used by the various monitoring algorithms and can be started via /group/online/dataflow/scripts/monitoringMon. The buffers "Events_LHCb" read the raw data from the detector and deliver it to the monitoring tasks which then perform the quality checks. The monitoring tasks for the RICH are RichDAQMon and RichRingMon. RichDAQMon runs the monitors checking the data integrity, number of hits and hitmaps, whereas RichRingMon runs the trackless ring-finding algorithm. Both tasks should consume a significant fraction of the data, well above 80%. The task RichRingMon is a little slower than RichDAQMon and will hence consume fewer events as each algorithm works on a best-effort basis.

MonitoringMon_withTasks.png

ErrorLogger

The error-logger is the central tool to keep an eye on the various monitoring tasks and can be started via = /group/online/dataflow/scripts/errorLog LHCb= for the LHCb partition (for other partitions, replace the partition name in the argument). All output from all tasks (HLT, monitoring, reconstruction) is redirected to this central tool - hence it can be a bit overwhelming.... To restrict the output, use the cursor-keys to navigate around and disable the parts you are not interested in. The key players for the RICH are
  • MONA08: Online Monitoring
  • CALD07: Calibration Farm
  • MONA09: Online reconstruction (OnlineBrunel)

The screenshot shows the 3 windows opened by the error logger. The actual messages are shown in the big window. The window on the right is used to control the error logger (enable / disable seeing messages from various farms, change the verbosity level from Warning to Info, etc). A third window (hidden here) is used for the history (not used).

ErrorLogger.png

 

Per-event display of RICH hits

  • Can be done using Panoramix
Line: 161 to 187
 
  • Alignment monitoring in online Brunel:
    Presenter_OnlineBrunel_Alignment.png
Added:
>
>
  • Monitoring starts and announces itself to Camera:
    Camera_AlgInitialise.png

  • MonitoringMon showing the list of active monitoring tasks - example with nothing running...:
    MonitoringMon.png

  • Presenter page: Shift manager page for Rich1:
    Presenter_ShiftRich1.png

  • Presenter page: Shift manager page for Rich2:
    Presenter_ShiftRich2.png

  • Error logger:
    ErrorLogger.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="TestpatternEffi_run70681.png" attr="" comment="HPD efficiency measured using a test-pattern on the calibration farm (not yet timed in)" date="1272459021" name="TestpatternEffi_run70681.png" path="TestpatternEffi_run70681.png" size="170003" stream="TestpatternEffi_run70681.png" tmpFilename="/usr/tmp/CGItemp59294" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="CameraGui_WithRing.png" attr="" comment="Camera GUI with trackless rings" date="1272807706" name="CameraGui_WithRing.png" path="CameraGui_WithRing.png" size="360024" stream="CameraGui_WithRing.png" tmpFilename="/usr/tmp/CGItemp27583" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_OnlineBrunel_Alignment.png" attr="" comment="Alignment monitoring in online Brunel" date="1272809266" name="Presenter_OnlineBrunel_Alignment.png" path="Presenter_OnlineBrunel_Alignment.png" size="256702" stream="Presenter_OnlineBrunel_Alignment.png" tmpFilename="/usr/tmp/CGItemp31410" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Camera_AlgInitialise.png" attr="" comment="Monitoring starts and announces itself to Camera" date="1272875487" name="Camera_AlgInitialise.png" path="Camera_AlgInitialise.png" size="85253" stream="Camera_AlgInitialise.png" tmpFilename="/usr/tmp/CGItemp31537" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="MonitoringMon.png" attr="" comment="MonitoringMon showing the list of active monitoring tasks - example with nothing running..." date="1272875553" name="MonitoringMon.png" path="MonitoringMon.png" size="71118" stream="MonitoringMon.png" tmpFilename="/usr/tmp/CGItemp31575" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="MonitoringMon_withTasks.png" attr="" comment="MonitoringMon showing the list of active monitoring tasks" date="1272876498" name="MonitoringMon_withTasks.png" path="MonitoringMon_withTasks.png" size="87248" stream="MonitoringMon_withTasks.png" tmpFilename="/usr/tmp/CGItemp31571" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_ShiftRich1.png" attr="" comment="Presenter page: Shift manager page for Rich1" date="1272877248" name="Presenter_ShiftRich1.png" path="Presenter_ShiftRich1.png" size="204342" stream="Presenter_ShiftRich1.png" tmpFilename="/usr/tmp/CGItemp31579" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_ShiftRich2.png" attr="" comment="Presenter page: Shift manager page for Rich2" date="1272877265" name="Presenter_ShiftRich2.png" path="Presenter_ShiftRich2.png" size="205232" stream="Presenter_ShiftRich2.png" tmpFilename="/usr/tmp/CGItemp31609" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="ErrorLogger.png" attr="" comment="Error logger" date="1272878269" name="ErrorLogger.png" path="ErrorLogger.png" size="108741" stream="ErrorLogger.png" tmpFilename="/usr/tmp/CGItemp31768" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 222010-05-02 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 18 to 18
 
  • Get accounts for the ShiftDB, eLogs, ticket- and Savannah systems
  • If you're working from remove, set-up your ssh links and NX clients to log into the online systems
  • Familiarise yourself with the Presenter, Camera and how to run Panoptes offline on raw data in IP8
Added:
>
>
  • make sure that you execute the script /group/rich/scripts/rich_login.sh in your login script on the online PCs and that the CMT directory User_release_area points to /group/rich/sw/cmtuser
 

Mailing list

Subscribe to the mailing lists (... @cern.ch):
Line: 80 to 81
 
  • HistogramDB. For completeness - it is unlikely you will need to edit the display properties of any histogram. However, here is where you can...

CAMERA

Added:
>
>
The CAMERA error reporting tool is used to display all information gathered by the online monitoring. Information is shown in green (e.g. monitoring algorithm started, found a ring , etc), warnings are shown in yellow and errors in red. By clicking on a particular message, more information (if available) is shown. The example below shows the GUI with an hitmap where two isolated rings have been identified by the trackless ring-finding algorithm. CameraGui_WithRing.png
 

Presenter Pages

Added:
>
>
The Presenter is the official LHCb tool to look at histograms produced by the various online and offline monitoring algorithms. In the online system, the Presenter can be started with startOfficialMonitor
 

DataManager pages

Line: 111 to 118
  TestpatternEffi_run70681.png
Added:
>
>

Alignment monitoring

The alignment of each of the 4 HPD panels monitored online using OnlineBrunel. The page shown below shows the output of the monitoring - in the next step, automated fits and alerts will be added.

Presenter_OnlineBrunel_Alignment.png

 

Per-event display of RICH hits

Line: 146 to 158
 
  • HPD efficiency measured using a test-pattern on the calibration farm (not yet timed in):
    TestpatternEffi_run70681.png
Added:
>
>
  • Alignment monitoring in online Brunel:
    Presenter_OnlineBrunel_Alignment.png
 
META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="TestpatternEffi_run70681.png" attr="" comment="HPD efficiency measured using a test-pattern on the calibration farm (not yet timed in)" date="1272459021" name="TestpatternEffi_run70681.png" path="TestpatternEffi_run70681.png" size="170003" stream="TestpatternEffi_run70681.png" tmpFilename="/usr/tmp/CGItemp59294" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="CameraGui_WithRing.png" attr="" comment="Camera GUI with trackless rings" date="1272807706" name="CameraGui_WithRing.png" path="CameraGui_WithRing.png" size="360024" stream="CameraGui_WithRing.png" tmpFilename="/usr/tmp/CGItemp27583" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_OnlineBrunel_Alignment.png" attr="" comment="Alignment monitoring in online Brunel" date="1272809266" name="Presenter_OnlineBrunel_Alignment.png" path="Presenter_OnlineBrunel_Alignment.png" size="256702" stream="Presenter_OnlineBrunel_Alignment.png" tmpFilename="/usr/tmp/CGItemp31410" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 212010-04-28 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Changed:
<
<
This page summarises the efforts of the RICH Data Quality
>
>
This page summarises the efforts of the RICH Data Quality with instructions for the RICH and the RICH DQ piquet.

The RICH DQ piquet can be done from remote institutions outside CERN

As this is a TWiki page, please feel free to add and correct information here... LHCb is in its start-up phase and instructions will likely evolve with more experience.

 
Added:
>
>

As a RICH DQ piquet

Preparations

  • Subscribe to the relevant mailing lists
  • Get accounts for the ShiftDB, eLogs, ticket- and Savannah systems
  • If you're working from remove, set-up your ssh links and NX clients to log into the online systems
  • Familiarise yourself with the Presenter, Camera and how to run Panoptes offline on raw data in IP8
 

Mailing list

Changed:
<
<
A dedicated mailing list has been created: lhcb-rich-dataquality AT cern.ch
>
>
Subscribe to the mailing lists (... @cern.ch):
  • lhcb-rich-dataquality
  • lhcb-rich-operations
  • lhcb-rich-software
  • lhcb-data-quality
  • lhcb-online-users
  • lhcb-online
  • lhcb-run-news

Ticket / issues tracking systems

Several systems are being used to track issues, request information or actions, etc. Please register with all of them. You will also need an account on the online cluster.

ELog

Several electronic log-books are used to keep track of any information relevant to operational issues
 

Meetings

Changed:
<
<
Meetings will be held every other week on Wednesdays, 10:00 - 12:00 (CERN time) or when necessary.
>
>
  • Daily run meeting at IP8, 9am (CERN time)
  • RICH Operations: Wednesdays, 10:35 (CERN time)
 
Changed:
<
<
>
>

Previous Trainings, etc.

Several old training slides are available. Please have a look at them as most information is still valid.
 
Deleted:
<
<

For the Shifter

 
Changed:
<
<

Getting ready

  • Register with
  • Read through the online-monitoring TWiki and familiarise yourself how to run the monitoring software PANOPTES manually in case some data-files need to be analysed with new settings, updated software, etc.
  • When running PANOPTES at IP8 remember:
    • Same code for online and offline analysis
    • Only difference is the origin of the data analysed
    • Make sure you don't interfere with online monitoring / data-taking, in particular
      • Make sure the environment variable DIM_DNS_NODE does not point to a system used by online (e.g. mona08, ecsXX)
      • Make sure the CAMERA settings do not point to the ones used by the online monitoring (r2ecs01)

Daily tasks

  • Go through the RICH eLog and register all new issues affecting data-quality into the Savannah issue tracker
  • Go through the CAMERA messages and register all new issues affecting data-quality into the Savannah issue tracker, keep a life window of CAMERA on your desktop and follow what is happening
  • Make sure the relevant experts are aware of the issue and follow up

Tasks to do in the (near) future

  • Use the online event-display (based on Panoramix) and check that (reconstructed) rings can be seen around tracks
  • Monitor the physics performance plots using the online Presenter
  • Collaborate with general LHCb data-quality shifter
    • Verify the control histograms of production jobs are OK

Issues which affect data quality

The following list summarises which issues affect the data-quality and should be followed up with the experts. However, the list is not exhaustive - when in doubt report any issue to the Savannah portal and follow up with the expert.

Summarise new issues on the general TWiki

  • HPDs being disabled in the UKL1 boards (likely L0 board upset)
  • Event- and bunchID mis-matches (synchronisation issues)
  • Invalid ODIN time
  • repeated messages about invalid SmartRefs where the HPD is not inhbited
  • repeated messages about HPDs with extended information
  • repeated messages about L0 ID mis-matches
  • repeated messages about parity footer errors

How to read (previous) CAMERA messages

In order to start CAMERA, follow the steps:
  • Log into the PLUS cluster at IP8
  • Type setupMonitoring
  • Type startCameraGui
This will bring up the GUI of the CAMERA client which shows the current messages

CAMERA internally uses a log file called warnings.out to store all messages sent by the monitoring algorithms. In order to keep this file small, the current file can be stored under a different name using the script /group/rich/scripts/newCameraLog (see How to use CAMERA in the control room for more details) To follow the information and errors reported by CAMERA in previous runs, etc, do the following

  • Log into the PLUS cluster at IP8
  • Type setupMonitoring
  • Change the directory to e.g. your home directory
  • Download a copy of the most recent CAMERA messages.
    • Check on the LHCb eLog when the shifter changed to a new CAMERA file. By default, the files are named like warnings_yymmddHHMM.out where yymmddHHMM is the relevant year, month, day, hour and minute.
    • To download, use the following command: wget r2ecs01:8888/data/warnings.out , (replacing the name of the file with the actual file name if necessary).
  • Start the CAMERA GUI with $PANOPTESROOT/scripts/runCamera.sh r2ecs01 warnings.out where warnings.out is the name of the CAMERA messages just downloaded

Experts to contact

Topic Name TelNr email
Reconstruction Chris Jones   jonesc[AT]hep.phy.cam.ac.uk
UKL1 Steve Wotton   wotton[AT]hep.phy.cam.ac.uk
  Gareth Rogers 78765 rogers[AT]hep.phy.cam.ac.uk
Monitoring Ulrich Kerzel 78765 Ulrich.Kerzel[AT]cern.ch
Alignment Antonis Papanestis   antonis.papanesti[AT]cern.ch
  Chris Blanks   Chris.Blanks[AT]cern.ch
  Anatoly Solomin   Anatoly.Solomin[AT]bristol.ac.uk
Trackless refractive index Susan Haines   haines[AT]hep.phy.cam.ac.uk
Trackbased refractive index Susan Haines   haines[AT]hep.phy.cam.ac.uk
Aerogel refractive index Davide Perego   Davide.Perego[AT]mib.infn.it
Ion feedback Young Min Kim   s0679231[AT]sms.ed.ac.uk
  Ross Young   r.d.young[AT]sms.ed.ac.uk
D* -> Dpi PID performance Andrew Powell  
Lambda PID performance Andrew Powell  
KShort PID performance Andrew Powell  
J/psi -> mumu PID performance Gemma Fardell   g.fardel[AT]ed.ac.uk
>
>

More detailed TWiki pages, web-links etc.

  • Detailed overview of the [https://lbtwiki.cern.ch/bin/view/Online/MonitoringExpertGuide][Monitoring for Experts]]

  • When working from remote, logging into the online systems can be very slow as the X protocol forwarding e.g. the Presenter or Camera window is very slow. Follow the instructions at Log into online systems to use the NX client. The NX client software can be obtained from NoMachine

  • HistogramDB. For completeness - it is unlikely you will need to edit the display properties of any histogram. However, here is where you can...

CAMERA

Presenter Pages

DataManager pages

Trackless Rings

A trackless ring finding algorithm runs on the Monitoring Farm based on an Elastic Neural Network. This approach does not rely on input of any other sub-detector and gives a rough performance estimate of the RICH. The presenter page shows the distribution of ring radii (sensitive to refractive index, and hence to temperature and pressure) and the photon yield for rings found in the gas radiators of RICH1 and RICH2.

(N.B. the second peak in the radii distribution in the top left plot is not yet understood)

Presenter_TracklessRings_RefOverlay.png

Hits per HPD

Several pages are available in the presenter to cross-check the current occupancy.

This page shows the pull of the expected vs actual number of hits per HPD in each RICH panel. The expected number of hits is calculated from a slowly moving average (over many events) whereas the actual number of hits is given by a fast moving average (over few events). Any large outliers indicate that an HPD does not see the expected number of events consistent with the current luminosity. Presenter_HPDHitPull.png

This 1D plot contains the same information and shows the number of hits (from the fast moving average) per HPD. The 1D representation has been added as it is easier to compare to a reference plot. The HPDs are arranged as columnNr*NrOfColums+NrOfHPDInColum. Presenter_HPDnHIt1DReference.png

HPD Efficiency

During the long abort gap between the bunch trains the 4 corner pixels of the HPD silicon chip is activated. This special data is recorded and analysed on the Calibration Farm. Ideally, each pixel activated should be seen in the monitoring process. One might expect that not each pixel is read out with 100% efficiency at all times - but in general the HPD efficiency should be close to 100%.

However, note that the timing of the HPD is not yet optimised as shown in the picture from run 70681 below. This will be done soon, until then HPD efficiencies deviating from 100% are not a cause of concern.

TestpatternEffi_run70681.png

 
Line: 117 to 131
 display. See also Rich_viewer.py in the Panoramix scripts/Python directory.
Deleted:
<
<

Tasks

 
Deleted:
<
<

Alignment and calibration

Refractive Index monitoring

  • With tracks: Code already exist to produce basic histograms
    • Add configuration to Panoptes
    • Spot refractive index variations (should be implemented as ROOT scripts)
    • Generate dedicated MC with different refractive index (vary pressure)
    • Standard offline reconstruction already produces the required histograms, need to find out how to (bulk) download all reqired histograms for a run

  • Without tracks using Markov Chains to find isolated rings (Susan) Presentation 2008-July-09
    • improve algorithm (esp for Rich1)
    • add to Panoptes / online monitoring

  • Aerogel (Davide)

Mirror alignment (Antonis + Chris Blanks)

  • Central mirrors (few thousand events sufficient)
  • All mirrors (~ 1M events needed, needs good tracking as input) - Guide for DQ Shifters

Magnetic distortion measurements
  • Input to alignment
  • Values measured during commissioning should be sufficient for start-up
  • Re-measurement for RICH1: takes about 150 mins, can be done e.g. on machine-development days
  • Re-measurement for RICH2: requires projector -> only during shutdown periods

Physics performance

  • Some of the algoritms are also to be used for online monitoring

DLL distributions:

  • Monitor change in DLL distributions online / Brunel

Photon statistics

  • Number of photons per track
  • Number of photons per radiator
as function of luminosity

Exclusive decays

D* -> D pi (Oxord)

Lambda -> p pi (Oxford)

Phi -> KK (Edinburgh)

KShort (Oxford)

J/psi -> mu mu (Edinburgh)

Conversion gamma -> ee
  • to be investigated if feasable

Detector related

Ion Feedback (Young-Min, Ross)

Hot / Cold pixels
* detect and mask hot and cold pixels, as well as dead columns

Average occupancy
  • should be stable at given luminosity

RICH Data Quality flags

The following flags (or similar) need to be defined:

OK data good for physics analysis, proceed with reconstruction
Investigate I Issues found which can be fixed quickly. Delay reconstruction
Investigate II Issues found which cannot be fixed quickly. Proceed with reconstruction and follow up in re-processing
BAD Data not usable for physics analysis from RICH point of view

Definitions of these flags

to do

RICH Reconstruction

  • Possible to avoid to use of the average HPD occupancy during hit cleaning
  • simiplify configuration / switch to Python configurables
  • Optimised settings for (early) data - current settings tuned towards DC06 simulation

Computing

--+++ Single pass and iterative tasks Some calibration tasks can be done in a single task running over the data, others need to be done iteratively.

At IP8

Using the PLUS farm quick checks can be performed at IP8 before the data is migrated to CASTOR. However, need to to lock the data while the checks are done to prevent automatic deletion as it is migrated to CASTOR.

At CERN

Data Quality checks will be done using the LXPLUS farm, maybe dedicated resources will be available. Access to RAW data seems to be necessary.

Job submission based on GANGA (Anatoly / Bristol)

Work in progress how to use GANGA for iterative procedures and a unified "front-end" to submit both to the PLUS farm at IP8 and LXPLUS at CERN.

"Technical MC"

Dedicated simulated events are needed to exercise and test the procedures, e.g. with the new detector geometry. This is coordinated with other sub-detectors in the Gauss meeting (by Gloria). For the RICH, Antonis and Sajan are present (?)

To Do (with priorities)

N.B Even though several tasks can be treated with lower priority at the start of data-taking, releasing the corresponding algorithms and options files takes considerable amount of time.

  1. Reconstruction
    1. Minimal set of algorithms to verify data is usable (-> options file)
    2. Define default monitors (-> options file)
      1. RichDAQMon (from online monitoring) to check for corrupted data
      2. track-based refractive index
      3. PID DLL: Comparison to reference histogram (based on analysis database)
      4. Photon statistics (#photons per track, radiator, ...)

  1. Alignment (Antonis, Chris, Anatoly)
    1. Magnetic distortion measurements: input to alignment (Malcom, Phillip, Roberta)
    2. Define procedure to verify alignment and check if new alignment is needed
    3. Ganga based alignment procedure (Anatoly)

  1. Refractive index: Monitoring and determination of new value if necessary
    1. track-less (Susan)
    2. track-based (Susan)
    3. aerogel (Davide)

  1. Detector stability
    1. Ion feedback (Young-Min, Ross, Edinburgh)
    2. Hot / cold pixels
    3. Average occupancy

  1. Physics performance (N.B. Considerable gap between "final" version of code + options file and use in the next released version!)
    1. Lambda -> p pi (X, Oxford)
    2. J/psi -> mu mu (Gemma Fardell, Edinburgh)
    3. D* -> D pi (Guy + X, Oxford)
    4. Phi -> KK (X, Edinburgh)
    5. KShort -> pi pi

Further tasks

  • Definition of quality flags
  • How to subscribe to trigger bits
  • Investigate how the PID related monitoring changes with imperfect knowledge of the refractive index
  • Generate dedicated simulated events (recent detector geometry, post DC06, different radiator pressures), discussed in Gauss-meeting (Antonis?)
  • Define "hot" pixel: Always on to above expected occupancy in a given region / luminosity
  • Access to computing ressources
  • Lock files in IP8
  • Access to RAW data from CASTOR
  • How to release new alignment and calibration constants
  • How to retrieve output (e.g. histograms, calibration constants), where to store them (permanently)
  • Metadata, how to associate output of data-quality jobs with checks performed, results, etc.
  • Histograms, etc available per file, per run?
  • Reconstruction: Possible to avoid the use of average HPD occupancy during hit cleaning ?
  • Move to Python configurables
  • Optimise reconstruction settings for (early) data
  • Add Panoptes to Ganga
  -- UlrichKerzel - 11 Jul 2008
Added:
>
>
  • Presenter page: HPD hit pull:
    Presenter_HPDHitPull.png

  • 1D representation of hits per HPD:
    Presenter_HPDnHIt1DReference.png

  • Trackless ring radii and photon yield:
    Presenter_TracklessRings_RefOverlay.png

  • HPD efficiency measured using a test-pattern on the calibration farm (not yet timed in):
    TestpatternEffi_run70681.png

META FILEATTACHMENT attachment="Presenter_HPDHitPull.png" attr="" comment="Presenter page: HPD hit pull" date="1272458921" name="Presenter_HPDHitPull.png" path="Presenter_HPDHitPull.png" size="157973" stream="Presenter_HPDHitPull.png" tmpFilename="/usr/tmp/CGItemp59365" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_HPDnHIt1DReference.png" attr="" comment="1D representation of hits per HPD" date="1272458953" name="Presenter_HPDnHIt1DReference.png" path="Presenter_HPDnHIt1DReference.png" size="189195" stream="Presenter_HPDnHIt1DReference.png" tmpFilename="/usr/tmp/CGItemp59304" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="Presenter_TracklessRings_RefOverlay.png" attr="" comment="Trackless ring radii and photon yield" date="1272458987" name="Presenter_TracklessRings_RefOverlay.png" path="Presenter_TracklessRings_RefOverlay.png" size="130679" stream="Presenter_TracklessRings_RefOverlay.png" tmpFilename="/usr/tmp/CGItemp59314" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"
META FILEATTACHMENT attachment="TestpatternEffi_run70681.png" attr="" comment="HPD efficiency measured using a test-pattern on the calibration farm (not yet timed in)" date="1272459021" name="TestpatternEffi_run70681.png" path="TestpatternEffi_run70681.png" size="170003" stream="TestpatternEffi_run70681.png" tmpFilename="/usr/tmp/CGItemp59294" user="kerzel_40hep_2ephy_2ecam_2eac_2euk" version="1"

Revision 202009-10-08 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 85 to 85
 
  Gareth Rogers 78765 rogers[AT]hep.phy.cam.ac.uk
Monitoring Ulrich Kerzel 78765 Ulrich.Kerzel[AT]cern.ch
Alignment Antonis Papanestis   antonis.papanesti[AT]cern.ch
Changed:
<
<
  Chris Blanks   Chris.Blank[AT]cern.ch
>
>
  Chris Blanks   Chris.Blanks[AT]cern.ch
 
  Anatoly Solomin   Anatoly.Solomin[AT]bristol.ac.uk
Trackless refractive index Susan Haines   haines[AT]hep.phy.cam.ac.uk
Trackbased refractive index Susan Haines   haines[AT]hep.phy.cam.ac.uk
Line: 135 to 135
 

Mirror alignment (Antonis + Chris Blanks)

  • Central mirrors (few thousand events sufficient)
Changed:
<
<
  • All mirrors (~ 1M events needed, needs good tracking as input)
>
>
 
Magnetic distortion measurements
  • Input to alignment
  • Values measured during commissioning should be sufficient for start-up

Revision 192009-01-14 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 92 to 92
 
Aerogel refractive index Davide Perego   Davide.Perego[AT]mib.infn.it
Ion feedback Young Min Kim   s0679231[AT]sms.ed.ac.uk
  Ross Young   r.d.young[AT]sms.ed.ac.uk
Changed:
<
<
D* -> Dpi PID performance Oxford, TBA  
Lambda PID performance Oxford, TBA  
>
>
D* -> Dpi PID performance Andrew Powell  
Lambda PID performance Andrew Powell  
KShort PID performance Andrew Powell  
 
J/psi -> mumu PID performance Gemma Fardell   g.fardel[AT]ed.ac.uk

Line: 159 to 160
 
Phi -> KK (Edinburgh)
Changed:
<
<
KShort (?)
>
>
KShort (Oxford)
 
J/psi -> mu mu (Edinburgh)

Revision 182008-09-02 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 24 to 24
 
Added:
>
>
  • When running PANOPTES at IP8 remember:
    • Same code for online and offline analysis
    • Only difference is the origin of the data analysed
    • Make sure you don't interfere with online monitoring / data-taking, in particular
      • Make sure the environment variable DIM_DNS_NODE does not point to a system used by online (e.g. mona08, ecsXX)
      • Make sure the CAMERA settings do not point to the ones used by the online monitoring (r2ecs01)
 

Daily tasks

  • Go through the RICH eLog and register all new issues affecting data-quality into the Savannah issue tracker

Revision 172008-09-02 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 22 to 22
 

Getting ready

Added:
>
>
    • lhcb-rich-dataquality[AT]cern.ch
 
  • Read through the online-monitoring TWiki and familiarise yourself how to run the monitoring software PANOPTES manually in case some data-files need to be analysed with new settings, updated software, etc.

Daily tasks

Revision 162008-08-26 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 21 to 21
 

Getting ready

  • Register with
Deleted:
<
<
 
Line: 58 to 57
 
  • Type startCameraGui
This will bring up the GUI of the CAMERA client which shows the current messages
Added:
>
>
CAMERA internally uses a log file called warnings.out to store all messages sent by the monitoring algorithms. In order to keep this file small, the current file can be stored under a different name using the script /group/rich/scripts/newCameraLog (see How to use CAMERA in the control room for more details)
 To follow the information and errors reported by CAMERA in previous runs, etc, do the following
  • Log into the PLUS cluster at IP8
  • Type setupMonitoring
  • Change the directory to e.g. your home directory
  • Download a copy of the most recent CAMERA messages.
Changed:
<
<
    • Check on the LHCb eLog when the shifter changed to a new CAMERA file. By default, the files are named like warnings_ddmmyy.out where ddmmyy is the relevant day, month and year.
    • The default file is warnings.out.
    • To download, use the following command: wget r2ecs01:8888/data/warnings.out , replacing the name of the file with the actual file name.
>
>
    • Check on the LHCb eLog when the shifter changed to a new CAMERA file. By default, the files are named like warnings_yymmddHHMM.out where yymmddHHMM is the relevant year, month, day, hour and minute.
    • To download, use the following command: wget r2ecs01:8888/data/warnings.out , (replacing the name of the file with the actual file name if necessary).
 
  • Start the CAMERA GUI with $PANOPTESROOT/scripts/runCamera.sh r2ecs01 warnings.out where warnings.out is the name of the CAMERA messages just downloaded

Revision 152008-08-25 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 18 to 18
 

For the Shifter

Added:
>
>

Getting ready

Daily tasks

  • Go through the RICH eLog and register all new issues affecting data-quality into the Savannah issue tracker
  • Go through the CAMERA messages and register all new issues affecting data-quality into the Savannah issue tracker, keep a life window of CAMERA on your desktop and follow what is happening
  • Make sure the relevant experts are aware of the issue and follow up

Tasks to do in the (near) future

 
  • Use the online event-display (based on Panoramix) and check that (reconstructed) rings can be seen around tracks
Added:
>
>
  • Monitor the physics performance plots using the online Presenter
  • Collaborate with general LHCb data-quality shifter
    • Verify the control histograms of production jobs are OK

Issues which affect data quality

The following list summarises which issues affect the data-quality and should be followed up with the experts. However, the list is not exhaustive - when in doubt report any issue to the Savannah portal and follow up with the expert.

Summarise new issues on the general TWiki

  • HPDs being disabled in the UKL1 boards (likely L0 board upset)
  • Event- and bunchID mis-matches (synchronisation issues)
  • Invalid ODIN time
  • repeated messages about invalid SmartRefs where the HPD is not inhbited
  • repeated messages about HPDs with extended information
  • repeated messages about L0 ID mis-matches
  • repeated messages about parity footer errors

How to read (previous) CAMERA messages

In order to start CAMERA, follow the steps:
  • Log into the PLUS cluster at IP8
  • Type setupMonitoring
  • Type startCameraGui
This will bring up the GUI of the CAMERA client which shows the current messages

To follow the information and errors reported by CAMERA in previous runs, etc, do the following

  • Log into the PLUS cluster at IP8
  • Type setupMonitoring
  • Change the directory to e.g. your home directory
  • Download a copy of the most recent CAMERA messages.
    • Check on the LHCb eLog when the shifter changed to a new CAMERA file. By default, the files are named like warnings_ddmmyy.out where ddmmyy is the relevant day, month and year.
    • The default file is warnings.out.
    • To download, use the following command: wget r2ecs01:8888/data/warnings.out , replacing the name of the file with the actual file name.
  • Start the CAMERA GUI with $PANOPTESROOT/scripts/runCamera.sh r2ecs01 warnings.out where warnings.out is the name of the CAMERA messages just downloaded

Experts to contact

Topic Name TelNr email
Reconstruction Chris Jones   jonesc[AT]hep.phy.cam.ac.uk
UKL1 Steve Wotton   wotton[AT]hep.phy.cam.ac.uk
  Gareth Rogers 78765 rogers[AT]hep.phy.cam.ac.uk
Monitoring Ulrich Kerzel 78765 Ulrich.Kerzel[AT]cern.ch
Alignment Antonis Papanestis   antonis.papanesti[AT]cern.ch
  Chris Blanks   Chris.Blank[AT]cern.ch
  Anatoly Solomin   Anatoly.Solomin[AT]bristol.ac.uk
Trackless refractive index Susan Haines   haines[AT]hep.phy.cam.ac.uk
Trackbased refractive index Susan Haines   haines[AT]hep.phy.cam.ac.uk
Aerogel refractive index Davide Perego   Davide.Perego[AT]mib.infn.it
Ion feedback Young Min Kim   s0679231[AT]sms.ed.ac.uk
  Ross Young   r.d.young[AT]sms.ed.ac.uk
D* -> Dpi PID performance Oxford, TBA  
Lambda PID performance Oxford, TBA  
J/psi -> mumu PID performance Gemma Fardell   g.fardel[AT]ed.ac.uk

 

Per-event display of RICH hits

  • Can be done using Panoramix

Revision 142008-08-21 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 15 to 15
 
Added:
>
>
 

For the Shifter

  • Use the online event-display (based on Panoramix) and check that (reconstructed) rings can be seen around tracks

Revision 132008-08-06 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 19 to 19
 

For the Shifter

  • Use the online event-display (based on Panoramix) and check that (reconstructed) rings can be seen around tracks
Added:
>
>

Per-event display of RICH hits

  • Can be done using Panoramix
  • Instructions from Thomas Ruf:
There is a framework for this implemented. You need to define your favored view, page layout, with whatever you want to display. This should be done with a python script. This python script gets registered in a dictionary

onlineViews[title] = 'Rich_2dView'

Then, the nextEvent loop script checks if for the current page title there exists an associated python script, which is then executed for the next event. All this is in place. Under Online, there is a first version for Rich display. See also Rich_viewer.py in the Panoramix scripts/Python directory.

 

Tasks

Alignment and calibration

Line: 38 to 56
 

Mirror alignment (Antonis + Chris Blanks)

  • Central mirrors (few thousand events sufficient)
  • All mirrors (~ 1M events needed, needs good tracking as input)
Added:
>
>
Magnetic distortion measurements
  • Input to alignment
  • Values measured during commissioning should be sufficient for start-up
  • Re-measurement for RICH1: takes about 150 mins, can be done e.g. on machine-development days
  • Re-measurement for RICH2: requires projector -> only during shutdown periods
 

Physics performance

  • Some of the algoritms are also to be used for online monitoring

Revision 122008-08-06 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 51 to 51
 as function of luminosity

Exclusive decays

Changed:
<
<
D* -> D pi (Raluca and Guy)
>
>
D* -> D pi (Oxord)
 
Lambda -> p pi (Oxford)

Phi -> KK (Edinburgh)
Changed:
<
<
KShort (Edinburgh)
>
>
KShort (?)
 
Changed:
<
<
J/psi -> mu mu
>
>
J/psi -> mu mu (Edinburgh)
 
Conversion gamma -> ee
  • to be investigated if feasable

Detector related

Changed:
<
<
Ion Feedback (Nick, Young-Min)
>
>
Ion Feedback (Young-Min, Ross)
 
Hot / Cold pixels
* detect and mask hot and cold pixels, as well as dead columns
Line: 135 to 135
 
    1. aerogel (Davide)

  1. Detector stability
Changed:
<
<
    1. Ion feedback (Nick, Young-Min, Edinburgh)
>
>
    1. Ion feedback (Young-Min, Ross, Edinburgh)
 
    1. Hot / cold pixels
    2. Average occupancy

  1. Physics performance (N.B. Considerable gap between "final" version of code + options file and use in the next released version!)
    1. Lambda -> p pi (X, Oxford)
Changed:
<
<
    1. J/psi -> mu mu (ee as well?)
>
>
    1. J/psi -> mu mu (Gemma Fardell, Edinburgh)
 
    1. D* -> D pi (Guy + X, Oxford)
    2. Phi -> KK (X, Edinburgh)
Changed:
<
<
    1. KShort -> pi pi (X, Edinburgh)
>
>
    1. KShort -> pi pi
  Further tasks
  • Definition of quality flags

Revision 112008-08-06 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 14 to 14
 
Changed:
<
<
>
>
 

For the Shifter

  • Use the online event-display (based on Panoramix) and check that (reconstructed) rings can be seen around tracks

Revision 102008-08-06 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 131 to 131
 
  1. Refractive index: Monitoring and determination of new value if necessary
    1. track-less (Susan)
Changed:
<
<
    1. track-based
>
>
    1. track-based (Susan)
 
    1. aerogel (Davide)

  1. Detector stability

Revision 92008-07-31 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 119 to 119
 
  1. Reconstruction
    1. Minimal set of algorithms to verify data is usable (-> options file)
    2. Define default monitors (-> options file)
Added:
>
>
      1. RichDAQMon (from online monitoring) to check for corrupted data
 
      1. track-based refractive index
      2. PID DLL: Comparison to reference histogram (based on analysis database)
      3. Photon statistics (#photons per track, radiator, ...)

Revision 82008-07-31 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 108 to 108
 Work in progress how to use GANGA for iterative procedures and a unified "front-end" to submit both to the PLUS farm at IP8 and LXPLUS at CERN.
Added:
>
>

"Technical MC"

Dedicated simulated events are needed to exercise and test the procedures, e.g. with the new detector geometry. This is coordinated with other sub-detectors in the Gauss meeting (by Gloria). For the RICH, Antonis and Sajan are present (?)
 

To Do (with priorities)

N.B Even though several tasks can be treated with lower priority at the start of data-taking, releasing the corresponding algorithms and options files takes considerable amount of time.

Revision 72008-07-30 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 16 to 16
 
Added:
>
>

For the Shifter

  • Use the online event-display (based on Panoramix) and check that (reconstructed) rings can be seen around tracks
 

Tasks

Alignment and calibration

Revision 62008-07-30 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 123 to 123
 
  1. Refractive index: Monitoring and determination of new value if necessary
    1. track-less (Susan)
    2. track-based
Added:
>
>
    1. aerogel (Davide)
 
  1. Detector stability
    1. Ion feedback (Nick, Young-Min, Edinburgh)

Revision 52008-07-29 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 12 to 12
 

Meetings

Meetings will be held every other week on Wednesdays, 10:00 - 12:00 (CERN time) or when necessary.
Changed:
<
<
>
>
 

Tasks

Line: 103 to 105
 Work in progress how to use GANGA for iterative procedures and a unified "front-end" to submit both to the PLUS farm at IP8 and LXPLUS at CERN.
Changed:
<
<

To Do

>
>

To Do (with priorities)

N.B Even though several tasks can be treated with lower priority at the start of data-taking, releasing the corresponding algorithms and options files takes considerable amount of time.

  1. Reconstruction
    1. Minimal set of algorithms to verify data is usable (-> options file)
    2. Define default monitors (-> options file)
      1. track-based refractive index
      2. PID DLL: Comparison to reference histogram (based on analysis database)
      3. Photon statistics (#photons per track, radiator, ...)

  1. Alignment (Antonis, Chris, Anatoly)
    1. Magnetic distortion measurements: input to alignment (Malcom, Phillip, Roberta)
    2. Define procedure to verify alignment and check if new alignment is needed
    3. Ganga based alignment procedure (Anatoly)

  1. Refractive index: Monitoring and determination of new value if necessary
    1. track-less (Susan)
    2. track-based

  1. Detector stability
    1. Ion feedback (Nick, Young-Min, Edinburgh)
    2. Hot / cold pixels
    3. Average occupancy

  1. Physics performance (N.B. Considerable gap between "final" version of code + options file and use in the next released version!)
    1. Lambda -> p pi (X, Oxford)
    2. J/psi -> mu mu (ee as well?)
    3. D* -> D pi (Guy + X, Oxford)
    4. Phi -> KK (X, Edinburgh)
    5. KShort -> pi pi (X, Edinburgh)

Further tasks

 
  • Definition of quality flags
  • How to subscribe to trigger bits
  • Investigate how the PID related monitoring changes with imperfect knowledge of the refractive index
Changed:
<
<
  • Generate dedicated simulated events (recent detector geometry, post DC06, different radiator pressures)
>
>
  • Generate dedicated simulated events (recent detector geometry, post DC06, different radiator pressures), discussed in Gauss-meeting (Antonis?)
 
  • Define "hot" pixel: Always on to above expected occupancy in a given region / luminosity
  • Access to computing ressources
  • Lock files in IP8

Revision 42008-07-22 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 30 to 30
 
  • Aerogel (Davide)
Changed:
<
<

Mirror alignment (Antonis + ?)

>
>

Mirror alignment (Antonis + Chris Blanks)

 
  • Central mirrors (few thousand events sufficient)
  • All mirrors (~ 1M events needed, needs good tracking as input)

Revision 32008-07-14 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 22 to 22
 
    • Add configuration to Panoptes
    • Spot refractive index variations (should be implemented as ROOT scripts)
    • Generate dedicated MC with different refractive index (vary pressure)
Added:
>
>
    • Standard offline reconstruction already produces the required histograms, need to find out how to (bulk) download all reqired histograms for a run
 
Added:
>
>
    • improve algorithm (esp for Rich1)
    • add to Panoptes / online monitoring
 
  • Aerogel (Davide)

Mirror alignment (Antonis + ?)

Line: 75 to 79
 

Definitions of these flags

to do
Added:
>
>

RICH Reconstruction

  • Possible to avoid to use of the average HPD occupancy during hit cleaning
  • simiplify configuration / switch to Python configurables
  • Optimised settings for (early) data - current settings tuned towards DC06 simulation
 

Computing

--+++ Single pass and iterative tasks

Line: 107 to 116
 
  • How to retrieve output (e.g. histograms, calibration constants), where to store them (permanently)
  • Metadata, how to associate output of data-quality jobs with checks performed, results, etc.
  • Histograms, etc available per file, per run?
Added:
>
>
  • Reconstruction: Possible to avoid the use of average HPD occupancy during hit cleaning ?
  • Move to Python configurables
  • Optimise reconstruction settings for (early) data
  • Add Panoptes to Ganga
  -- UlrichKerzel - 11 Jul 2008

Revision 22008-07-11 - UlrichKerzel

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

Line: 16 to 16
 

Tasks

Changed:
<
<

Alignment and callibration

>
>

Alignment and calibration

 

Refractive Index monitoring

Changed:
<
<
  • With tracks
>
>
  • With tracks: Code already exist to produce basic histograms
    • Add configuration to Panoptes
    • Spot refractive index variations (should be implemented as ROOT scripts)
    • Generate dedicated MC with different refractive index (vary pressure)

 
Line: 28 to 32
 

Physics performance

  • Some of the algoritms are also to be used for online monitoring
Deleted:
<
<
 

DLL distributions:

  • Monitor change in DLL distributions online / Brunel
Line: 52 to 55
 
Conversion gamma -> ee
  • to be investigated if feasable
Added:
>
>

Detector related

Ion Feedback (Nick, Young-Min)

Hot / Cold pixels
* detect and mask hot and cold pixels, as well as dead columns
 
Added:
>
>
Average occupancy
  • should be stable at given luminosity
 

RICH Data Quality flags

The following flags (or similar) need to be defined:
Line: 65 to 75
 

Definitions of these flags

to do
Added:
>
>

Computing

--+++ Single pass and iterative tasks Some calibration tasks can be done in a single task running over the data, others need to be done iteratively.

At IP8

Using the PLUS farm quick checks can be performed at IP8 before the data is migrated to CASTOR. However, need to to lock the data while the checks are done to prevent automatic deletion as it is migrated to CASTOR.

At CERN

Data Quality checks will be done using the LXPLUS farm, maybe dedicated resources will be available. Access to RAW data seems to be necessary.

Job submission based on GANGA (Anatoly / Bristol)

Work in progress how to use GANGA for iterative procedures and a unified "front-end" to submit both to the PLUS farm at IP8 and LXPLUS at CERN.
 

To Do

Changed:
<
<
  • Definition of quality flas
  • How to
>
>
  • Definition of quality flags
  • How to subscribe to trigger bits
  • Investigate how the PID related monitoring changes with imperfect knowledge of the refractive index
  • Generate dedicated simulated events (recent detector geometry, post DC06, different radiator pressures)
  • Define "hot" pixel: Always on to above expected occupancy in a given region / luminosity
  • Access to computing ressources
  • Lock files in IP8
  • Access to RAW data from CASTOR
  • How to release new alignment and calibration constants
  • How to retrieve output (e.g. histograms, calibration constants), where to store them (permanently)
  • Metadata, how to associate output of data-quality jobs with checks performed, results, etc.
  • Histograms, etc available per file, per run?
 -- UlrichKerzel - 11 Jul 2008

Revision 12008-07-11 - UlrichKerzel

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="DataQuality"

LHCb RICH Data Quality

This page summarises the efforts of the RICH Data Quality

Mailing list

A dedicated mailing list has been created: lhcb-rich-dataquality AT cern.ch

Meetings

Meetings will be held every other week on Wednesdays, 10:00 - 12:00 (CERN time) or when necessary.

Tasks

Alignment and callibration

Refractive Index monitoring

Mirror alignment (Antonis + ?)

  • Central mirrors (few thousand events sufficient)
  • All mirrors (~ 1M events needed, needs good tracking as input)

Physics performance

  • Some of the algoritms are also to be used for online monitoring

DLL distributions:

  • Monitor change in DLL distributions online / Brunel

Photon statistics

  • Number of photons per track
  • Number of photons per radiator
as function of luminosity

Exclusive decays

D* -> D pi (Raluca and Guy)

Lambda -> p pi (Oxford)

Phi -> KK (Edinburgh)

KShort (Edinburgh)

J/psi -> mu mu

Conversion gamma -> ee
  • to be investigated if feasable

RICH Data Quality flags

The following flags (or similar) need to be defined:

OK data good for physics analysis, proceed with reconstruction
Investigate I Issues found which can be fixed quickly. Delay reconstruction
Investigate II Issues found which cannot be fixed quickly. Proceed with reconstruction and follow up in re-processing
BAD Data not usable for physics analysis from RICH point of view

Definitions of these flags

to do

To Do

  • Definition of quality flas
  • How to
-- UlrichKerzel - 11 Jul 2008
 
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