Open translunar opened 1 month ago
I found a workaround, which is to load a pck11.pca, but this was hard to do because the tutorial link is still to the v0.3 version of that file, and so I had to do a little URL hacking to figure out what I needed to wget.
Hi Juno,
Thanks for the bug report. The tutorials need some updating to the paths, and I suspect the readme might still point to version 3 of the files: I'll fix this in #341.
Would it be possible for you to share the files used for creating this planetary constants input file? I'd like to reproduce the issue: from your code, it seems like everything should have worked.
Thanks
They are as listed: pck00010.tpc
and gm_de440.tpc
. These should be available from NAIF. Are you asking for some other file?
Yes: would you have a copy of the my_constants.tpc
created by the call to convert_tpc
so I can open it in the GUI? Both pck08.pca
and pck11.pca
are built using that same call in the tests, and they both include body 301.
PCK08:
PCK11:
The GUI is prebuilt for Linux and Windows on Github: https://github.com/nyx-space/anise/actions/runs/11367543965
Yeah. Oddly SPICE isn't loading 301 or 399 from pck 10 either, though I see the variables in the file. Here is the output file: constants.tpc.txt
And here is the input: pck00010.tpc.txt
Hey Juno,
Has the pck 11 or 08 versions been working for you? I can investigate this issue further at a later date. I'm also a bit surprised that the data present neither in SPICE nor ANISE since it sure looks present in the original tpc file.
Bug report
Describe the bug
I cannot access lunar planetary constants or frame data through anise.
To Reproduce
Steps to reproduce the behavior:
and then
almanac.describe(spk=True, bpc=True, planetary=True)
does not list 301. I believe this should be inde440.bsp
, but maybe I'm missing something. I spent a bunch of time staring at the documentation for MetaAlmanac and Almanac and couldn't figure this out.Expected behavior
I would expect loading the planetary constants and BPC files should yield planetary data for 301. I should also be able to get the MOON_J2000 frame, but I get the following error with
almanac.frame_info(Frames.MOON_J2000)
:Platform
Linux, Anise 0.4.4
Additional context
This comes from the tutorial, which suggests the following should work:
The tutorial may need to be updated, or else this code simply doesn't work.