Closed riverma closed 2 months ago
@LalaP: what information does OPS need to verify DSWx-S1 processing? Please let me know if what I captured above is sufficient. @hhlee445: we need delivery information of DSWx-S1 at CMR, like collection name, granule ID signature. Could you help provide:
Update on the second bullet point above:
Looked into it and i don't think there's a direct predictive quality to the DSWx-S1 granule ID signature that will tie back to input RTCs or MGRS Tile Set IDs. I think we'd have to search the DSWx-S1 collection and request matches for the InputGranules
field against the input RTCs for a given product we think should exist.
See the Metadata tab for this example granule: https://search.uat.earthdata.nasa.gov/search/granules/granule-details?p=C1261113948-POCLOUD&pg[0][v]=f&pg[0][gsk]=-start_date&g=G1264681475-POCLOUD&q=DSWX&tl=1719277753!3!!
mgrs_set_id maps to mgrs_tiles
example:
MS_112_60 -> mgrs_tiles list ['23VNJ', '23VNK', '23VPJ', '23VPK', '24VUP', '24VUQ', '24VVP', '24VVQ']
MS_112_59 -> mgrs_tiles list ['23VNL', '23VPL', '23WNM', '23WPM', '24VUR', '24VVR', '24VWR', '24WVS', '24WWS']
Thank you @hhlee445!
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
The current DSWx-S1 validator script returns only a list of MGRS tile set IDs. For OPS to use this information to audit whether processing is performing correctly and delivering the right products to CMR, this information needs to be manually converted to expected granule IDs that CMR should contain and OPS needs to manually check CMR.
Describe the feature request
The validator script should include an additional feature that takes the list of expected tile set IDs, and returns the list of granule IDs expected to be produced while also checking CMR if they are already delivered.