The Principles
- Last UpdatedNov 14, 2025
- 1 minute read
The process operates by merging the clash data with information read from a pre-prepared template file and then outputting the result of this merger to the required macro file. The template file must contain all necessary commands for the module to which the data is to be transferred, with coded keywords marking the locations into which the clash data is to be loaded. Design then substitutes its clash report data for these keywords.
The keywords to be used in the template file, each of which is identified by $...$ markers, are as follows:
|
$CLA1$ |
First clashing item |
|
$CLA2$ |
Second clashing item |
|
$CLATYPE$ |
Clash type |
|
$CLAPOS$ |
Clash position in World coordinates |
|
$CLATEXT$ |
Clash description as output in a standard report; for example HH TOU BOX 1 of /VESS1 with HEAD TUBE of /BRAN1 |
|
$CLANUM$ |
Clash number |
|
$CLAOWN1$ |
Significant element owning first clashing item |
|
$CLAOWN2$ |
Significant element owning second clashing item |
|
$ |
Used to represent a single $ character in the macro file |
Note: The use of the $ character in this context identifies these keywords as escape codes, as defined in Part I of the Software Customization Reference Guide.