/*!
-\page ghs3dprl_hypo_page MG-Tetra-hpc (Parallel) Parameters hypothesis
+\page ghs3dprl_hypo_page MG-Tetra Parallel Parameters hypothesis
-\n MG-Tetra-hpc Parameters hypothesis works only with <b>MG-Tetra-hpc</b> code (formerly tepal)
-which is the parallel implementation of MeshGems-Tetra (formerly TetMesh-GHS3D) algorithm.
-This algorithm is a DISTENE commercial software, its use requires a licence.
+\n MG-Tetra Parameters hypothesis works only with <b>MG-Tetra</b>
+meshing algorithm which uses <b>MG-Tetra-hpc</b> code (formerly tepal)
+which is the parallel implementation of MG-Tetra (formerly TetMesh-GHS3D) algorithm.
+This algorithm is a DISTENE commercial software, its use requires a license.
\n
See http://www.distene.com and http://www.meshgems.com/volume-meshing-meshgems-tetra.html.
\n MG-Tetra-hpc (Tepal V3 in fact) gives the possibility to generate a partitioned
configuration with 64Go RAM to only try to make a partition of a mesh with
200 million tetrahedrons, no result guaranteed (in 2010).
\n
-\note The Plugin doesn't load in the Memory the supposedly large resulting meshes.
+\note The plug-in doesn't load in the memory the supposedly large resulting meshes.
The meshes are saved in MED files and can be imported in the user-defined location via menu File-Import-MED Files.
\n Pay attention, that Salome GUI needs 2Go RAM to load a MED
file with 5 million tetrahedrons.
</li>
<li>
<b>MED Name</b> - allows to define the path and the prefix of the
-resulting MED files ("DOMAIN" by default).
+resulting MED files ("DOMAIN" by default).
If the path is not defined, the environment variable $SALOME_TMP_DIR
is used. If $SALOME_TMP_DIR is not defined as well, the environment
variable $TMP is used.
in Nb_Part by the elementary algorithm implemented in Tepal.<br>
</li>
<li>
-<b>Keep Files</b> - if this box is checked, input files of Tepal
-(GHS3DPRL.points and GHS3DPRL.faces) are not deleted after use (...if the
+<b>Keep Files</b> - if this box is checked, input files of MG-Tetra-hpc
+(GHS3DPRL.points and GHS3DPRL.faces) are not deleted after use (if the
background mode was not used).
</li>
<li>
-<b>Tetra_hpc in Background</b> - if this box is checked, Tetra_hpc execution
+<b>Tetra_hpc in Background</b> - if this box is checked, MG-Tetra-hpc execution
and MED file generation are launched in background mode and the user
-can even exit Salome. Pay attention that in this case Tepal algorithm works
+can even exit Salome. Pay attention that in this case MG-Tetra-hpc algorithm works
independently of "killSalome.py", and sometimes on another host.
</li>
<li>
-<b>Merge subdomains</b> - if this box is checked, merge the subdomains
+<b>Merge subdomains</b> - if this box is checked, merge the sub-domains
into one mesh and write the output .mesh(b).
</li>
<li>
-<b>Tag subdomains</b> - if this box is checked, use the parallel subdomain
+<b>Tag subdomains</b> - if this box is checked, use the parallel sub-domain
index as tag into the merged output mesh or not (used in combination with the
-merge_subdomains option).
+<b>Merge subdomains</b> option).
</li>
<li>
-<b>Output interfaces</b> - if this box is checked, write the parallel subdomains interface
-triangles into the merged output mesh (used in combination with the merge_subdomains option).
+<b>Output interfaces</b> - if this box is checked, write the parallel
+sub-domains interface triangles into the merged output mesh (used in
+combination with the <b>Merge subdomains</b> option).
</li>
<li>
-<b>Discard subdomains</b> - if this box is checked, discard the parallel subdomains
+<b>Discard subdomains</b> - if this box is checked, discard the parallel sub-domains
(mesh, global numbering and interfaces).
</li>
<h1>Modifying MG-Tetra-hpc Advanced Parameters</h1><br>
-GHS3DPRL Plugin launches a standalone binary executable <b>tetrahpc2med</b>.<br>
-tetrahpc2med launches tetra_hpc, waits for the end of computation, and
-converts the resulting output tepal files into MED files.<br>
+MG-Tetra Parallel plug-in launches a standalone binary
+executable <b>tetrahpc2med</b>.<br>
+tetrahpc2med launches MG_Tetra-hpc, waits for the end of computation, and
+converts the resulting output files into MED files.<br>
Some advanced optional parameters are accessible as arguments.<br>
-If keep_files option is checked, it is possible to re-launch tetrahpc2med
-or tetra_hpc in the Terminal as a command with custom parameters.<br>
+If <b>Keep Files</b> option is checked, it is possible to re-launch
+\a tetrahpc2med or MG-Tetra-hpc in the Terminal as a command with
+custom parameters.<br>
<li>
<b>Advanced tetrahpc2med Parameters</b> - type <b>tetrahpc2med --help</b> in the Terminal. <p>
\n
</li>
-<h1>Saving user's preferred GHS3DPRL Advanced Parameters</h1><br>
-GHS3DPRL Plugin launches standalone binary executable tetrahpc2med.<br>
+<h1>Saving user's preferred MG-Tetra Parallel Advanced Parameters</h1><br>
+MG-Tetra Parallel plug-in launches standalone binary executable tetrahpc2med.<br>
You may rename file tetrahpc2med as tetrahpc2med.exe for example, and replace
tetrahpc2med by a shell script at your convenience to overriding parameters.
<br>... or else $PATH modification... .<br>
#we have renamed binary executable tepal as tepal64_v2.exe.
#typical command to launch tepal v1 :
#tepal -f /tmp/myname/GHS3DPRL -n 16 > /tmp/myname/tepal.log
-#this file is an exemple to transform this call for tepal v2.0,
+#this file is an example to transform this call for tepal v2.0,
# (beta version using .mesh input file)
#you have to adapt for your convenience.
#third problem is convert tepal v2 output files GHS3DPRL*.mesh
# to v1 input files GHS3DPRL*.faces an GHS3DPRL*.points.
-#you have to work on the same physical disk and same path input and ouput files : $SAME_DIR
+#you have to work on the same physical disk and same path input and output files : $SAME_DIR
#you have to work on different physical disk but same path and name for executable files
# (and shared libraries) : $DIFF_DIR
export LD_LIBRARY_PATH=$DIFF_DIR/tepal-2.0.0/bin/Linux_64:${LD_LIBRARY_PATH}
export PATH=$DIFF_DIR/tepal-2.0.0/bin/Linux_64:$PATH
-#small test betweeen friends
+#small test between friends
#rm hostnames.log
#mpirun -n $4 hostname >> hostnames.log
export SIMULOGD_LICENSE_FILE=29029@is142356
export LICENSE_FILE=/product/distene/dlim8.var.sh
-#mpirun with necessary set envenvironment
+#mpirun with necessary set environment
export TMP_ENV="-x PATH -x LD_LIBRARY_PATH -x DISTENE_LICENSE_FILE -x DLIM8VAR \
-x SIMULOGD_LICENSE_FILE -x LICENSE_FILE"
#mpirun $TMPENV -n $4 which tepal64_v2.exe >> hostnames.log
#convert output files tepalv1 format
/through_salome_path/mesh2facespoints.py $IN_FILES
-#copy ouputs files from $SAME_DIR to local current directory (something like /tmp/myname)
+#copy output files from $SAME_DIR to local current directory (something like /tmp/myname)
cp -f hostnames.log $IN_DIR
cp -f $IN_FILES* $IN_DIR
