Valid D3PLOT Command Line Arguments

Device types that are valid are:

(Older versions of D3PLOT also supported 2d X11 graphics on Linux platforms. This was withdrawn in D3PLOT 14.0, and 2d graphics is no longer supported.)

By default the top right corner of the desktop is used.

The most common arrangement is two screens side by side, for which "left" and "right" may be used. However "top" and "bottom" are also available for the case of two screens one above the other, and the options may be concatenated for a 2x2 display.

These options can be combined with -maximise to fill the relevant screen.

Users on Windows platforms where tools such as NVidia's "NView" are available may find that it is better to leave window placement to that tool, so that D3PLOT's windows behave in a fashion consistent with other application windows.

This option is intended for use where the desktop is spread as a "Single Logical Screen" over multiple monitors.

The above may be concatenated for a 2x2 display, for example

Command file name
Flag to exit when command file run complete if desired

JavaScript

JavaScript Arguments

Checkpoint file to replay
Number of lines to execute in checkpoint file

Optional "project" working directory.

This specifies an alternate initial location for view, cut-section, group, settings and external data files. Useful if the directory containing analysis data is read-only so that these files have to be located elsewhere

Specifying a custom "oa_pref" file.

This causes an extra, optional "oa_pref" file to be read.

<filename> must be a valid "oa_pref" file.

If it has no path prefixed, the file is assumed to be in the OA_INSTALL directory. Any legal filename may be used.

The following output formats are available:

Specific states may be selected as follows:

-states=all

<none>

Two new methods of generating cutdown models are available:

Method 1 involves feeding all relevant options on the command line. This can only produce one cutdown model. Eg:

-ptfcut_batch -reorder
<-vel/-acc/-plastic/-stress/
-strain/-von_stress/-von_strain>
-states=<[start, end, optional_inc]/odd/even>
-o=<output> <input>

Method 2 involves specifying options in a file and invoking that using the -ptfcut_batch= flag. This method can be used to generate multiple cutdown models, each with its own components, formats and states

-ptfcut_batch=<options_file> <input>

Example options_file:

-reorder -vel -states=odd -o=vel.ptf
-acc -o=acc.ptf

There is currently no option to select specific parts for the cutdown model. All parts are processed by default.

Methods of writing out the HDF5 envelope data file using the batch mode:

To write out the HDF5 file with envelope data, we need to set '-d=batch' flag to run D3PLOT in batch mode.

-env_out writes out the HDF5 file for the 'filename.ptf' model file provided.

Users need to provide a settings file with all the necessary options already set like integration points, reference frames and data components etc.  

<install-dir>d3plot22_x64.exe -d=batch -env_out -set="<settings file path>\d3plot001.set" "<model_path>\filename.ptf"

We write out envelope data for all the states by default through batch. Selection of subset of states through the settings file is not supported for batch writing.

Using this option will prevent D3PLOT from reading a human-readable ASCII groups file (group nnn .asc) but it will still read any cached binary groups file ( jobname .grp) that is left over from an earlier D3PLOT session which used groups in this model.

For more information see the GROUPS section of this manual.

The model list file should contain the full pathname of one file from each model that D3PLOT should open. Each file should be on a separate line and it should be the first item on each line.

By default each model will be read into Window 1, but you can specify which windows a model is read into by specify a bitwise encoded number after the model name (W1=1, W2=2, W3=4, W4=8, etc.)

e.g. if you read in 4 models with the following file:

model1.ptf 1

model2.ptf 2

model3.ptf 4

model4.ptf 3

model1.ptf would go into W1, model2.ptf into W2, model3.ptf into W3 and model4.ptf into W1 and W2. Contact Oasys Ltd Support if you need further explanation.

Run D3PLOT in "batch" mode where the main application window is not displayed on the screen. For this option to work you must also specify a command file " -cf=filename " and the name of the PTF file to open.

This option will automatically set " -exit " so that D3PLOT terminates after playing the command file.

Redirect output from the console window to a file on Windows.

To redirect output on Unix/Linux use the shell redirection options (typically > for <stdout>, & for <stderr>)

-eo=<filename> is designed for the user to suppress the console and redirect logfile output to the specified filename. In order to permit multiple sessions to coexist on the same machine the process id will be appended to the <name> part of the filename to give <name>_pid.<ext>.

If plain "-eo" or "-eo=default" are found then filename generation is automatic, and the first valid of:

%TEMP%\this_log_<pid>.txt
%TMP%\this_log_<pid>.txt
%HOMESHARE%\this_log_<pid>.txt
%USERPROFILE%\this_log_<pid>.txt

will be used.

Read/Write checkpoint files

Start writing the checkpoint files upon D3PLOT startup

Read checkpoint files and Show checkpoint playback panel upon D3PLOT startup.

Directory path to write checkpoint files

TRUE/FALSE, turn on/off the writing of the checkpoint files (default is FALSE)

TRUE/FALSE, turn off the initial checkpoint files panel (default is FALSE)

If the writing of the checkpoint files is OFF, the reading will also be OFF

< directory > must be a valid directory name on your system.

If the value is <none> then the checkpoint files are not recorded for the D3PLOT session.

Run D3PLOT without the console window.

(The extra time history ( .xtf ) and contact force ( .ctf ) databases are also opened if present.)

For example:

Correct syntax is:

" -eo = default " is illegal.

" -eo=default "