Settings...
Settings...
Some miscellaneous settings that control belt fitting are available here. Preferences may also be saved automatically to you $home oa_pref file using |
When the *BELT_PATH keyword defining the points that make up the basic belt path are read they contain both an explicit coordinate <x1, y1, z1> and an optional node <nid>:
*BELT_PATH
<npts>
<bits> <x1> <y1> <z1> (<nid>)
(Optional row 1 of further data depending on <bits>)
(Optional row 2 of further data depending on <bits>)
Prior to V14 PRIMER applied a hard-wired tolerance of 5mm when comparing the coordinates of node <nid> with the explicit coordinates <x1, y1, z1>, and the action taken was as follows:
| Pre-V14 behaviour when dealing with node / point coordinate differences. | |
| Point within 5mm of node | Move point silently to nodal coordinate |
| Point more than 5mm from node | Remove reference to node, use point coordinate |
From PRIMER V14 onwards this behaviour is now much more controllable as follows:
|
The mapping tolerance can be controlled The default of 5mm can be changed to any reasonable value. (Note that this value is the same as that used in New Dummy when looking for nodes on the new dummy onto which to map the existing belt path.) This can also be set by the preference shown. |
Preference:
primer*belt_path_match_tol:
|
||||||
|
The way point / node coordinate mismatches are handled can be controlled Three behaviours are available if the point and node coordinates do not match within the given tolerance:
The behaviour if the node and point are within tolerance is unchanged, ie move point to node coordinate. |
Preference:
primer*belt_path_match_method:
|
Seatbelt and dummy keyout formatControls the version of PRIMER for which the post *END cards written for ocupant related data are formatted. |
|
||||||
|
This setting affects the following PRIMER -specific keywords:
Warning: Choosing a format for an earlier version of PRIMER will attempt to format the relevant cards for that version, but it will inevitably mean that some data are lost and as a consequence that behaviour may not be the same. In some cases, for example "new" versus "old" style belt meshing, it may not be possible to express the data from the current PRIMER version in the older format. As a consequence it is recommended that this option is only used as a last resort. This output format may also be set by the preference: primer*mdumm_keyout_format: current | V14 | V13 | V12 | V11 |
|||||||