Forum Replies Created
-
Posts
-
Hello,
thanks for your inquiry. By default, stiffness of RC members does not change when adding/varying rebars. This is a common assumption in all civil design programs.You add rebar to the cross-section (Section properties) if you want to calculate its strength; to add rebars on elements (this does not affect the analysis results, as told before) use the Assign / Rebar command. This will affect only RC checking.
Hello,
you can assign partial end releases by input the rotational stiffenss (see Assign / End Releases, and check the option “Input stiffnesses”).Hello,
if not specified in the window, units of material properties are consistent with the model. For instance, check the material library in NextFEM installation folder C:\Program Files\NextFEM\NextFEM Designer 64bit\data\Steel-MC EN.nfm (open as plain text). You’ll find:
K [N/s/°C] – conductivity
Cp [N*m/(kg*°C)] – Specific heat
a_T [1/°C] – thermal distorsion linear coeff.
Conductivity for steel is assumed as 54 W/mK (1W=1Nm/s, hence 1N/(s*°C) = 1 W/mK), then this value is converted into model units.Hope this helps, regards
Hello,
the problem is related to pythonnet, not to our API. You need to use the List object from .NET to access the method. Please find attached amended script.Hello,
thanks for your interest. Yes, the new command for beam loading allows to insert values and positions as arrays. We don’t have a change log for minor releases.Hello, the previous minor patch brake something, a new patch will be released today and then please update again to 2.2.0.4.
We get the correct results by using the attached script.Thanks for your appreciation.
Also, we can issue academic licenses for some of the modules for free – if needed, let us know by using the contact page: https://www.nextfem.it/it/request-a-quote/Dear prof. Luciano,
thanks for writing to us, we immediately released a patch for this. Please re-download version 2.2.0.3 from now on (https://www.nextfem.it/it/download/) and re-install it over the existing copy.ps.
you can rewrite the Python code as attached, wihtout hard-coding the API path.Hello,
we investigated the issue and turned out that there’s probably a problem in your local ISP – unfortunately we can do nothing for that. We can advice you retry with a VPN (i.e. using Opera browser).Dear Jevon,
thanks for your contact. Actually our services are running fine and this is the first time we hear about the problem you encontered.
To help solving this, please tell us from where (which country) you’re connecting, we can involve our IT in this.
regardsHi Stephen,
no, there’s no documentation on xml format as well, as it is easily readable. If you have some specific queries please write a mail to us or have a look at Devs’ manual (https://www.nextfem.it/it/help-support/) – it could be easier to transmit info via API than using XML of JSON format.Hello,
sorry no documentation on this, that option imports the same model as in XML format, but in Json. Contents must be the same, except that Json format can be written in a more compact (but less readable) way.Hello,
loadPackage has not been made for working directly in OpenSees shell, please use inside script. Anyway, rSpectrum has been tested only with procedure011.tcl included with NextFEM Designer.