...
AOI tracks are often too large to be covered by 1 S1-GUNW for a given date-pair
once all the ifgs for a specific date-pair are generated an S1-GUNW-AOI_TRACK product is produced
to generate these products, facet on the S1-GUNW products and submit the following job:
Action:
Standard Product S1-GUNW - S1-GUNW Completeness Evaluator [develop]
Queue:
factotum-job_worker-large
Result: this job will look at an S1-GUNW and check if it “completes” the track for a given date-pair. If so S1-GUNW-AOI_TRACK product is generated. Otherwise, the evaluator silently completes without producing anything.
note that these jobs are automatically submitted by the trigger rule
s1gunw-aws-s1gunw-completeness-evaluator
and you should not normally need to submit them on-demandonce an S1-GUNW-AOI_TRACK product is produced, the S1-GUNW products will be published to ASF and ARIA-products via the following pipeline: TODO: delivery pipeline
Checking the Delivery to ASF
In addition to using the various ops reports, you can go directly to ASF: https://search.asf.alaska.edu/ and us their search by “list” feature. Copying the GUNW ids into this feature can illustrate the delivery publically! This is generally a good method of “delivering” the final AOI to science customers. Here is an example.
Notes on Errors:
This is not an error, but a confusing behavior. If any GUNW from an entire date pair is abset, then none of the GUNWs will deliver. So even if you facet on missing GUNWs, this process will complete without error, but not deliver your desired ASF.
...
Notes
Faceting in Tosca and Figaro
...