Open niarenaw opened 2 weeks ago
@niarenaw can you also provide specific time range and geojson file?
2024-06-06T00:00:00Z
to 2024-06-07T23:59:59Z
(delivery time)2022-11-10T00:00:00Z
to 2022-11-10T23:59:59Z
(temporal/acquisiton time){ "type": "FeatureCollection", "features": [{ "type": "Feature", "properties": { "type": "S2", "identifier": "17RNH" }, "geometry": { "type": "MultiPolygon", "coordinates": [ [ [ [ -81.0001987094, 25.3167339867, 0.0 ], [ -79.909362219, 25.3126993615, 0.0 ], [ -79.9180080699, 24.3212402892, 0.0 ], [ -81.0001971338, 24.3250964058, 0.0 ], [ -81.0001987094, 25.3167339867, 0.0 ] ] ] ] } }] }
Checked for duplicates
Yes - I've already checked
Describe the bug
In adressing https://github.com/nasa/opera-sds/issues/48, some unexpected behavior was observed using the data subscriber script. Several thousand RTC products were generated then delivered to ASF UAT. The goal was to generate DSWx-S1 products for the tile/date pairs listed in ticket above. The following commands were run (in the listed order):
FIRST COMMAND: Trigger all RTC downloads given delivery time range
SECOND COMMAND: Trigger all RTC downloads given delivery time range + tile
THIRD COMMAND: Trigger all RTC downloads given temporal time range + tile
Despite running the following for many tile/date combos, certain products that we expected to make were never generated. One such pair is: (17RNH, 2022-11-10). I would also expect each command to cause all submitted jobs to dedupe as each triggers a subset of the previous, but new jobs were always kicked off. After all jobs were run, the only way to trigger certain missing products was to run the data subscriber with in a loop with --native-id=RTC for each RTC that was derived from the SLC that covered the MGRS tile on the missing date.
What did you expect?
Reproducible steps
Environment