Flow123d  jenkins-Flow123d-linux-release-multijob-198
Public Types | Static Public Member Functions | List of all members
GenericField< spacedim > Class Template Reference

#include <generic_field.hh>

Public Types

typedef FieldValue< spacedim >
::Integer 
IntegerScalar
 Index value type. More...
 
typedef Field< spacedim,
IntegerScalar
IndexField
 Index valued field. More...
 

Static Public Member Functions

static auto region_id (Mesh &mesh) -> IndexField
 
static auto subdomain (Mesh &mesh) -> IndexField
 

Detailed Description

template<int spacedim>
class GenericField< spacedim >

Definition at line 26 of file generic_field.hh.

Member Typedef Documentation

template<int spacedim>
typedef Field<spacedim, IntegerScalar> GenericField< spacedim >::IndexField

Index valued field.

Definition at line 32 of file generic_field.hh.

template<int spacedim>
typedef FieldValue<spacedim>::Integer GenericField< spacedim >::IntegerScalar

Index value type.

Definition at line 30 of file generic_field.hh.

Member Function Documentation

template<int spacedim>
auto GenericField< spacedim >::region_id ( Mesh mesh) -> IndexField
static

Returns an instance of a scalar integer field that provides ID's of regions.

Definition at line 18 of file generic_field.impl.hh.

Here is the caller graph for this function:

template<int spacedim>
auto GenericField< spacedim >::subdomain ( Mesh mesh) -> IndexField
static

Returns an instance of a scalar integer field that provides ID's of subdomains used for domain decomposition.

TODO: FieldElementwise just use provided data pointer (unsafe solution), so currently we store the data into a mesh. Which is safe as long as we have one mesh for whol calculation. After we have FieldFE that use some sort of Vector class with own memory management, we should use these to pass the data in safe way.

Definition at line 39 of file generic_field.impl.hh.

Here is the caller graph for this function:


The documentation for this class was generated from the following files: