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

Euler Parameter Dataset not checked for existence of rotation data #357

Open
ChristopherRabotin opened this issue Dec 10, 2024 · 1 comment

Comments

@ChristopherRabotin
Copy link
Member

Bug report

Describe the bug

When trying to rotate from the Moon ME frame into J2000, the code does not check to see if the frame 31007 is available as an Euler Parameter.

To Reproduce

Steps to reproduce the behavior:

  1. Load the provided moon_fk.epa and the high precision Moon PA BPC file
  2. Build an Orbit from latlongalt in the Moon ME frame
  3. Attempt to transform this to its J2000 position, and see the error.

Expected behavior

It should correctly compute the rotation.

Platform

Windows

Additional context

Annoyingly, the MOON_ME and MOON_PA frame IDs do not match the ones from the published datasets. Ideally the framework would provide them to avoid having something like:

from anise.astro import Frame
from anise.astro.constants import Frames, CelestialObjects

my_frame = Frame(CelestialObjects.MOON, 31007)
@ChristopherRabotin
Copy link
Member Author

Similarly, the TF file delivered with ANISE does not match the expected BPC file stored on the Nyx Cloud. It should be https://naif.jpl.nasa.gov/pub/naif/generic_kernels/fk/satellites/moon_de440_220930.tf .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant