Does mintpy already support the multi-burst product obtained by the submit_insar_isce_multi_burst_job function of hyp3's api?

[litao xu]

Dear MintPy Developers：

 I am currently using the submit_insar_isce_multi_burst_job function in hyp3_sdk v7.3.0 API (https://hyp3-docs.asf.alaska.edu/using/sdk_api/), which can get the result of multiple burst concatenations. However, I found that the latest version of mintpy does not seem to support it. Is there any parameter setting that can support it? The product name obtained by submit_insar_isce_multi_burst_job is S1A_172_E093_8_N42_6_E095_1_N43_4_20180210_20180318_VV_INT20_7445_unw_phase_clipped.tif, which is different from the existing single burst product name S1_240777_IW2_20220317_20220410_VV_INT20_55E0_unw_phase_clipped.tif. My temporary solution is to rename the file, I wonder if this works?

[Kavya Kinjalk]

I tried to fix this, the only issue was how the folder/file name was being read. I have submitted a PR, if that gets merged it should work properly. It was just a few simple changes to prep_hyp3.py. If you want, you can patch your prep_hyp3.py from my fork. If you come across any issues, let me know. 

[litao xu]

Dear Kavya Kinjalk, thank you for contributing the code, it solved my problem perfectly. Meanwhile, I have an additional small question, I am experiencing error reporting during modif_network in my study area where the descending track uses multiple bursts of different sub-strips IW1 and IW2, but it is normal for me to deal with ascending and descending track's and other study area's where the ascending and descending track is only a single iw, may I ask you if you have any case where you are using the inter-iw sub-strips?

[Kavya Kinjalk]

Hello,

I apologize for the delay in my reply. I was hoping you could explain the error in more detail? providing logs can be really helpful, as I did not personally come across any issues. If you managed to fix it, great! Please let us know what happened and how you fixed it, maybe it will help someone else! :)

A few updates to the situation:

1. ASF is currently working on renaming the folder structure. This GitHub issue can provide more detail. It should make original code compatible again.

2. ISCE2 should start supporting Sentinel-1C data as well. If you want to immediately work with S1C data, please patch your code from here. Hyp3 is waiting on the release - might take a while.