- The \b dimension \b of \b a \b mesh is characterized by two parameters: the size of the space wherein the mesh is immersed, and the (maximum) size of the mesh cells.
Examples: 3D surface mesh (3D space, 2D cells), 3D mesh (3D space, 3D cells), curved 2D mesh (2D space, 1D cells)...
-- \b Field: physical quantity whose value varies in space and time. Represented by a result vector V obtained from one or more tables of values A, at any point of space covered by a mesh and in time defined by its temporal resolution. The size of V is called the number of \b components (equal to the number of components of A).
+- \b Field: physical quantity whose value varies in space and time. Represented by a result vector V obtained from one or more tables of values A, at any point of space covered by a mesh and in time defined by its temporal resolution. The size of V is called the number of \b components (equal to the number of components of A).
A <b>P1 field</b> is a field where values are stored at node level, a <b>P0 field</b> is a field where values are stored
-at cell level.
+at cell level.
- \b Intensive \b field: represents intensive physical data (i.e. which do not depend on the amount of material).
Examples: density, power density, temperature, pressure.
- \b Extensive \b field: represents extensive physical data (i.e. proportional to the size of the physical system represented).
- \b Conservativity: preservation of conservation laws governing physical quantities during their discretization or their interpolation.
- \b Projection: modification (by interpolation) of the entity on which a field is defined. The projection is called \b conservative if the interpolation uses intersection detection. The projection is said \b not \b conservative if the interpolation localizes a cloud of points in a mesh.
- The \b Gauss \b integration \b points are the geometrical points where the numerical integration of a given quantity is performed. Precise location of these nodes and a sufficient number (related to the approximation order of the integration term) allow for an exact integration in the case of polynomial functions integration.
-- \b Kriging: a linear estimation method guaranteeing minimum variance. The estimate at a given point P is obtained locally from the point values on a neighbourhood of P.
+- \b Kriging: a linear estimation method guaranteeing minimum variance. The estimate at a given point P is obtained locally from the point values on a neighborhood of P.
- \b Code \b coupling: run of two numerical codes (or two instances of the same code) in such a way that information
-is passed from one instance to the other.
+is passed from one instance to the other.
*/
-# \ref f-p0p1
-# \ref f-number
-# \ref f-struct-ordering
-
+
\ref faq-python
-# \ref f-hellow
-# \ref f-pyimport
Take a look at \ref library
\subsubsection f-visu How can I visualize a mesh and/or a field?
-Use the PARAVIS module of SALOME to visualize your MED file. The following dedicated filters have been
+Use the PARAVIS module of SALOME to visualize your MED file. The following dedicated filters have been
written specifically for MED files: Extract group, Extract cell types, ELNO Mesh, ELNO Points, ELNO Surface.
\subsubsection f-p0p1 What does a P0- (or P1-) field mean?
When converting a structured mesh to unstructured one, or when storing a field onto a structured
mesh, the numbering convention detailed in \ref MEDCoupling::MEDCouplingStructuredMesh::buildUnstructured() is used.
-\subsection faq-python MEDCoupling scripts in Python
+\subsection faq-python MEDCoupling scripts in Python
\subsubsection f-hellow "Can you show me a simple example to get me started"
TODO
\subsubsection f-pyimport "When trying to execute my Python script I have 'ImportError: No module named MEDCoupling'"
-Check that the environment variables PYTHONPATH and LD_LIBRARY_PATH (PATH under Windows) are correctly set.
+Check that the environment variables PYTHONPATH and LD_LIBRARY_PATH (PATH under Windows) are correctly set.
If you have a full SALOME installation, use the 'shell' command that will automatically set up everything as it
should be:
\code{.sh}
\subsubsection f-coher "How to control the validity of my mesh"
Use the methods \ref MEDCoupling::MEDCouplingUMesh::checkConsistencyLight() "MEDCouplingUMesh::checkConsistencyLight()" or
-\ref MEDCoupling::MEDCouplingUMesh::checkConsistency() "MEDCouplingUMesh::checkConsistency()"
+\ref MEDCoupling::MEDCouplingUMesh::checkConsistency() "MEDCouplingUMesh::checkConsistency()"
\subsubsection f-groups "How can I read/write groups on a mesh"
Take a look at \ref AdvMEDLoaderAPIMeshReading and \ref AdvMEDLoaderAPIMeshWriting.
\subsection faq-interp Projection, interpolation, remapping
\subsubsection f-proj How to project a field from one mesh to the other
-This the job of the interpolation algorithms in the MED library. For starters, take a look at the
-\ref interpolation "general introduction on interpolation". Also
+This the job of the interpolation algorithms in the MED library. For starters, take a look at the
+\ref interpolation "general introduction on interpolation". Also
\ref cpp_mcfield_remapper_highlevel "this simple example" gives a good first illustration.
-Finally, if you are intereseted in parallel projection (C++ only!), you should take a
-look at the \ref para-dec "DEC".
+Finally, if you are intersected in parallel projection (C++ only!), you should take a
+look at the \ref para-dec "DEC".
\subsubsection f-proj-formula Which formula are used in the field projection algorithms
The documentation for non \ref glossary "P0 field" (i.e. non \ref glossary "cell-based fields") is still an
Re-compile in debug mode (with \c CMAKE_BUILD_TYPE=Debug), and use either valgrind or gdb
to spot the place where the segfault happens.
The most common source of mistake is some memory mis-allocation and/or deallocation.
-With this respect using the auto pointer class
+With this respect using the auto pointer class
\ref MEDCoupling::MCAuto "MCAuto"
-can be of great help.
-
+can be of great help.
+
\n
\n
\n
