[cig-commits] r16528 - doc/snac

echoi at geodynamics.org echoi at geodynamics.org
Mon Apr 12 10:00:27 PDT 2010


Author: echoi
Date: 2010-04-12 10:00:27 -0700 (Mon, 12 Apr 2010)
New Revision: 16528

Modified:
   doc/snac/snac.lyx
Log:

Changed the paragraph on the issues with remesher into an itemized list.
	- Also, added a bullet for phase field.



Modified: doc/snac/snac.lyx
===================================================================
--- doc/snac/snac.lyx	2010-04-12 16:36:02 UTC (rev 16527)
+++ doc/snac/snac.lyx	2010-04-12 17:00:27 UTC (rev 16528)
@@ -1,4 +1,4 @@
-#LyX 1.6.4.1 created this file. For more info see http://www.lyx.org/
+#LyX 1.6.0 created this file. For more info see http://www.lyx.org/
 \lyxformat 345
 \begin_document
 \begin_header
@@ -2228,11 +2228,32 @@
 
 \begin_layout Standard
 The current remeshing algorithm, however, has some limitations.
- Domain decomposition, the parallelism implemented in SNAC, often makes
- it difficult to map variables between meshes when a parallel boundary (virtual
+ 
+\end_layout
+
+\begin_layout Itemize
+Phase field is not accurately remapped.
+ Phase field is not a physical variable but a set of integers registered
+ at each tetrahedron to represent the element's material type.
+ Although starting from integer values, a phase field for more than one
+ material types ends up including some real numbers after remeshing: due
+ to numerical diffusion during the recovery process.
+ Fractional material ID is not defined both physically and numerically in
+ the current version of SNAC.
+ Although rounding-off is forced for the continuation of calculation, the
+ mass of each phase is not guaranteed to be conserved.
+\end_layout
+
+\begin_layout Itemize
+Domain decomposition, the parallelism implemented in SNAC, often makes it
+ difficult to map variables between meshes when a parallel boundary (virtual
  boundary between subdomains assigned to more than one processor) of the
  old mesh has moved too far away from the corresponding one of the new mesh.
- Also, this remeshing works best in the case of lateral extension because
+ 
+\end_layout
+
+\begin_layout Itemize
+Also, this remeshing works best in the case of lateral extension because
  the nodes are moved back to their original positions.
  If a mesh has shrunk laterally and then remeshing moves all the nodes back
  to their original horizontal positions, it is impossible to remap variables
@@ -2243,8 +2264,12 @@
 assume
 \emph default
  states and properties of material for the unmappable regions.
- Finally, note that Fig.
  
+\end_layout
+
+\begin_layout Itemize
+Finally, note that Fig.
+ 
 \begin_inset CommandInset ref
 LatexCommand ref
 reference "fig:Remeshing.-Lagrangian-mesh"



More information about the CIG-COMMITS mailing list