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

Marking "noisy" acquisitions/output products #12

Open
scottstanie opened this issue Jan 31, 2023 · 0 comments
Open

Marking "noisy" acquisitions/output products #12

scottstanie opened this issue Jan 31, 2023 · 0 comments
Labels
quality metrics Statistics or metrics relating to the question "how uncertain are we?" research A deeper question that may require extended research to answer

Comments

@scottstanie
Copy link
Collaborator

Q. How could we mark "noisy" acquisitions that aren't worth pulling?

We will be pulling $k$ old SLCs along with each new SLC to estimate/produce a new product. We almost certainly to not want to just pull the $k$ most recent SLCs (c.f. the Norwegian InSAR service, who basically skips the entire winter).

This is a two part issue:

  1. What quality metrics can we produce that best tell is what are the old SLCs that are worth re-pulling?
  2. Operationally, how can we mark our output products (or label Sentinel products) so we know that certain historical ones aren't worth using to estimate the latest phase?
@scottstanie scottstanie added research A deeper question that may require extended research to answer quality metrics Statistics or metrics relating to the question "how uncertain are we?" labels Jan 31, 2023
@scottstanie scottstanie added this to the IF Delivery milestone Mar 23, 2023
@scottstanie scottstanie removed this from the IF Delivery milestone Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
quality metrics Statistics or metrics relating to the question "how uncertain are we?" research A deeper question that may require extended research to answer
Projects
None yet
Development

No branches or pull requests

1 participant