alos2App ionospheric correction errors #671
-
I am processing two frames of ALOS-2 ScanSAR data (WD1, 5-subswaths). One of the subswaths of one of the frames is showing up with a different ionospheric correction estimate. I tried changing the number of looks in the ionospheric estimation, but I get the same result. I attach an image of the estimate before filtering (ion_20rlks_224alks.ion). I don't see this discontinuity in either the lower or upper interferogram phase, so I don't know where it is coming from, but it causes errors in the final ionospheric correction near the area where the discontinuity is located. Is this coming from the original stitching of the subswaths and frames? I notice that there is a data window position shift between the two frames. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
The swath phase differences now use some default values stored in the scripts. These are values estimated using a large number of datasets, so they are more precise. However, occasionally the actual values are different from these default values. Subswath five of the second frame in this case apparently has a different phase difference, so we have to use the estimated value. See below for details of settings. after that we need to rerun from ion_subband. |
Beta Was this translation helpful? Give feedback.
-
Hi Eric and Cunren, I need to apply this option to correct a phase jump in the ion_80rlks_448alks.ion file between swaths 3 and 4 When I set the relevant options to
I get the error The error seems straightforward to correct, but the software keeps crashing. How can I fix it? Thanks a lot |
Beta Was this translation helpful? Give feedback.
-
Hi Eric, It is just one frame. I followed your advice by setting the flag to
because the jump is between swaths 3 and 4. But then I obtained the same error than before. Then I switched it to
And that solved the problem. I don't know why but the double brackets made the difference. Thanks for your help |
Beta Was this translation helpful? Give feedback.
The swath phase differences now use some default values stored in the scripts. These are values estimated using a large number of datasets, so they are more precise. However, occasionally the actual values are different from these default values. Subswath five of the second frame in this case apparently has a different phase difference, so we have to use the estimated value. See below for details of settings.
https://github.com/isce-framework/isce2/blob/main/examples/input_files/alos2/alos2App.xml#L311-L317
after that we need to rerun from ion_subband.