Pith. sign in

REVIEW 4 major objections 6 minor 9 references

The inter-cluster time synchronization systems within the Baikal-GVD detector

T0 review · 4 major / 6 minor · reviewed 2026-08-14 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗ Review JSON

Pith's one-line read Baikal-GVD's five operating clusters share one timeline to better than 5 nanoseconds, according to in-situ tests reported in this paper.

desk verdict Useful engineering report on Baikal-GVD's inter-cluster timing, with a plausible 5 ns claim that the paper's own cross-checks support only loosely. read the letter →

arxiv 1908.05533 v1 pith:GBGKCCFZ submitted 2019-08-15 physics.ins-det astro-ph.HE

Baikal-GVD Collaboration: A.D. Avrorin , A.V. Avrorin , V.M. Aynutdinov , R. Bannash , I.A Belolaptikov , V.B. Brudanin , N.M. Budnev , G.V. Domogatsky
show 44 more authors
A.A. Doroshenko R. Dvornicky A.N. Dyachok Zh.-A.M. Dzhilkibaev L. Fajth S.V Fialkovsky A.R. Gafarov K.V. Golubkov N.S. Gorshkov T.I. Gress R. Ivanov K.G. Kebkal O.G. Kebkal E.V. Khramov M.M. Kolbin K.V. Konischev A.V. Korobchenko A.P. Koshechkin A.V. Kozhin M.V. Kruglov M.K. Kryukov V.F. Kulepov M.B. Milenin R.A. Mirgazov V. Nazari A.I. Panfilov D.P. Petukhov E.N. Pliskovsky M.I. Rozanov E.V. Rjabov V.D. Rushay G.B. Safronov B.A. Shaybonov M.D. Shelepov F. Simkovic A.V. Skurikhin A.G. Solovjev M.N. Sorokovikov I. Stekl O.V. Suvorova E.O. Sushenok V.A. Tabolenko B.A. Tarashansky S.A. Yakovlev
This is my paper · ORCID
classification physics.ins-detastro-ph.HE
keywords Baikal-GVDneutrinotelescopetimesynchronizationWhiteRabbitSSBTCherenkovdetectorinter-clustercalibration
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

Baikal-GVD is a cubic-kilometre neutrino telescope being deployed in Lake Baikal as an array of independent clusters, and this paper is about making those clusters share one clock. A high-energy neutrino can deposit light in more than one cluster, so merging such events requires the cluster timestamps to agree. The paper argues that the inter-cluster synchronization accuracy does not exceed 5 ns, using two independent systems: White Rabbit and the detector-specific SSBT. This matters because 5 ns matches the detector's 200 MHz sampling step, so events spanning cluster boundaries can be reconstructed on a single timeline. If true, the five currently operating clusters—and the nine planned for the first stage—can be treated as one detector for event reconstruction.

What carries the argument

The machinery is a pair of independent timestamping networks installed in the cable cap of each cluster. White Rabbit, a fibre-optic synchronization technology, stamps each cluster trigger signal through a DIO board, while SSBT assigns its own time marks using a thermally stabilised rubidium master clock. A per-second pulse generated by White Rabbit is fed into SSBT, letting the two systems measure each other's clock offsets; connecting an external rubidium reference to White Rabbit reduces the PPS timing spread from about 10 ns RMS to about 5 ns RMS. The absolute check is a laser source whose flashes reach clusters 2 and 3 with a known 18.6 m path difference, so the measured inter-cluster delay should be about 85 ns.

What would settle it

Re-measure the laser-to-cluster distances with independent survey and check whether the 18.6 m difference is accurate to about 1 m; if its uncertainty exceeds roughly 1 m (about 5 ns in water), the 81–83 ns measured delays cannot by themselves substantiate the claimed 5 ns absolute synchronization accuracy.

Watch

Extended reading notes

Core claim

The central claim is that the two independent synchronization systems installed on all five operating clusters of Baikal-GVD keep the cluster trigger timestamps aligned to better than 5 ns. The evidence is an in-situ calibration: a laser source illuminates clusters 2 and 3, whose distances from the laser differ by 18.6 m, corresponding to about 85 ns of light travel time. White Rabbit records $81 \pm 3$ ns between the two clusters and SSBT records $83 \pm 5$ ns, both consistent with the geometric expectation. The paper also measures the SSBT fiber-optic delay between the two clusters as $9.32 \times 10^{-7}$ s using the per-second pulse output of the White Rabbit board. Taken together, the authors conclude that the relative and absolute inter-cluster timing accuracy does not exceed 5 ns.

Load-bearing premise

