search

relativeorbit / fufiters

run hyp3-isce2 via github actions
MIT License
2 stars 0 forks source link

Use static output folder names #1

Closed scottyhq closed 6 months ago

scottyhq commented 6 months ago

hyp3-isce2 creates unique 4 character output folder suffixes for each processing run so that results would never be overwritten:

https://github.com/ASFHyP3/hyp3-isce2/blob/71482140bde97ed36a9d681b4baee5486a68ad16/src/hyp3_isce2/burst.py#L371

For the fufiters workflow there are some advantages to having consistent product names, in particular you avoid accidental duplicate datasets and STAC catalogs don't have to be updated if products are re-processed. So we can just remove the token string:

S1_023790_IW1_20230621_20231218_VV_INT20_B6F2 -> S1_023790_IW1_20230621_20231218_VV_INT20

scottyhq commented 6 months ago

closed by https://github.com/relativeorbit/hyp3-isce2/commit/0615095226a341a8b070c295a12f4e022dc790b2

scottyhq commented 6 months ago

Turns out other libraries expect this specific naming structure from hyp3: https://github.com/insarlab/MintPy/blob/0c74de929d6656954fe7b1c127b7bd1ca67f8e7d/src/mintpy/prep_hyp3.py#L32

So sticking with a fixed 4 digit code (FFTS) instead of a random code:

S1_023790_IW1_20230621_20231218_VV_INT20_B6F2 -> S1_023790_IW1_20230621_20231218_VV_INT20_FFTS