|
programmer's documentation
|
Variables definition initialization, according to calculation type selected by the user. More...
Functions/Subroutines | |
| subroutine | fldvar (nmodpp) |
| Variables definition initialization, according to calculation type selected by the user. More... | |
| subroutine | add_variable_field (name, label, dim, ivar) |
| add field defining a general solved variable, with default options More... | |
| subroutine | add_user_scalar_fields |
| add fields defining user solved scalar variables, with default options More... | |
| subroutine | add_model_scalar_field (name, label, iscal) |
| add field defining a non-user solved scalar variable, with default options More... | |
| subroutine | add_model_field (name, label, dim, iscal) |
| add field defining a non-user solved scalar variable, with default options More... | |
| subroutine | fldvar_check_nvar |
| Check nvarmx is sufficient for the required number of variables. More... | |
| subroutine | fldvar_check_nscapp |
| Check nscamx is sufficient for the required number of model scalars. More... | |
Variables definition initialization, according to calculation type selected by the user.
| subroutine add_model_field | ( | character(len=*), intent(in) | name, |
| character(len=*), intent(in) | label, | ||
| integer, intent(in) | dim, | ||
| integer, intent(out) | iscal | ||
| ) |
add field defining a non-user solved scalar variable, with default options
It is recommended not to define variable names of more than 16 characters, to get a clear execution listing (some advanced writing levels take into account only the first 16 characters).
| [in] | name | field name |
| [in] | label | field default label, or empty |
| [in] | dim | field dimension |
| [out] | iscal | variable number for defined field |
| subroutine add_model_scalar_field | ( | character(len=*), intent(in) | name, |
| character(len=*), intent(in) | label, | ||
| integer, intent(out) | iscal | ||
| ) |
add field defining a non-user solved scalar variable, with default options
It is recommended not to define variable names of more than 16 characters, to get a clear execution listing (some advanced writing levels take into account only the first 16 characters).
| [in] | name | field name |
| [in] | label | field default label, or empty |
| [out] | iscal | variable number for defined field |
| subroutine add_user_scalar_fields | ( | ) |
add fields defining user solved scalar variables, with default options
| subroutine add_variable_field | ( | character(len=*), intent(in) | name, |
| character(len=*), intent(in) | label, | ||
| integer, intent(in) | dim, | ||
| integer, intent(out) | ivar | ||
| ) |
add field defining a general solved variable, with default options
It is recommended not to define variable names of more than 16 characters, to get a clear execution listing (some advanced writing levels take into account only the first 16 characters).
| [in] | name | field name |
| [in] | label | field default label, or empty |
| [in] | dim | field dimension |
| [out] | ivar | variable number for defined field |
| subroutine fldvar | ( | integer | nmodpp | ) |
Variables definition initialization, according to calculation type selected by the user.
| [out] | nmodpp | number of activated paricle physic models |
| subroutine fldvar_check_nscapp | ( | ) |
Check nscamx is sufficient for the required number of model scalars.
| subroutine fldvar_check_nvar | ( | ) |
Check nvarmx is sufficient for the required number of variables.
1.8.7