Warning

Forum for OpenSees users to post questions, comments, etc. on the use of the OpenSees interpreter, OpenSees.exe

Moderators: silvia, selimgunay, Moderators

Post Reply
Fameh
Posts: 10
Joined: Wed Nov 12, 2014 11:30 am

Warning

Post by Fameh »

Hello,

Can someone please help me understand the following warning message:
Warning: CTestNormDispIncr::setEquiSolnAlgo() - no SOE

Thanks
dschmuhl
Posts: 13
Joined: Sun Jan 13, 2013 8:20 am
Location: The Ohio State University

Re: Warning

Post by dschmuhl »

I am also currently dealing with this message and am not sure what exactly it is. I have looked at the source code and I see that has something to do with asking if a solution algorithm has been set, but I am not sure about the details of "theAlgo" object and what it encapsulates, so I am having a hard time figuring out where the message originates. Any help from other on this would be appreciated.
fmk
Site Admin
Posts: 5884
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Re: Warning

Post by fmk »

use the system command before the test command
dschmuhl
Posts: 13
Joined: Sun Jan 13, 2013 8:20 am
Location: The Ohio State University

Re: Warning

Post by dschmuhl »

Frank,

Thanks for the response! In my case, I do have the system command before the test command when this message presents. This is my analysis setup:

constraints Transformation
numberer RCM
system UmfPack
set testTypeStatic NormDispIncr
test $testTypeStatic 5.e-4 250 0
algorithm NewtonLineSearch 0.8
integrator DisplacementControl $IDctrlNode $IDctrlDOF $Dincr
analysis Static;
GiuseppeDelGobbo
Posts: 28
Joined: Fri Oct 18, 2013 6:35 am
Location: University of Oxford

Re: Warning

Post by GiuseppeDelGobbo »

Has this been solved? I am getting the same warning only when I used algorithm NewtonLineSearch
fmk
Site Admin
Posts: 5884
Joined: Fri Jun 11, 2004 2:33 pm
Location: UC Berkeley
Contact:

Re: Warning

Post by fmk »

i have removed the message from the source code .. it will be reflected in code next time i get it up .. it will now spit out the warning only if it is the actual testing phase instead of when the test is actually created.
Post Reply