The laser calibration assumes the 18.6 m difference in distance from the light source to clusters 2 and 3 is known to better than the claimed few-nanosecond accuracy, but the paper does not report the survey uncertainty of that distance.

Editorial extensions

If this is right

  • If the 5 ns accuracy holds, events depositing light in several clusters can be merged into one reconstructed event on a common timeline.
  • The two independent synchronization systems provide mutual verification, so a fault in one does not silently corrupt the other's timestamps.
  • The achieved accuracy matches the detector's 200 MHz sampling step, meaning the existing electronics can use the cross-cluster alignment without extra corrections.
  • The same deployment method extends to the planned nine-cluster array, since each cluster receives the same per-second pulse cross-check and laser calibration.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • The paper's 5 ns statement is an upper bound set partly by the SSBT time resolution; a higher-rate reference would likely show the White Rabbit chain holds the clusters to tighter alignment, but that is not demonstrated here.
  • Instead of a single laser position, coincident atmospheric muons crossing several clusters would map all pairwise cluster delays and show whether the 5 ns accuracy holds across the whole array, not only the cluster 2–3 pair.
  • When the array grows to nine clusters, each new cluster needs its own survey tie; if the survey uncertainty is kept below about 1 m, the same per-second pulse and laser checks should transfer the demonstrated accuracy.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

4 major / 6 minor

Summary. The paper describes the inter-cluster time synchronization system of the Baikal-GVD neutrino telescope, which consists of two independent systems: the detector-specific SSBT and the widely used White Rabbit (WR). Both systems assign time marks to trigger signals from different clusters, enabling multi-cluster event merging. The authors report in-situ checks: a PPS cross-comparison showing an RMS of ~5 ns when an external rubidium clock is used, and a laser calibration test in which the measured inter-cluster time differences (81 ± 3 ns for WR, 83 ± 5 ns for SSBT) are consistent with an expected ~85 ns delay corresponding to an 18.6 m path-length difference. The paper concludes that the accuracy of inter-cluster synchronization does not exceed 5 ns.

Significance. If the 5 ns claim is robust, it is an important practical result for Baikal-GVD: it demonstrates that the dual-system synchronization architecture meets the requirements imposed by the 200 MHz sampling of the detector, and it gives confidence in multi-cluster event reconstruction. The paper's strength is its use of two independent timing systems and an external rubidium reference, along with an absolute laser-based cross-check. The measurements are internally consistent and the quoted statistical errors are modest. However, the absolute accuracy claim is not fully supported by the evidence as presented: the laser test relies on an expected delay whose systematic uncertainty is not documented, and the PPS test is a relative comparison. The headline conclusion therefore overreaches what the data currently establish.

major comments (4)
  1. [Section 3 (laser calibration, Figs. 3.2–3.3)] The expected delay of ~85 ns is derived from an 18.6 m path-length difference, but the manuscript does not report the survey uncertainty on this distance nor the optical group velocity used for the distance-to-time conversion. A 1 m uncertainty in the distance corresponds to roughly 4.5 ns of propagation time in water, and a comparable uncertainty in the group velocity would have the same effect; both are already at the scale of the claimed 5 ns accuracy. As a result, the agreement between the measured delays (81 ± 3 ns WR, 83 ± 5 ns SSBT) and the expected value cannot be distinguished from a chance agreement, and the absolute 5 ns bound is not established by this test.
  2. [Section 3 (PPS cross-check, Fig. 3.1)] The PPS measurement with an RMS of ~5 ns quantifies the relative disagreement between the WR and SSBT timestamps; it shows that the two systems track each other but does not tie the combined timeline to an absolute external reference. The conclusion that 'the accuracy of the inter-cluster synchronization doesn't exceed 5 ns' therefore overstates what this test alone can demonstrate. Additionally, the text states that the SSBT time resolution is ~10 ns 'with the possibility of improvement up to 5 ns' while reporting a PPS RMS of ~5 ns; the relationship between these two numbers needs clarification (for example, whether the quoted resolution refers to raw timestamps and the 5 ns RMS is obtained after some calibration).
  3. [Section 5 (Conclusion)] The conclusion that the accuracy of the inter-cluster synchronization does not exceed 5 ns is stronger than the evidence presented. The laser test yields statistical uncertainties of 3–5 ns, and the systematic uncertainty in the expected delay is unquantified; the PPS RMS is a relative, not absolute, measure. The claim should be qualified to state what has actually been measured, for example 'the relative agreement between WR and SSBT is characterized by ~5 ns RMS, and the laser test is consistent with expectations within the quoted statistical uncertainties,' unless an explicit error budget for the absolute calibration is added.
  4. [Section 3 (Figs. 3.1 and 3.3)] The manuscript does not report event counts or the data-taking period for the distributions shown in Figs. 3.1 and 3.3. These numbers are needed to assess the statistical robustness of the quoted RMS and mean values and to determine whether the small differences between the WR (81 ± 3 ns) and SSBT (83 ± 5 ns) results are significant. Adding this information, or explaining its absence, would strengthen the quantitative basis of the paper.
