All the standard Adams Tire tire and road property files employ the TeimOrbit format. TeimOrbit formatting is a way of organizing data into:
■Blocks denoted by brackets "[", "]"
■Subblocks denoted by parenthesis "(", ")"
■Tables denoted by braces "{", "}"
A subblock is always the child of a block. A table can be a child of either a block or a subblock.
For example, a TeimOrbit file might contain the following blocks and subblocks:
[BLOCK_1]
PARAMETER_1 = 1.0
(SUB-BLOCK_1)
PARAMETER_2 = 2.0
{TABLE_1}
1.0 2.0
2.0 3.0
[BLOCK_2]
PARAMETER_2 = 'TWO'
{TABLE_2}
1.0 2.0
2.0 3.0
(SUB-BLOCK_2)
PARAMETER_1 = 'ONE'
Parameters and tables are located for reading according to the block and/or subblock in which they reside. Therefore, PARAMETER_2 in BLOCK_2 is not confused with PARAMETER_2 in BLOCK_1. This example, which uses realistic names, illustrates where parameter are placed:
[VERTICAL_DATA]
STIFFNESS = 310.0
DAMPING = 14.3
[LATERAL_DATA]
STIFFNESS = 232.0
DAMPING = 11.2
Any strings beginning with a dollar sign "$" or an exclamation sign "!" are ignored and, therefore, are used as comments. Before you create your own property file, we recommend that you review some existing files to learn how they are structured.
In general tire and road property files start with a [MDI_HEADER]section, for example:
[MDI_HEADER]
FILE_TYPE = 'tir'
FILE_VERSION = 3.0
FILE_FORMAT = 'ASCII'
This information in the MDI_HEADER header is just for information purposes, but has no effect on the reading of the parameters in the Adams Tire code.