Page Comparison

...

• once all acq-lists have been generated, facet on such acq-lists in Tosca

  • you can query by the AOI id and then facet on the S1-GUNW-acq-list dataset

• then submit the localizer jobs:

  • Action: Standard Product S1-GUNW slc_localizer [develop]

  • Queue: factotumaria-jobstandard_worker-{large,small} (Confirm correct queue Jack McNelis product-localizer (Perhaps create a dedicated queue on factotum like we did for the evaluator.)

  • asf_ngap_download_queue: factotum-job_worker-slc_sling-asf

    • Note the other queue slc-sling-extract-asf is an ASG

  • esa_download_queue: factotum-job_worker-slc_sling-scihub

    • Note the other queue slc-sling-extract-scihub is an ASG

  • spyddder_sling_extract_version: develop

  • Result: this job will iterate over the SLCs listed in the acq-list and submit a data sling job

    • these sling jobs take acquisition-S1-IW_SLCs as an input and will download the corresponding SLC from ASF (relatively old acquisition) or Scihub (acquisition is less than 2 weeks old) to s3 and register the SLC in the S1-IW_SLC dataset in GRQ

  • Notes:

    • Acquisition lists are in one-to-one correspondence with ifg-cfgs

    • SLCs can be shared among acquisition lists and ifg-cfg's within an AOI. Therefore, #SLCs < # acq-lists = #ifg-cfgs within your AOI. As an example, within an AOI, there were ~700 SLCs for 2300 ifg-cfgs.

    • Say you run the localizer and you see that you have a bunch ifg-cfgs haven’t been created even though most of the sling jobs have been completed successfully. You may have only a few SLCs to download (or much less than the ifg-cfgs that are missing). Check the unique SLCs in the ops report.

    • If you have the proper trigger rules set up and activated, every time a new SLC is slinged and put into the system, then an ifg-cfg is created. This is a helpful trigger rule to have. Currently it is called acqlist_evaluator.

...