Configuration

The complete program is controlled by a system of variables. To allow user and model-specific variations, the necessary variables are loaded from several configuration files.

Configuration Files

The control script does not explicitly require a configuration file. There are several configuration steps, none of which is mandatory.

  1. Static configuration with .cfg file(s) located on the hard-drive
  2. DRIVER-command in the .par file
  3. Environment variables
  4. Command line

The system will search and execute configuration files first, then the DRIVER-command, etc. Any of the steps can be omitted or appear more than once.

The configuration file and DRIVER-command share the same syntax.

Static configuration

The system will search for static configuration files in the following directories, and execute the file if it exists.

Linux Windows
${tosca}/SMATsoResources/tosca.cfg %tosca%\SMATsoResources\tosca.cfg
${tosca}/linux_a64/SMATsoResources/tosca.cfg %tosca%\win_b64\SMATsoResources\tosca.cfg
${CATInstallPath}/SMATsoResources/tosca.cfg %CATInstallPath%\SMATsoResources\tosca.cfg
${HOME}/tosca.cfg %HOME%\tosca.cfg
<Input_dir>/tosca.cfg <Input_dir>\tosca.cfg

where:

  • <Input_dir> - the directory where the job is started from ( where the .par file is located ).
  • CATInstallPath may consist of more than one directory. The list is unfolded so every entry is a separate search directory.

DRIVER-command

Please refer to the DRIVER-command documentation for a detailed description of its features.

OPTIONS-command

The OPTIONS-command in the .par file is parsed by the driver in order to determine certain execution details. Available options, currently supported by the driver, are listed in the following table:

Option Description
USE_ABQ_UNROLL

Controls the enrolling of *LOADCASEs inside a *STEP. Possible values: YES, NO, ON, OFF, SELECTIVE. Default: OFF

Note: SELECTIVE means that the unrolling only happens if the first *STEP is a pre-loading step.

RESULT_OUTPUT

Controls the post-processing output. Possible values: OLD_ONF, SIM, SIM_AND_ONF. Default: OLD_ONF

Example:

        OPTIONS
          USE_ABQ_UNROLL = SELECTIVE
          RESULT_OUTPUT = SIM
        END_
      

Environment Variables

Tosca Structure uses and sets several environment variables during the optimization. Some can be configured by the user (either in the installation process, directly using standard operating system procedures or via Tosca Structure configuration files). Internal variables cannot (should not) be set or changed manually.

Most of the variables have value of either 0 or 1, meaning whether it is ON or OFF. To enable the feature it controls set it to 1 (ON), to disable - either leave out the definition of the variable, or set it to 0 (OFF).

Environment variable Set by default Usage
SMA_TSO_ABAQUS_PATH=<path_to_exe> NO

Abaqus path. The same variable is used with ToscaStructure. It is equivalent to $fe_solver_exe.

SMA_TSO_ANSYS_PATH=<path_to_exe> NO

Ansys path. The same variable is used with ToscaStructure. It is equivalent to $fe_solver_exe .

SMA_TSO_MSCNASTRAN_PATH=<path_to_exe> NO

MSC Nastran path. The same variable is used with ToscaStructure. It is equivalent to $fe_solver_exe .

SMA_TSO_FESAFE_PATH=<path_to_exe> NO

fe-safe path. The same variable is used with ToscaStructure. It is equivalent to $life_solver_exe .

ABA_NO_SITE_JOB_COMPLETION=1 YES

Used to skip some post completion check from Abaqus, which makes the Abaqus run faster.

ABA_TOSCA_PROTOTYPE=1 YES

Used to activate specific features in Abaqus in order to make it possible to work with ToscaPython driver.

Note: Set internally by the driver. Relevant only for simultaneous mode.

ABA_TOSCA_OVERLAY=1 YES

Used by Abaqus to overwrite the ODB file with each design cycle, instead of appending frames to a single file.

Note: Set internally by the driver. Relevant only for simultaneous mode.

ABA_TOSCA_STALL=1 NO

Used by Abaqus to be held in-memory while running Tosca optimization module.

Note: Set internally by the driver. Relevant only for simultaneous mode.

ABA_TOSCA_JOB_STALL=1 YES

Used by Abaqus to be held in-memory while running Tosca optimization module. Allows more than one instance.

ABA_ALLOW_NFORC=1 YES

Used by Abaqus to allow writing of internal forces for connector elements.

SMA_TSO_POST_REPORT=1 NO

Used by Tosca Python Driver to enable/disable ToscaReport post processing tool at the end of the job.

SMA_TSO_POST_SMOOTH=1 NO

Used by Tosca Python Driver to enable/disable ToscaSmooth post processing tool at the end of the job.

SMA_TSO_POST_ONF2SIM=1 NO

Used by Tosca Python Driver to enable/disable Onf2Sim post processing tool at the end of the job.

SMA_TSO_ABAQUS_DIAGNOSTICS=1 NO

Used by Tosca Python Driver to enable archiving of solver diagnostic files (SAVE.msg, SAVE.dat and SAVE.sta).

SMA_TSO_ABAQUS_DIAGNOSTICS=2 NO

Used to append stderr output stream from the solver to TOSCA.OUT .