-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to set ISCE stackSentinel.py parameters in order to run MiaplPy? #60
Comments
Hi @geoglee If your current directory is the project directory, then setting the autoPath to yes would read all data automatically. ./testProject/testProject.template MiaplPy/miaplpy/defaults/miaplpyApp.cfg Line 22 in 3771804
Also you can manually set path to data as bellow in your template file: MiaplPy/miaplpy/defaults/auto_path.py Lines 21 to 38 in 3771804
|
Thank you so much @mirzaees ! |
you are very welcome @geoglee Regarding stripmap, yes, I have run it for TerraSAR data before and it worked |
Hello I have been using MintPy and MiaplPy, and have managed to get good results. Recently, I have had an issue when loading an SLC stack. The SLC stack was generated with the following parameters: I ran the MiaplPy software with the suggested command "miaplpyApp.py kawerau.cfg --runfiles --dir ." the prepc_slc_isce.py application crashes, and I am unsure why. I thought it may be due to
The only difference I could think of between this SLC stack and other SLC stack that worked fine with miaplpy, is co-registration method: "NESD" was used here, and I had used "geometry" in the past with the SLC stack that were loaded into Miaplpy without issue. Perhaps the the choice of number of swaths could be a factor? I am stuck as to the issue. Below is the report of the run, is there anything else I could provide to help diagnosing the issue? Thanks for any help --RUN-at-2023-09-25 11:35:24.796217--
|
P.S. I am running the latest version of MiaplPy V0.2.1, which was downloaded ~20092023 |
Hi @Jesse-kearse |
Hi @mirzaees , yes I had run mintpy on the same SLC stack prior to miaplpy. Thanks for your advice! I will try your suggestion and let you know how it goes. Cheers |
hi @mirzaees , Actually, I had not run mintpy on this particular SLC stack, and there were no .rsc files in the /merged/geom_reference/ dir or the /merged/SLC/*/ directory. Any other ideas? Thanks again for your help. |
Hi @Jesse-kearse, |
I also have a similar issue. @mirzaees
After running ISCE2 command, the slc.full file was not generated.
I successfully used MintPy with the files generated by above command. I know there are a lot of example of command to make run_files in ISCE, Thanks |
Hi @mirzaees Thank you for offering to take a look. I have created the a zip archive "SLC_zip.zip" that contains the files you requested. You can download with the following command: rsync -av --progress rsync://[email protected]/kearsejess/ password: gJbmvnmtUU Thanks again. |
Hi @Jesse-kearse
one more issue is about the baselines you provided which seems to be a raster file for each date. however, miaplpy assumes text files in the following format if your reference date is
I don't know why your baselines are like this but stackSentinel.py should create those text files. You will still get error if your baselines are not in that format |
Hi @gjustin40 |
Thanks for taking the time to look at the files, @mirzaees , I really appreciate your help. The workflow I used was SLC: "stackSentinel.py -s /insar/raw/track_08/ -d /insar/raw/dem/dem.wgs84 -b '-38.16 -37.53 176.07 177.73' -n '1 2' -m 20180112 -a ./aux/ -o ./orbits -C NESD -W slc" I realise now that the post processing that I had done with StaMPS (which includes a multi-looking step) was probably the reason for the modified geometry files. But with your recent update this will no longer be an issue! thanks, I will git pull and re-install. The baseline files I sent were from ./merged/baselines/ dir. Sorry I misinterpreted which baseline information you wanted. The files in ./baselines/ dir are in the correct format: 20180112_20180301/20180112_20180301.txt, so that should be fine. I will let you know how it goes. Thanks again. |
Following git pull and re-installation it was a successful completion of "miaplpyApp file.cfg --runfiles --dir ." Thanks @mirzaees |
You are very welcome @Jesse-kearse |
@mirzaees Sorry for the really late reply. I run my stackSentinel.py with the following parameter I wonder if the problem arises from my multilooking settings of Thanks! |
@geoglee |
@geoglee If you only have the "merged" directory and sub directories, you may be missing the files that the .slc.full.vrt files are referencing. In my workflow, .slc.full.vrt files point to burst.slc.vrt files in the "coreg_secondarys" directory, one above "merged". The raw data is contained in the burst.slc files within the same directory. I ran into this issue by mistake when I deleted a whole bunch of files (to gain extra disc space) thinking I only needed the merged// files. You can check by opening the *.slc.full.vrt files and checking the path in |
...checking the path in SourceFilename relativeToVRT |
Thank you a lot for helping me! For the path problem, awkwardly, I rechecked the template and just found that I didn't turn on the auto path function since I thought the default setting (auto) was yes till I noticed the comment behind miaplpy.load.autoPath. As I turn on the auto path function, Miaplpy seems to work right now (though it's still running). Hope it can operate normally till the final step. I'll report the outcome later. Another question about the stackSentinel.py settings. I'm not sure whether multilooking (-z, -r) and num_connections (-c) will affect the Miaplpy processing results. Any ideas? Besides, I already put the keyword "Sen" into the file name of my template, but the message still outputs |
Hello,
I used to analyze Sentinel1 images with MintPy and I found that MiaplPy seems to need different input. However, I'm confused about how to set stackSentinel.py parameters so that I can get coregistered SLC data in full resolution. Is there any document/discussion that could be referenced? (I can hardly find one so far)
Thank you
The text was updated successfully, but these errors were encountered: