Forum Replies Created

Viewing 15 posts - 31 through 45 (of 261 total)
  • Author
    Posts
  • in reply to: Re: Thin wall geometry such as a boat hull #5915
    NextFEM Admin
    Keymaster

    Hello,
    sure you can – in Rhino, the hull has to be a simple mesh to be imported correctly via NextFEM-Grasshopper plugin.
    Then you can assign thickness from Sections mask, or do a simple parametric design with a few python lines.

    in reply to: Type initializer for ‘nflib.nflib’ threw an exception #5910
    NextFEM Admin
    Keymaster

    in Control Panel, open International Settings. In Administration options mask and Non-Unicode program language, click Change system locale setting… and set the language to English.

    This should not be required anymore since version 2.5.0.3.

    in reply to: Type initializer for ‘nflib.nflib’ threw an exception #5905
    NextFEM Admin
    Keymaster

    Hello,
    yes, in Control Panel, open International Settings. In Administration options mask and Non-Unicode program language, click Change system locale setting… and set the language to English.
    Then restart the program.

    in reply to: Cracking verification #5803
    NextFEM Admin
    Keymaster

    Version 2.3 was accounting a reduction factor by means of Eurocode 2 on quasi-permanent combos, which is not actually considered in NTC. Our internal rules prevent us to act on past versions (v2.3 does not receive updates since the end of June), however we understand your needs and we decided, exceptionally, to release a small update for your version. Please check for minor updates from inside the program.

    in reply to: Cracking verification #5791
    NextFEM Admin
    Keymaster

    Thanks, we checked element 623 in v2.4 and we confirm there’s no issue. Compared with v.2.3, the current version has been revised for SLS verifications, both for Eurocode and Italian codes.
    As a workaround, you could run the checking set “NTC_CA” included for SLS combinations.

    in reply to: Cracking verification #5788
    NextFEM Admin
    Keymaster

    Please retry now, there was limitations on uploading capabilities

    in reply to: Cracking verification #5769
    NextFEM Admin
    Keymaster

    Hello,
    the section which is mostly compressed is the one with the worse rebarDiameterRatio maybe due to the composite bending you have in the bottom pic (hence corner bar is more stressed).
    Could you share the model by uploding it at the bottom of Support page?

    in reply to: Performing checks takes a long time #5763
    NextFEM Admin
    Keymaster

    Hello,
    checking speed for RC structures in actual version 2.4 has been improved.
    However, if you’re still using 2.3 you could use some strategies to speed-up the process:
    – use less stations: if you don’t have trapezoidal distributed loads on beam, in most cases it’s safe to adopt 3 stations instead of 5
    – the option “Save results in NXF file” does not affect checking speed
    – proceed by combinations groups or by element groups: for caching reasons, in v2.3 you’re advised to proceed by groups of elements or combinations (ULS, ELS, and so on) since checking results are cumulated into model.

    in reply to: Set rigid diaphragms using NextFEMpy module #5745
    NextFEM Admin
    Keymaster

    Dear Luciano,
    we’re still working on nextfempy module, the last calls have been added today. Please update to nextfempy 0.1.3.

    thanks

    in reply to: Slab rebar design #5701
    NextFEM Admin
    Keymaster

    Static rebar design does not perform design on slabs. Checking should work: maybe you’re requesting checks on combinations (default optionin Verifications mask), but you don’t have combos in the model. Select “ALL” for load case.

    in reply to: Slab rebar design #5698
    NextFEM Admin
    Keymaster

    Hello,
    for the first issue, the “Wall__” identifier is needed to assign rebar to a slab or a wall, hence the group cannot be renamed. I needed, you can create another group with a more frindly name.

    For the error in checking, you’re using a deprecated script. In your version there’s no need to call the Wood-Armer moments scripts, since from ver. 2.1 the Wood-Armer moments are available directly in view (see Area forces, mm**WA* components) and in tables (see Extract data mask, Area Forces).

    If you need to use then in checking, try calling directly the following quantities. Use this as a script in Verifications mask:

    
    @_mxWAbot
    mmaxX
    @_myWAbot
    mmaxY
    @_mxWAtop
    mminX
    @_myWAtop
    mminY
    

    EDIT: actual version 2.4 supports also shear checking in slabs.

    in reply to: Thanks for implementing nextfempy module #5684
    NextFEM Admin
    Keymaster

    Dear Luciano,
    thanks for your appreciation.
    NextFEMpy was developed to allowing everyone to use NextFEM Designer without loading all the libraries, but through the REST API server (included in NextFEM Designer plugins).
    A sample code for VIKTOR platform is already available in our GitHub page, we’ll show the usage also with VIKTOR asap.

    NextFEMpy was designed to be compatible with all the previous API used with pythonnet. There’s no need to convert old code for more perfomance, it should be the same with both approaches.

    Also NextFEM Server could be used with the same approach; we’ll provide samples.

    in reply to: concrete shell reinforcement design (script) #5453
    NextFEM Admin
    Keymaster

    Hello,
    thanks for your suggestion; if you tried with our scripting engine to compile a script for the so-called “sandwich” model for shell design, let us know and we’ll try to improve/implement it.
    Btw, we considered to implement this in the past, but by now there’s no request from our paid customer for this, hence we suspended the development. Instead, we implemented the shear check for slabs into Concrete module.

    in reply to: CatenaryCableElement from OpenSees #5225
    NextFEM Admin
    Keymaster

    Hello,
    CatenaryCableElement is already supported for model import and export. Actually, some distributed loads could not be applied to the element, but lumped to equivalent nodal loads. You can test it with version 2.3.

    EDIT: I forgot to mention: to set a truss as a cable, in Element Properties set CableNL to 1.

    in reply to: p-delta analysis strange behaviour #5214
    NextFEM Admin
    Keymaster

    As told, the program does not have internal automatic meshing. Hence, I simply mean breaking the beam in 2 pieces. Please note that this is required only for single beam model, general structures always have internal (not bounded) nodes.

Viewing 15 posts - 31 through 45 (of 261 total)