8000 Nirspec improvements in blotting for outlier detection, JP-2050 by jemorrison · Pull Request #6326 · spacetelescope/jwst · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Nirspec improvements in blotting for outlier detection, JP-2050 #6326

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

Merged
merged 8 commits into from
Sep 8, 2021

Conversation

jemorrison
Copy link
Collaborator
@jemorrison jemorrison commented Sep 3, 2021

Partially resolves JP-2050

Description

There was a bug in the NIRSpec IFU blotting. An new routine was added to assign_wcs.util.in_ifu_slice that determines which ra, dec, lambda of the median cube fall in a NIRSpec slice. blot_cube_cube.py was updated to use this information

Checklist

  • Tests
  • Documentation
  • Change log
  • Milestone
  • Label(s)

@hbushouse
Copy link
Collaborator

Looks like a couple of unit tests need updating (see CI failures)

@codecov
Copy link
codecov bot commented Sep 3, 2021

Codecov Report

Merging #6326 (beb27a5) into master (f9d2fb8) will decrease coverage by 0.34%.
The diff coverage is 64.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6326      +/-   ##
==========================================
- Coverage   78.00%   77.66%   -0.35%     
==========================================
  Files         402      402              
  Lines       34633    34841     +208     
==========================================
+ Hits        27017    27060      +43     
- Misses       7616     7781     +165     
Flag Coverage Δ *Carryforward flag
nightly 78.29% <96.38%> (ø) Carriedforward from f9d2fb8
unit 56.94% <2.94%> (-0.08%) ⬇️

*This pull request uses carry forward flags. Click here to find out more.

Impacted Files Coverage Δ
jwst/outlier_detection/outlier_detection_step.py 83.59% <ø> (-4.53%) ⬇️
jwst/outlier_detection/outlier_detection_ifu.py 64.84% <52.27%> (-25.54%) ⬇️
jwst/cube_build/blot_cube_build.py 68.89% <66.10%> (-31.11%) ⬇️
jwst/cube_build/ifu_cube.py 76.75% <78.94%> (-1.88%) ⬇️
jwst/assign_wcs/util.py 81.63% <100.00%> (+0.04%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f9d2fb8...beb27a5. Read the comment docs.

Copy link
Collaborator
@hbushouse hbushouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK mechanically to me, although I'm no expert on IFU WCS transforms. My eyes are picking up what I'm guessing will be flake8 failures, but I don't see the results of that in the latest CI test run. It's only showing the results of the docs build. Should try to trigger a rerun of all CI tests.

@@ -221,7 +221,7 @@ def define_cubename(self):
fg_name = fg_name.lower()
newname = self.output_name_base + fg_name + '_s3d.fits'
if self.output_type == 'single':
newname = self.output_name_base + fg_name + '_single_s3d.fits'
newname = self.output_name_base + fg_name + '-single_s3d.fits'
if self.coord_system == 'internal_cal':
newname = self.output_name_base + fg_name + '_internal_s3d.fits'
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the "single" file names are being changed to use a hyphen as the separator, instead of underscore, should the "internal" names be changed the same way here?

@jemorrison
Copy link
Collaborator Author

@eslavich @hbushouse I have been getting the CI/macOS failure quite a bit recently. Is there really something wrong or do I just ignore it ? I don't understand the information when I click on 'Details'

@eslavich
Copy link
Contributor
eslavich commented Sep 8, 2021

I've been running into macOS errors as well, but they don't seem to be consistent (I've seen a failure and a success after rerunning the same commit).

The doc build failure can be resolved by rebasing on master.

@jemorrison
Copy link
Collaborator Author

@eslavich
So I did a 'git fetch upstream'
'git rebase upstream/master'
But a git status says nothing changed so I have nothing to add with a commit. In the past I have gone in and touched a file to make something to commit and then pushed it up. But there must be a better way of 'rebasing on master'

@eslavich
Copy link
Contributor
eslavich commented Sep 8, 2021

But a git status says nothing changed so I have nothing to add with a commit.

That only happens if there's a conflict to resolve. It sounds like git was able to rebase automatically, which means all you need to do afterwards is force push to the remote.

@jemorrison jemorrison merged commit f86c126 into spacetelescope:master Sep 8, 2021
@jemorrison
Copy link
Collaborator Author

@hbushouse merged code to hopefully fix NIRSpec blotting. So you can continue with testing

@jemorrison jemorrison deleted the NIRSpec_Outlier branch November 4, 2021 22:03
loicalbert pushed a commit to talensgj/jwst that referenced this pull request Nov 5, 2021
…etelescope#6326)

* updates

* updated in_ifu_slice

* upates

* update test using in_ifu_test

* flake8 fix for test

* Updated change log

* fix single name

* fix typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0