22.1. Running Autodyn on Windows Platforms

Autodyn, by default, runs in interactive mode, with the graphics window and interface displayed. If desired, you may also run Autodyn in batch mode where no graphics interface is shown. You may experience an increase in speed since the graphics do not need to be generated or refreshed. Also, by running Autodyn in batch mode it is possible to stack jobs to run consecutively while your PC is unattended (for example, overnight).

Autodyn can be executed from the operating system command line and accepts a number of command line arguments. The following command can be used to run Autodyn from the command line:

<installation path>\v162\aisol\AUTODYN\Winx64\AUTODYNWRAPPER.exe -noinput

The following table describes the command line arguments that can be used to control Autodyn file operations and execution behavior at start-up.

Argument

Operation Type

Operation

-noinput

Interactive (Serial\Parallel)

Opens the Autodyn GUI in order to create\execute models manually. In order to run a parallel simulation using the GUI, the -noinput option should be used in combination with the -mpi and -slaves options described below. This option is not relevant when used in combination with -mpi mscluster.

-i "<Autodyn model file>"

Batch (Serial\Parallel)

<Autodyn model file> is the name of the model file (including the path, if necessary). Using this option will run Autodyn in batch mode.

-beta

 

When running in batch mode, the model will run without beta options by default. Specifying this option will enable the model to run with beta features on.

-s <number of slave executables>

Batch (Parallel)

<number of slave executables> must be an integer that indicates the number of slave executables that will be used for the simulation. This option will have no effect on models that do not have the parallel options turned on.

-mpi <mpi type>

Batch (Parallel)

<mpi type> must be either pcmpi, intelmpi, msmpi, or mscluster.

If either of the -slaves or -machines options are used and the mpi type option is not defined, the simulation will be run using the default option pcmpi.

-machines "<machine name>"

Batch (Distributed Parallel)

<machine name> must be a string containing a list of machine names that will be used to run the slave executables and the number of slaves that will be run on each machine. The master executable is run on the local machine by default. The string should be constructed with the machine name followed by a colon followed by the number of slaves to be run on the machine. Multiple machine definitions should be separated by commas; for example "MachineA:2,MachineB:3".

-nodes "<node names>"

Batch (Parallel – Microsoft HPC)

<node names> is an optional argument. If used it should list the node names of specific nodes the job should run on. If this option is not used then the job scheduler will use whichever nodes are available. The sum of cores available on the nodes specified must be greater than or equal to N+1, where N is the number of slaves required (defined by the -slaves argument) otherwise the job will not run. Node names should be separated by commas; for example "NodeName1,NodeName2".

Putting a file named endbat.dat in either the configuration folder or data folder will cause a simulation to stop at the end of the current cycle. Once stopped, Autodyn will delete the endbat.dat file.

Putting a file named savenow.dat in either the configuration folder or data folder will force the simulation to write a restart file at the end of the current cycle. Once the restart file has been written out, Autodyn will delete the savenow.dat file and it must be re-created to write out a new restart file.

An example batch file below shows how to stop a job that is running in batch mode.

REM write out endbat.dat in data directory 
cd /D "D:\Analysis Data" 
echo null>endbat.dat

Autodyn will use the user temporary folder for temporary files and log file creation. This folder must have read/write permission for the user. The location of the folder for Windows 7 systems is C:\Users\username\AppData\Local\Temp.


Release 16.2 - © SAS IP, Inc. All rights reserved.