APPCRASH -- Recorder Node

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

Moderators: silvia, selimgunay, Moderators

Post Reply
jhoutenbos
Posts: 3
Joined: Mon Mar 23, 2015 10:52 pm
Location: Delft University of Technology

APPCRASH -- Recorder Node

Post by jhoutenbos »

L.S.,

When I run the following (very simple) example, this results in an 'APPCRASH' (i.e. 'OpenSees.exe has stopped working') without any further warnings:

#---------------------------------------------------------------------------------------------------------
wipe all

model BasicBuilder -ndm 3 -ndf 6

# nodal coordinates:
# source nodalcoords.tcl
node 1 0 0 0
node 2 1 0 0
node 3 0 1 0
node 4 1 1 0
node 5 0 2 0
node 6 1 2 0
node 7 0 3 0
node 8 1 3 0
node 9 0 4 0
node 10 1 4 0
node 11 0 5 0
node 12 1 5 0
node 13 0 6 0
node 14 1 6 0
node 15 2 0 0
node 16 2 1 0
node 17 2 2 0
node 18 2 3 0
node 19 2 4 0
node 20 2 5 0
node 21 2 6 0
node 22 3 0 0
node 23 3 1 0
node 24 3 2 0
node 25 3 3 0
puts "nodal coordinates ok"

# boundary conditions:
fix 1 1 1 1 0 0 0
fix 2 1 1 1 0 0 0
fix 13 1 1 1 0 0 0
fix 14 1 1 1 0 0 0
fix 15 1 1 1 0 0 0
fix 21 1 1 1 0 0 0
# fix 22 1 1 1 0 0 0
puts "boundary conditions ok"

# young's modulus
set E1 300000000
# poisson's ratio
set nu1 0
# thickness plate section
set h1 0.1
# mass density
set rho1 24

# sections:
section ElasticMembranePlateSection 1 $E1 $nu1 $h1 $rho1
puts "sections ok"

# connectivity:
# source connectivity.tcl
element ShellMITC4 1 1 2 4 3 1
element ShellMITC4 2 3 4 6 5 1
element ShellMITC4 3 5 6 8 7 1
element ShellMITC4 4 7 8 10 9 1
element ShellMITC4 5 9 10 12 11 1
element ShellMITC4 6 11 12 14 13 1
element ShellMITC4 7 2 15 16 4 1
element ShellMITC4 8 4 16 17 6 1
element ShellMITC4 9 6 17 18 8 1
element ShellMITC4 10 8 18 19 10 1
element ShellMITC4 11 10 19 20 12 1
element ShellMITC4 12 12 20 21 14 1
element ShellMITC4 13 15 22 23 16 1
element ShellMITC4 14 16 23 24 17 1
element ShellMITC4 15 17 24 25 18 1
puts "connectivity ok"

# recorders
recorder Element -file element.out force
recorder Node -file node.out -dof 1 2 3 4 5 6 disp
recorder Node -file reactions.out -dof 1 2 3 4 5 6 reaction
puts "recorders ok"

# loads
pattern Plain 1 Linear {
load 7 0 0 -1 0 0 0
load 8 0 0 -1 0 0 0
load 18 0 0 -1 0 0 0
}
puts "loads ok"

# system of equations
system BandGeneral
puts "system of equations ok"

# DOF numberer
numberer RCM
puts "DOF numberer ok"

# constraint handler
constraints Plain
puts "constraint handler ok"

# test NormDispIncr 1.0e-6 15

# algorithm
algorithm Linear
puts "algorithm ok"

# integrator
integrator LoadControl 1.0
puts "integrator ok"

# analysis type
analysis Static
puts "analysis type ok"

# analysis
analyze 1
# puts "analysis ok"

# loadConst -time 0.0

# print -closeOnWrite analysis_summary.out
puts "finished"
wipe
#---------------------------------------------------------------------------------------------------------

However, when both the 'Recorder Node'- lines are commented, the code runs fine. Can anyone tell me why this happens? The version used is 2.4.5, (rev. 5939). Also, when the last 2 elements are removed (element 14,15) including the corresponding nodes (24,25) the script also finished.

Many thanks in advance.
kamehdikhani
Posts: 12
Joined: Fri Oct 10, 2014 8:21 am
Location: ikiu- imam khomeini international university

Re: APPCRASH -- Recorder Node

Post by kamehdikhani »

hi Dear jhoutenbos
in using recorder Node command u should specify which node you want to record
for example :
recorder Node -file nodesD.out -time -node 1 2 3 4 -dof 1 2 disp

ref :
http://opensees.berkeley.edu/wiki/index ... e_Recorder
jhoutenbos
Posts: 3
Joined: Mon Mar 23, 2015 10:52 pm
Location: Delft University of Technology

Re: APPCRASH -- Recorder Node

Post by jhoutenbos »

Thanks for your reply!

I assumed that the default for omitting <-node> would be 'all nodes', as this was indeed what happened until OpenSees started to crash... When I try the syntax:

#------------------------------------
recorder Node ... <-nodeRange $startNode $endNode> ...
#------------------------------------

this still results in an APPCRASH, (using start=1 and end=25). When I change this into e.g.:

#------------------------------------
recorder Node -file node.out -node 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 -dof 1 2 3 4 5 6 disp
recorder Node -file node2.out -node 21 22 23 24 25 -dof 1 2 3 4 5 6 disp

recorder Node -file reactions.out -node 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 -dof 1 2 3 4 5 6 reaction
recorder Node -file reactions2.out -node 21 22 23 24 25 -dof 1 2 3 4 5 6 reaction
#------------------------------------

so splitting into multiple recorders, the script works again. Any idea why this is the case? Is there a maximum number of nodes which can be specified per recorder?

Again, many thanks in advance.
kamehdikhani
Posts: 12
Joined: Fri Oct 10, 2014 8:21 am
Location: ikiu- imam khomeini international university

Re: APPCRASH -- Recorder Node

Post by kamehdikhani »

hi
i think you make mistake in use of command
you should use node range in this format e.g. :

recorder Node -file nodeDisp.out –time -nodeRange 10 25 -dof 2 disp

try it and read this ref :

http://opensees.berkeley.edu/OpenSees/m ... al/258.htm
jhoutenbos
Posts: 3
Joined: Mon Mar 23, 2015 10:52 pm
Location: Delft University of Technology

Re: APPCRASH -- Recorder Node

Post by jhoutenbos »

Thank you for your reply.

When typing 'min=1 max=25' I meant filling this into the format from the reference guide, i.e.:

#---------------
recorder Node -file node.out -nodeRange 1 25 -dof 1 2 3 4 5 6 disp
#---------------

This is what you mean right? Because this still results in a crash. Or am I missing something here..?
Post Reply