Simulation

The Simulation object stores metadata information about the simulation. There must be exactly one simulation object on the simulation file, created by the Simulation keyword. It can also be used to optionally define simulation options (used by GeMA to configure its behaviour) and simulation constants (available for querying by the model).

Example

Simulation 
{
  name         = 'Steady state conduction',
  modelVersion = '1.0',
  description  = 'A simple heat conduction model for a square plate with different\n'..
                 'prescribed border temperatures.\n'..
                 'Reference: "Fundamentals of the Finite Element Method for Heat and Fluid Flow"\n'..
                 '           Lewis at al, example 5.2.1',

  options = {
    maxThreads         = 4,
    defMatrixBuildMode = 'hashLayout',
    disabledWarnings   = {'FixedBcForInvalidDof', 'ConflictingFixedBcValue'},
  },

  constants = {
    g     = 9.8,
    gUnit = 'm/s2',
  },  
}

Fields

Field	Description	Type	Required
name	The simulation name.	String	Yes
modelVersion	The model version in which this simulation files where written. When running the simulation, if the current model version is incompatible with the file version, a warning will be shown.	String	Yes
description	An optional description about the simulation role.	String	No
options	An optional table storing simulation options that can be used to control some global framework and/or plugin behaviours. Each table entry is keyed by the option name while its value should be compatible with the framework expected values for the given option. Default values are defined in the configuration file. Given values can be queried both during model loading and at the orchestration script through the options global table, also keyed by option name.	Table	No
constants	An optional table storing user given constants that can be queried during model loading and at the orchestration script. This constants are not internally used by GeMA. Each table entry is keyed by the constant name and its value can be any Lua type. Default constants can also be defined in the configuration file. Given values can be queried both during model loading and at the orchestration script through the constants global table, also keyed by constant name.	Table	No