Currently, the checks that pint_pal does to make sure the "correct" BIPM and ephemeris versions are being used are based on a file tracked as part of pint_pal, namely src/pint_pal/defaults.py. This was appropriate when this code was only being used for a single data release (the NANOGrav 15-year), but different data releases (say IPTA DR3 and NG20) might want to make different choices for these values.
The best solution to this would seem to be to store this configuration in the corresponding data repository instead of the pint_pal repository.
rossjjennings
commented
6 months ago
Currently, the checks that
pint_paldoes to make sure the "correct" BIPM and ephemeris versions are being used are based on a file tracked as part ofpint_pal, namelysrc/pint_pal/defaults.py. This was appropriate when this code was only being used for a single data release (the NANOGrav 15-year), but different data releases (say IPTA DR3 and NG20) might want to make different choices for these values.The best solution to this would seem to be to store this configuration in the corresponding data repository instead of the
pint_palrepository.