Truncation and removal of DAF data corrupt data (summaries OK) #262
Comments
ChristopherRabotin
added
Kind: bug
ChristopherRabotin
added this to the Version 0.4.0: Performance improvements in datasets and various fixes milestone
ChristopherRabotin
added a commit
to ChristopherRabotin/gnss-rtk
that referenced
this issue
Jun 23, 2024
You must copy add the DE440s.bsp file to the data folder for rinex. Rinex expects that this file be available in the AstroData structure. I could not add it myself because Github doesn't allow adding git lfs to public forks WARNING: The DE440s.bsp file is large. Once nyx-space/anise#262 is fixed, you should truncate this DE file to only contain a few years and a few planetary ephemerides instead of the whole solar system
This was referenced Jun 23, 2024
ChristopherRabotin
removed this from the Version 0.4.4: Building BSP files and more CLI functionality milestone
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Describe the bug
When using the anise-cli or the API to modify or truncate a given DAF file, the summary byte pointers are probably messed up as the data cannot be reread correctly. The human-relevant summary data looks nominal however.
To Reproduce
The branch assigned to this issue expands on the
test_spk_truncate_chebytest to check that the data can be correctly queried. In fact, it cannot be correctly queried.Expected behavior
I expect the DAF files to be queriable and to match exactly the original data if not removed or truncated away.
Platform
Linux, Rust, not platform relevant.
The text was updated successfully, but these errors were encountered: