-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
Operation killed issue using, two INSAR scenes to process #197
Comments
The dask.persist() command materializes the results in memory. Do you have sufficient RAM to handle both the processing and the results? The code snippet you provided is recommended for educational purposes as it includes all the operations on the data. However, it is not the most efficient for big data processing. Instead, you can use the sbas.compute_interferogram_multilook() function, which optimizes the workflow immediately storing the results on disk. The usage of this function is well demonstrated in the PyGMTSAR examples. |
Thank you very much for describing it. I got it. I will do as suggested and share updates :) |
In case you cannot resolve it on your side, don’t hesitate to share your test notebook on Google Colab with public read access. |
Thank you so much ! I definitely will once I give it a try :) |
Hi there dear Alexey Pechnikov, I couldn't do that step to generate interferogram. I tried with the code you suggested but I get some errors. I have attached my notebook. I am looking forward to listening to your suggestion. Thanks a lot |
Please share a link to a public Google Colab notebook that reproduces your issue, so I can review it. |
Okay thanks I will share it, let me get it in the google colab |
Hey there,
I am using 2 reframed sentinel-1 scenes to generate a large interferogram. AT the phase computation and correlation stage, the operation kills and the python interpreter terminates.
When I try to process again, I have to start from the scratch to do all steps because I need to run sbas = Stack(WORKDIR, drop_if_exists=True).set_scenes(scenes) to set the sbas parameter prior to running any sbas_computations (e.g., sbas reframe, sbas align, or geocode).
What could be the reason for such termination of session ? How to better handle such problem. Also, is there a way so that I don't need to restart from the scratch in case of such terminations, in order to save time ?? It might be lack of my knowledge in coding to be not able to handle this issue, but I am looking forward to your suggestions.
Thank you so much in advance for your guidance and patience...
The text was updated successfully, but these errors were encountered: