TensorNodeStart free trial

FEA Tool manual › Chapter 16

Import and export

Chapters
  1. 1 Getting started
  2. 2 The interface
  3. 3 Coordinate systems and conventions
  4. 4 Modelling
  5. 5 Materials
  6. 6 Sections
  7. 7 Supports, releases and modifiers
  8. 8 Loads
  9. 9 Load combinations
  10. 10 Meshing
  11. 11 Static analysis
  12. 12 Dynamic and seismic analysis
  13. 13 Results
  14. 14 Design
  15. 15 Scripting and the AI model builder
  16. 16 Import and export
  17. 17 Verification
  18. 18 Scope and limits
  19. 19 Troubleshooting
  20. 20 Glossary and notation
On this page
  1. 16.1 Opening and saving TensorNode models
  2. 16.2 Formats read
  3. 16.3 Mapping of sections, grades, codes and units
  4. 16.4 Formats written
  5. 16.5 Limits of the readers

The FEA Tool reads models from BIM and analysis programs and writes them back with the design results, so it can sit between the architectural model, another analysis program and the design. This chapter lists the formats, what is read and written in each, how sections, grades and units are mapped, and the limits of each reader.

16.1 Opening and saving TensorNode models

A model saved from the FEA Tool (Ctrl+S, or Model > Save and open) is a JSON file holding the whole model: nodes, members, areas, sections, area sections, materials, supports, springs, releases, offsets, modifiers, load patterns with their loads, joint patterns, combinations, envelopes, grids, groups, the mass source, the seismic and design settings, the user spectra and records, and the display units. It opens with Import, by dropping it on the model view, or from Save and open. Results are not stored; run the analysis after opening.

16.2 Formats read

Import in the header (or the Import / Export tab) reads:

Table 16.1 Formats read by the FEA Tool
FormatFilesWhat is read
IFC 2x3, IFC4, IFC4.3.ifc (ISO 10303-21)units; beams, columns and members with their placement and axis (or the axis of the extruded body); the structural analysis model; sections from the profile definitions; member results from structural result groups
Table text export.s2k, .$2kunits, joints, frame connectivity, section assignments and properties, materials, restraints, load pattern and combination definitions, element forces of frames, and effective lengths in TensorNode's own table
Building model text.e2k, .$etunits, stories, point coordinates, line connectivity of columns, beams and braces at each story, frame sections and auto-select lists; the model only, without forces
Older table text.s2k (version 7 style)system units, joints, restraints, materials, frame sections and frames
SPACE GASS text file.txtunits, nodes, members, restraints, sections, materials, titles, combinations, member forces; TensorNode data in comment lines
CSV or TSV.csv, .tsvone row per member (or per member and combination): end coordinates required; section, material, type, level, case, station, forces, effective lengths and design data optional; units from a header line or columns
TensorNode exchange JSON.json (datum-bim/1)units, levels, sections, materials, load cases, members with their ends, ids and results
Script.py, .jsopened in the script console in its language

Every reader returns a model or a plain message and never stops the app. Members that cannot be used (a missing node, a coordinate that is not a number, zero length or more than 100 km long) are left out with a note. Duplicate ids keep the last definition.

Vertical axis. Formats whose vertical axis is Y (SPACE GASS by default) are turned so that Z is up, keeping the handedness: (x,y,z)TN=(X,−Z,Y)(x, y, z)_{\text{TN}} = (X, -Z, Y).

Imported results become the design actions. When a file carries member forces (table text with element forces, SPACE GASS member forces, CSV forces, IFC results), the members can be designed straight away with those forces, without a new analysis: the design actions are the envelope of the imported combinations (or of the cases when there are no combinations). The sign convention of the table text is used for every format: PP positive in tension and axis 3 the major axis. For IFC, ForceX is taken as tension positive and MomentZ about the profile's local z axis as the major-axis moment.

The Design tab after a CSV file of six members was imported, listing each member with its section, module and utilisation
Figure 16.1 After an import: the members of the file are listed in the Design tab with their section, design module and utilisation.

