Closed cmarshak closed 1 year ago
Please view the following looking at the first job. We don't need to generate the IFG to understand the error. I localize the important metadata to recreate the reported error.
https://gist.github.com/cmarshak/6c4f8acbb6466ed4ce8fe13f14de78e2
As you can see for the input granules, there are two orbit files obtained.
ref_orb_paths = list(set(list(map(lambda g: get_orb.downloadSentinelOrbitFile(g)[0], ref_granules))))
ref_orb_paths
['S1A_OPER_AUX_POEORB_OPOD_20230705T080713_V20230614T225942_20230616T005942.EOF',
'S1A_OPER_AUX_POEORB_OPOD_20230706T080750_V20230615T225942_20230617T005942.EOF']
When I pass both orbits into geo2rdr, I get the error reported. When I pass just the first, same error. When I pass just the second, I get an error.
I do not understand the precise issue here. It would be good to understand what is happening from @dbekaert and @sssangha.
Let's resume this on Monday.
Unfortunately, a bug for SET interpolation has cropped up for ~1/3 of jobs on track 106. This error did not show up previously on track 4 at all. Both had approximately 10k jobs. Here are some sample inputs and logs.
and
The relevant error shows up as
This error previously came up when we had #131, in which duplicate orbit xmls was causing the job to fail. However, as I will demonstrate below, this is coming likely due to something more nuanced.