I’m running a single graph of polarimetric decomposition on Sentinel-1 scene using gpt.
The command hangs once the processing is part complete (1/3 judging by this image) with no error message.
I am using SNAP 5 and have allocated around 24GB RAM to gpt.
Any help would be appreciated! For now I will test a different scene.
If the process has been killed, you should see some message from gpt. Can you try again and post a screenshot of GPT?
Should yes, but in the end it just hangs and it doesn’t say why it stops processing.
I just see that it is using restituted orbits instead of precise orbits. Update SNAP to version 6 and try to run the graph again, let’s see.
Updated to SNAP 6.
Graph gets to 20% and says ‘Database closed’ and then hangs.
No error message. My intuition says it’s a resource issue but there seems to be enough space and RAM, plus the graph works in the GUI.
Frustrating because I am running a service based on automated SNAP processing with gpt, and I think this is a bug created by the Sentinel-1 format change!
The steps in the graph are:
Again the graph works in the SNAP GUI but not in the command line. Perhaps someone could test the graph ?
When I use “gpt -e” the graph hangs at just past 20% processing.
Resolved by calling gpt with the -c parameter set at 75% of the java heap space.
“gpt -c 24G”
The java heap space is set using -Xmx in gpt.vmoptions.
This has also reduced the time for my processing chain to run by a factor of 4
gpt --diag was also helpful.