Append state variable depends on the scheme kind
allocate function pointers, and append pdf to scheme%varSys
Type | Intent | Optional | Attributes | Name | ||
---|---|---|---|---|---|---|
type(tem_varSys_type), | intent(inout) | :: | varSys |
global variable system |
||
type(tem_varMap_type), | intent(out) | :: | stateVarMap |
Store position of state variable in global varSys |
||
type(mus_varSys_solverData_type), | intent(in), | target | :: | solverData |
Contains pointer to solver data types |
|
type(mus_scheme_header_type), | intent(in) | :: | schemeHeader |
identifier of the scheme |
||
type(tem_stencilHeader_type), | intent(in) | :: | stencil |
compute stencil defintion |
||
integer, | intent(in) | :: | nFields |
number of fields |
||
character(len=*), | intent(in) | :: | fldLabel(:) |
array of field label prefix. Size=nFields |