This repository contains the data exchange format for optical fiber link clock comparisons.
This document as been prepared for the European Partnership on Metrology Project TOCK.
This data format was developed for the European Metrology Programme for Innovation and Research (EMPIR) Projects OFTEN and ROCIT. The format implements the universal formalism presented by Lodewyck et al. (2020) and handles both microwave clocks, optical clocks and designed oscillators (DOs) such as ultrastable cavities and signals disseminated by optical fiber links.
Clock comparison is understood to mean measuring the ratio of the frequencies of two clocks. Time transfer and time comparison are beyond the scope of this format.
Participating laboratories designate a number of oscillators that form the user-level nodes of the network. User-level links relate the frequencies of pairs of these designated oscillators. When labs compare clocks, they use an agreed time window, e.g. 1 second, during which each measures their clock against a local designated oscillator. User-level link data is shared in a central repository and can be accessed by other users. Combining the retrieved and measured data is used to relate the two local designated oscillators across the agreed time window, potentially through a series of intermediate designated oscillators. This allows the frequency ratio of the clocks to be determined. The frequency fluctuations of intermediate designated oscillators should cancel out in the ratio of clock frequencies.
The data exchange is based on the publication of a comparator output for each pair of adjacent oscillators.
The comparator output
where the nominal frequency ratio
NOTE: The relation between the comparator output and the transfer beat is exposed in a different way than in Lodewyck et al. (2020). The aim of the presentation chosen here is to seamlessly publish in a unified way comparator outputs and transfer beats.
NOTE: In general
$\Delta_{A\rightarrow B} \neq - \Delta_{B\rightarrow A}$ .
NOTE: With
$s_B = 1$ , the comparator output is the same as the transfer beat, typically used in fiber links and optical combs.
NOTE: With
$s_B = \hat{\nu}^0_B$ , the oscillator B nominal frequency, the comparator output is given in relative frequency units typical for microwave and optical clocks.
The data format is defined by the following set of requirements:
-
A file, or a set of files, located in the data's main directory report on the chosen constants and related information. This file is written in YAML, and has the extension .yml. A single file for all institutes may be used, or different files for each institute, the latter being equivalent to the former after concatenating all the YAML files. The files contain entries specifying the constant used to produce the comparator output
$\Delta_{A\rightarrow B}$ , using the following format:name
comparator name, in the form INSTITUTEB_OSCB-INSTITUTEA_OSCA
String numrhoBA
numerator of the nominal frequency ratio $\rho^0_{B,A}$ Arbitrary precision floating point denrhoBA
denominator of the nominal frequency ratio $\rho^0_{B,A}$ Arbitrary precision floating point sB
scaling factor Double precision floating point nu0A
nominal value $\hat{\nu}^0_A$ for the frequency of A (optional)Arbitrary precision floating point grsA
Gravitational redshift correction for the oscillator A, in relative units (optional) Float uA_sys
fractional uncertainty of the oscillator A (optional) Float nu0B
nominal value $\hat{\nu}^0_B$ for the frequency of B (optional)Arbitrary precision floating point grsB
Gravitational redshift correction for the oscillator B, in relative units (optional) Float uB_sys
fractional uncertainty of the oscillator B (optional) Float interval
Duration of each measurement, in seconds (optional) Float lag
Fractional timetag location wrt the interval (1=end of the interval) (optional) Float weighting
Weighting function of the frequency counter (optional) "lambda" or "pi" ref_osc
Local reference oscillator (optional) String NOTE: The comparator output does not depend on the
nu0A
ornu0B
values. They are only used for data processing.NOTE:
nu0A
ornu0B
values should be given for accurate oscillators (discrepancy between its actual frequency and its nominal frequency must be$\lessapprox 10^{-13}$ ), such as masers and optical clocks.NOTE: For input data, it is reccomended to have A as the accurate oscillator for which to specify
nu0A
,grsA
anduA_sys
.nu0B
,grsB
anduB_sys
are there for simmetry.NOTE: This specification does not allow to change the parameters such as the nominal frequency ratio in the course of a campaign. This is deemed sufficient for most cases.
-
The comparator output
$\Delta_{A\rightarrow B}$ is stored in data file or files located in a folder calledINSTITUTEB_OSCB-INSTITUTEA_OSCA
. Any file name is acceptable, provided the lexicographic order of the filename matches the chronological order of the data. The data files contain:-
An optional header, whose lines must start with
#
. The content of the header is chosen by the person who produces that data, and is purely informative, i.e. not necessary to process the data. -
Column 1: date and time in Modified Julian Date (MJD)
-
Column 2: comparator output
$\Delta_{A\rightarrow B}$ -
Column 3: validity flag (0 = invalid, 1 = valid but experimental, 2 = valid)
-
Column 4: time-varying systematic uncertainty (optional, for accurate clocks only)
-
Column >4: custom information. Not used in automatic data analysis scripts.
-
With the examples listed in the table below, we show that the file format defined in section 1.1 can ac- commodate with many different physical representations of the data, including the transfer beats that are currently shared, but also pure optical to optical frequency ratios. These representations are selected by choosing appropriate NFRs, scaling factor, and reference oscillators.
Ref. | Physical interpretation of the comparator | |||
---|---|---|---|---|
+1 | local RF | Beatnote | ||
-1 | local RF | Beatnote with opposite sign | ||
local RF | Beatnote in relative units, with respect to |
|||
+1 | local RF | Transfer beat with prefered sign convention (A = clock; B = DO) | ||
-1 | local RF | Transfer beat with opposite sign (A = clock; B = DO) | ||
+1 | A | Frequency of B, referenced to A (e.g., A is a maser or optical clock) | ||
A | Frequency of B, referenced to A (e.g., A is a maser or optical clock), relative units | |||
local RF | Difference of reduced frequency ratios, using an external reference x | |||
A | Relative systematic correction ( |
NOTE: The reference oscillator must be accurate, in the sense that the discrepancy between its actual frequency and its nominal frequency must be
$\lessapprox 10^{-13}$
The frequency ratios between remote oscillators can be calculated from the comparator outputs using the
equations:
where the numrhoBA
and denrhoBA
in the yaml file).
NOTE: In the special case where nominal frequencies ratios are consistently defined from a set of agreed upon nominal frequencies (
$\rho^0 _{B,A} = \hat{\nu}^0_B/\hat{\nu}^0_A$ and$s_B = \hat{\nu}^0_B$ ), remote reduced frequency ratios can be computed with a simple sum of comparator outputs. The example implementation of a clock network proposed in the Appendix F of Lodewyck et al. (2020) is written using this convention.
See the Example folder for fictitious data used to test the data format before the March 2023 campaign of the project ROCIT.