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

Update version #356

Merged
merged 5 commits into from
May 9, 2024
Merged

Update version #356

merged 5 commits into from
May 9, 2024

Conversation

ortk95
Copy link
Owner

@ortk95 ortk95 commented May 9, 2024

Pull request checklist

  • Add a clear description of the change
  • Add any new tests needed
  • Run spell check on new text visible to user (documentation, GUI etc.)
  • Check any changes to requirements.txt are reflected in setup.py and conda-forge feedstock
  • Check code passes CI checks (run run_ci.sh or check GitHub Actions)

See CONTRIBUTING.md for more details.

ortk95 added 5 commits May 8, 2024 16:38
`Body.add_satellites_to_bodies_of_interest` will now silently handle any `SpiceSPKINSUFFDATA` errors if that `other_target_id` doesn't have an associated name in the SPICE kernels. This ensures that ID codes for non-existent satellites don't raise unneeded errors.

This is basically equivalent to the previous (pre v1.10.0) behaviour, as before #352 any body without a defined name would raise a `NotFoundError` rather than a `SpiceSPKINSUFFDATA` error.
Make `add_satellites_to_bodies_of_interest` more permissive of SPICE errors
This ensures that if the bodies are the same, the `SpiceBODIESNOTDISTINCT` will be raised first (by the subpoint calculations), rather than potentially getting a more cryptic divide by zero error from the `target_diameter_arcsec` calculation. This shouldn't have any real change in runtime functionality, but should help to make things a little more explicit and clear.
Ensure `SpiceBODIESNOTDISTINCT` is raised first if the target and observer are the same
@coveralls
Copy link

Pull Request Test Coverage Report for Build 9014719657

Details

  • 8 of 8 (100.0%) changed or added relevant lines in 2 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.08%) to 99.578%

Totals Coverage Status
Change from base Build 8984144154: 0.08%
Covered Lines: 2913
Relevant Lines: 2925

💛 - Coveralls

@ortk95 ortk95 changed the title Uodate version Update version May 9, 2024
@ortk95 ortk95 merged commit 9ab04d2 into main May 9, 2024
38 checks passed
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

Successfully merging this pull request may close these issues.

2 participants