minor comments (6)
  1. [Section 2] There is a typo in the description of White Rabbit: 'SPEC (Simple PCIe FMC сarrier) joint' contains a duplicated word and a misspelled word; also 'DIOWRSPEC' should be written as 'WR SPEC DIO board' or 'DIO WR SPEC'.
  2. [Section 3] The sentence 'the clock travel difference is 50 ns per 1 s' is unclear; it should specify whether this is the relative drift rate between the WR and SSBT clocks and how it was measured.
  3. [Section 3] The expected delay of ~85 ns for an 18.6 m path difference is only approximate: using a typical water group index of 1.34–1.35 gives about 82–84 ns. The paper should state the value and uncertainty of the group velocity or refractive index used for this conversion.
  4. [General] An explicit error budget table summarizing the contributions to the synchronization accuracy (trigger time reference, WR and SSBT resolutions, clock stability, fiber calibration, geometry) would greatly improve the transparency of the central claim.
  5. [References] Reference [6] appears to concatenate two conference papers (ICALEPCS 2009 and ISPCS 2018); these should be separate references with distinct URLs/DOIs.
  6. [Section 2] The statement that 'During the period from April to June 2019 there weren’t any failures of any system components' is relevant to reliability but not to the accuracy claim; consider moving it to a reliability section or providing a quantitative context.

Circularity Check

0 steps flagged · score 1.0 of 10

No significant circularity: the 5 ns inter-cluster synchronization accuracy claim is based on in-situ PPS and laser comparisons that are independent of the claimed result.

full rationale

The paper's central claim (Section 5: 'the accuracy of the inter-cluster synchronization doesn't exceed 5 ns') is supported by two measurements in Section 3: the PPS comparison between the independent WR and SSBT systems (Fig. 3.1), which gives an RMS of ~5 ns in grand-master mode, and the laser calibration in which the measured inter-cluster delays (81 ± 3 ns for WR, 83 ± 5 ns for SSBT) are compared with the expected ~85 ns delay from an 18.6 m geometric path difference. Neither measurement is defined in terms of the conclusion. The SSBT fiber-delay calibration (9.32e-7 s for clusters 2 and 3) is a standard correction applied before the laser estimate, and the laser benchmark (distance difference) is external to the synchronization systems. The paper's assumed component errors (WR ~1 ns, SSBT ~10 ns with improvement to 5 ns) are stated as contributing factors, not as the measured accuracy itself. The unquantified survey uncertainty of the 18.6 m path difference could weaken the absolute accuracy claim, but that is a systematic-error limitation, not a circular derivation.

Assumptions & free parameters 0 free parameters · 3 assumptions · 0 invented entities

The central claim uses measured calibration values (such as the SSBT fiber-optic delay 9.32e-7 s for clusters 2 and 3), but these are direct measurements, not parameters fitted to make the conclusion true. No free parameters, no invented entities, and no circularly defined quantities are introduced; the axioms listed are the standard physical and hardware assumptions on which any such timing calibration depends.

assumptions (3)
  • standard math The speed of light in water is used to convert the 18.6 m distance difference to an expected time difference of ~85 ns.
    Section 3 uses the geometric path difference to predict the laser arrival time difference; this assumes the standard refractive properties of the medium.
  • domain assumption The White Rabbit and SSBT time stamps correctly represent the arrival times of the trigger signals or PPS pulses.
    The entire cross-calibration relies on the time stamping electronics in both systems working as specified; the paper describes the hardware but does not independently verify its absolute latency.
  • domain assumption The laser flashes are simultaneous for both clusters and the cluster geometry is known to sufficient accuracy.
    The laser calibration comparison uses the stated 18.6 m distance difference without an uncertainty estimate; this is the load-bearing geometric assumption.

how reviews work

0 comments
Cite this review

Pith. "Pith review of The inter-cluster time synchronization systems within the Baikal-GVD detector." pith.science (2026). https://pith.science/paper/GBGKCCFZ

@misc{pith2026190805533,
  author       = {Pith},
  title        = {Pith review of: The inter-cluster time synchronization systems within the Baikal-GVD detector},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/GBGKCCFZ}},
  note         = {Machine review of arXiv:1908.05533}
}
read the original abstract

