You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have found some comments about the ph_grid error in step 2. Actually, it is due to the nan value or error value ( lon and lat) in the pscands.1.ll, which is produced by the psclonlat code. This bug of nan value or error value will also cause the hgt error in the pscands.1.hgt, which is producted by the pscdem code. I have tested the question with sentinel-1 data, and found the data with line number < 34000 usually not cause the bug. But if the data with line number > 34000 or 35000 usually cause the bug in the PATCH_, whose line input number > 34000 or 35000 (refer to patch.in in the PATCH_). So, it seems there are some bugs on the psclonlat.c and pscdem.c code in the /src folder of StaMPS. I hope someone can help to check and resolve this question. I don't know much about programming.
The text was updated successfully, but these errors were encountered:
I have found some comments about the ph_grid error in step 2. Actually, it is due to the nan value or error value ( lon and lat) in the pscands.1.ll, which is produced by the psclonlat code. This bug of nan value or error value will also cause the hgt error in the pscands.1.hgt, which is producted by the pscdem code. I have tested the question with sentinel-1 data, and found the data with line number < 34000 usually not cause the bug. But if the data with line number > 34000 or 35000 usually cause the bug in the PATCH_, whose line input number > 34000 or 35000 (refer to patch.in in the PATCH_). So, it seems there are some bugs on the psclonlat.c and pscdem.c code in the /src folder of StaMPS. I hope someone can help to check and resolve this question. I don't know much about programming.
The text was updated successfully, but these errors were encountered: