Differences

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

--- doc:user:remeshing:remeshing [2016/06/13 17:11] – [CopyRemesher] joris
+++ doc:user:remeshing:remeshing [2016/06/13 17:19] – [File 2 : script] joris
@@ Line 258: / Line 258: @@
         autoRemesh.setBalancing(True)
+        autoRemesh.makeAnim = False
         autoRemesh.execute()
@@ Line 272: / Line 274: @@
   * ''setInteractionToPostStep'' gives to FENRIR the user number of the interaction on which post-remeshing operations should be executed (typically, any contact interaction), here number 1.
-  * Finally, the line ''autoRemesh.setBalancing(True)'' is the magical ingredient that makes everything taste better... I will talk more about this in a [[#Balancing|following section]].
+  * The line ''autoRemesh.setBalancing(True)'' is the magical ingredient that makes everything taste better... I will talk more about this in a [[#Balancing|following section]].
+  * Finally, the line ''autoRemesh.makeAnim = False'' indicates that we have no wish to make a save a picture every time that a fac is saved (to make an anim later on). If set to ''True'', then after each time integration, all facs will be loaded and a screenshot will be saved as a .bmp in the folder Anim, located in the workspace, just as is traditionally done when clicking on the button ''makeAnimation'' in Metafor GUI.
 Now that you have altered your test case to include remeshing, and that you have defined this little script, all that remains is to launch Metafor and execute your script (execute, not load/meta). Everything should work out perfectly.
@@ Line 464: / Line 468: @@
   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 ====