-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add logic for manually specifying reference dates mid-stack #334
Merged
scottstanie
merged 23 commits into
isce-framework:main
from
scottstanie:reference-updates
Sep 15, 2024
Merged
Add logic for manually specifying reference dates mid-stack #334
scottstanie
merged 23 commits into
isce-framework:main
from
scottstanie:reference-updates
Sep 15, 2024
Conversation
This file contains 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 accounts for the fact that we may pass in several compressed SLCs for a single run, and we wish to make the phase linking outputs referenced to something besides the first SLC. For example, if we had 1_1_3 1_4_6 7_7_9 10 11 12 And we wanted to output interferograms relative to `7`, we need to specify that to the phase linking functions; otherwise, it will output things relative to day 1. Since we dont write out rasters corresponding to compressed SLC inputs, we'd have nothing from day 7 to re-refrence later. Note that an alternative might be to always write out rasters for every input in a ministack, including the compressed inputs. The downside is that during a normal local Sequential run with multiple ministacks, you write out redundant rasters and need to remove/select the right ones afterward. But if that way seems cleaner later, we could revert this commit.
…d_phase_sequential`
…inking` in `single`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 logic to specify a reference date changeover while not breaking the time series.
This feature is planned to be used for the opera SAS, where ministacks are run as a full block through unwrapping; it's unlikely to be widely useful to people who are processing larger stacks using the Sequential workflow.