16.3 Mapping of sections, grades, codes and units

Sections. Every section name is reduced to a signature of its family and dimensions, so 310UB40.4, 310 UB 40.4, SHS100x100x6.0 and 100 x 100 x 6 SHS are recognised, and W310x39 (CSA) is matched to W12x26 (AISC). A name of the same family whose last number is within 3 % maps to the nearest catalogue designation with a note (530 UB 92 to 530UB92.4). A section that cannot be mapped is kept with its properties for the analysis and marked Not mapped for the design.

Design code. Inferred from the libraries the sections belong to (a CSA metric W name counts for Canada, an AISC name for the US), or chosen in the header.

Steel grade. From the material name (A992, A36, A500 Gr C, 350W, 300W, S235 to S460), or from FyF_y (the highest grade not above 1.02Fy1.02F_y). AS sections carry their own yield stress.

Units. Lengths in m, mm, cm, in or ft and forces in kN, N, kip, lb, kgf or tonf, in any mix, are converted on import. The model is then held in kN and m.

Effective lengths. Lx=Ly=LbL_x = L_y = L_b = member length by default, editable for each member, and read from CSV, JSON, TensorNode's own table in the table text, or the IFC property set.

16.4 Formats written

Export writes the model and its design results:

Table 16.2 Formats written by the FEA Tool
ExportContent
IFC with Pset_DATUM_Designthe original IFC file unchanged, with one property set on each element (same GlobalIds): utilisation, status, governing check, design code, module, section, the design actions (kN, kNm) and LxL_x, LyL_y, LbL_b in m
IFC4 modelproject, units, site, building, storeys; beams, columns and members with an axis and a swept profile (I, channel, hollow rectangle, hollow circle, angle or rectangle) with the library dimensions; materials; the property set above; the member results as one result group per load case or combination
Table text, model and results (.s2k)units, joints, restraints, frames, section assignments (with sections changed in TensorNode), section properties, materials, load patterns, combinations, element forces, effective lengths and a design results table
Table text, section changes (.s2k)the section assignments set in TensorNode and the design results, to be imported into an existing model ("add to existing model"); a new section must already exist in the target model
SPACE GASS text filenodes (Y vertical), members, restraints, updated sections and materials, combinations, titles; TensorNode data (original ids, case names, internal forces, lengths, design results) in comment lines that SPACE GASS skips
CSVone row per member and combination: geometry, section, lengths, actions, code, module, utilisation, status and governing check; readable by the CSV reader
JSON (datum-bim/1)the exchange format with a design results block (id, GUID, utilisation, status, check, module, section), for a link on the BIM side to fill shared parameters

The IFC export with property sets keeps the original file intact up to the end of its data section, so the round trip back to the BIM program changes no geometry. In the IFC4 model export, imported GlobalIds are reused and new ones are generated deterministically, so exporting twice gives the same ids.

16.5 Limits of the readers

  • Curved frames, cables, shells and solids in the text formats are not read; node generation lines in SPACE GASS files, spherical coordinates and cylindrical coordinates in a local system are not read either.
  • IFC results are read from member (curve) reactions in result groups only; point reactions and surface results are not. The IFC schema fixes no sign convention for member internal forces, so check the convention of the exporting program.
  • IFC members given only by faces are reduced to the principal axis of their corners: the line runs through the centre of the body, not along the modelled reference line. Such members rarely share end points, so check the supports, connections and effective lengths after import.
  • Building model text files (.e2k) carry the model only. Member forces must come from a table text export, a .s2k with results, or CSV.
  • Simultaneous actions are not paired: each extreme of the envelope is used, which is conservative.
  • Concrete and timber members in most files carry no reinforcement or grade strengths: the module defaults are used and the member is marked Needs input until you give them (Section 14.5).

After any import, run the model check, look at the model in 3D and in elevation, and compare the total load or the reactions with the source program before designing.