Configuring Adams > Learning the Basics > Command-Line Parameters

Command-Line Parameters

In addition to using the Adams Selection Menu and entering selection codes and responding to prompts, you can enter command-line parameters. You enter command-line parameters at the operating system prompt.
To enter command line parameters, you enter the command to run Adams Selection Menu, followed by a series of strings representing prompt selections. You can enter the complete selection codes or abbreviations. To indicate pressing Enter, use -none or its abbreviation (-n). Use spaces to separate the various parameters. As the command executes, menus or prompts do not appear.
If you make an error in a command-line parameter, an error message appears and prompts you to enter exit. If you enter exit, the command aborts and displays the Adams Selection Menu.
The following table lists information about the keywords and parameters:
 
Keyword
If LINUX
Options
Parameters
/top_dir/mdi
 
exit
Action: exit command menu 
/top_dir/mdi
-c
ru-standard
Action: run solver with standard executable

Arguments:
abc.acf : adams command file
 
Example

LINUX: mdi -c ru-st i abc.acf ex  
Windows: mdi ru-st abc.acf ex  
/top_dir/mdi
-c
ru-user
Action: run solver with user executable

Arguments:
abc.dll or abc.so : user executable
abc.acf : adams command file
 
Example

LINUX: mdi -c ru-u abc.so i abc.acf ex  
Windows: mdi ru-u abc.dll abc.acf ex  
/top_dir/mdi
-c
cr-user
Action: create user executable

Argument:
y/n : yes/no option to link in debug mode
.o : object file compiled with FORTRAN, C or C++
or
.c, .cxx,.f : source file
or
.lst : list of object or source files
-n : (none) to mark end for list of arguments
abc.dll or abc.so : name of library to be created
e : exit
 
Example

LINUX: mdi -c cr-u n sub.f -n cam.so ex
Windows: mdi cr-u n sub.f -n cam.dll ex
/top_dir/mdi
-c
aview
Action: launch aview

Arguments:
cr-user : refer to cr-u option listed above
ru-standard : run standard aview executable
              i/b/f - option for interactive, interactive-file or                           batch mode
ru-user : run aview with user executable
              i/b/f - option for interactive, interactive-file or                           batch mode
              abc.dll - view user library
              xyz.dll - solver user library
              d - running in debug mode (this only applies to               Linux). Users can utilize this command to               debug their user subroutine with the gdb               debugger.
              eg: mdi -c ru-u d abc.so i abc.acf ex
 
Example

LINUX: mdi -c aview ru-u i abc.so xyz.so ex
Windows: mdi aview ru-s i abc.dll xyz.dll ex
/top_dir/mdi
-c
acar
Action: launch acar
----------------------------------------------------------------
Create
---------------------------------------------------------------
Options
cr-acarprivate : acar private library (use / MDI_ACAR_PRIVATE_DIR for lib)
cr-acarsite : acar site library (use /MDI_ACAR_SITE for lib)
cr-solverprivate: acar solver library (use /MDI_ACAR_PRIVATE_DIR for lib)
cr-solversite : acar solver site library (use /MDI_ACAR_SITE for lib)
cr-privatebin : Create custom binary file
cr-sitebin : Create custom binary file
Arguments:
y/n : yes/no option to link in debug mode
.o : object file compiled with FORTRAN, C or C++
or
.c, .cxx,.f : source file
or
.lst : list of object or source files
-n : (none) to mark end for list of arguments
acar_solver.dll or acar_solver.so : name of user library to be created at above mentioned directory for the library
e : exit
 
 
 
For more details check: Running Adams Products > On Windows

--------------------------------------------------------------
Run
--------------------------------------------------------------
ru-acar       : with either the Private, Site or Std binary
ru-private  : private acar.bin
ru-site      : site acar.bin
ru-standard : standard acar.bin
  ru-solver      : run adams car with private, site and standard solver
 
Example

LINUX: mdi -c acar ru-sol i abc.acf ex
Windows: mdi acar ru-sol abc.acf ex
/top_dir/mdi
-c
acsi
Action: launch co-simulation interface
 
Example

LINUX: mdi -c  
Windows: mdi acsi 
/top_dir/mdi
-c
adriveline
Action: launch adriveline
 
Options:
----------------------------------------------------------------
Create
---------------------------------------------------------------
cr-adrivelinepriv : adriveline private library(use / MDI_ADRV_PRIVATE_DIR for lib)
cr-adrivelinesite : adriveline site library
(use /MDI_ADRIVELINE_SITE for lib)
cr-solverprivate : adriveline solver library (use / MDI_ADRV_PRIVATE_DIR for lib)
cr-solversite : adriveline solver site library
(use /MDI_ADRIVELINE_SITE for lib)
cr-privatebin : Create custom binary file
cr-sitebin : Create custom binary file
 
