Closed u-anurag closed 4 years ago
For the database folder, are you thinking an OpenSees model database, or text files with the relevant information? Text files generally may be a little easier for people to work with.
Just text files with the standard .out extension. See the code I have added to this branch. https://github.com/u-anurag/OpenSeesPy/commit/cfe84a02d911add5f1d919c2a15c657785a2ef43
That makes sense. Looks good to me. If we are always saving all the element stress/strains, the file sizes could become quite large. How would you feel about:
if ele_forces == True:
recorder('Element', '-file', EleForceFile, '-dT', deltaT=0.01, '-ele', *eleList, '-dof',*dofList, 'localForce')
Also, doesn't close on write slow down the saving process significantly? I haven't actually tested this, but I did see a warning on the wiki: https://openseespydoc.readthedocs.io/en/latest/src/nodeRecorder.html It might be cleaner to let the user issue the wipe command themselves at the end of the analysis.
This is complete now.
Add procedure to save an Output Database folder with files for node and element data, analysis output such as displacement, drift, element force, base shear, stress and strain.