structuralanalysisformat / structuralanalysisformat-doc Goto Github PK

Loads StructuralCurveAction and StructuralCurveMoment can be assigned to an Internal edge and Edge of member the load is applied to, by setting the value of Force action = On edge

Then it is decided weather the 'Edge' index has any value
-> if yes -> the load is assumed to be on edge of the member
-> if no -> the load is assumed to be on internal edge and looks at the value Internal Edge for its position

Images above are from page StructuralCurveAction, note that in StructuralCurveMoment it is not clearly specified as seen below:

PROPOSAL:

• add new possible value for enum Force action called 'On internal edge' to distigiush between Internal edge and other edges.

Update name of materials in the sheet StructuralCrossSections so it links properly to materials in StructuralMaterialSheet. Check the example file and update it.

As well as in CurveAction and CurveMoment. It is not possible to combine local LCS with projection = projection
(the attribute is being read only if LCS = global)

StructuralCrossSection:

• CS16: parameters values do not make sense (geometry)
• CS17: I section is missing two parameters
• CS18: Double rectangle is missing one parameter

StructuralCurveMemeber

• B45: Number of nodes does not fit to the defined geometry (polyline is meant to be closed) -> add N115

Extend the functionality of line support with the option to be applied also on internal edges.

Proposed:
Add column internal edge - reference to StructuralCurveEdge
Extend force action enum - On edge

Example:

It will allow to export similar analysis setups:

SAF file:
SAF_internal_edge_proposal.xlsx

Originally posted by @scia-nv in #22

The sentece

StructuralCurveEdge can be placed on StructuralSurfaceMemberRegion, but the relation is always to 2D member (StructuralSurfaceMember) where StructuralSurfaceMemberRegion is placed.

implies that internal edge can be placed on StructuralSurfaceMemberRegion. This is not true, it can go through subregion unaffected by it.

• Improve clarity by moving this sentence to Notes and rewriting it.
• Add an explanatory picture

two links in StructuralCrossSection:

are switched.

Hi everyone,
according to collected feedback with no disagreement, we will do the proposed changes in SAF 2.0.0 and SAF 1.0.9

• Issue 1 : Multi-type reference columns have been introduced.

• - StructuralCurveAction : Add 2 new columns, "2D member region" and "2D member opening" which will act as reference columns to StructuralSurfaceMemberRegion and StructuralSurfaceMemberOpening respectively (SAF 2.0.0)

• - StructuralCurveMoment : Add 2 new columns, "2D member region" and "2D member opening" which will act as reference columns to StructuralSurfaceMemberRegion and StructuralSurfaceMemberOpening respectively (SAF 2.0.0)

• - StructuralEdgeConnection : Add 2 new columns, "2D member region" and "2D member opening" which will act as reference columns to StructuralSurfaceMemberRegion and StructuralSurfaceMemberOpening respectively (SAF 2.0.0)

• Issue 2: StructuralSurfaceActionDistribution name too long use as worksheet name

• Set the worksheet name to "StructuralSurfaceActionDistri" in SAF 1.0.9

• Issue 3: Fundamental issue with reference to StructuralSurfaceActionDistribution on StructuralSurfaceAction

• Add new "2D member distribution" column which acts as the reference to StructuralSurfaceActionDistribution in SAF 1.0.9

• Add a new enumeration, similar to the "Force action" enumeration which will specify which kind of type the StructuralSurfaceAction references

Originally posted by @sonkaste17 in #7 (comment)

In Introduction, there is a space where it is not supposed to be:

In the StructuralLoadCombination there is one space which is not supposed to be there:

For StrucutralPointSupport LCS does not make sense.
For Supports applicable on edges, the edge LCS is taken into account but it is not described.
For Supports applicable on 1D members - LCS is related to the LCS of the member. Is it mentioned in spec?

Thank you for the investigation, similar needs to be done for loads.

Update the new object result on 2D edge with a warning - under the construction

New company finished the implementation - move the company to the implementation from implementation in progress.

The description is missing important answers to questions like

• What does specify where the CSS for certain span will be positioned? - Hard to understand now

