#include <FieldsPiWisConst.h>
Inheritance diagram for FieldsPiWisConst::
Public Methods | |
| FieldsPiWisConst () | |
| FieldsPiWisConst (int n, const char *fieldname) | |
| FieldsPiWisConst (const GridFE &grid, bool elementsRsubdomains, const char *fieldname) | |
| FieldsPiWisConst (int nfields, const GridFE &grid, bool elementsRsubdomains, const char *fieldname) | |
| ~FieldsPiWisConst () | |
| virtual void | redim (int nsf, const char *fieldname) |
| void | redim (const GridFE &grid, bool elementsRsubdomains, const char *fieldname) |
| void | redim (int nfields, const GridFE &grid, bool elementsRsubdomains, const char *fieldname) |
| FieldPiWisConst& | operator() (int i) |
| const FieldPiWisConst& | operator() (int i) const |
| virtual FieldWithPtValues& | component (int i) |
| virtual const FieldWithPtValues& | component (int i) const |
| virtual Field* | getFieldBase (int i=1) const |
| virtual void | attach (Field &field, int i=1) |
| void | attach (FieldPiWisConst &field, int i=1) |
| void | attach (FieldsPiWisConst &fields) |
| void | valueElm (Ptv(NUMT) &vec, int element) |
| void | valueElm (Ptv(NUMT) &vec, int element) const |
| virtual void | valuePt (Ptv(NUMT) &vec, const Ptv(real) &x, real t=DUMMY) |
| virtual void | valueFEM (Ptv(NUMT) &vec, const FiniteElement &fe, real t=DUMMY) |
| void | fill (NUMT value) |
| void | setValueElm (int element, const Ptv(NUMT) &vector) |
| void | fill (const FieldsFEatItgPt &f) |
| virtual Grid* | getGridBase () |
| virtual int | getNoFields () const |
| virtual int | getNoValues () const |
| virtual bool | ok () const |
| CLASS_INFO | VIRTUAL_CAST (FieldsPiWisConst) ASSIGNMENT_OPERATOR(FieldsPiWisConst) |
| COPY_CONSTRUCTOR (FieldsPiWisConst) | |
Protected Attributes | |
| VecSimplest(Handle(FieldPiWisConst)) | sdsfvec |
NAME: FieldsPiWisConst - vector field corresponding to FieldPiWisConst
DESCRIPTION:
This class offers a vector or tensor field where each component is a "FieldPiWisConst" object. The documentation of this class is implicitly contained in class "FieldsFE", "FieldsWithPtValues" and "Fields".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
attaches a scalar field as component number "i" in the vector field. Reimplemented from Fields. |
|
|
See documentation of one of the overloaded functions. Reimplemented from FieldsWithPtValues. |
|
|
gives access to a scalar component in the vector field. Reimplemented from FieldsWithPtValues. |
|
|
See documentation of one of the overloaded functions. |
|
|
the version that takes a "NUMT" fills all the values in the fields with the supplied value, while the other version makes repeated calls to "FieldPiWisConst fill(FieldsFEatItgPt&,int". |
|
|
returns a "Field" base class pointer for component number "i" in the vector field. Used when reading/writing vector fields from/to SimRes files. This function will return a "NULL" pointer in some subclasses of "Fields" that are not represented as a vector of scalar fields. Reimplemented from Fields. |
|
|
enables access to the (common) underlying grid for the field components. NOTE: This function will return a "NULL" pointer in many subclasses of "Fields". It is, at present, only used for some special vector field classes. Reimplemented from Fields. |
|
|
returns the number of scalar fields that make up the vector field. Reimplemented from Fields. |
|
|
returns the total number of degrees of freedom in the vector field. For example, for a 3D velocity field, represented in terms of trilinear finite elements with X nodes, the "getNoValues" function should return "3*X". Reimplemented from Fields. |
|
|
Reimplemented from Fields. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
redimensions the number of scalar fields that make up the vector field. Reimplemented from Fields. |
|
|
|
|
|
|
|
|
|
|
|
Reimplemented from Fields. |
|
|
this function works mainly as the other "valuePt functions in the "Field" hierarchy, except that certain problems may occur if the point is on the boundary between two subdomains. Now we force an element by element search for the point and return the value of the field in that element. In case the point is on the boundary, the field value corresponding to the element that first gives a hit is returned. Previously, we tested if the point was a node and then always returned "DUMMY" and gave a warning. This is not a good solution because in higher order elements, internal nodes do not represent a problem, and the field may be multi-valued at general points in between the nodes along a boundary between two subdomains. Hence, the only satisfactory solution is thought to be the one which is implemented now. The routine now works in conjunction with f.ex. finite differences or nodal point integration in FEM, but the "effective" boundaries of the subdomains (in the numerical calculations) are in fact influenced by the search algorithm in case the point is on the boundary between two subdomains. This is a topic for further research. Reimplemented from Fields. |
|
|
|