doc:user:remeshing:remeshing
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
doc:user:remeshing:remeshing [2016/06/13 17:03] – [Using other remeshing criteria] joris | doc:user:remeshing:remeshing [2016/06/13 17:29] – [Dynamic balancing] joris | ||
---|---|---|---|
Line 258: | Line 258: | ||
| | ||
autoRemesh.setBalancing(True) | autoRemesh.setBalancing(True) | ||
- | | + | |
+ | autoRemesh.makeAnim = False | ||
+ | | ||
autoRemesh.execute() | autoRemesh.execute() | ||
| | ||
Line 272: | Line 274: | ||
* '' | * '' | ||
| | ||
- | * Finally, the line '' | + | * The line '' |
+ | |||
+ | * Finally, the line '' | ||
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 415: | Line 419: | ||
CopyRemesher(side, | CopyRemesher(side, | ||
- | 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, |
- | + | ||
- | < | + | |
==== Transfinite Meshers ==== | ==== Transfinite Meshers ==== | ||
Line 434: | Line 436: | ||
By default, the transfer of data is done using Philippe' | By default, the transfer of data is done using Philippe' | ||
- | For the advanced | + | For the __advanced__ |
==== Changing the transfer method ==== | ==== Changing the transfer method ==== | ||
Line 466: | Line 468: | ||
cell.addOption(INTPT_NB, | cell.addOption(INTPT_NB, | ||
- | To understand all these options, please look at [[doc: | + | To understand all these options, please look at [[doc: |
==== Changing the fields to transfer ==== | ==== Changing the fields to transfer ==== | ||
Line 545: | Line 547: | ||
Since we conserve the inertial forces and correct the internal ones, this post-remeshing algorithm works quite well for quasi-static and low speed dynamic computations. For high speed dynamic computations, | Since we conserve the inertial forces and correct the internal ones, this post-remeshing algorithm works quite well for quasi-static and low speed dynamic computations. For high speed dynamic computations, | ||
+ | |||
+ | ==== Options ==== | ||
+ | |||
+ | The complete '' | ||
+ | |||
+ | setBalancing(executeBalancing, | ||
+ | | ||
+ | The first argument has already been described and indicates whether balancing should be done or not. | ||
+ | |||
+ | For the advanced user, a few options can be played with by changing the three of arguments. | ||
+ | |||
+ | First of all, it is possible to deactivate the '' | ||
+ | |||
+ | Second, the number of iterations for each step of the balancing can be changed. By default, seven iterations are tried before increasing the fraction of the unbalanced forces and starting again. | ||
+ | |||
+ | Finally, the tolerance can also be changed. The parameter $\alpha$, used to ponder the unbalanced forces, starts at 1 and is progressively divided by 2 when a step fails. Once $\alpha$ becomes smaller than the tolerance, the algo stops itself, returns an error, and the temporal interation does not restart. The default value of 0.001 can be changed if needed. |
doc/user/remeshing/remeshing.txt · Last modified: 2024/03/01 16:17 by boman