This PR proposes an attempt to solve #92 and avoids to compute the correction layers twice.
At the moment, the correction layers are computed 1) to feed them to the geocodeSlc correction module 2) to allocate them inside the CSLC-S1 data product.
In this PR, the corrections are computed once, saved on disk and read when it is time to allocate them in the dataset.
May be there is a smarter way to do this but this PR gives a first stab to the issue.
This PR proposes an attempt to solve #92 and avoids to compute the correction layers twice.
At the moment, the correction layers are computed 1) to feed them to the geocodeSlc correction module 2) to allocate them inside the CSLC-S1 data product.
In this PR, the corrections are computed once, saved on disk and read when it is time to allocate them in the dataset. May be there is a smarter way to do this but this PR gives a first stab to the issue.