Baseline: nan reported in metadata text file

[asjohnston-asf]

We've had a report of a burst insar job reporting nan for the perpendicular baseline in the metadata date file. This causes MintPy processing to fail when including that interferogram in an SBAS time series stack.

• https://azdwr-hyp3.asf.alaska.edu/jobs/de7e9b1a-941e-4744-bcca-444a5023b2e2

S1_275818_IW2_20220622_20220728_VV_INT20_6F73.txt

{
  'apply_water_mask': False,
   'granules': [
    'S1_275818_IW2_20220622T132025_VV_1160-BURST',
    'S1_275818_IW2_20220728T132027_VV_DE17-BURST'
  ],
  'looks': '5x1'
}

[asjohnston-asf]

Two other jobs with the same reference burst and two other jobs with the same secondary burst all reported value baseline values:

• https://azdwr-hyp3.asf.alaska.edu/jobs/1a3aa363-a220-410f-bdda-578e6eac6091
• https://azdwr-hyp3.asf.alaska.edu/jobs/b7a988c9-f69e-41ac-9133-658694caf602
• https://azdwr-hyp3.asf.alaska.edu/jobs/651ee18e-7430-4f3f-a722-eff745250ee3
• https://azdwr-hyp3.asf.alaska.edu/jobs/0bc3e190-5f53-467a-8ad8-2757335ae61d

[asjohnston-asf]

The baseline value is sourced from topsProc.xml in make_metadata_file() at https://github.com/ASFHyP3/hyp3-isce2/blob/develop/src/hyp3_isce2/packaging.py#L351 . This could point to an underlying issue with isce2; we'd have to run this interferogram outside of HyP3 and inspect the topsProc.xml file to confirm.

[Alex-Lewandowski]

Looking at a quick search on Vertex, the baseline should be 0.0 but ends up nan in the output metadata txt file.