ForkMaster/smesh
1
0
Fork 0
mirror of https://git.salome-platform.org/gitpub/modules/smesh.git synced 2025-01-18 15:00:37 +05:00
Code Issues Packages Projects Releases Wiki Activity

Fix for the bug IPAL22851: Sub-shapes spelling

Browse Source
This commit is contained in:
ana 2012-01-13 14:37:34 +00:00
parent 53a497b9c8
commit 61b2416dce
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/salome/gui/SMESH/input/constructing_meshes.doc
View File

@ -132,7 +132,7 @@ failure is provided.
\image html meshcomputationfail.png \image html meshcomputationfail.png
After you select the error, <b>Show Subshape</b> button allows After you select the error, <b>Show Sub-shape</b> button allows
visualizing the geometrical entity that causes it. visualizing the geometrical entity that causes it.
\image html failed_computation.png "Example of the invalid input mesh" \image html failed_computation.png "Example of the invalid input mesh"
@ -144,7 +144,7 @@ computation reporting. There are the following possibilities: always
show information box, only if an error occurs or never. show information box, only if an error occurs or never.
By default, the information box is always shown after mesh computation operation. By default, the information box is always shown after mesh computation operation.
<b>Publish Subshape</b> button publishes the subshape, whose meshing <b>Publish Sub-shape</b> button publishes the sub-shape, whose meshing
failed, in GEOM component as a child of the mesh geometry, which failed, in GEOM component as a child of the mesh geometry, which
allows analyzing the problem geometry and creating a submesh on it in allows analyzing the problem geometry and creating a submesh on it in
order to locally tune hypotheses. order to locally tune hypotheses.
@ -171,7 +171,7 @@ evaluation will be displayed in the following information box:
<li> <li>
If the mesh contains concurrent submeshes, it is possible to change If the mesh contains concurrent submeshes, it is possible to change
the priority of their computation, i.e. to change the priority of the priority of their computation, i.e. to change the priority of
applying algorithms to the shared subshapes of the Mesh shape.</li> applying algorithms to the shared sub-shapes of the Mesh shape.</li>
<em>To change submesh priority:</em> <em>To change submesh priority:</em>
@ -205,7 +205,7 @@ is:
<li><i>2D</i> Netgen 1D-2D with Hypothesis <b>Netgen Simple parameters</b> <li><i>2D</i> Netgen 1D-2D with Hypothesis <b>Netgen Simple parameters</b>
(Number of Segments = 12)</li> (Number of Segments = 12)</li>
</ul> </ul>
The submeshes become concurrent if they share subshapes that can be meshed The submeshes become concurrent if they share sub-shapes that can be meshed
with different algorithms (or different hypothesises). with different algorithms (or different hypothesises).
In the example, we have three submeshes with concurrent algorithms, In the example, we have three submeshes with concurrent algorithms,
because they have different hypotheses. because they have different hypotheses.

2
doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc
View File

@ -14,7 +14,7 @@ import BLSURFPlugin
box = geompy.MakeBoxDXDYDZ(200., 200., 200.) box = geompy.MakeBoxDXDYDZ(200., 200., 200.)
geompy.addToStudy(box, "box") geompy.addToStudy(box, "box")
# get subshapes # get sub-shapes
Face_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["FACE"])[0] Face_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["FACE"])[0]
Edge_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["EDGE"])[0] Edge_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["EDGE"])[0]
Vertex_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["VERTEX"])[0] Vertex_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["VERTEX"])[0]