PLE forum
Warning stop joint - Printable Version

+- PLE forum (http://www.ple4win.nl/forum)
+-- Forum: Support (http://www.ple4win.nl/forum/forumdisplay.php?fid=5)
+--- Forum: Ple4Win Calculation (http://www.ple4win.nl/forum/forumdisplay.php?fid=30)
+--- Thread: Warning stop joint (/showthread.php?tid=175)



Warning stop joint - shaswin - 12-05-2011

What is the cause of this warning?

[attachment=178]

Iteration process will not be satisfied (within MAXGIT=50) due to this warning, can someone explain it.




RE: Warning stop joint - Dr. J Foerster - 16-05-2011

As this is an undocumented, internal error it is very difficult to determine what exactly is happening from the screen shot alone.

Would it be possible to mail us the project files where this error occurs?



RE: Warning stop joint - shaswin - 17-05-2011

The project file has been sent to you.


RE: Warning stop joint - Dr. J Foerster - 19-05-2011

Thank you for the project files.
We assigned ticket no. 1035 to this issue.

It took a while to figure this one out as the code generating the warning message was buggy Angry

The problem is that in your case the program has difficulties filling the ADDCROS output table. With SOILNB filled and a pipeline with joints the program does not find a solution even after 250 iterations (Warning "ADDCROS iteration stopped (>250)").
At that point 2 of your joints exceed the maximum angle they can bend (those are the "Stop joint..." warnings, ???????? should read SOILNB, 0 should be the node number of the joint).

As no equilibrium was found, the data of the last iteration might be close to equilibrium, or way off. There is no way to tell.

Currently, there is no easy way in your case to allow the program to successfully calculate DF6.1. It might help to allow a larger maximum angle in the joints, maybe the data in SOILNB can be changed, it is a matter of trial-and-error.

We keep improving the iteration process(es) in Ple4Win. As a result of your thread in this forum, we have changed the ADDCROS-iteration process so that the next version (yes, there will be one shortly Big Grin ) will find a solution.