The recorder is too tired to work???

[burnningcat]

Dear Sir,

I build 6 storey model in OpenSees with the beamwithhiges element. Totally there are 375 elements. Then I try to record the stress-strain relationship of all these elements, because I want to check in any step if there is a plastic hinge in a certain element.

For each element I record the response of 2 sections and for each section I record 4 fibers. So totally there are hundreds of the recorders.
But I find that after record like 500 files, the recorder seems too tired and refuse to work! I mean in one time, it can not record too many files. The solution is record 300 files in a time, and run the analysis agiain and record the other 300 files…But it is quite boring and very easily to make mistake.

So dear sir, I kindly ask if there is a way to record all the files in a time? Thank you very much!!

[PSJ]

I think I have a similar problem. I have a model of a tall steel structure (40 stories) so i have generated many recorders (3000+). However only 509 of the output files are generated when i attempt to load all of the recorders. I have cut the number of recorders I define into groups of 500 and run each group individually so i am very confident this is not an error in my recorder commands. Has anyone else encountered this problem? Any proposed methods to trouble shoot it or work around it?

[oleviuqserh]

Hi burnningcat and PSJ. Have you tried to put the model into a loop to automatize the generation of those remaining recorders? I mean, the basic idea would be:

------------------------------
set numExecutions 3

for {set i 1} {$i <= $numExecutions} {incr i} {
wipe

# here goes the model script...
…

# Recorder definitions...
if {$i == 1} {
# first bundle of recorders
} elseif {$i == 2} {
# second bundle of recorders
} elseif {$i == 3} {
# third bundle of recorders
}

# here goes the analysis procedure...
…
}
------------------------------

This is actually the Frank's approach to run hundreds of simulations automatically… for more info, there is a pdf document uploaded here:
[url] http://opensees.berkeley.edu/OpenSees/p ... essing.pdf [/url]
explaining how to make the loop in detail… the script shown in page 12 is strongly recommended for large models, because the model is run once! (note that it has been defined before the program reaches the loop 'foreach'…)

Hope this helps you.

[fmk]

there is a limit imposed by the operating system on the # of files a program can have access too .. you do realize that you can record the information for more than 1 element in a file .. i.e. one recorder could be used for all 375 elements.