<< Click here to display Table of Contents >> Navigation: Data Table:

Toggle Table

Contents

Almost all input data tables which specify data along the pipeline can be 'toggled', i.e. the column(s) defining where on the pipeline the subsequent data is to be applied can be changed by the user. This allows the user to choose the most convenient way to enter the point's data.

Independently from the toggle chosen the value of the parameter(s) eventually will be assigned to elements (or nodes).

For almost all input data tables applies:

•All subsequent data in the toggle column should have increasing values.

•The data in the first row is applicable for all parts of the pipeline before the indicated position in that row (when present).

•The data in the last row is applicable for all parts of the pipeline after the indicated position in that row (when present).

•Elements between two reference points with different parameter values a linear interpolation is applied.

•In tables with a 'Start' and 'End' toggle, the 'End' toggle value should be after the 'Start' toggle or be left empty.

When toggle values do not increase the table test will report the error 'Column data not increasing'. It is not possible to check the identifier sequence during the table test, in that case function error 'Exx0/90: table name, identifier not in sequence' will be reported.

Exceptions to some of those rules are tables GROUPS, MATL, COATING, SLACK, C-DML, NODALL, SECTION, SECT318, SECTBEL, SUPANG, SWEIGH and the 'Δ' abbreviations tables.

The 'toggle states':

Abbreviation	Name	Description
Identifier	Identifier	Define the point(s) by its identifier label. You can choose between labels defined in the ORIGIN- and POLYDIF-table and those additionally defined in the ADIDENT-table. Also the programmatically added identifiers can be used. See design function's 2 output table IDENTS for all available identifiers. Best practice is to use identifiers to specify data along the pipeline. All other 'toggles' are more affected by changes in the configuration: node numbers and distances may change, whereas the identifiers will mostly keep their correct positions.
AX-L	Along pipeline axis	Define the point(s) by the distance from the pipeline origin along the pipeline axis. The distance is relative to the pipeline origin, AX-L = 0 unless the offset is specified differently in table ORIGIN.
AX-LP	Along projected pipeline axis	Define the point(s) by the distance from the pipeline origin along the projection of the polygon lines on the horizontal X0Y-plane. The distance is relative to the pipeline origin, AX-LP = 0 unless the offset is specified differently in table ORIGIN.
		So the AX-L length coordinate is the accumulation of the white arrows (of equal lengths) on the pipeline (bend) and the AX-LP length coordinate is the accumulation of the blue arrows measured along the projection on the polygon lines.
Node	Node number	Define the point(s) by its node number (≥ first node ≤ last node). In this state, it is not possible to define a point between nodes.
Element	Element number	Define the point(s) by its element number (≥ first element ≤ last element). The actual coordinate is the middle of the element. In this state, it is not possible to define a point somewhere else on that element.
X-P	X-coordinates	Define the point(s) by the absolute x-coordinate. X-P values should be increasing. If the pipeline has several points with the same x-coordinate, the data is applied to all those points!

For tables SISPRC, PIPES, SUPPORT and ADIDENT (tables from design function 2) an extra 'Δ' is added to the abbreviations because these 'distances' are relative to a REFIDENT column. Being relative values they can also be negative, including node and element numbers. A negative value means a distance back towards the origin.

The REFIDENT data in subsequent rows do not have to contain increasing values.

If in a row of these tables:

-	the REFIDENT is undefined, the value in the column with the Δ abbreviation will be interpreted as absolute value relative to the origin.
-	the Δ abbreviation is undefined, it is considered to be zero.
-	both REFIDENT and Δ abbreviation fields are undefined, the resulting AX-L position will be zero.

The same rules apply when toggled to ΔX-P and ΔAX-LP

When toggled to Δ Node/Element also the same rules apply, except when the REFIDENT is undefined, then the Δ Node/Element will be interpreted as the absolute Node/Element number which should always be greater then zero. So, when both fields are undefined, Node/Element number zero will result in an error during calculation of the design function.

When toggled to 'Identifier' the REFIDENT should be left empty, otherwise an error will be reported during calculation of the design function.

Toggle (last modified: Aug 14, 2025)