Currently, multiburst product names as are not parse-able my MintPy without code changes. It's likely better to change the naming scheme for the products than to update MintPy.
Single burst products follow the naming convention outlined here and we'll want to come up with something that follows a similar pattern.
S1_bbbbbb_iis_yyyymmdd_yyyymmdd_pp_INTnn_uuuu
S1 :The imaging platform name, always S1 for Sentinel-1.bbbbbb: Relative burst ID values assigned by ESA. Each value identifies a consistent burst footprint; relative burst ID values differ from one sub-swath to the next.ii: The imaging mode, currently only IW is supported.s: The sub-swath number, either 1, 2, or 3, indicating which sub-swath the burst is located in.yyyymmdd_yyyymmdd: The acquisition dates of the reference (older) scene and the secondary (newer) scene.pp: The polarization of the product, either HH or VV.INT The product type (always INT for InSAR)nn: The pixel spacing in meters, which will be 80, 40, or 20, based upon the number of looks selected when the job was submitted for processing.uuuu: The filename ends with the ASF product ID, a 4 digit hexadecimal number.
Currently, multiburst product names as are not parse-able my MintPy without code changes. It's likely better to change the naming scheme for the products than to update MintPy.
Single burst products follow the naming convention outlined here and we'll want to come up with something that follows a similar pattern.
S1_bbbbbb_iis_yyyymmdd_yyyymmdd_pp_INTnn_uuuuS1:The imaging platform name, always S1 for Sentinel-1.bbbbbb: Relative burst ID values assigned by ESA. Each value identifies a consistent burst footprint; relative burst ID values differ from one sub-swath to the next.ii: The imaging mode, currently only IW is supported.s: The sub-swath number, either 1, 2, or 3, indicating which sub-swath the burst is located in.yyyymmdd_yyyymmdd: The acquisition dates of the reference (older) scene and the secondary (newer) scene.pp: The polarization of the product, either HH or VV.INTThe product type (always INT for InSAR)nn: The pixel spacing in meters, which will be 80, 40, or 20, based upon the number of looks selected when the job was submitted for processing.uuuu: The filename ends with the ASF product ID, a 4 digit hexadecimal number.