When CSLC products are staged with a polarization other than "VV" (such as "HH"), the chimera precondition functions do not detect this and update the algorithm parameters runconfig appropriately. There is a subdataset field used to index into the HDF5 metadata file that needs to have the correct polarization reflected in the path.
What did you expect?
The polarization of the input CSLC products for DISP-S1 processing is correctly reflected in the algorithm parameters runconfig staged for the job.
Reproducible steps
The following S3 location contains triage details from a job that staged HH CSLC products:
s3://opera-dev-lts-fwd-collinss/triage/R3/3.0.0-RC.4.0/triaged_job-job-WF-SCIFLO_L3_DISP_S1-20240506T054101.16763Z_task-06ed0636-1655-438c-aec9-07bbe7967dc9/
Rerunning this job using the native ID of one of the input granules should be sufficient to reproduce this bug.
Environment
- Version of this software [e.g. vX.Y.Z]
- Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...
Checked for duplicates
Yes - I've already checked
Describe the bug
When CSLC products are staged with a polarization other than "VV" (such as "HH"), the chimera precondition functions do not detect this and update the algorithm parameters runconfig appropriately. There is a
subdatasetfield used to index into the HDF5 metadata file that needs to have the correct polarization reflected in the path.What did you expect?
The polarization of the input CSLC products for DISP-S1 processing is correctly reflected in the algorithm parameters runconfig staged for the job.
Reproducible steps
Environment