Switch to MVE Noise Est For Single Noise-only RangeLine in RSLC (NSDS-4938) - #347
Open
rad-eng-59 wants to merge 1 commit into
Open
Switch to MVE Noise Est For Single Noise-only RangeLine in RSLC (NSDS-4938)#347rad-eng-59 wants to merge 1 commit into
rad-eng-59 wants to merge 1 commit into
Conversation
noise rangeline
bhawkins
approved these changes
Aug 5, 2026
bhawkins
left a comment
bhawkins
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Normally I prefer not to modify user inputs, but in this case it seems reasonable enough.
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.
Handful of mixed-mode RSLC workflow fails as a result of not-enough noise-only range lines (simply one range line) in MEE-based noise estimator when either the requested output grid simply uses less than around two seconds of a L0B product or the respective L0B is too short (
< 2 seconds).This quick PR simply switches the method to MVE and issues a warning rather than raising exception (current behavior).
The issue has been reported in this jira ticket.
As an example, this has been tested for a mixed-mode with three L0Bs that failed in previous production.
Here is the respective HH NESZ plot for three AZ blocks of science band (aka A). This is a fixed PRF with three TX gaps where a large portion of the frame covers the water.