In the current pipeline, the LUT corrections are generated twice
1) to create the cumulative LUTs in slant range and azimuth directions to pass to the geocodeSlc core module 2) to generate the LUTs to include inside the generated CSLC-S1 product
This is unnecessary and it might lead to a significant increase in runtime if we decided to have a finer spacing for the LUTs which currently is 200 m x 200 m.
What did you expect?
I expected the LUT corrections to be computed once.
One option to solve this is to dump the individual corrections to disk in the scratch directory and read them when it is time to allocate them inside the HDF5 product.
vbrancat
commented
1 year ago
Checked for duplicates
Yes - I've already checked
Describe the bug
In the current pipeline, the LUT corrections are generated twice 1) to create the cumulative LUTs in slant range and azimuth directions to pass to the
geocodeSlccore module 2) to generate the LUTs to include inside the generated CSLC-S1 productThis is unnecessary and it might lead to a significant increase in runtime if we decided to have a finer spacing for the LUTs which currently is 200 m x 200 m.
What did you expect?
I expected the LUT corrections to be computed once.
One option to solve this is to dump the individual corrections to disk in the scratch directory and read them when it is time to allocate them inside the HDF5 product.
Reproducible steps
No response
Environment
No response