fields. The library contains the data structure to describe meshes and
fields as C++ objects (MEDCoupling package). It provides a set of
functions to manage the persistency toward the med file format
-(MEDLoader package), and to process the data througt interpolation and
+(MEDLoader package), and to process the data through interpolation and
localization algorithms (INTERP_KERNEL and REMAPPER packages), for
example to perform field projections from a mesh to another.
:align: center
What we call MEDMEM library in this document is represented by the
-orange packages on this diagram. The white packages reprensent the old
-deprecated MEDMEM library. The blue packages represent the aditionnal
-components for field manipulation througth the user interface (TUI and
+orange packages on this diagram. The white packages represent the old
+deprecated MEDMEM library. The blue packages represent the additional
+components for field manipulation through the user interface (TUI and
GUI).
The MEDMEM library comes also with this set of atomic libraries for
the MEDCoupling classes describing the meshes and fields.
Note that the read functions required the parameter
-:tt:`dimrestriction`. This parameter discreminates the mesh dimensions you
+:tt:`dimrestriction`. This parameter discriminates the mesh dimensions you
are interested to relatively to the maximal dimension of cells
contained in the mesh (then its value could be 0, -1, -2 or -3
depending on the max dimension of the mesh). A value of
----------------------------------------
:objectives: Make the projection of a field from a source mesh to a
- target meshe. The source mesh and the target mesh are
+ target mesh. The source mesh and the target mesh are
two different mesh of the same geometry.
The input data of this use case are:
.. Example 01: Create a field from an image
.. ----------------------------------------
-
fields. The library contains the data structure to describe meshes and
fields as C++ objects (MEDCoupling package). It provides a set of
functions to manage the persistency toward the med file format
-(MEDLoader package), and to process the data througt interpolation and
+(MEDLoader package), and to process the data through interpolation and
localization algorithms (INTERP_KERNEL and REMAPPER packages), for
example to perform field projections from a mesh to another.
:align: center
What we call MEDMEM library in this document is represented by the
-orange packages on this diagram. The white packages reprensent the old
-deprecated MEDMEM library. The blue packages represent the aditionnal
-components for field manipulation througth the user interface (TUI and
+orange packages on this diagram. The white packages represent the old
+deprecated MEDMEM library. The blue packages represent the additional
+components for field manipulation through the user interface (TUI and
GUI).
The MEDMEM library comes also with this set of atomic libraries for
the MEDCoupling classes describing the meshes and fields.
Note that the read functions required the parameter
-:tt:`dimrestriction`. This parameter discreminates the mesh dimensions you
+:tt:`dimrestriction`. This parameter discriminates the mesh dimensions you
are interested to relatively to the maximal dimension of cells
contained in the mesh (then its value could be 0, -1, -2 or -3
depending on the max dimension of the mesh). A value of
----------------------------------------
:objectives: Make the projection of a field from a source mesh to a
- target meshe. The source mesh and the target mesh are
+ target mesh. The source mesh and the target mesh are
two different mesh of the same geometry.
The input data of this use case are:
.. Example 01: Create a field from an image
.. ----------------------------------------
-
if READ_PHYSICAL_DATA:
mesh = MEDLoader.ReadUMeshFromFile(filepath,meshName,meshDimRelToMax)
# Note that the read function required the parameter
- # meshDimRelToMax. This parameter discreminates the meshdim you
+ # meshDimRelToMax. This parameter discriminates the meshdim you
# are interested to relatively to the maximal dimension of cells
# contained in the mesh in file (then its value could be 0, -1, -2
# or -3 depending on the max dimension of the mesh. 0 means "no
for fieldName in fieldNames:
print(" %s"%fieldName)
-
+
# A field name could identify several MEDCoupling fields, that
# differ by their spatial discretization on the mesh (values on
# cells, values on nodes, ...). This spatial discretization is
# specified by the TypeOfField that is an integer value in this
# list:
- # 0 = ON_CELLS
- # 1 = ON_NODES
- # 2 = ON_GAUSS_PT
+ # 0 = ON_CELLS
+ # 1 = ON_NODES
+ # 2 = ON_GAUSS_PT
# 3 = ON_GAUSS_NE
#
# As a consequence, before loading values of a field, we have
itNumber = fieldIteration[0]
itOrder = fieldIteration[1]
print(" (%s,%s)"%(itNumber,itOrder))
-
+
if READ_PHYSICAL_DATA:
medCouplingField = MEDLoader.ReadField(typeOfDiscretization,
filepath,
rmedfilename = filepath
-# Load the meshe data
+# Load the mesh data
meshname = "Grid_80x80"
fieldname = "Pulse"
dimrestriction = 0 # no restriction
{
meshPtr->Register();
//1st call to getTinyInfo to get tiny array of key integers value
- //to corectly resize local copy of distant instance addressed by 'meshPtr'
+ //to correctly resize local copy of distant instance addressed by 'meshPtr'
//1st value of returned array is the type of instance. Thanks to
//CORBA and its type-check no use of this value is necessary.
SALOME_TYPES::ListOfDouble *tinyD;
