Repository navigation
Automate updating IERS_B and LeapSecond files whenever a release is made #1697
Description
Just a reminder, so we do not need to do something like #1693 every time.
EDIT: we may also want to consider more generally whether we really want to have this 3 MB file as part of the package, or whether there should be some automatic download upon first use of UT1 (or sidereal time or local coordinates).
EDIT: this now also applies to the built-in LeapSecond.dat file.
Activity
astrofrog commentedon May 3, 2014
@mhvk - re-scheduling this to 1.0.0, but does the file need to be updated by hand for 0.4?
mhvk commentedon May 3, 2014
@astrofrog - yes, you're right; see #2428
mhvk commentedon Jan 13, 2015
Removed the milestone, as I know I am not the right person to do this. However, this, and the automatic downloading/updating of IERS A are important; see #3274 and discussion therein.
mhvk commentedon Jan 13, 2015
Also see #3275 for the download of IERS A; I guess this issue should strictly be for the automatic update of IERS B with astropy releases.
pllim commentedon Oct 30, 2019
Is this still relevant?
mhvk commentedon Oct 30, 2019
I fear so. Indeed, we should now also ensure we always ship with the latest leap-second table...
pllim commentedon Oct 30, 2019
Until this can be automated, should it be documented in release procedures document?
mhvk commentedon Oct 30, 2019
Yes, good idea...
pllim commentedon Oct 30, 2019
@mhvk , do you want to open a PR, as you would understand the best where we should add that action item in the release time line.
[-]Post-0.3: automate updating IERS file whenever a release is made[/-][+]Automate updating IERS_B and LeapSecond files whenever a release is made[/+]update iers for release
pllim commentedon Mar 29, 2022
We now have https://github.com/astropy/astropy/blob/main/.github/workflows/update_iers.yml . Can we close this?
mhvk commentedon Jan 11, 2024
Closing since we now have our
astropy-ierspackage.