From: eap Date: Mon, 15 Oct 2018 12:19:20 +0000 (+0300) Subject: Typo and whitespace fixes by Kunda X-Git-Tag: V9_2_0a2~5 X-Git-Url: http://git.salome-platform.org/gitweb/?p=modules%2Fmed.git;a=commitdiff_plain;h=8cf67f405062312f2544099554edd6991b39fd05;hp=5efa8da4c0377f66765a10522f15f2368c54779b Typo and whitespace fixes by Kunda http://www.salome-platform.org/forum/forum_9/454200149#834683007 --- diff --git a/doc/dev/sphinx/fr/medcalc-userguide-api.rst b/doc/dev/sphinx/fr/medcalc-userguide-api.rst index 6997bb396..8aaa7b614 100644 --- a/doc/dev/sphinx/fr/medcalc-userguide-api.rst +++ b/doc/dev/sphinx/fr/medcalc-userguide-api.rst @@ -30,7 +30,7 @@ programs as in python scripts for data processing on meshes and 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. @@ -70,9 +70,9 @@ library: :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 @@ -267,7 +267,7 @@ The variables :tt:`mesh` and :tt:`field` in this code example are instances of 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 @@ -437,7 +437,7 @@ Example 08: Make a projection of a field ---------------------------------------- :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: @@ -525,4 +525,3 @@ library. .. Example 01: Create a field from an image .. ---------------------------------------- - diff --git a/doc/dev/sphinx/medcalc-userguide-api.rst b/doc/dev/sphinx/medcalc-userguide-api.rst index a15fff8d3..42c345ade 100644 --- a/doc/dev/sphinx/medcalc-userguide-api.rst +++ b/doc/dev/sphinx/medcalc-userguide-api.rst @@ -30,7 +30,7 @@ programs as in python scripts for data processing on meshes and 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. @@ -70,9 +70,9 @@ library: :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 @@ -267,7 +267,7 @@ The variables :tt:`mesh` and :tt:`field` in this code example are instances of 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 @@ -437,7 +437,7 @@ Example 08: Make a projection of a field ---------------------------------------- :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: @@ -525,4 +525,3 @@ library. .. Example 01: Create a field from an image .. ---------------------------------------- - diff --git a/doc/tut/medloader/explore.py b/doc/tut/medloader/explore.py index 4ed13e21a..1085e5b0f 100644 --- a/doc/tut/medloader/explore.py +++ b/doc/tut/medloader/explore.py @@ -42,7 +42,7 @@ for meshName in meshNames: 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 @@ -54,15 +54,15 @@ for meshName in meshNames: 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 @@ -86,7 +86,7 @@ for meshName in meshNames: itNumber = fieldIteration[0] itOrder = fieldIteration[1] print(" (%s,%s)"%(itNumber,itOrder)) - + if READ_PHYSICAL_DATA: medCouplingField = MEDLoader.ReadField(typeOfDiscretization, filepath, diff --git a/doc/tut/medloader/testamel.py b/doc/tut/medloader/testamel.py index 686b9eabb..1021cbc97 100644 --- a/doc/tut/medloader/testamel.py +++ b/doc/tut/medloader/testamel.py @@ -33,7 +33,7 @@ filepath = os.path.join(os.path.abspath(os.path.dirname(__file__)),filename) rmedfilename = filepath -# Load the meshe data +# Load the mesh data meshname = "Grid_80x80" fieldname = "Pulse" dimrestriction = 0 # no restriction diff --git a/src/MEDCouplingCorba/Client/MEDCouplingMeshClient.cxx b/src/MEDCouplingCorba/Client/MEDCouplingMeshClient.cxx index dee9e8ee6..58436cc3e 100644 --- a/src/MEDCouplingCorba/Client/MEDCouplingMeshClient.cxx +++ b/src/MEDCouplingCorba/Client/MEDCouplingMeshClient.cxx @@ -95,7 +95,7 @@ void MEDCouplingMeshClient::fillMeshFromCorbaData(MEDCouplingMesh *meshCpp, SALO { 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;