-
Notifications
You must be signed in to change notification settings - Fork 180
JP-3857 cube build code style changes #9347
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
JP-3857 cube build code style changes #9347
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9347 +/- ##
==========================================
+ Coverage 75.60% 75.62% +0.01%
==========================================
Files 368 368
Lines 36916 36908 -8
==========================================
+ Hits 27911 27912 +1
+ Misses 9005 8996 -9 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
97889c1 to
da8fadf
Compare
4dc93ee to
b554e3c
Compare
|
@melanieclarke take a look at this PR.I am re-running the regression test now and will post the link when they are finished. I have lost momentum on this PR so if you see something in general missing let me know and I can fix it before you do a detailed review |
Thanks @jemorrison - I glanced through and these look like good changes so far. This module could still use even more unit tests, but we don't need to get them all in now. |
melanieclarke
left a comment
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's a lot here - I think we're going to have to iterate a few times to get this ready for merge. I'll start by sending some initial comments from read-through, up to the ifu_cube.py file. More later!
0f74ca5 to
0960ffd
Compare
melanieclarke
left a comment
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.
Another round of suggestions/requests - I've now done an initial read-through up to but not including the C code and tests.
|
@melanieclarke Let me take another stab at c code. I think I did not fully clean that code up. |
Sure, just let me know when you're done and I'll come back around. |
|
@melanieclarke When you have time look at the c code: cube_match_sky_driz.c |
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.
@jemorrison - I started to look through your updates from yesterday, but it looks like GitHub hid a large chunk of comments from you. Can you please check under the fold from yesterday's round of comments?
I'll start looking at cube_match_sky_driz.c.
melanieclarke
left a comment
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.
Comments for cube_match_sky_driz.c:
In general, this looks like a pretty good level of detail. I think the Python signature and parameter descriptions are the most important part of the docs here. It would be helpful to review them and clean them up a bit - make sure all parameters are listed and in the right order. If you can, listing the Python input types is helpful (e.g. "ndarray of float" is better than "double array").
This comment was marked as resolved.
This comment was marked as resolved.
c3023d5 to
ce943e9
Compare
melanieclarke
left a comment
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 found a few more minor things on read-through, but I think we're getting close. The extra comments for the C code are very helpful.
The only significant issue is that there's a missing Exception in the IFU offset file handling code, noted below.
3ab0daf to
5e1d7be
Compare
|
@melanieclarke See if the way I modified the exception in cube_build_step.py is ok with you. |
melanieclarke
left a comment
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.
Almost there, just a couple more small things that keep getting buried:
- change log should note that there are new exception names
- there are still some "shepherds" in instrument_defaults that need to be replaced with Shepard
|
I think we made it! Can you link to the latest regtest run? |
|
@melanieclarke added the link to the latests (today) regression test run - all passing |
melanieclarke
left a comment
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 approve! Thanks for all your hard work on this one. I think it's a significant improvement in maintainability and documentation for this module.
Helps to Resolve JP-3857
Closes #
This PR addresses updates to cube_build code to conform to the code style changes.
Tasks
Build 12.0(use the latest build if not sure)no-changelog-entry-needed)changes/:echo "changed something" > changes/<PR#>.<changetype>.rst(see changelog readme for instructions)docs/pageRegression test passed: https://github.com/spacetelescope/RegressionTests/actions/runs/14668760965
(https://github.com/spacetelescope/RegressionTests/blob/main/docs/running_regression_tests.md))
- [ ] Do truth files need to be updated ("okified")?
- [ ] after the reviewer has approved these changes, run
okify_regteststo update the truth files