Capturing the step of analysis that a FBE fails
Moderators: silvia, selimgunay, Moderators
Capturing the step of analysis that a FBE fails
Is there a way that we can view in which step of analysis the warning of type: "ForceBeamColumn2d:update - failed to get compatible element forces & deformations for element: 2<dw:<< ...." is taking place? I am running an analysis in which the only problem is that the above warning appears for one element (in only one time step after one iteration), although the analysis continues without any other problem and it converge to a solution. Are we able to "capture" in which time step this occurs so to find out what could be the cause of the warning?
Re: Capturing the step of analysis that a FBE fails
that message should stop the current analysis step .. if it does:
set failsOutput [open fail.txt w]
while {$t < $tFinal} {
set ok [analyze 1 $dt]
if {$ok != 0} {
puts $failsOutput "Problem at time: [getTime]"
.. your usual stuff
}
close $failsOutput
in the script before you try other things
open a file and in the script when an analysis step fails spit out a warining to yourself.
set failsOutput [open fail.txt w]
while {$t < $tFinal} {
set ok [analyze 1 $dt]
if {$ok != 0} {
puts $failsOutput "Problem at time: [getTime]"
.. your usual stuff
}
close $failsOutput
in the script before you try other things
open a file and in the script when an analysis step fails spit out a warining to yourself.
Re: Capturing the step of analysis that a FBE fails
In my case it seems that the current analysis step doesn't stop when the warning message occurs. I am transferring what is appearing on the screen during the analysis (at the end and after some more steps, the analysis finishes without any problem)
...
CTestNormDispIncr::test() – iteration: 1 current Norm: 0.00218257 (max: 0.01, Norm deltaR: 542.135)
WARNING – ForceBeamColumn3d::update – failed to get compatible element forces & deformations for element: 8(dW: << 3.11392e-007, dW0: 1.90313e-005)
CTestNormDispIncr::test() – iteration: 1 current Norm: 0.0021708 (max: 0.01, Norm deltaR: 582.041)
CTestNormDispIncr::test() – iteration: 1 current Norm: 0.0020197 (max: 0.01, Norm deltaR: 540.048)
...
...
CTestNormDispIncr::test() – iteration: 1 current Norm: 0.00218257 (max: 0.01, Norm deltaR: 542.135)
WARNING – ForceBeamColumn3d::update – failed to get compatible element forces & deformations for element: 8(dW: << 3.11392e-007, dW0: 1.90313e-005)
CTestNormDispIncr::test() – iteration: 1 current Norm: 0.0021708 (max: 0.01, Norm deltaR: 582.041)
CTestNormDispIncr::test() – iteration: 1 current Norm: 0.0020197 (max: 0.01, Norm deltaR: 540.048)
...
Re: Capturing the step of analysis that a FBE fails
let me look .. must be failing in a newstep() .. i need to know static or transient analysis? & what integrator?
Re: Capturing the step of analysis that a FBE fails
Here are the comands used for the analysis:
test NormDispIncr 1.0e-2 100 1
algorithm ModifiedNewton -initial
system BandGeneral
numberer RCM
constraints Transformation
integrator DisplacementControl 54 1 $dU 1 $dU $dU
analysis Static
...
test NormDispIncr 1.0e-2 100 1
algorithm ModifiedNewton -initial
system BandGeneral
numberer RCM
constraints Transformation
integrator DisplacementControl 54 1 $dU 1 $dU $dU
analysis Static
...
Re: Capturing the step of analysis that a FBE fails
can you send me the script .. everything would seem to indicate that an error should be returned .. so i need to step through the code to see what is up.
fmckenna ATTTT berkeley DOTTTTTTTTTTTT edu
fmckenna ATTTT berkeley DOTTTTTTTTTTTT edu
Re: Capturing the step of analysis that a FBE fails
fmk wrote:
> can you send me the script .. everything would seem to indicate that an
> error should be returned .. so i need to step through the code to see what
> is up.
> fmckenna ATTTT berkeley DOTTTTTTTTTTTT edu
Any conclusion about this matter? (Did you receive the script?)
> can you send me the script .. everything would seem to indicate that an
> error should be returned .. so i need to step through the code to see what
> is up.
> fmckenna ATTTT berkeley DOTTTTTTTTTTTT edu
Any conclusion about this matter? (Did you receive the script?)
Re: Capturing the step of analysis that a FBE fails
if you could send it again as it possibly went into my spam. what is your email adrdess?
actually why don't you also cc it to: ftmckenna ATTTT gmail DOTTTT com
actually why don't you also cc it to: ftmckenna ATTTT gmail DOTTTT com
Re: Capturing the step of analysis that a FBE fails
I just sent it again (in both addresses). My address is ending at ... @cha.forthnet.gr
Thank you
Thank you
Re: Capturing the step of analysis that a FBE fails
nothing has arrive in either mailbox! did you get any sending error messages?
Re: Capturing the step of analysis that a FBE fails
fmk wrote:
> nothing has arrive in either mailbox! did you get any sending error
> messages?
No error message. Strange...
> nothing has arrive in either mailbox! did you get any sending error
> messages?
No error message. Strange...
Re: Capturing the step of analysis that a FBE fails
actually it is in the spam folder!
Re: Capturing the step of analysis that a FBE fails
running SPEAR.txt i see no element failures? what version OpenSeesX.X.X (rev YYYY) and operating system are you running. if windows, are you running the 32 or 64bit executable?
Re: Capturing the step of analysis that a FBE fails
I think it is the latest version: 2.4.3 rev5695. Windows 64-bit
Re: Capturing the step of analysis that a FBE fails
can you download the latest and see if the error is still there .. 2.4.4. rev 5730