FE Solver Information

This section lists parameter for defining more detailed information about the FE solver.

Configuration Parameter

Example

Remarks

${fe_solver}

${fe_solver} = "abaqus";

Specification of the finite element solver interface. The following solvers are supported:

Abaqus, ANSYS®, MSC Nastran®

${fe_solver_exe}

${fe_solver_exe} = "C:/solver/solver.exe";

Path to the corresponding executable finite element solver.

${fe_solver_cmdline}

${fe_solver_cmdline} = "job= ${__FE_MODEL__}";

Definition of the command line for the finite element analysis. All command line options which should be used for the solver call have to be defined using this variable.

${fe_solver_add_call}

${fe_solver_add_call}= "mem = 100Mb";

Additional command line options for the solver call. These statements are added to the fe_solver_call variable.

${fe_check_file}

${fe_check_file}= "${__FE_MODEL__}. f06";

Definition of a check file that is parsed after the finite element analysis to check if the solver run finished correctly.

To avoid this check set:

${fe_check_file}="";

${fe_check_string}

${fe_check_string}= "FATAL MESSAGE";

Case sensitive string that is searched in the check file (${fe_check_file}). Action is determined by ${fe_check_type}.

${fe_check_type}

${fe_check_type} = "failed";

${fe_check_type} = "succeeded";

Specification if the existence of the check string (${fe_check_string}) in the check file (${fe_check_file}) defines that the job failed or the job has succeeded.

failed: SIMULIA Tosca Structure 2017 stops if the check string is found in check file.

succeeded: The check string must be found in check file for SIMULIA Tosca Structure 2017 to con­ tinue. SIMULIA Tosca Structure will also stop if the check file is cannot be found, assuming the FE- solver has not run correctly.

Remark

  1. The solver call is assembled by the $fe_solver_exe, $fe_solver_c­ mdline and $fe_solver_add_call variables during the runtime, i.e.: 
    > $fe_solver_exe $fe_solver_cmdline $fe_solver_add_call
    For the default settings for Abaqus in the tosca_ctrl.cfg: 
    ${fe_solver_exe} = "/usr/bin/abaqus";

${fe_solver_cmdline} = "job=${__FE_MODEL__} analysis interactive";

${fe_solver_add_call}="";
    this would be combined to the following call (for example holeplate.par): 
    > /usr/bin/abaqus job=holeplate analysis interactive
    Lets assume you want to use 4 cpus for Abaqus. Set: 
    ${fe_solver_add_call}="cpus=4";
    And the new solver call would be: 
    > /usr/bin/abaqus job=holeplate analysis interactive cpus=4
  2. Relative executable paths are allowed as well as paths using environment variable PATH.
  3. UNC Path are allowed. Valid paths are: 
    $tosca_prep='\\apps\tosca\bin\tosca_prep';

$tosca_prep="\\\\apps\\tosca\\bin\\tosca_prep";

$tosca_prep="//apps/tosca/bin/tosca_prep";

$tosca_prep='//apps/tosca/bin/tosca_prep';
    Invalid paths are: 
    $tosca_prep=\\\\apps\tosca\bin\tosca_prep;

$tosca_prep="\\\\apps\tosca\bin\tosca_prep";

$tosca_prep=//apps/tosca/bin/tosca_prep;