Transverse planes
and Horizontal planes
The user must be able to define a table containing a number of transverse reference planes. In the Domain Expert tutorial, the purpose of entity Transverse planes
is described in detail.
...
Parameter name | Dimension | Determined by | Reference | In Class |
| [#] | VR: User only | Number of instances | General |
| [Str] | VR: User only | Name of object | General |
| [-] | USR: User or system/equation | Case index | General |
| [-] | VR: User only | Frame number | General |
| [mm] | VR: User only | Frame spacing | Dimensions |
| [m] | VR: User only | X position, in longitudinal direction | Dimensions |
Z | [m] | VR: User only | Z position, in vertical direction | Dimensions |
Nr
, Names$
and CaseID
in both Horizontal planes
and Transverse planes
.Frame_Nr
, Frame_spacing
and X
in Transverse planes
.Z
in Horizontal planes
....
Volume
in the Knowledge Browser, select the Parameter tab of the Properties window and enter @MODIFY
in the Data field.
...
Loa
in the Knowledge Browser, select the Parameter tab of the Properties window and enter @ORDER:1
in the Data field....
X
in entity Transverse planes
in the Workbase:X = Frame_nr * (Frame_spacing/1000)
For each case, representing a transverse reference plane, this relation will be calculated. Parameter Frame_spacing
does not have a @MULTVAL attribute, thus the value provided for Frame_spacing
will be constant for each case.
...
CaseID
in entity Transverse planes
in the Workbase:CaseID = ORCA(1)
The function ORCA(1) returns the current case number (during execution). Later on, this calculated value is used to refer to one of the transverse reference planes.
...