Forum Replies Created
-
Posts
-
We cannot reproduce the problem, all the conversion runs fine starting from any combination of lenght and force units.
ActiveTcl 8.6.9 is ok, this is apparently due to the distribution of OpenSees that came along with some tcl init files.
DIscard then and use another built of OpenSees, like: https://github.com/eesd-epfl/OpenSees/blob/master/Win64/bin/OpenSees.exeThanks for the file. We cannot reproduce the error, because analysis with OS runs fine in our pc.
I can advice to place opensees.exe in the installation folder and ActiveTcl 8.6 must be installed and added to path (see https://www.activestate.com/products/tcl/downloads/).Sorry, no support for OpenSees solver. If the springs are not part of NonLinear module, please attach the model.
Hello,
it mainly depends on type of seismic isolator. If damping is provided, you can use dashpot (see https://www.nextfem.it/it/a-survey-on-non-linear-analysis-in-nextfem-designer-part-1/).
If bilinear behaviour and damping are present, a bilinear spring with dashpot could be used.We released a minor patch, no need to change any option.
Please use command ?/Updates/Check for minor updates.Thanks for your feedback. Yes, eccentricity in section is useful in verifications, it does not reports moments as you wanted to.
We’ll introduce an option in the next update to switching from one to another approach.Dear,
this happens for 2 different reasons in both solvers:
– in the built-in solver, the rigid link is modelled with penalty method. this is equivalent to a kinematic constraint; in other words, the rigid link does not have a beam-like behaviour
– in Opensees, a kinematic constraint is applied directly with “equalDof”. Please note that this is different from “rigidLink beam” behavior (this last was the one you expected).This is not the proper way to model this (it can interfere with rigid diaphragms) – please use a offset in the section of the element, by moving the center of the section in its properties.
Thanks for your interest in NextFEM Designer!
Yes, we confirm the problem you encountered, it is an issued of the last release.
An update for this is already available, please press CTRL+U to update.Hello,
please set, in Analysis options, Static, Non-linear and P-Delta options. Or, for other types of analyses, check “second-order” option.Hello,
thanks for your interest in NextFEM Designer. This is an old sample, will be removed – it is working only for running outside the program, you should simply import manually the results via “File\Import OpenSees results”.
In general, OpenSees script can be imported when having a few simple expressions inside. Also “include” has to be avoided if possible.If you set OpenSees as solver, you can input your model directly inside Designer and perform automated analyses, without any additional requirements.