-
Notifications
You must be signed in to change notification settings - Fork 187
JP-4285: Cube Build updates #10433
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
Open
jemorrison
wants to merge
13
commits into
spacetelescope:main
Choose a base branch
from
jemorrison:cb_check
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
JP-4285: Cube Build updates #10433
Changes from 12 commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
b7b95cb
added print
jemorrison a0166a9
testing
jemorrison 45dc715
Loaded for comments
jemorrison 32530bd
Loaded for comments
jemorrison 825a27e
clean up interface and remove single type cubes used in old outlier d…
jemorrison 56967ee
add change log
jemorrison 7144ced
cleaned up tests
jemorrison 464b501
fix syntax error in test and update docs
jemorrison 4145b0c
update calspec2 tests in regression tests
jemorrison 9e5af96
updates from review
jemorrison 92bee69
add unit test for suffix
jemorrison 36df3c3
change test to monkey patch
jemorrison 0af9fe3
update unit test
jemorrison File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Clean up cube build interface, removing the parameters ``pipeline`` and ``single``, which were intended for internal use only. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,16 +17,6 @@ each band will be created. | |
| ``cube_build``, it sets ``pipeline=2``. When running stand-alone or in | ||
| :ref:`calwebb_spec3 <calwebb_spec3>` pipeline, the parameter ``pipeline=3`` is set for ``cube_build``. | ||
|
Comment on lines
12
to
18
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Looks like this section still needs to be removed. There are also some comments below about the "pipeline rules" for output_type that I think need to be updated. |
||
|
|
||
| - ``pipeline=2`` sets up the rules for making :ref:`calwebb_spec2 <calwebb_spec2>` pipeline type cubes. For NIRSpec data the default | ||
| rules produce cubes with a single grating and filter and with a linear wavelength dimension. For MIRI data | ||
| the default rules produce a single IFU cube containing the two channels in the input data with a non-linear | ||
| wavelength dimension. In both cases, the input filename suffix ``cal`` is replaced with ``s3d``. | ||
|
|
||
| - ``pipeline=3`` setups up the results for making :ref:`calwebb_spec3 <calwebb_spec3>` pipeline type cubes. For NIRSpec data | ||
| the default rules will produce a single IFU cube from the same grating and filter, while for MIRI data a single | ||
| IFU cube is created for each channel and band. In both cases, the output IFU cube will contain the grating and | ||
| filter name (NIRSpec) or channel and band (MIRI). | ||
|
|
||
| ``channel [string]`` | ||
| This is a MIRI only option and the valid values are 1, 2, 3, 4, and ALL. | ||
| If the ``channel`` argument is given, then only data corresponding to that channel will be used in | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 also add a
breakingchange note, since we're removing step parameters?