Metafor

ULiege - Aerospace & Mechanical Engineering

User Tools

Site Tools

You are here: metafor.ltas.ulg.ac.be » doc » Documentation » Automatic Remeshing Process
Trace:
doc:user:remeshing:remeshing

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
doc:user:remeshing:remeshing [2016/06/13 17:02] – [Changing mesh density during the computation] jorisdoc:user:remeshing:remeshing [2016/06/13 17:19] – [File 2 : script] joris
Line 258: Line 258:
                          
         autoRemesh.setBalancing(True)         autoRemesh.setBalancing(True)
-            +     
 +        autoRemesh.makeAnim = False 
 +    
         autoRemesh.execute()         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.   * ''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. 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 346: Line 350:
 Two different remeshing criteria have been implemented yet, one based on a ''[[doc/user/results/courbes_res#valueextractor|ValueExtractor]]'', the other on time. 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     #Stop Criterion
Line 359: Line 363:
  
 But then, there is also a simple criterion based on time, if you want to remesh every few seconds or so. 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={}):     def getParameters(_p={}):
Line 415: Line 419:
   CopyRemesher(side, p['remeshing'].oldDomain, domain, density).execute()   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 ==== ==== Transfinite Meshers ====
Line 434: Line 436:
 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). 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 ==== ==== Changing the transfer method ====
Line 466: Line 468:
   cell.addOption(INTPT_NB, 5)   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 ==== ====  Changing the fields to transfer ====
doc/user/remeshing/remeshing.txt · Last modified: 2024/03/01 16:17 by boman
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki