The following table lists macros and their respective properties that you can use in a GED configuration file. The most frequently-used macros are listed first.
Macro |
Description |
Properties Available |
Notes |
P |
Pipeline |
Name |
|
C |
Component |
BranchLength |
|
C0 |
The connecting component (such as a weld) in a joint |
Same as for Component |
|
C1 |
The first connected component |
||
C2 |
The second connected component |
||
M |
Material |
CharacteristicBore |
See below
|
M0 |
The connecting component material in a joint |
Same as for Material |
|
M1 |
The material assigned to the first connected component in a joint |
||
M2 |
The material assigned to the second connected component in a joint |
||
I |
Information element |
FlyText |
Short description |
PC |
Parent component properties |
Same as for Component |
|
POD |
The root element in a POD file |
Name |
|
PGS |
Pipeline graphic sheets collection |
Count |
Number of sheets |
CKP[name] |
Component keypoint, specified by name. For example, CKP[Run_1] refers to the component keypoint called Run_1. Coordinate keypoint using the following syntax: $CKP[Run_1].Z for the Z-coordinate keypoint. |
Bore |
|
CL[name] |
Component leg, specified by name. |
Length |
Length (mm)
|
CG[name] |
Component graphics, specified by name. |
SheetNumber |
Sheet number for component |
MKP[name] |
Material keypoint, specified by name. |
Bore |
See CKP[name] |
ML[name] |
Material leg, specified by name. |
Length |
See CL[name] |
S |
Spool |
Any spool attribute |
Not every macro can be used at any element. For example, using a component, or C, macro at a PIPELINE element is meaningless because it is not clear which of the many components in the pipeline should be used to evaluate the macro. Conversely, a pipeline, or P, macro can be used at a COMPONENT element because a component only belongs to one pipeline.
Element being evaluated |
Macros available |
PIPELINE/SQL PIPELINE/EXECUTE |
P, POD, PGS |
COMPONENT/EXECUTE |
P, PC, POD, PGS, C, CG, CKP, CL, M, MKP, ML |
COMPONENT/SQL (No FILTER) |
P, PC, POD, PGS, C, CG, CKP, CL, M, MKP, ML,S |
COMPONENT/SQL (With FILTER) |
P, POD, PGS |
COMPONENT/FILTER |
P, PC, POD, PGS, C, CG, CKP, CL, M, MKP, ML |
INFORMATION/EXECUTE |
P, POD, PGS, I |
INFORMATION/SQL (No FILTER) |
P, POD, PGS, I |
INFORMATION/SQL (With FILTER) |
P, POD, PGS |
INFORMATION/FILTER |
P, POD, PGS, I |
MATERIAL/EXECUTE |
P, POD, PGS, M, MKP, ML |
MATERIAL/SQL (No FILTER) |
P, POD, PGS, M, MKP, ML |
MATERIAL/SQL (With FILTER) |
P, POD, PGS |
MATERIAL/FILTER |
P, POD, PGS, M, MKP, ML |
JOINT/EXECUTE |
P, POD, PGS, C0, C1, C2, M0, M1, M2 |
JOINT/SQL |
P, POD, PGS, C0, C1, C2, M0, M1, M2 |
CharacteristicBore and Sizen properties:
CharacteristicBore (string)
SIZE1 (single), SIZE1Units (string)
SIZE2 (single), SIZE2Units (string)
SIZE3 (single), SIZE3Units (string)
These properties allow access to key nominal size information without requiring knowledge of the keypoint structure and enable linking to data tables more straightforward. The examples below show the derived properties for a flange and a tee:
-
Flange
CharacteristicBore = 6in
SIZE1 = 6, SIZE2 = 0, SIZE3 = 0
SIZE1Units=in, SIZE2Units=in, SIZE3Units=in -
Tee
CharacteristicBore = 6x4in
SIZE1 = 6, SIZE2 = 4, SIZE3 = 0
In the case of olets, the component SIZE properties report SIZE1 as the size of the main pipe, and SIZE2 as the size of the branch pipe. In contrast, the material SIZE properties report SIZE1 as the size of the branch pipe, and SIZE2 = 0. If the main paper size is needed, use the component-derived properties.