• How is the first css aligned?

• How are other css aligned after the first one?

Please update material properties on sheet StructuralMaterial to reasonable values for specific materials.

Radimpex has implemented older versions of saf, also provided new logo.

Fix the values in HOUSE example presented on saf.guide/getting-started/saf-examples to be aligned with the specification.

Issues:

• Sheet Model, "System of units" enum = "Metric units" , should be "Metric"
• Sheet StructuralCurveMember "LCS" enum = "Standard", should be one of allowed enums from https://www.saf.guide/structural-analysis-elements/structuralcurvemember
• Add StructuralCurveActionThermal object
• Add StructuralSurfaceActionDistri object

Adjustments:

• Sheet StructuralLoadCase, LC 2 row "Action type" = "Accidental", changed to "Permanent"
• Sheet StructuralCurveMoment, "Value 1 [kNm/m]" = "0", changed to "1" for all rows
• Sheet StructuralCurveMoment, "Load case" = "LC1", changed to "LC2"

Content changes that are released with new releases - those are described in release notes.

Other smaller changes: typo fixes, improving clarity of description.... - these were until now described in release notes as well.

We would like release notes to be precise and short, thus removing the 'other changes notes' from them.

-> create a new page. Where all the other changes and improvements in documentation will be stored. These notes are not relevant for somebody who wants implement newer or older documentation. But we still want to keep track of all the changes in the documentation.

For StructuralSurfaceActionThermal and StructuralCurveActionThermal description is unclear concerning the linear variation. Make sure clear for everybody that temperatures are always differences - delta T, not the actual temperature of the surface.

if TempT = 5°C and TempB = 10°C - it means one of the sides got 5 degrees hotter and the other 10 degrees hotter, than the original temperature of the surfaces.

Row in description copied from another object.

Since the move from gitbook, not all the files used then and not now are not yet cleared. Delete the image forlder that is no longer in use and might be confusing for others.

Dear SAF-Team,
With the current Documentation on www.saf.guide, in encounter the issue that the property tables are not displayed in their full width. Changing the size of the browser does not change the width of the property table. See the picture attached. I encounter that on Google Chrome as well as on MS Edge.

Dlubal is supporting version 1.0.5 on import and export. Below is a detailed list

• StructuralMaterial Yes
• StructuralCrossSection Yes
• CompositeShapeDef No
• StructuralPointConnection Yes
• StructuralCurveEdge Yes
• StructuralCurveMember Yes
• StructuralCurveMemberVarying Yes
• StructuralCurveMemberRib Yes
• StructuralSurfaceMember Yes
• StructuralSurfaceMemberOpening Yes
• StructuralSurfaceMemberRegion No
• StructuralStorey Yes
• StructuralProxyElemen No
• StructuralPointSupport Yes
• StructuralSurfaceConnection Yes
• StructuralCurveConnection Yes
• StructuralEdgeConnection Yes
• RelConnectsStructuralMember Yes
• RelConnectsSurfaceEdge Yes
• RelConnectsRigidCross Yes
• RelConnectsRigidLink Yes
• RelConnectsRigidMember Yes
• StructuralLoadGroup Yes
• StructuralLoadCase Yes
• StructuralLoadCombination Yes
• StructuralPointAction Yes
• StructuralPointMoment Yes
• StructuralCurveAction Yes
• StructuralCurveMoment Yes
• StructuralSurfaceAction Yes
• StructuralSurfaceActionThermal No
• StructuralCurveActionThermal No
• StructuralPointActionFree No
• StructuralCurveActionFree No
• StructuralSurfaceActionFree No
• StructuralSurfaceActionDistribution No

update the logo and ccurrently supported object by FEM-Design from StruSoft to released documentation as well as the latest under construction.

Scia is supporting both thermal loads now.

When an image presents an information (not just visuals) it is sometimes too big to get the information from it easily and quickly. It would be better for those images to be smaller.

The url for version 2.0.0 was changed, but the link was updated only in the latest documentation. It is necessary to update it in the relased verison 2.1.0 as well

