MotionView in Batch Mode

Batch mode allows you to generate a solver input model file from an MDL model file and run the solver job without starting the MotionView user interface.

The batch utility is available at:

On Windows: ~altair_install/io/translators/bin/win64/mdl_batch.bat
On Linux: ~altair_install/altair/scripts/mdl_batch

Where ~altair_install is the directory where the application is installed.

The following syntax is used:

mdl_batch [input_filename] [output_filename] [solver_name] <options>

input_filename: The name of the input file.
output_filename: The name of the output file. Basename only.
solver_name: The name of the solver to which to export.

Registered solvers include:

Argument: Solver Name
MotionSolve: MotionSolve
ADAMS: ADAMS
Abaqus: Abaqus

<options> (solver-specific)

The format is: -Option:Value


`-ANALYSIS:var_name` or `-ANALYSIS:ALL`	Select the analysis for the export with the given varname of the analysis. or Use ALL to export solver file for all existing analyses in the MDL. If this option is not specified, the solver file will be created with the active analysis if there any in the MDL.
`-SCRIPT:scriptname`	Execute the solver script with the scriptname after the export. The script with the scriptname should be registered into MotionView using the preference statement *RegisterSolverScript() through a preference file.
`-MAF:true` or `-MAF:false`	An .maf file will be generated along with the solver deck. or An .maf file will not be generated. Note: This will override a setting related to writing an MAF file that is saved in the input file (.mdl).
`-CHECKMODEL:true` or `-CHECKMODEL:false`	The model is checked for errors before writing of the solver deck. In the case of errors, a log is generated (runfile_mdlbatch.log) and the solver deck is not created. or The solver deck is created without checking the model for errors. Default: false

Example

C:\Users\Tutorials>"C:\Program Files\Altair\2017\io\translators\bin\win64\mdl_batch.bat" front_susp.mdl
        C:/Users/Tutorials/Runs/ride.xml MotionSolve -ANALYSIS:an_ride_frnt-SCRIPT:MotionSolve

In this example, the mdl_batch would export the model from front_susp.mdl to MotionSolve XML ride.xml with the analysis an_ride_frnt and execute the solver script MotionSolve.

Note: The MotionSolve script is registered by default.

C:\Users\Tutorials>"C:\ProgramFiles\Altair\2017\io\translators\bin\win64\mdl_batch.bat" front_susp.mdl 
C:/Users/Tutorials/Runs/all_analysis.admADAMS-ANALYSIS:ALL-MAF:true

In this example, the mdl_batch would export the model from front_susp.mdl to ADAMS adm all_analysis_[analysis_varname].adm and acf for all analyses present in the mdl along with saving a corresponding .MAF file for each analysis.