Arguments:
y/n : yes/no option to link in debug mode
.o : object file compiled with FORTRAN, C or C++
or
.c, .cxx,.f : source file
or
.lst : list of object or source files
-n : (none) to mark end for list of arguments
adriveline_solver.dll or adriveline_solver.so : name of user library to be created at above mentioned directory for the library
e : exit
 
For more details check: Running Adams Products > On Windows
--------------------------------------------------------------
Run
--------------------------------------------------------------
ru-adriveline : with either the Private, Site or Std binary
ru-private       : private adriveline.bin
ru-site         : site adriveline.bin
ru-standard    : standard adriveline.bin
  ru-solver         : run Adams car with private, site and standard solver
Example

LINUX: mdi -c adriveline ru-sol i abd.acf ex
Windows: mdi adriveline ru-sol abd.acf ex
/top_dir/mdi
-c
aexplore
Action: launch aexplore job-server and web-server
 
Arguments:
ru-jobserver : starts job server
ru-webserver : starts webserver
 
Example

LINUX: mdi -c aexplore ru-jobserver  
Windows: mdi aexplore ru-jobserver
/top_dir/mdi
-c
ainsight
Action: launch ainsight
 
Example

LINUX: mdi -c ainsight
Windows: mdi ainsight
/top_dir/mdi
-c
appt
Action: launch post processor
 
Example

LINUX: mdi -c appt
Windows: mdi appt
/top_dir/mdi
-c
redit
Action: Launch msc registry editor
 
Example

LINUX: mdi -c redit
Windows: mdi redit
/top_dir/mdi
 
 
Action: msc registry tools
 
Supported commands:

cd : change directory; absolute or relative paths
example: cd /vendor/tools/interface/settings

pwd : print working directory

set : set property - absolute or relative path to property name
example: set /graphics/perf/DoubleBuffering TRUE
set ../../loads/Max_settings 12

unset : unset property - absolute or relative path to property name
example: unset /graphics/perf/DoubleBuffering

get : print individual property's value - absolute or relative path
example: get /graphics/driver/HPUX11

ls : prints all property names and values, datatypes, ranges
in current directory only

dir : prints all property names and values, datatypes, ranges
in current directory and subdirectories, recursively

files : lists locations of the implementation registry files,
number of lines last parsed from each

prompt : changes prompt
example: prompt pwd - changes prompt to display current
directory
prompt normal - changes prompt to display
default 'REG>>' string
 
 
 
verbose : toggles verbose mode on and off. default=on

exit : saves changes and exits

quit : exits without changes
 
Example

LINUX: mdi -c rtool
set //TOP_DIR/MDI/ACar/Preferences/privateDir /usr/people/someone/new_private

WINDOWS: mdi rtool
set D://TOP_DIR/MDI/ACar/Preferences/privateDir D:/people/someone/new_private
/top_dir/mdi
-c
python
Actions: Launch python command prompt
 
Example

LINUX: mdi -c python
WINDOWS: mdi python
/top_dir/mdi
-c
help
Actions: Launch help options
/top_dir/mdi
-c
flextk
Actions: launch flex toolkit

Options:
--------------------------------------------------------------------
Translate
-------------------------------------------------------------------
mnf2mtx : MNF file to Matrix file
msc2mnf : MSC/NASTRAN file to MNF file
mnfload : Add Load-cases to MNF file
unv2mnf : Universal file to MNF file
mnfxform : MNF file to XFORM file
mnfres : Export flex body nodal simulation results
abq2nas : Abaqus input file to NASTRAN input file
 
Example

LINUX: mdi -c flextk msc2mnf NASTRAN_OUT2_file
WINDOWS: mdi flextk msc2mnf NASTRAN_OUT2_file
/top_dir/mdi
-c
durtk
Actions: launch durability toolkit

--------------------------------------------------------------------
Options
--------------------------------------------------------------------
durfilter : Filter durability files
mnf2fes  : Translate MNF to nCode FES file
res2dur   : Translate results to durability files
 
Example

LINUX: mdi -c durtk
WINDOWS: mdi durtk
/top_dir/mdi
-c
cmm
Actions: update custom memory model
 
For more details, see Setting Custom Memory Model Size.
 
Example

LINUX: mdi -c cmm
WINDOWS: mdi cmm
-> Update 8 values prompted
/top_dir/mdi
-c
-meplot
Actions: Displays standard plots
Example

LINUX: mdi -c meplot plot_temp_name res_name
WINDOWS: mdi meplot plot_temp_name res_name
/top_dir/mdi
-c
-makeleaf
Actions: Executes Makeleaf without running the Leaf Spring Editor
Example

LINUX: mdi -c makeleaf leaf_template_file
WINDOWS: mdi makeleaf leaf_template_file
where:
■The -n indicates pressing Enter in response to the second subroutine file prompt and e represents exit. Because the last e is a response to the menu, the operating system prompt returns after creating the library file.
■The y answers the question about working in debug mode and the -n indicates a return in response to the second subroutine file prompt. The system level returns after linking the library file. You must use spaces to separate the various parameters. When entering source files, be sure the .f or .c extension is lowercase.