Changes between Version 6 and Version 7 of AstroBearAmr

Timestamp:

05/20/11 11:49:15 (14 years ago)

Author:

Brandon Shroyer

Comment:

—

AstroBearAmr

@@ -95 +95 @@
 == Round 2:  Refined Bookkeeping and Elliptic Solvers ==
 
-Now that we have constructed a simple AMR routine, we will add a few routines to improve MHD calculations and simplify AMR tree management.  We will also add sink particles and the elliptic solver step to the code, expanding the capabilities of our AMR routine.
+Now that we have constructed a simple AMR routine, we will add a few routines to improve MHD calculations and simplify AMR tree management.  We will also add sink particles and the elliptic solver step to the code, expanding the capabilities of our AMR algorithm.
 
 {{{
@@ -148 +148 @@
 
 [[BR]]
-== Dealing with !MaxLevel ==
-Up to this point we've assumed we are on an intermediate level of the AMR tree. What is different if we are on the highest level !MaxLevel?
+== Round 3:  The Maximum Level of Refinement ==
+Up to this point we've assumed we are on an intermediate level of the AMR tree, with a level above us and a level below us. What is different if we are on the highest level {{{MaxLevel}}}?
 
 {{{
@@ -194 +194 @@
 END SUBROUTINE AMR
 }}}
-We've basically wrapped the following routines that deal with child nodes inside of conditionals that prevent their execution on the !MaxLevel
- * !SetErrFlags - We won't be refining any regions so no need to set error flags
- * !AgeNodesChildren - We have no children to age
- * !BackupNodes - There are no level !MaxLevel+1 nodes to backup
- * !CreateChildrens - We don't create level MaxLevel+1 grids
- * !InheritOverlaps - Since level !MaxLevel nodes have no children there is no inheritting that needs to be done
- * AMR - We are on the !MaxLevel 
- * !ApplyChildrenData - No child data to apply
- * !UpdateChildMask - No children to modify the childmask
-
-
-
-= Dealing with Lower Levels =
+
+Nodes on {{{MaxLevel}}} will not have any children, and thus {{{MaxLevel}}} is the stopping case for our recursive AMR algorithm.  {{{AMR()}}} should therefore not call itself on {{{MaxLevel + 1}}}.  Similarly, none of the functions that only apply to creating, initializing, or responding to child nodes should be on {{{MaxLevel}}}.  This means no error flags, no child grid creation, and no restriction operations.
+
+In the code block above, we've applied the conditional
+{{{
+If (n < MaxLevel)
+}}}
+to the following routines that deal with child nodes.  This prevents these routines from being executed on the highest allowable level of refinement:
+ * {{{SetErrFlags(n)}}}
+ * {{{AgeNodesChildren(n)}}}
+ * {{{BackupNodes(n)}}}
+ * {{{CreateChildrens(n)}}}
+ * {{{Inherit*Overlaps(n)}}} (all the different permutations of the {{{InheritOverlaps}}} functionality.
+ * {{{AMR(n)}}}
+ * {{{ApplyChildrenData(n)}}}
+ * {{{UpdateChildMask(n)}}}
+
+[[BR]]
+= Round 4: Behavior on the Lower Levels =
 
 {{{