Differences

This shows you the differences between two versions of the page.

--- doc:user:remeshing:remeshing [2016/06/13 17:02] – [Changing mesh density during the computation] joris
+++ doc:user:remeshing:remeshing [2016/06/13 17:13] – [File 2 : script] joris
@@ Line 258: / Line 258: @@
         autoRemesh.setBalancing(True)
+        autoRemesh.makeAnim = False
         autoRemesh.execute()
@@ Line 346: / Line 348: @@
 Two different remeshing criteria have been implemented yet, one based on a ''[[doc/user/results/courbes_res#valueextractor|ValueExtractor]]'', the other on time.
-Previously, the one relying on a valueExtractor was used in a very simple way : on one side of the part, with the field ''IF_MESH_QUALITY''. But is can be used with any ''[[doc/user/results/courbes_res#valueextractor|ValueExtractor]]'' you want, and on any geometrical entity. For example, let us assume that we want a criterion based on the aspect ratio, which is to be evaluated on two different sides. Then we simply define a skin with these two sides and we have the following :
+Previously, the one relying on a ''valueExtractor'' was used in a very simple way : on one side of the part, with the field ''IF_MESH_QUALITY''. But is can be used with any ''[[doc/user/results/courbes_res#valueextractor|ValueExtractor]]'' you want, and on any geometrical entity. For example, let us assume that we want a criterion based on the aspect ratio, which is to be evaluated on two different sides. Then we simply define a skin with these two sides and we have the following :
     #Stop Criterion
@@ Line 359: / Line 361: @@
 But then, there is also a simple criterion based on time, if you want to remesh every few seconds or so.
-In this case, you must first define a vector containing all the times at which you want to remesh (''p[stopTime]''), then use the key ''p[integrationNumber]'' to set the right remeshing time depending on the integration. See below for the example :
+In this case, you must first define a vector containing all the times at which you want to remesh (''p[stopTime]''), then use the key ''p[integrationNumber]'' to set the right remeshing time depending on the integration. See below, or see ''apps.remeshing2.fullAuto.cont2cRemeshing'', for the example :
     def getParameters(_p={}):
@@ Line 415: / Line 417: @@
   CopyRemesher(side, p['remeshing'].oldDomain, domain, density).execute()
-Therefore, if you have a complex domain, just divide it into the appropriate sides and copy/remesh as you see fit.
+Therefore, if you have a complex domain, just divide it into the appropriate sides and copy/remesh as you see fit. However, when you want to remesh one side, copy another side, and that the two sides have a common edge, then you must first use CopyRemesher, then Gen4remesher, in order ensure that the nodes of the edges are also copied and not regenerated !
-<note> When you want to remesh one side, copy another side, and that the two sides have a common edge, then you must first use CopyRemesher, then Gen4remesher, in order ensure that the nodes of the edges are also copied and not regenerated ! </note>
 ==== Transfinite Meshers ====
@@ Line 434: / Line 434: @@
 By default, the transfer of data is done using Philippe's complex "FVTM" routine with all its default parameters (see [[doc:user:meshtransfer:datatransferbetweenmeshes]], in French).
-For the advanced user, changing these parameters is possible (in the ''main()'' function of the [[#File 2 : script|script]])
+For the __advanced__ user, changing these parameters is possible (in the ''main()'' function of the [[#File 2 : script|script]])
 ==== Changing the transfer method ====
@@ Line 466: / Line 466: @@
   cell.addOption(INTPT_NB, 5)
-To understand all these options, please look at [[doc:user:meshtransfer:datatransferbetweenmeshes|Philippe's doc]]
+To understand all these options, please look at [[doc:user:meshtransfer:datatransferbetweenmeshes|Philippe's doc]].
 ====  Changing the fields to transfer ====