Skip to content

Result tables

Filtering, sorting and extracting numbers — getting the value you need out of a solved model without scrolling.

Results & reports 2 min read

Diagrams show what is happening; tables give the number. Everything on screen is available as a table, filtered to the members, positions and combinations you care about.

What can be tabulated

TableContains
Member forces, , , at the stations along selected members
Member extremesMaximum and minimum per member, with governing combination
DisplacementsNodal translations and rotations
ReactionsPer node, per case and combination
Surface resultsMoments and membrane forces at nodes or element centres
Design check resultsUtilisation, governing combination, clause, intermediate values
Model dataNodes, members, sections, materials, supports, loads

A report needs the inputs as much as the outputs, and the model-data table is the record of what was analysed.

A docked Node results table with columns Node, Ux, Uy, Uz, Rx, Ry, Rz and |u|, a filter box, 69 rows, the load case Roof cladding and services and an Export button
The nodal results table docked under the viewports for the steel hall: 69 rows, one per node, with Ux, Uy, Uz in mm, the three rotations in degrees and |u|, a filter, the load case it reads, and Export.69 rows · Roof cladding and services

Filtering

Tables grow as members × positions × combinations. Reduce in this order:

  1. Selection — tabulate only the members you are designing.
  2. Combinations — one combination, or an envelope over a set, rather than all.
  3. Positions — member ends, mid-span and the extreme, rather than every mesh node.
  4. Quantity — only the columns you will use.

A table filtered to "these six columns, this envelope, these positions" is reviewable. A dump of everything is not; putting one in a report hides a result rather than presenting it.

Positions

Member forces are sampled at eleven stations along each analysis element: its two ends and every tenth of its length between.

PositionUse
Member endsConnection design
Every betweenThe diagram, and the stations the design checks read
Maximum and minimumReported per member with its position and combination, in the extremes table

There is no face-of-support or contraflexure position. Read the face value off the diagram, or give the member a node at the face so a station falls there.

Governing combinations

Every extreme value carries the combination that produced it. The tables include that column by default.

The Extremes table showing members E14, E12, E13, E11 and others with My,max, My,min and N,min values, their position along the member, and the governing combination 6.10 · Snow leading
The Extremes table for the ULS envelope: every member ranked by its worst value, each row carrying the quantity, the value, the position x along the member and the governing permutation — here “6.10 · Snow leading” for the top rows.912 rows · ULS (EN 1990 6.10)

Sorting to find the problem

Sort a design-check table by utilisation, descending — the fastest way through a model:

UtilisationMeaning
Above 1.0Needs attention
0.9 to 1.0Needs a decision about margin
Exactly 0, or absurdly lowUsually a member never loaded or never assigned a section — a modelling error, not a light member

Getting numbers out

On Pro, tables can be exported for a spreadsheet or a hand calculation, and included directly in a report. When you copy values out, copy the combination column with them: the number on its own loses the context that makes it verifiable.

Something wrong or unclear on this page? Tell us, and it gets corrected.