Hello @thho,
My hardware is Xeon® Silver 4210 CPU @ 2.20GHz, 40 CPUs, 2 threads per socket.
Regarding parallelism, page #20 on StaMPS manual says:
Parallelisation of steps 1-5 for patch processing.
You can run stamps_mc_header(start step,end step) just like conventional
stamps(start step,end step) to increase the processing speed of the first 4 steps of StaMPS. You can specify the number of cores to be used using setparm(‘n cores’,XX), where XX are the number of cores to be used.
Anyway, I tried to use setparm(‘n_cores’, something bigger that 1) but it says that I cannot do that because I don’t have need for that, something like that. I think it’s because I have only 1 patch.
I tried it again later, and it let me set the n_cores parameter, but when I typed stamps_mc_header it says:
Decrease number of cores, as lesser patches are being processed…
1Done
Hello @ABraun,
I used stamps(0,x) because it says on page #20:
Re-start processing from last succesfull step.
You can run stamps(0,end step) or stamps_mc_header(0,end step) with the startstep set to 0. In this case StaMPS will check which is the last completed step for each patch prior to starting the next step.
That’s why I uset stamps(0,x), I wanted to be sure that the last step is completed. And that is exaclty the reason for my question -
If it starts from the last completed step, why does stamps(0,6) starts from
**** step 4 ****
…
**** step 5 ****
…
I want to emphasize that it does only minor calculations (if any) now, and then procceed to step 6. It’s not like running steps 4 and 5 for the first time.
Hi everyone, I’m running Stamp s and at step 1 it gives me an error message ps_load_initial_gamma. I checked the snap export and everything is ok.
The error is on line 70. I share the screenshot.
thanks suribabu but it didn’t help, i decided to modify line 69 by removing the +1.
I would like to ask you two questions.
is it correct what I did?
i don’t understand how it works, but it seems to work.
i share the screenshoot and the modified file.ps_load_initial_gamma.m (7.3 KB)
I hope I didn’t make an irreparable mistake.
2)I would like to understand why it doesn’t work, does anyone have any ideas?
Instead of changing code. Please reprocess the mt_prep_snap step once again. I feel changing code is not a good idea because it’s working for most of the users.
ok thanks suribabu for the advice I am re-running mt_prep_snap with these parameters 0.40 4 26 70 200 because the export contains two complete iw’s (IW2 and IW3). In this way the patches contain about 5 million pixels, is this correct approach?
I performed a test with 6 interferograms. The final project will use 137. I decided to make 6 product stacks. What do you think? Could the test be too few interfergrams?
Thanks suribabu for the help, I am exporting 16 more images. I hope this solves the problem. I have tried mt_prep_snap again, it does not give any error, no empty interferograms.
hi @suribabu , I imported all 131 images, I used mt_prep_snap with the following setting 0.4 26 4 70 200, I restored the ps_load_intial gama script but now it gives me an error when it gets to PATCH_3 I add a screenshot:
I read on the forum to double check all the interfergrams and @ABraun says to execute everything on a single PATCH (Workflow between SNAP and StaMPS - #503 by Gijs), how can I solve it according to you?
what did you mean by “Better go for python wrappers”?
One last thing to ask @suribabu, the last post you wrote was about my problem "One more solution for this without unintalling the Matlab, insar_processor Changes Doris to snap.
like below. "?
thank you all for the help. I am learning a lot.
this is only an option when your area is small and the error is related to the merging of the patches. Can’t say what’s the reason in your case, sorry.
dear @ABraun , i checked pscands.1.ij files in all 131 patches and there are many empty files. But I checked the files in rslc and diff0 there are no empty files. i checked the ifg there are no wrong files. Maybe there is something wrong with mt_prep_snap, I’m trying with less patch, is that wrong?