Example Mapping File
The mapping file is acceptable in comma separated value (.csv) format. There are seven columns in each line (record). Each section must be separated by a blank line.
The first three lines includes the header information and contain the following, in this order:
■Reference template address
■Subsytem major role
■Subsytem minor role
Template | mdids://acar_concept/templates.tbl/_rigid_chassis_bed_bof.tpl |
Major role | body |
Minor role | any |
The next (non-blank) line contains the titles for the columns. These titles should be constant, in this order (please note that this line is informational only):
■Class
■Acar_name
■Options
■Values
■Apre_name
■Options
■Comments
Class | acar_name | options | values | apre_name | options | comments |
Class: Class is the Adams Car entity type such as ConstructionOptions, HardPointPair, HardPoint (single), PartPair, Part and so on. This is the same as the tag used in the XML subsystem file.
The line containing class name should have blank columns. The line below this line will contains mapping information about that entity type.
Acar_name: This column contains the names of the Adams Car entity without prefix. Example 'ge[lr]_spindle' should be written as 'spindle'. This column should have values from the line below its class definition line. This is the name in Adams Car that the corresponding object from Adams Car should map to.
Options: [Only used if the class type is of "ConstructionOption".] This is the option name used in Adams Car for the design option. Note that in order to map Adams Car Construction options within Adams Car template, your template based product should contain
Design Options.
Values: [Only used if the class type is of "ConstructionOption".] This is the value used in the parameter variable associated with the relevant design option.
Apre_name: This column contains the name of the Adams Car entity in the subsystem (that is, the entity that needs to be mapped into Adams Car).
Comments: This column contains user entered comments. This column may or may not contain any value. It is not used for mapping, but may be useful for modification of the mapping file itself.
As an example, please see the following Construction Option section for a body subsystem:
ConstructionOption | | | | | | |
| number_of_body_mounts | 1 bushing | 1 | body_mounts | 1 | |
| | 2 bushings | 2 | | 2 | |
| | 3 bushings | 3 | | 3 | |
| | 4 bushings | 4 | | 4 | |
| | 5 bushings | 5 | | 5 | |
| | 6 bushings | 6 | | 6 | |
| | 7 bushings | 7 | | 7 | |
| | 8 bushings | 8 | | 8 | |
| | 9 bushings | 9 | | 9 | |
For all other sub-sections, only two columns are needed (names from Adams Car). For example, the following Hardpoint section for the same body subsystem:
HardPointPair | | | | | | |
| body_mount_1 | | | body_mount_1 | | |
| body_mount_2 | | | body_mount_2 | | |
| body_mount_3 | | | body_mount_3 | | |
| body_mount_4 | | | body_mount_4 | | |
| body_mount_5 | | | body_mount_5 | | |
| body_mount_6 | | | body_mount_6 | | |
| body_mount_7 | | | body_mount_7 | | |
| body_mount_8 | | | body_mount_8 | | |
| body_mount_9 | | | body_mount_9 | | |
For further examples of the mapping file format, see the examples in the Adams installation:
<install_dir>/acar/map