Adams Car Package > Adams Driveline > Configuring Your Product > Managing Tables Through Configuration Files

Managing Tables Through Configuration Files

As explained in Database Structure, a template-based product's database is comprised of a number of directories or tables in which you store files. In addition to the standard set of table directories, you can create your own tables.

Generally, you only add table directories to the databases defined in your private configuration file. As the site manager, you may decide to add tables for general use in the site configuration file.

Learn more about creating tables and the standard table entries:

■Creating Tables

■Standard TABLE Directory Entries

Creating Tables

At start up, your template-based product determines when to create new table directories as follows:

1. Your template-based product verifies that all database directories defined in the private configuration file contain table directories for the corresponding table directories also defined in the private configuration file.

2. If a table directory does not exist inside the database, your template-based product creates one.

3. If a site configuration file exists, your template-based product ensures that for any table directory specified in the site configuration file, a corresponding table directory exists for all database directories defined in both the site and private configuration files.

4. Your template-based product ensures that for all table directories specified in the shared configuration file, a corresponding table directory exists for all database directories defined in the private, site (if it exists), and shared configuration files.

The TABLE keyword entry for creating tables has the format:

TABLE TABLE_CLASS

TABLE_NAME

TABLE_EXTENSION

where:

■TABLE_CLASS - A string identifying the table.

■TABLE_NAME - The name that you want used to access the table.

■TABLE_EXTENSION - The three-character extension of files stored in the table. Your template-based product only recognizes files in the table that have the extension that you specify.

For example, the following creates a table that stores aerodynamic forces:

TABLE aeroforces /staff/my_name/my_db.cdb/aeroforces.tbl aer

Adding the table definition shown above in the configuration file causes your template-based product to recognize and correctly access files stored in that particular database table.

Standard TABLE Directory Entries

The TABLE directory entries in the shared configuration file are briefly explained in the following table:

The entry:	Defines tables for:
TABLE assembly assemblies.tbl asy	Assembly files that list the subsystems that make up Adams Car assemblies.
TABLE template templates.tbl tpl	Template files that define the topology and major role (for example, suspension or steering) of Adams Car models.
TABLE subsystem subsystems.tbl sub	Subsystem files that contain information unique to the specific instance of the template the subsystem file references.
TABLE aero_force aero_forces.tbl aer	Aero_force files that contain wind-force mappings.
TABLE bushing bushings.tbl bus	Bushing files that define a six degree-of-freedom force relationships between user-specified locations on two parts.
TABLE linear bushing bushings.tbl lbf	Bushing files that define a six degree-of-freedom force relationship between user-specified locations on two parts, using constant coefficients for each of the six degrees of freedom.
TABLE bumpstop bumpstop.tbl bum	Bumpstop files that define a force-displacement relationship between user-specified locations on two parts.
TABLE damper dampers.tbl dam	Damper files that define a force-velocity relationship between user-specified locations on two parts.
TABLE linear damper dampers.tbl ldf	Damper files that define the linear damping force relationship between user-specified locations on two parts, using a constant damping coefficient.
TABLE flex_body flexbodys.tbl mnf	Files that define flexible body representations usually through modal neutral files.
TABLE powertrain powertrains.tbl pwr	Powertrain files that define the engine speed-torque relationship at different throttle positions.
TABLE differential differentials.tbl dif	Differential files that define the slip speed-torque characteristics of a differential.
TABLE reboundstop reboundstops.tbl reb	Rebound stop files that define a force-displacement relationship between user-specified locations on two parts.
TABLE shell_graphic shell_graphics.tbl shl	Shell graphic files.
TABLE spring springs.tbl spr	Spring files that define a force-displacement relationship between user-specified locations on two parts.
TABLE linear spring springs.tbl lsf	Spring files that define the linear elastic force relationship between user-specified locations on two parts, using a constant stiffness coefficient.
TABLE steering_assist steering_assists.tbl ste	Steering_assist files that contain torsion bar data relating torsion bar deflection to both torque and pressure.
TABLE tire tires.tbl tir	Tire files that define data needed to characterize tire behavior (a tire model).
TABLE road roads.tbl rdf	Road files that define roads that the contact algorithms in the Adams Tire module use.
TABLE driver_controls driver_controls.tbl dcf	Driver control files that contain maneuver descriptions for the Driving Machine. Also includes XML event files. For additional information, see Note in Using the Driving Machine.
TABLE driver_data driver_data.tbl dcd	Driver data files that contain data for the Driving Machine.
TABLE driver_loadcase driver_loadcases.tbl dri	Driver loadcase files that contain driving signals used in a data-driven, full-vehicle analysis. The driver loadcase specifies inputs to the vehicle.
TABLE loadcase loadcases.tbl lcf	Loadcase files that contain data used in suspension analyses.
TABLE suspension_curve suspension_curves.tbl scf	Suspension curves used in the Conceptual Suspension Modeling module.
TABLE wheelenv wheel_envelopes.tbl wen	Wheel-envelope files that contain location vector information that represents the wheel-center location and orientation in space. They are used for wheel-envelope analyses.
TABLE plot_config plot_configs.tbl plt	Plot configuration files that define a suite of plots to be automatically generated after completion of an analysis.
TABLE driver_road driver_roads.tbl drd	Adams Driver road definitions.
TABLE driver_knowledge driver_knowledge.tbl kno	Adams Driver knowledge file. (Obsolete).
TABLE driver_input driver_inputs.tbl din	Adams Driver input files used in an Adams Driver full-vehicle analysis. (Obsolete).

They are the standard set of tables that are distributed with your template-based product's database. You cannot reconfigure TABLE entries. Changing these values disables your template-based product's ability to assign properties to a class of entities.

Managing Property Files Through Configuration Files

A PROPFILE environment variable in the configuration file assigns a default property file used when creating the following entity types: bumpstop, bushing, damper, reboundstop, spring, and tire.

A PROPFILE environment variable in a configuration file has the following format:

PROPFILE PROPFILE_CLASS PROPFILE_NAME

where:

■PROPFILE_CLASS is a string that identifies the property file.

■PROPFILE_NAME is the name of the property file.

For example:

PROPFILE bushing mdids://shared/bushings.tbl/mdi_0001.bus

You can define the property files in the private, site, or shared configuration files.

Managing Test Rigs Through Configuration Files

A TESTRIG environment variable in the configuration file assigns a default test rig to a particular class of assemblies.

A TESTRIG environment variable in a configuration file has the following format:

TESTRIG TESTRIG_CLASS TESTRIG_NAME

where:

■ASSEMBLY_CLASS is a string that identifies the type of assemblies which correspond to the test rig.

■TESTRIG_NAME is the name of the test rig model.

For example:

TESTRIG four_post .__MY_FOURPOST

You can define the default test rigs in the private, site, or shared configuration files.