Add step to combine previous amplitudes/amplitude dispersions for cleaner PS/SHP estimation #179
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
…o avoid false positives
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.
Closes #78
Tested by running once on 10 dates, 2 bursts:
Comparing the amplitude dispersion for the stack of 10 (left) and the "combined_dispersion.tif" (middle), the results are the same except at layover/shadow regions.
Another comparison: the amplitude dispersion from using only 5 dates (left) with the combined (middle). The whole area has higher amplitude dispersion from incorporating more data, leading to fewer false positive PS
We're also adding one special case to lower the amplitude dispersion threshold to pick PS for just the first ministack, before we're passed any compressed SLCs. one ministack is too noisy to have a typicl 0.25-ish threshold.