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
Fixed offset calculation in Background2D.to_3d #4728
Conversation
Signed-off-by: cgalelli <claudio.galelli@obspm.fr>
Codecov Report
@@ Coverage Diff @@
## main #4728 +/- ##
=======================================
Coverage 76.00% 76.00%
=======================================
Files 223 223
Lines 32018 32019 +1
=======================================
+ Hits 24336 24337 +1
Misses 7682 7682
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Signed-off-by: cgalelli <claudio.galelli@obspm.fr>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cgalelli
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @cgalelli, the remaining test fails are unrelated
…8-on-v1.0.x Backport PR #4728 on branch v1.0.x (Fixed offset calculation in Background2D.to_3d)
…8-on-v1.1.x Backport PR #4728 on branch v1.1.x (Fixed offset calculation in Background2D.to_3d)
I tried to fix the bug presented in issue #4724 by @maxnoe
Background2D.to_3d was using cartesian offset instead of angular separation. Implemented using
astropy.coordinates.angular_separation