Dear STKO team,
I attached my model, and I have some problems:
1/ Is there any problem in the final result if some steps did not converge, but the process continue to go ahead? (as the upper notice in Figure 1)
2/ my time history is 60s, however the model got some errors at 12.79s with error "Assertion failed in file socksm.c . ..." (as the bottom notice in Figure 1). what is the meaning of this error?
Thank for your support.
Buu
Running Error: "Destroying lib handle"
Running Error: "Destroying lib handle"
- Attachments
-
- soil_domain.rar
- (2.62 MiB) Downloaded 254 times
-
- Figure 1.PNG (475.21 KiB) Viewed 2178 times
Re: Running Error: "Destroying lib handle"
The "Destroying lib handle" is not the error itself. It is a message that appears every time OpenSees closes and you previously used the MPCO recorder. It's just a log message to make sure the MPCO recorder correctly destroys the handle to the HDF5 library.
The error instead appears to be due to the parallel communication in OpenSees (MPI Error) after a non-convergence.
Unfortunately in your case something went wrong and created a crash in the MPI library (not OpenSees itself). However, the error might be due to a bug in some elements/materials in OpenSees. Unfortunately it is not so easy to find.
You can start by changing some components until you find which one is causing the issue.
The error instead appears to be due to the parallel communication in OpenSees (MPI Error) after a non-convergence.
It's fine because, when a time step does not converge, and you are using the Adaptive Time Step utility in STKO, opensees will try to reduce the time step and repeat the calculation.1/ Is there any problem in the final result if some steps did not converge, but the process continue to go ahead? (as the upper notice in Figure 1)
Unfortunately in your case something went wrong and created a crash in the MPI library (not OpenSees itself). However, the error might be due to a bug in some elements/materials in OpenSees. Unfortunately it is not so easy to find.
You can start by changing some components until you find which one is causing the issue.