Since the change to read the docs, we now have two ways of navigating between verisons. One is the SAF versions page and one is integreated int the read the docs website. The one integrated is probably hidden from the user. - explain it more how to get to the latest under development page and the diference between two diferent ways of choosing the versions.

discussed in discussion #25

• add new object to latest documentation.

Example value and description both have missing * symbol.

It is in the code, but isn't escaped, so it is translated to italics.

• escape all the * so they are visible in the table

In SAF we have "supports" objects (StructuralPointSupport ... ) with predefined constraints. These constraints have multiple possible values. Now, we are not explaining enough difference between tension-only and compression-only (flexible tension only / flexible compression only). This behaviour is related to position of support that is not described in the documentation. Currently, the compression acts always in opposite direction to the positive GCS axis - Please add that information to all relevant support objects. See the picture below.

ConSteel has implemented import of SAF models.

• Update who supports saf with ConSteel implementation

New company has impleneted SAF and provided supported objects - update their info in the latest and released documentation

Hello SAF community!

So far in SAF, we did not provide the possibility for defining the non linear combination. The proposal is to create a new value for attribute "Type" = "Non linear" with relevant "Category" = "ULS (Ultimate Limit State)", "SLS (Serviceability Limit State)" and "Not defined" in the object StructuralLoadCombination. Then provide a list of load cases in the specific combination. This structure can cooperate together with result 1D (ResultInternalForce1D) where results of the non linear analysis can be written down for non linear combinations.

Review - Proposal for object StructuralLoadCombination

Example:
StructuralLoadCombination

ResultInternalForce1D

This approach provides the ability to define non linear combinations in SAF and possibly write results in the object ResultInternalForce1D. What is not covered in the definition are imperfections for the specific combination (the setup for non linear calculation). This can be written down to SAF to the new columns for every non-linear combination. Do you want to have in SAF also the definition of imperfection as input for your analysis software?

Do you think we are missing something?

Thank you,
Štěpán

Originally posted by @sonkaste17 in #51

In the introduction to the object, there is a sentence: By default..... SAF is a format for everybody and every software handles these things differently.

• delete this sentence as there is no default option

Internal nodes serve to connect members to anywhere onto another member, not only at the ends. This is not properly described in the documentation

• add a description with example case in notes
• add a link to notes from description of the internal nodes

The description of new combination type 'nonlinear' is not described properly, clarify the description.
Add under construction tag.

The aforementioned enums are missing some values:

There is a contradiction in pages StructuralCurveAction and StructuralCurveMoment. Required value for 'Location' is 'yes' but it should be 'yes if coordinate system = Global' as it is described in the description below the table.

In ResultInernalForce1D in the note, it says:

The amount of data can be limited due the limitation of xlsx format.

Therefore the results can be written to SAF in a form of multiple tables. In the similiar logic as the StructuralProxyElement.

but in StructuralProxyElement there is no explanation how that works. Explain it more.

Create a link to discussion on the welcome page of SAF so people know where to go to discuss SAF

We finished the transition to read the docs. Now, after we created stable and latest versions, we will work only on latest.

-> update release notes - version in progress

• Please add on sheet StructuralLoadGroup, row dedicated to LG1 value for column "Relation" - field is required.

Value = "Standard"

Based on the discussed proposal #112
Create new object for latest documentation of SAF.

SAF has 1D results already and 2D results on edge coming up, add new object group in Who supports SAF called Results.

Discussed in #77

Table headers are longer than necessary, sometimes defining the width of the whole column.

Change the names to:

Column header | Data type | Example / enum definition | Required value | Description
(Alt. Row Header)

GitBook in recent days deployed an update of the interface of provided pages. It caused tables to be a bit messy now.

Action point:

• Do the styling changes in tables (Header, columns width)
• Investigate the possibility of the dynamic behaviour of tables on Gitbook

With growing number of implementers, the table "Who supports SAF" is no longer sufficient, it no longer fits to smaller screen. To be able to fit properly everybody:

• make images smaller - for most screens this will help to fit all in one page, so everybody is visible
• add the scroll bar - for smaller screen it will be possible to scroll right to see the full table