-
Notifications
You must be signed in to change notification settings - Fork 32
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
Pull common parts of skymatch from romancal and jwst into stcal #310
base: main
Are you sure you want to change the base?
Pull common parts of skymatch from romancal and jwst into stcal #310
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #310 +/- ##
==========================================
- Coverage 82.57% 79.42% -3.16%
==========================================
Files 57 61 +4
Lines 10272 11241 +969
==========================================
+ Hits 8482 8928 +446
- Misses 1790 2313 +523 ☔ View full report in Codecov by Sentry. |
c7e296c
to
9ab3734
Compare
9ed58df
to
cfaf7eb
Compare
2aee80f
to
6202d38
Compare
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.
This looks great, thanks William! I just had a few questions about whether some of the ruff and mypy problems could be fixed instead of ignored.
I also had a few questions about the code itself, but those also exist on jwst main, so they're technically beyond the scope of this PR. But I'm still curious to know the answers to those and I figure now is as good a time as any to ensure the code is written as cleanly as possible
The functionality to support this conversion is not yet | ||
implemented and at this moment `convf` is ignored. |
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.
Are there plans to implement this? If not, perhaps now is a good time to remove the option
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.
Based on ancient (>9 years old) discussions with relevant people, this feature, in theory, may not be needed for JWST. In practice, however, we don't know. I suggest leaving this alone as is.
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.
This is actually being used in places
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.
Can you please point me to where? If that's the case, this comment in the docstring should be removed
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.
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.
Thats all logging but I'm not qualified to tell if we want to keep any parts of those logs
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.
I don't think "used in logging" qualifies as being used given that convf
is hard-coded to equal 1.0 and therefore has no effect on the scaling reported in the log messages. So I agree with Mihai we should leave this as-is, including the docstring
I agree they should be fixed. However, as you said they are beyond the scope of this PR. I think for making it possible to trace the history of changes it makes sense to move the code in as close a state as possible from JWST to stcal and then do a follow on PR making cleanups and addressing the issues uncovered here. |
IMO making the code adhere to the more stringent style rules in stcal remains within the scope. I don't much like ignoring them. I think the downstream testing should assuage any concerns that those changes might break something. I agree that my comment RE the potentially unnecessary use of |
eb4b7d8
to
2e6b1c9
Compare
96da6e5
to
46a88e2
Compare
b5c4516
to
d0976cb
Compare
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 for all the updates! Before merging I think it would be good to update spacetelescope/jwst#8901 such that we can see if the changes are likely to work well with jwst. Perhaps you were already planning to do so.
d0976cb
to
705f544
Compare
I am not finished updating everything yet. |
705f544
to
f41b760
Compare
@emolter I believe this is ready now. |
docs/conf.py
Outdated
("py:class", "stsci.imagestats.ImageStats"), # intersphinx isn't working here | ||
("py:class", "spherical_geometry.polygon.SphericalPolygon"), # intersphinx isn't working here |
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.
These should be working with the intersphinx links I added. I believe the fix may require some fixes in the documentation for those packages.
It is possible something is off in the stcal
docs causing the link failure. Please feel free to push changes to attempt to fix this.
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.
All my previous questions have been answered now.
I don't think the changes have been so large that it would be helpful for me to go through it again, but let me know if you'd like me to.
So this looks good to me pending fixing the bug that is causing the failing jwst regtests
dbcfe42
to
ba04e8e
Compare
This is from jwst commit 2491b40a25f42bf2c10d242178434fe6c7d75847
ba04e8e
to
1801b3a
Compare
This PR pulls the common parts of skymatch from romancal and jwst into stcal to be shared.
Note, no tests are included because it is well tested by the step tests in both romancal and jwst.
Tasks
docs/
pageno-changelog-entry-needed
)changes/
:echo "changed something" > changes/<PR#>.<changetype>.rst
(see below for change types)"git+https://github.com/<fork>/stcal@<branch>"
)jwst
regression testromancal
regression testnews fragment change types...
changes/<PR#>.apichange.rst
: change to public APIchanges/<PR#>.bugfix.rst
: fixes an issuechanges/<PR#>.general.rst
: infrastructure or miscellaneous change