Skip to content
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

Merged
merged 5 commits into from
Jan 13, 2025
Merged

Jigsaw Fixes #5703

merged 5 commits into from
Jan 13, 2025

Conversation

chkim-usgs
Copy link
Contributor

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation change (update to the documentation; no code change)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

  • I have read and agree to abide by the Code of Conduct
  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • I have added myself to the .zenodo.json document.
  • I have added my user impacting change to the CHANGELOG.md document.

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:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

  • I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

Copy link

github-actions bot commented Jan 6, 2025

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.

Copy link

github-actions bot commented Jan 6, 2025

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.

@Kelvinrr Kelvinrr self-assigned this Jan 6, 2025
@@ -1880,7 +1880,7 @@
</description>
<type>boolean</type>
<default>
<item>yes</item>
<item>no</item>
Copy link
Collaborator

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.

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

Copy link

github-actions bot commented Jan 7, 2025

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.

@chkim-usgs
Copy link
Contributor Author

Working on test fix.

Copy link

github-actions bot commented Jan 8, 2025

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.

@Kelvinrr Kelvinrr merged commit d2486e7 into DOI-USGS:dev Jan 13, 2025
2 checks passed
AustinSanders pushed a commit to AustinSanders/ISIS3 that referenced this pull request Jan 13, 2025
* Add some fixes

* Update changelog

* Require update

* Test fix
AustinSanders added a commit that referenced this pull request Jan 14, 2025
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants