Analysis record

This record describes the type of analysis, which should be performed. The analysis record can be splitted into optional meta-step input records (see below). Then certain attributes originally in analysis record can be specified independently for each meta-step. This is marked by adding ``M'' superscript to keyword. Then the attribute format is Keyword$^M$ #(type).

The general format of this record can be specified in

• ``standard-syntax''
  

  *AnalysisType	nsteps #(in)
  	[renumber #(in)]
  	[profileopt #(in)]
  	attributes #(string)
  	[ninitmodules #(in)]
  	[nmodules #(in)]
  	[nxfemman #(in)]

  
  
• ``meta step-syntax''
  

  *AnalysisType	nmsteps #(in)
  	[ninitmodules #(in)]
  	[nmodules #(in)]
  	[nxfemman #(in)]

  
  
  immediately followed by nmsteps meta step records with the following syntax:
  

  nsteps #(in) attributes #(string)

  
  
  

  The nmsteps parameter determines the number of ``metasteps''. The meta step represent sequence of solution steps with common attributes. There is expected to be nmsteps subsequent metastep records. The meaning of meta step record parameters (or analysis record parameters in ``standard syntax'') is following:

  • nsteps - determines number of subsequent solution steps within metastep.
  • renumber - Turns out renumbering after each time step. Necessary when Dirichlet boundary conditions change during simulation. Can also be turned out by the executeable flag -rn.
  • profileopt - Nonzero value turns on the equation renumbering to optimize the profile of characteristic matrix (uses Sloan algorithm). By default, profile optimization is not performed. It will not work in parallel mode.
  • attributes - contains the metastep related attributes of analysis (and solver), which are valid for corresponding solution steps within meta step. If used in standard syntax, the attributes are valid for all solution step.
  • ninitmodules - number of initialization module records for given problem. The initialization modules are specified after meta step section (or after analysis record, if no metasteps are present). Initialization modules allow to initialize the state variables by values previously computed by external software. The available initialization modules are described in section 5.7.
  • nmodules - number of export module records for given problem. The export modules are specified after initialization modules. Export modules allow to export computed data into external software for postprocessing. The available export modules are described in section 5.8.
  • nxfemman - 1 implies that an XFEM manager is created, 0 implies that no XFEM manager is created. The XFEM manager stores a list of enrichment items. The syntax of the XFEM manager record and related records is described in section 4.11.
  • eetype - optional error estimator type used for the problem. Used for adaptive analysis, but can also be used to compute and write error estimates to the output files. See adaptive engineering models for details.

Not all of analysis types support the metastep syntax, and if not mentioned, the standard-syntax is expected. Currently, supported analysis types are

• Linear static analysis, see section 3.1.2,
• Eigen value dynamic, see section 3.1.4,
• Direct explicit nonlinear dynamics, see section 3.1.5,
• Direct explicit (linear) dynamics, see section 3.1.6,
• Implicit linear dynamic, see section 3.1.7,
• Incremental linear static problem, see section 3.1.8,
• Non-linear static analysis, see section 3.1.9.