Configuring Adams > Applying Advanced Settings > Template-Based Environment Variables

Template-Based Environment Variables

The following environment variables are used in various Adams template-based products.
 
Variable name:
Variable value:
What it does:
MDI_AENG_HHT_ERROR
Any positive number
Sets the HHT integrator as the default integrator, with a default error tolerance of the value specified.
MDI_CDB_EXPAND_PATH
yes/no
Writes the expanded file names to the adm deck.
MDI_<product name>_PRIVATE
 
 
MDI_ACAR_PRIVATE_CFG+
MDI_ADRV_PRIVATE_CFG+
MDI_AENG_PRIVATE_CFG*
MDI_RAIL_PRIVATE_CFG*
MDI_AIR_PRIVATE_CFG*
 
Defines the path to your private configuration file.
MDI_ACAR_PRIVATE_DIR+
MDI_ADRV_PRIVATE_DIR+
MDI_AENG_PRIVATE_DIR*
MDI_RAIL_PRIVATE_DIR*
MDI_AIR_PRIVATE_DIR*
 
Defines the path to the private repository.
MDI_ACAR_SITE+
MDI_ADRIVELINE_SITE+
MDI_AENGINE_SITE*
MDI_ARAIL_SITE*
MDI_AIRCRAFT_SITE*
 
Defines the path to the site repository.
MDI_UPDATE_CFG
yes/no
This environment variable tells Adams Car whether the private configuration file should be automatically updated during the session to reflect CDB Database changes. This auto-update of the private configuration file is also referred to as the 'live' configuration file. Adams Car defaults to the 'live' private configuration file, and the MDI_UPDATE_CFG environment variable allows a user to turn off the auto-update feature, essentially returning to the v2003 release behavior. To disable the auto-update of the private configuration file, simply add the following line into your private configuration file:
ENVIRONMENT MDI_UPDATE_CFG no
This will turn off the “Update Private Config File” toggle on the Add Database to Session and Remove Database From Session dialogs. However, the user may still activate these toggles if they wish.
MSC_ADAMS_VDM_DEBUG
0,1,2,3
Causes additional diagnostic information during full vehicle simulations.
-------------------------------------------------
0- No additional output.

1 and 2 - Additional output in .sdf and .sdl files.

3 - Same as 1, plus _runTime.log file with extensive driving machine diagnostics. This setting produces a large output file and slows execution speed.
MSC_ADAMS_VDM_SI2FLAG
0,1,2,3
Allows the user to override default adaptations of the steering actuator when used with certain integrators.
0 - No adaptations (default for I3 integrator.)

1 - Switch motions to forces in closed loop situations (default for HHT integrator.)

2 - Apply functions directly to motions in open loop situations.

3 - Both adaptations (default for SI2 and SI1 integrators.
MSC_SD_DEFAULT_XML
 
You can use this environment variable to set the path to a custom SmartDriver Setting Template file (.smartdriver.xml). The SmartDriver Setting Template file (basically an .xml event file without events) is used to set default values for Event files. Those defaults are used when:
converting .dcf format Event files to .xml format Event files.
creating new Event files using the Event Builder.
If MSC_SD_DEFAULT_XML is not set, the SmartDriver Setting Template file path search order is as follows:
1. Home directory ($HOME\.smartdriver.xml)
2. <Adams Installation>\<platform> ($topdir\$MDI_CPU\.smartdriver.xml)
MSC_ACAR_LIST_COMMENTS
yes/no
If this environment variable is set to "NO", the assembly and subsystem files will not include comment lines in the parameter variable and hardpoint tables.
MSC_ACAR_ERROR_ON_
MISSING_NODE_ID
yes/no
If this environment variable is set to "yes", reading a subsystem will be aborted if a flexible body node ID specified in the subsystem cannot be found. If this variable is not set, or set to "no", and a flexible body node ID specified in the subsystem cannot be found, a warning will be issued and the closest node will be used instead.
MSC_USE_FORTRAN_STYLE_RELOAD_MESSAGE_FILE
0/1
Use the Fortran style msg file behavior upon reload
For more information, refer to About Private Configuration Files and Setting Up the Environment Through Configuration Files.
*MSC Partner products.
+Superseded by the Adams registry
 
Note:  
The environment variables marked with a '+' must be set in the Adams registry. Environment variables set in the OS (for example, in the Windows registry), or the shell environment prior to starting Adams, will be overwritten by those registry values. Once in Adams, environment variables can be set or changed using the putenv() design time function.

List of Variable Values for MDI_ACAR_ANL_LOG*

 
assembly
flexible_bodies
general_variables
nsprings
subsystem_all
aforces
friction
hardpoints
parts
switch_parts
bumpstops
gears
interface_parts
parameters
testrig
bushings
general_parameters
model
property_files
user_entities
dampers
general_splines
nrods
reboundstops
wheels