Forum Replies Created
-
Posts
-
Hello,
please clarify your question, in particular the final one. The program allows any kind of modelling, hence simply check end releases at the end. I see from your model that the moment is correctly released at the top of the pillars.
It is not clear why you want to apply restraints on the joints; you may want to apply only internal constraints or releases.Hello,
as stated, IronPython is not officially supported.You can try compiling the script to see if the issue is more clear. Use:
ipyc /main:yourScript.py /target:exe
and then launch the resulting .exe . If it works, it’s an issued on IPy side.
Hello,
IronPython is not officialy supported, however I can suggest trying with IronPython 3.4.1 instead of 2, with .NET Framework.Dear Luciano,
update is out, please see API https://www.nextfem.it/api/html/M_NextFEMapi_API_addThermalDistLoad.htmLet us know, regards
Dear Luciano,
thanks for your inquiry, please wait the next minor patch for having this solved. We’ll also try to add an API method for adding temperature loads.Regarding the sign of temperature gradient: starting from a user’s dT, the gradient is applied to the section as to have -dT/2 on the positive Y+ face of the section, and dT/2 on the negative Y- face of the section. We’re evaluating to invert this sign as to have positive temperature on Y+.
Yes, this is a valid option.
In practice, rebar stiffness is always neglected, while to account for cracked concrete the Young’s modulus can be reduced (up to 50% as per Italian code – other codes can have different limits).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.