-
Notifications
You must be signed in to change notification settings - Fork 171
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
Jigsaw Fixes #5703
Jigsaw Fixes #5703
Conversation
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5703". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5703". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
@@ -1880,7 +1880,7 @@ | |||
</description> | |||
<type>boolean</type> | |||
<default> | |||
<item>yes</item> | |||
<item>no</item> |
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 we make it so update=true is forced on if the h5adjustments is set to true? Lynn pointed out that it is confusing to force update=false since the cubes are being updated. Which I think is a reasonable change.
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.
Yes, we can default update=true
for when adjustment_input=<file.h5>
. Currently, it would be more of a cosmetic change since a set adjustment_input
will inherently update the cubes and the update
flag is checked in another part of the code. Basically, there is some duplication of code that we can refactor later down the road.
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.
Does not seem to be a way to set default value for another param via another param but did lift the restriction so users can set update=true
when setting the adjustment_input
option.
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5703". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
Working on test fix. |
The build and test suite have started for your pull request. To view your build log, please reference the build with source version: "PR_5703". Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch. |
* Add some fixes * Update changelog * Require update * Test fix
* Jigsaw Fixes (#5703) * Add some fixes * Update changelog * Require update * Test fix * Version ticks for RC2 * Fix truth data for isis 9.0 * Moved bugfix version and rc back to appended string --------- Co-authored-by: Christine Kim <[email protected]>
Description
Changes
OUTADJUSTMENTH5
default to no and fixes bug to allow this param set on read-only images.Related Issue
Addresses #5700
How Has This Been Validated?
Types of changes
Checklist:
Licensing
This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words: