Choose timezone
Your profile timezone:
[In-situ timing] Subgroup meeting #2
→
Europe/Zurich
Description
https://cnrs.zoom.us/j/99656897436?pwd=UHcyWnRORnNoQmMzZ2JLeXNrSXZ4QT09
ID: 996 5689 7436
pwd: 9mUAMU
Points addressed/discussed during the meeting:
- Is the availability of process D data (dynamic positioning) mandatory to trigger the intra-DOM calibration (process E)? A priori no, one could consider trigger the process E as soon as the process B (static calibration) data are available. To be rediscussed in the context of the workflow optimisation by Valentin/Alfonso.
- How often should the in situ timing updated? A priori, it should be very stable. Only hardware changes (or firmware tbc) could really impact the intra-DOM calibration.
Currents limitation:
- the knowledge of the list of runs relevant for the calibration is currently a concern. It should be largely improved with the new operation model: validation by the run coordination at the operation meeting every wednesday, information propagation via dedicated defect, formal signoff by the run coordination/operation teams/calibration experts. The infrastructure is +/- available. We just need to agree on the decision process. This is also part of the workflow optimisation by Valentin/Alfonso.
- the retrieval of the which reference PMT was used for the intra-DOM calibration in lab is also a concern. As of today, one needs to browse in the elog https://elog.km3net.de/DU+Integration/ This is not viable with the increasing production. This should be addressed in a machine-readable way. Some developments have also been initiated by BT following a request by Valentin; to be investigated if the production data could be also made available.
There are minutes attached to this event.
Show them.
