-
Notifications
You must be signed in to change notification settings - Fork 76
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
Use small angular offsets when determining compass properties #2867
Conversation
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.
Seems reasonable and does fix the N-E arrows on ImvizDitheredExample notebook. Thanks!
There are 2 failures that just need their results updated. |
575d48f
to
afef68a
Compare
@@ -98,18 +98,26 @@ def calc_compass(image_wcs, x, y, len_deg_e, len_deg_n): | |||
|
|||
|
|||
def calc_compass_radius(image_wcs, x, y, radius_px): |
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.
@ejeschke , this function was actually from ginga
:
Are you interested to have a similar patch over at ginga
?
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.
That looks like a good change, so sure!
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.
OK please see ejeschke/ginga#1102 . Thanks!
Description
While debugging an issue with GWCS coordinates with @bmorris3, I found that one issue is that if an image with a bounding box is used, and if we were to not reset the bounding box to
None
as we do currently in jadviz, the compass properties will fail in some cases - this is because before this PR, the pixel scale along the N and E directions was determined by adding 1 deg to the RA and Dec, but this is too large as this may then fall outside the image and return NaN (with spacetelescope/gwcs#497).In any case, I think it makes sense to use small angular offsets when trying to do this calculation regardless of whether we decide to not disable the bounding box etc. I don't think there is any downside to using small offsets, and it will be more future-proof.
Change log entry
CHANGES.rst
? If you want to avoid merge conflicts,list the proposed change log here for review and add to
CHANGES.rst
before merge. If no, maintainershould add a
no-changelog-entry-needed
label.Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
trivial
label.