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.
- On Windows: ~altair_install/io/translators/bin/win64/mdl_batch.bat
- On Linux: ~altair_install/altair/scripts/mdl_batch
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.
- 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 |
-MAF:true will generate an .maf file along with the solver
deck.
Note: This will override a setting related to writing an MAF file that is
saved in the input file (.mdl).
|
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
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
.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.