Edge indexing for reference between SAF objects FIX

[scia-nv]

Dear SAF implementers,

In SAF we are indexing (numbering) the edges of StrucuturalSurfaceMember, StructuralSurfaceMemberOpening, StructuralSurfaceMemberRegion and StructuralSurfaceActionDistri. The order of edges is defined as follows, the first edge of the object (the lowest index) = first curve that is defining the boundary, the second edge of the objects (index for an edge before + 1) = second curve etc.. For distinguishing between individual edges of an object and application of load objects (or constrains defining objects) to specific edges, indexing of edges were introduced. Unfortunately, the indexing of edges is not consistent in referencing between all objects in the released versions of SAF documentation.

I would like to know how you handle the references between objects that are related to edges? On edges of objects above following objects are referencing: StructuralEdgeConnection, RelConnectsSurfaceEdge, RelConnectsRigidMember, StructuralCurveAction, StructuralCurveMoment.

Following definition for edges indexing (reference) can be found in SAF:

• StructuralEdgeConnection: Indexing of edges starting with ‘1’ (example value = 1)

• RelConnectsSurfaceEdge: indexing of edges starting with ‘0’ (example value = 1)

• RelConnectsRigidMember: Not specified (example value = 3;1)

• StructuralCurveAction: Not specified (example value = 1)

• StructuralCurveMoment: Not specified (example value = 1)

Did you implement both indexing types? Starting with ‘0’ for RelConnectsSurfaceEdge and from ‘1’ for other objects? Or are you consistent and you are starting with index 1 for 1st edge for all objects?

Proposals for fix:

• For RelConnectsSurfaceEdge: There are three options, please let us which suits you and also feel free to come with your own proposal.

a) Change indexing starts with ‘1’ in already released SAF versions. In case you have not implemented indexing starting with index = 0, we can adjust and unify the already published doc (1.x.x and 2.0.0.)
b) Change indexing start with ‘1’ for a future major release of SAF. In case you have already implemented indexing starting with index = 0, we can unify the indexing with the next release with major changes in SAF.
c) Keep it as it is. In case you do not see the need for any action also there is an option to keep it as it is even for future releases.

• For RelConnectsRigidMember, StructuralCurveAction, StructuralCurveMoment adjust the description to be clearly stated that indexing of edges starts with number 1. This would be only a SAF specification improvement in case you are starting the indexing with ‘1’ as the most under stable value for SAF users.

Consequences:
Improved and clear description.

Please let us know by the 7th of September what is your opinion on edges indexing is and feel free to discuss it there. Important is how you handle the indexing for RelConnectsSurfaceEdge and how you implemented indexing for RelConnectsRigidMember, StructuralCurveAction, StructuralCurveMoment based on that we can agree on change that will improve the SAF.

Best regards,
Štěpán Šonka

[scia-nv]

Hi,

how stakeholders are handling the edges referencing can be seen in the table below. Clear is, that object RelConnectsSurfaceEdge is the possible cause of unwanted changes during the model exchange. The constrain applied to the specific edge can move to +1/-1 edge on the referenced object.

Stakeholders	StructuralEdgeConnection	RelConnectsSurfaceEdge	RelConnectsRigidMember	StructuralCurveAction	StructuralCurveMoment:
Graphisoft	1	0	1	1	1
AxisVM	1	0	1	1	1
Strusoft FEM-design	1	0	1	x	x
Radimpex	1	1	1	1	1
Scia Engineer	1	1	1	1	1

[scia-nv]

Scia Engineer is going to be aligned with specs for version Scia Engineer 21.1 and all released SAF versions. It means for RelConnectsSurfaceEdge the indexing starts from "0".