Repository navigation
Towards the ultimate in Time precision: BIPM17 corrections #8130
Description
Talking to @luojing1211 from PINT (and mostly to remind ourselves), one additional correction that pulsar timing people make happens for conversion to TT -- which appears to have different versions, the most current being TT(BIPM17) [1]. It can be the difference between pulsar timing arrays detecting gravitational waves or not... We should follow the BIPM, though may need to think about how to ensure that one can also use pure-ERFA/SOFA.
[1] ftp://ftp2.bipm.org/pub/tai/ttbipm/TTBIPM.17
EDIT: link to BIPM sercive responsible for this: https://www.bipm.org/en/bipm-services/timescales/
p.s. Related precision issues: improve interpolation in IERS tables (#1803) and GPS-UTC corrections (#2134)
Activity
pllim commentedon Nov 15, 2018
To ensure future accessibility to the cited work, is there a proper reference other than FTP link? If so, please also include that in this issue. Thanks!
mhvk commentedon Nov 15, 2018
@pllim - OK, added link to BIPM time service above (it works in conjunction with IAU). Let me also ping @taldcroft to think about what should be default. Options:
TT(BIPM)(as we do for IERS). Files are not very big, but it means that results might very slightly change (10s of ns level) with time.TTone uses.I think we need the context manager, and would go for a default of "best possible".