Analysis record

This record describes the type of analysis, which should be performed. The general format of this record can be specified in

• ``standard-syntax''
  

  *AnalysisType	nsteps(in) #
  	[renumber(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. Nonzero value of optional parameter renumber 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 6.23.
  • 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 6.24.
  • nxfemman - number of xfem managers. Xfem managers wrap eXtended Finite Element (xfem) data: they manage the list of enrichment items and associated enrichment functions, and their geometry representation. The number of xfem managers required is problem dependent, typically a single xfem manager is used. The syntax of xfem manager record and related records is described in section 7.11.

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 6.1,
• Eigen value dynamic, see section 6.3,
• Direct explicit nonlinear dynamics, see section 6.4,
• Direct explicit (linear) dynamics, see section 6.5,
• Implicit linear dynamic, see section 6.6,
• Incremental linear static problem, see section 6.7,
• Non-linear static analysis, see section 6.8.