Added AVIRIS-5 support#679
Merged
Merged
Conversation
pgbrodrick
approved these changes
May 1, 2025
Collaborator
|
Looks good. We will handle code redundancy in a future PR. Thanks for bringing this up, @adamchlus! Merging. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds support for AVIRIS-5 data. Unlike AVIRIS-3, it does not include default
INVERSION WINDOWS,as these can be set in theapply_oecall. We may want to consider adding defaults in the future.Note: There is some code redundancy in
template_construction.pyin the code block that sets the fid. For example, AVIRIS-NG, AVIRIS-3, AVIRIS-5, and PRISM all use the same filename template but have separate conditional statements. A similar issue exists inapply_oe.