This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Warning stop joint
12-05-2011, 03:37 PM,
#1
Warning stop joint
What is the cause of this warning?

   

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

16-05-2011, 04:21 PM,
#2
RE: Warning stop joint
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?
17-05-2011, 07:37 AM,
#3
RE: Warning stop joint
The project file has been sent to you.
19-05-2011, 09:18 AM, (This post was last modified: 19-05-2011, 10:27 AM by Dr. J Foerster.)
#4
RE: Warning stop joint
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.


Forum Jump:


Users browsing this thread: 1 Guest(s)