Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WARNING: Tried to get polar motions for times after IERS data is valid (need clearer message in warning on how to set software default) #12608

Closed
mzechmeister opened this issue Dec 18, 2021 · 12 comments · Fixed by #12625

Comments

@mzechmeister
Copy link

Currently, I get:

WARNING: Tried to get polar motions for times after IERS data is valid.
Defaulting to polar motion from the 50-yr mean for those.
This may affect precision at the 10s of arcsec level [astropy.coordinates.builtin_frames.utils]

raised in:

warnings.warn(wmsg.format('after'), AstropyWarning)

Which files do I need to update (and how) to resolve this warning?

The warning message could be made more user friendly.

@mzechmeister
Copy link
Author

After quite some debugging, I think the problem was caused by an url with is not updated anymore: iers_conf.iers_auto_url = 'https://astroconda.org/aux/astropy_mirror/iers_a_1/finals2000A.all'
I switched to:
iers_conf.iers_auto_url = 'https://datacenter.iers.org/data/9/finals2000A.all'
Probably, I spotted the link here: astropy/astropy-iers-data#20.

Thus the warning could a give hint to check this file.

@pllim
Copy link
Member

pllim commented Dec 21, 2021

@mhvk , would an extra message to remind user to check conf.iers_auto_url completely cover such a problem or can this warning also be triggered by other causes?

@mhvk
Copy link
Contributor

mhvk commented Dec 21, 2021

Yes, I think we could expand the warning. But we should also move the link back!

@pllim
Copy link
Member

pllim commented Dec 22, 2021

@mhvk , can you please clarify what you mean by "move the link back"? It's been a while since I looked at that part of the code.

@pllim
Copy link
Member

pllim commented Dec 22, 2021

@mzechmeister
Copy link
Author

@pllim, I prefer here to only comment.

@mhvk
Copy link
Contributor

mhvk commented Dec 22, 2021

@pllim - I have this vague memory that we had to change the link to this astroconda one because the regular finals200A.all became unavailable. Though I think that was actually a link to some .mil site to the astrometry group there. Of course, also fine to just ensure astroconda is kept up to date - I'm not sure who's responsible for that, though...

@pllim
Copy link
Member

pllim commented Dec 22, 2021

I am now confused. We don't point to astroconda.

IERS_A_URL = 'ftp://anonymous:mail%40astropy.org@gdc.cddis.eosdis.nasa.gov/pub/products/iers/finals2000A.all' # noqa: E501

@mhvk
Copy link
Contributor

mhvk commented Dec 22, 2021

@mzechmeister - now I'm super-confused too - where did your configuration come from? Is that default IERS_A_URL changed in making the conda astropy packages?

@mzechmeister
Copy link
Author

It seems the problem started with #9427, and, I guess, I used astropy/astropy-iers-data#20 to solve my problem mzechmeister/serval#33 (comment). It's hard to keep track, when the url changes all the time.

@mhvk
Copy link
Contributor

mhvk commented Dec 22, 2021

OK, that makes sense, and though the URL changes are largely out of our control, I'm sorry it led to your problems! Bottom line, I think, is that it would be useful for the warning message to point to some documentation about how to solve this...

@pllim
Copy link
Member

pllim commented Dec 22, 2021

All said though, it is recommended that you use the default, because we test it in the CI. We are not responsible for custom settings.

@pllim pllim changed the title WARNING: Tried to get polar motions for times after IERS data is valid. WARNING: Tried to get polar motions for times after IERS data is valid (need clearer message in warning on how to set software default) Dec 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants