What is a trick/smart way to manage large data generated because of non-linear analysis in ETABS?
I have 15 storey building whose non-linear time history(6 GMs of different durations) analysis is creating data of ~40GB. What is the the best way to manage this data without running out of your local PC memory?
Some suggestions:
1. Limit the hinge locations only to members expected to yield. For instance, if the column remains elastic (and better be), no need to assign hinge.
2. Reduce the output time steps, i.e. per 0.1 second. Perform3D software makes the input and output time steps different, reducing the output file size. It might be same case for Etabs, but please make sure first by a comparison trial.
3. Fiber elements also require more data. Shear wall need this, but end-hinge is mostly enough for frame element.
4. If the floors do not contribute much in lateral resistance, it can also be removed and replaced by load to beams.
Anyway, it is normal for NLTHA output to have GBs size.
You can increase the time step between ground acceleration of time-history (exclude some data).
- Badges
- Science topic
- Similar topics
- Phytochemistry
- Extracts