[Processing Request]: DISP-S1 catch-up mode request

[gracebato]

Venue

PST

Product

DISP-S1

SAS Version

No response

SDS Version

No response

Input Data

CASE 1: Missing large # of DISP-S1 at the beginning but has satellite acquisitions:
46541 (Edgecumbe, AK)

• missing data: 2016-10-18, 2016-11-11, 2017-08-08, 2017-08-20, 2017-09-01, 2017-09-13, 2017-09-25, 2017-10-07, 2017-10-19, 2017-10-31, 2017-11-12, 2018-04-17, 2018-04-29, 2018-05-11
  11114 (Sacramento, CA)
• missing data: 2016-08-10, 2016-09-03, 2016-09-27, 2016-10-21, 2016-11-14, 2016-12-08, 2017-01-01, 2017-01-01, 2017-01-13, 2017-01-19, 2017-01-25, 2017-02-18, 2017-03-14, 2017-03-26, 2017-04-07

CASE 2: Missing DISP-S1 in the middle but has satellite acquisitions:
08622 (New York, NY)

• missing data on 2021-02-08 and 2021-02-20
  11115 (Central California, CA)
• missing data: 2024-11-20 (there are more between 2016-2017 but may not satisfy the 27-burst requirement)

CASE 3: Needs restart after a large gap due to no satellite acquisition:
24726 (Salome, Az)

• run first historic processing from 2016-07-09 to 2021-08-06
• run forward mode for last batch: 2021-08-18 to 2021-10-19 (11 CSLCs). Note this must be connected with 2021-08-06.
• break the timeseries (no connection with 2021-10-19) and restart historic processing from 2025-05-29 to 2025-12-31 (there are 17 CSLCs so a ministack can be constructed)

33065 (Unimak, AK)

• run first historic processing from 2016-07-23 to 2020-10-12
• run forward mode for last batch: 2020-10-24 to 2021-10-19 (8 CSLCs). Note this must be connected with 2020-10-12.
• break the timeseries (no connection with 2021-10-19) and restart historic processing from 2025-05-29 to 2025-12-31 (there are 17 CSLCs so a ministack can be constructed)

Share Results

• Google Earth Engine (GEE)
• NASA Distributed Active Archive Centers (DAAC) User Acceptance Testing (UAT)

Additional Notes

No response

[hhlee445]

@gracebato Can you provide us the gap time range?

[hhlee445]

@gracebato For frame 11115, only 25 of the 27 expected CSLC bursts are available on 2024-11-20; therefore, this date is excluded from the consistency database.

[gracebato]

Hi @hhlee445 -- we should not be missing the two CSLCs for this date. Is it likely that we missed to process them?
I see the following OPERA CSLC bursts are missing, is this what you've noticed from your end as well?
T042-088913-IW2
T042-088918-IW2

They should not be missing. I see them in ASF's S1 Burst version here.

[gracebato]

@hhlee445 @LucaCinquini
Below is probably easier to see and cross check. You can see there that OPERA CSLCs are missing for those two bursts on Nov 20 2024 -- hence the consistent burst database missed this date. But ASF's version have them processed.

ASF version
OPERA version

[hhlee445]

@gracebato

Frame 46541: DISP-S1 processing is complete.
Frames 11114 and 8622 are still running.
Frame 24726 is finished through 2021-08-06T01:33:06; 2025 data will be processed after the cycle is reset.
Frame 33065 is complete through 2020-10-12; 2025 data cannot be processed due to insufficient sensing time.

Processed data is located at
s3://opera-int-rs-pop1/products/DISP_S1/