You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for maintaining the Apexpy package. I'm very happy with the package, but unfortunately, the Apex class cannot be initialized after the end of 2024 due to the end of the underlying IGRF-13 model. It would be very appreciated if you could provide a new release of Apexpy with the latest IGRF-14 coefficients.
All the best.
Describe the bug
The Apex class cannot be initialized for a date after 2025.0 because the underlying IGRF-13 is only valid until the end of 2024.
To Reproduce
The following leads to a crash of the running Python kernel:
Open a Python session and run: apexpy.Apex(date=2025.1)
Additional context
A new version of the IGRF model is available (IGRF-14), which can be used to update the builtin grids.
The text was updated successfully, but these errors were encountered:
Hi @ancklo you are correct! We currently have a pull request open that will address this problem #147. In the meantime, you can use the Test PyPi installation or the pull request version, which does have IGRF-14. Sorry for the inconvenience I hope to have it available later this week.
Hello,
Thank you for maintaining the Apexpy package. I'm very happy with the package, but unfortunately, the Apex class cannot be initialized after the end of 2024 due to the end of the underlying IGRF-13 model. It would be very appreciated if you could provide a new release of Apexpy with the latest IGRF-14 coefficients.
All the best.
Describe the bug
The Apex class cannot be initialized for a date after 2025.0 because the underlying IGRF-13 is only valid until the end of 2024.
To Reproduce
The following leads to a crash of the running Python kernel:
apexpy.Apex(date=2025.1)
Additional context
A new version of the IGRF model is available (IGRF-14), which can be used to update the builtin grids.
The text was updated successfully, but these errors were encountered: