NODAL_SUPPORTS with SteelEffectiveLength

How to use NODAL_SUPPORTS with SteelEffectiveLength with the new API ?
I have this but there is a problem with NODAL_SUPPORTS :

#—-Longueurs efficaces
rfem.types_for_steel_design.SteelEffectiveLengths(
	no=1,members=[],member_sets = barres_poteaux,
	flexural_buckling_about_y = True, flexural_buckling_about_z = True,
	torsional_buckling = False, lateral_torsional_buckling = True,
	principal_section_axes = True,geometric_section_axes = False,
	name = 'Longueur_Efficace_Poteau',
	nodal_supports = [[rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.SupportType.SUPPORT_TYPE_FIXED_ALL,
					 True, 0.0, rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.EccentricityType.ECCENTRICITY_TYPE_NONE,
					 0.0, 0.0, 0.0, 0.0, rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.SupportInY.SUPPORT_IN_Y_SUPPORT_STATUS_YES]],
	factors = [[1.0, 1.0, 1.0, 1.0, 1.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0]],
	intermediate_nodes = True, different_properties = True,                                                                                 
	factors_definition_absolute = False,
	import_from_stability_analysis_enabled = False,
	determination_mcr_europe = rfem.types_for_steel_design.SteelEffectiveLengths.DETERMINATION_MCR_EUROPE_EIGENVALUE)

Mod Edit: code formatting

Hi amazigh,

welcome to the Dlubal Community :slightly_smiling_face:

I would recommend to format code using backticks, which is much easier to read and which will increase the chance that other users help.

Best regards
Sören

Hey mate,

I don’t actually have a steel add-in so can’t test this myself, but I’ve used the api a bit so I figured I’d see if I could maybe find a solution :slight_smile:

Looking at the NodalSupportsRow section of the
SteelBoundaryConditions — Dlubal API documentation

I think you are maybe missing some arguments, nodes List[int] is probably the most important as I assume it dictates which node the support is applied to (I assume you have to create the nodes first).

Try this,

nodal_supports = [[
    1,  # no
    "",  # description
    rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.SupportType.SUPPORT_TYPE_FIXED_ALL,
    True,   # support_in_z
    0.0,    # support_spring_in_y
    rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.EccentricityType.ECCENTRICITY_TYPE_NONE,
    0.0,    # eccentricity_ez
    0.0, 0.0, 0.0,  # restraint_spring_about_x, _about_z, _warping
    rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.SupportInY.SUPPORT_IN_Y_SUPPORT_STATUS_YES,
    rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.RestraintAboutX.RESTRAINT_ABOUT_X_SUPPORT_STATUS_YES,
    rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.RestraintAboutZ.RESTRAINT_ABOUT_Z_SUPPORT_STATUS_YES,
    rfem.types_for_steel_design.SteelEffectiveLengths.NodalSupportsRow.RestraintWarping.RESTRAINT_WARPING_SUPPORT_STATUS_YES,
    [1, 2]  # nodes -> replace with your node IDs
]]

Some of these arguments (like description) are probably option, but I always like to fill them all out in the order they appear in the documentation (and give comments for easy matching) when I first try a new piece of code :slight_smile:

Let me know how you go, I probably won’t be able to help to much because I don’t actually have the add in to test…

Samuel

Hi amazigh,

we have been able to replicate the issue - the problem is probably that steel design effective lengths generally do not return the complete settings for nodal_supports.

For that already bug ID 240654 is registered.

Reagrds

Hi Thomas,
Did you solved the problem ?
Kind regards,

Not yet, still in the backlog but we will look on that with higher priority now.
Let you know, when it’s fixed.
Regards

2 Likes