Skip to content

WIP: Add GPS time scale - #11269

Closed
taldcroft wants to merge 1 commit into
astropy:mainfrom
taldcroft:time-gps-scale
Closed

taldcroft wants to merge 1 commit into
astropy:mainfrom
taldcroft:time-gps-scale

Conversation

@taldcroft

@taldcroft taldcroft commented Jan 22, 2021 •

Copy link
Copy Markdown
Member

Description

This pull request is to add a new GPS time scale gps_scale which is TAI - 19 sec. This is basically a go-back and change of course from #1879.

This is the first instance of adding a new custom time scale that is not handled by ERFA. At first glance it isn't too hard, though of course if we keep doing this then the transform graph will start getting longer and longer. But for this first one just enumerating the transforms was easy enough.

I do wish we could have a do-over on #1164 and call the time format gps_sec (ala cxcsec) and have gps for the name of the scale. So it goes.

This is a work in progress pending discussion. To do:

  • Docs
  • Tests
  • Changelog

Fixes #11265

@pllim

pllim commented Apr 28, 2021

Copy link
Copy Markdown
Member

Should we move the milestone given the upcoming feature freeze and the WIP state of this PR?

@taldcroft taldcroft modified the milestones: v4.3, v5.0 Apr 30, 2021
@github-actions

github-actions Bot commented Sep 3, 2021

Copy link
Copy Markdown
Contributor

Hi humans 👋 - this pull request hasn't had any new commits for approximately 7 months. I plan to close this in 30 days if the pull request doesn't have any new commits by then.

In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary.

If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock.

If you believe I commented on this pull request incorrectly, please report this here.

@github-actions github-actions Bot added the Close? Tell stale bot that this issue/PR is stale label Sep 3, 2021
@github-actions

github-actions Bot commented Sep 4, 2021

Copy link
Copy Markdown
Contributor

Hi humans 👋 - this pull request hasn't had any new commits for approximately 7 months. I plan to close this in 30 days if the pull request doesn't have any new commits by then.

In lieu of a stalled pull request, please consider closing this and open an issue instead if a reminder is needed to revisit in the future. Maintainers may also choose to add keep-open label to keep this PR open but it is discouraged unless absolutely necessary.

If this PR still needs to be reviewed, as an author, you can rebase it to reset the clock.

If you believe I commented on this pull request incorrectly, please report this here.

@pllim

pllim commented Sep 4, 2021

Copy link
Copy Markdown
Member

Ops, sorry for the double bot post. Hopefully I fixed the bug upstream.

@github-actions github-actions Bot added the closed-by-bot Closed by stale bot label Oct 6, 2021
@github-actions

github-actions Bot commented Oct 6, 2021

Copy link
Copy Markdown
Contributor

I'm going to close this pull request as per my previous message. If you think what is being added/fixed here is still important, please remember to open an issue to keep track of it. Thanks!

If this is the first time I am commenting on this issue, or if you believe I closed this issue incorrectly, please report this here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Close? Tell stale bot that this issue/PR is stale closed-by-bot Closed by stale bot Enhancement time

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GPS time unexpected isot representation

2 participants