Description

The command line (or Command Prompt on Windows) can be used to either launch Fidelity Pointwise or run Glyph scripts in batch mode. The syntax for each OS is shown below.

GUI Mode
$pointwise_home_path/pointwise
Batch Mode
$pointwise_home_path/pointwise -b script ?script_args?

The optional argument ?script_args? can be used to pass a list of arguments to the specified Glyph script. For more information about passing arguments to a Glyph script, see the video in the Demonstration section below.
GUI Mode
$pointwise_home_path/pointwise
Batch Mode
$pointwise_home_path/pointwise -b script ?script_args?
$pointwise_home_path/Pointwise.app/Contents/MacOS/tclsh script ?script_args?

Scripts can be run in batch mode either by launching the Fidelity Pointwise app with the -b flag or by launching the tclsh provided with the Fidelity Pointwise installation. The optional argument ?script_args? can be used to pass a list of arguments to the specified Glyph script. For more information about passing arguments to a Glyph script, see the video in the Demonstration section below.
GUI Mode
$pointwise_home_path/win64/bin/Pointwise.exe
Batch Mode
$pointwise_home_path/win64/bin/tclsh.exe ?script ?script_args??

Scripts can be run in batch mode by launching the tclsh provided with the Fidelity Pointwise installation. The optional argument ?script_args? can be used to pass a list of arguments to the specified Glyph script. For more information about passing arguments to a Glyph script, see the video in the Demonstration section below.

For more information on running Fidelity Pointwise in batch mode, please see the Glyph Reference Manual installed with Fidelity Pointwise.

Additional Command Line Options

  • ?-usage?
  • ?-version?
  • ?-language spec?
  • ?-tbbinit num?
  • ?-dirmode current | saved?
  • ?-noshaders?
  • ?-environment env_file?
  • ?-scriptType language?
  • ?startup_script | file?

The command line options are discussed in further detail as follows:

  • -usage: Displays this usage information in a dialog box. The application exits when the dialog is closed. The default is NONE.
  • -version: Displays the executable's version string to stdout and exits.
  • -language spec: Specifies the Fidelity Pointwise runtime language. At this time, the only valid values for spec are: en-us for US English.
  • -tbbinit num: Controls the maximum number of calculation threads that Fidelity Pointwise can spawn. By default, this number is set to 0 to allow an unlimited number of calculation threads.
  • -dirmode current | saved: Determines where the file dialogs will start. current will force the dialogs to start in the current working directory despite the preference setting. saved will force the dialogs to start in the saved directory. Note that this parameter does not change the preference setting in the GUI. Refer to the description of the Miscellaneous frame in the Preferences section for information on how to set this up via the GUI.
  • -noshaders: This executes Fidelity Pointwise without using OpenGL shaders.
  • -environment env_file: Specifies the environment file (env_file) to load after Fidelity Pointwise starts. You can learn more about environment files in the Open Environment section.
  • -scriptType language: Specifies the type of script being run either in batch mode or as a startup script. Note that the script type specified in language, must match one of the scripting languages specified in the Scripting Languages frame in the Preferences panel.
  • startup_script | file: Specifies the Glyph script (startup_script) to execute or the Fidelity Pointwise project file (*.pw) to load after Fidelity Pointwise starts. If defined, the file name must follow all switches and be the last command line argument. The default is NONE.

Demonstration

Passing Arguments to a Glyph Script