Currently in Lake Baikal, a new generation neutrino telescope is being deployed: the deep underwater Cherenkov detector of a cubic-kilometer scale Baikal-GVD. Completion of the first stage of the telescope construction is planned for 2021 with the implementation of 9 clusters. Each cluster is a completely independent unit in all the aspects: triggering, calibration, data transfer, etc. A high-energy particle might leave its trace in more than a single cluster. To be able to merge events caused by such a particle in more clusters, the appropriate inter-cluster time synchronization is vital.

Figures

Figures reproduced from arXiv: 1908.05533 by the authors.

Figure 2
Figure 2. Synchronization and data transfer systems of Baikal-GVD in 2019. [PITH_FULL_IMAGE:figures/full_fig_p003_2.png] view at source ↗
Figure 2
Figure 2. Scheme of electronics of cable cap [PITH_FULL_IMAGE:figures/full_fig_p004_2.png] view at source ↗
Figure 3
Figure 3. shows the location of the Baikal-GVD clusters and the laser calibration source. The [PITH_FULL_IMAGE:figures/full_fig_p005_3.png] view at source ↗
Figures from the paper (1 more)
Figure 3
Figure 3. Figure 3: Time differences distribution between laser flash events on Cluster 2 and Cluster 3 [PITH_FULL_IMAGE:figures/full_fig_p006_3.png]

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

9 extracted references · 9 canonical work pages

  1. [1]

    Avrorin, V

    A. Avrorin, V . Aynutdinov, I. Belolaptikov et al., The Gigaton volume detector in lake Baikal, Nuclear Instruments and Methods in Physics Research, Section A: Accelerators, Spectrometers, Detectors and Associated Equipment 2011 vol.639 #1 p.30–32

    work page 2011

  2. [2]

    Avrorin, A.D

    A.V . Avrorin, A.D. Avrorin, V .M. Aynutdinov et al., The prototyping/early construction phase of the BAIKAL-GVD project, Nuclear Instruments and Methods in Physics Research, Section A: Accelerators, Spectrometers, Detectors and Associated Equipment 2014 vol.742 p.82–88

    work page 2014

  3. [3]

    Avrorin, A.D

    A.V . Avrorin, A.D. Avrorin, V .M. Aynutdinov et al., Baikal-GVD results, EPJ Web of Conferences 2016 vol.116 p.11005

    work page 2016

  4. [4]

    Aynutdinov, R

    V .M. Aynutdinov, R. Bannasch et al., The data acquisition system for Baikal-GVD , EPJ Web of Conferences 2016 vol.116 p.5004

    work page 2016

  5. [5]

    Avrorin, A.V

    A.D. Avrorin, A.V . Avrorin, V .M. Aynutdinov et al., The optical detection unit for Baikal-GVD neutrino telescope, EPJ Web of Conferences 2016 vol.121 p.5008

    work page 2016

  6. [6]

    Serrano, et al., The White Rabbit Project., ICALEPS 2009, ICALEPCS TUC004, 2009 http://accelconf.web.cern.ch/accelconf/icalepcs2009/papers/tuc004.pdf M

    J. Serrano, et al., The White Rabbit Project., ICALEPS 2009, ICALEPCS TUC004, 2009 http://accelconf.web.cern.ch/accelconf/icalepcs2009/papers/tuc004.pdf M. Lipiński, et al., ISPCS2018, CERN, Switzerland, 2018

    work page 2009

  7. [7]

    Time Synchronization with White Rabbit - Experience from Tunka-HiSCORE

    R. Wischnewski, M. Brückner and A. Porelli, “Time Synchronization with White Rabbit - Experience from Tunka-HiSCORE” in Proceed . 34th International Cosmic Ray Conference, 2015, The Hague, The Netherlands, PoS (ICRC2015) 1041

    work page 2015

  8. [8]

    Brückner and R

    M. Brückner and R. Wischnewski, A time stamping TDC for SPEC and ZEN-platforms based on White Rabbit, ICALEPS-2017, doi:10.18429/JACoW-ICALEPCS2017-THPHA088 Conference, 2015, The Hague, The Netherlands, PoS (ICRC2015) 1041

    work page doi:10.18429/jacow-icalepcs2017-thpha088 2017

Show all 9 references
  1. [9]

    Wlostowski, https://www.ohwr.org/project/whiterabbit/uploads/ae3282acd8f9f6c5a9067b061202277d/ wr_external_reference.pdf 7

    T. Wlostowski, https://www.ohwr.org/project/whiterabbit/uploads/ae3282acd8f9f6c5a9067b061202277d/ wr_external_reference.pdf 7

Pith tools

Reviewed August 14, 2026 · model on record in the stance chip above.