WR Timing distribution for Experiments: Monitoring Tools Specification Meeting
Useful links:
RF Timing Vistar: https://op-webtools.web.cern.ch/vistar/?usr=LHCRFTiming
WR Cosmos pages: https://cosmos.cern.ch
Minutes - 7.7.25
Present: ATLAS (Thilo), ALICE(Filip), LHCb (Paolo), CMS (Jeroen, Michelangelo, Jan), ESE (Lilith, Sophie, Jan), CSS (Greg, Aleksandra), Louis (DRD7.3b)
-Current OP Vistar: the cogging part was mostly used at LHC startup and is less used now. The very useful part during operation is the "network" drawing with the green dots and the QPLL status
-the information of the clock source for experiments is important to keep as it is used as a reference for BPTx
-Although the "TTC backbone" will remain operational, the BPTx will have to be switched to the WR system as there are no real way to duplicate the system with 2 different clock sources (BPTx signals are sensitive and cannot be split)
-the comparison between WR BC and BPTx will have to be implemented and monitored with history as this information is crucial to understand the real drift of the WR BC vs beam. Current display on the OP Vistar is too slow and difficult to exploit
-a new structure in DIP will have to be proposed for the WR distribution. Each of the experiments will implement it the same way to ease the development of the new vistars
-we should also make sure that the BPTx values are properly logged into Timber
-Network Vistar: should show a digested version of the Mondi tool. The criteria and parameters to be used to give a good & digested interpretation of the status of each switch in the way between GPS, Gmswitch and the Exp end node will be discussed with Ioan's team. 6 switches are one the way from the Grand Master to each experiment
-Experiment specific Dashboard: Greg & Ola proposed that the Dashboard could be interactive (for each experiment to customize its prefered setup to be displayed on the main monitoring screens - using menus and drag&drop solutions ). This has been appreciated by the experiments, but we should also make sure the interactivity is not required for the Dashboard to be operational (the default setting should be already complete)
-a similar dashboard should be proposed for each lab connected to the WR network (typically 1 or 2 per experiment)
-Suggestions from experiments:
-a logbook related to WhiteRabbit activities would be very useful
-a mail should be sent to Timing Experts and Run coordinators when a major action impacting white rabbit is foreseen
-labs connectivity: ongoing but quite slow. Should be finished around september
-ACTIONS:
-Aleksandra to propose a first mock up of the various display panels end of September, using the CMS system installed in CMS as a baseline
-she will need data from the RF team in order to know which parameters/registers are available on the WR2RF (Sophie to push as well)
-She will contact Lilith to see how to put this in place, get the names of the equipment to access, etc
-Aleksandra and Sophie to define a new branch of the DIP tree to add data expected from the experiment for White Rabbit