Physics

Physics objects are responsible for helping analysis processes build the equation system that will be solved. In general, the process is responsible for the core of the analysis algorithm, while the physics implements aspects that are particular to a specific equation. In a FEM analysis, for example, physics cooperate to produce element local matrices that will be merged into the global matrix by the FEM process.

Physics are implemented in GeMA by plugins and created in the simulation file with the PhysicalMethod keyword. The available physics and their particular options are described in each physics plugin documentation

Example

PhysicalMethod 
{
  id       = 'HeatPhysics',
  typeName = 'ThermoFemPhysics',
  type     = 'fem',

  mesh               = 'myMeshName',
  boundaryConditions = {'Border temperature'},

  enableGeneration   = true,
}

Fields

Field (*)	Description	Type	Required
id	The physics name.	String	Yes
typeName	The name of the plugin that will be used to create this physics. If the plugin exports several object types, the plugin name should be followed by a dot followed by the requested physics object type.	String	Yes
	Examples: typeName = "ThermoFemPhysics", typeName = "HydroFemPhysics.Flow"
description	A description of the physics.	String	No
type	The type of physics object. Identifies the kind of process that this physics object is related, such as the "fem" process.	String	Yes

(*) Physics objects are implemented by plugins. Some of the additional fields on the exemple above, like mesh and boundaryConditions are common to all FEM physics and are documented on the Common Fem physics plugin options page, while others, like enableGeneration are specific to the plugin and are documented on the ThermoFemPhysics plugin documentation.