Changes between Version 2 and Version 3 of AstroBearAmr

Timestamp:

05/18/11 16:00:47 (14 years ago)

Author:

Brandon Shroyer

Comment:

—

AstroBearAmr

@@ -64 +64 @@
  * '''{{{CreateChildrens(n)}}}'''-- A favorite of hillbillies everywhere, this routine creates child nodes on level {{{n+1}}} using the refinement flags set on level {{{n}}}.
  * '''{{{InheritOldNodeOverlapsChildren(n)}}}''' -- Nested grids mean that spatial relationships (overlaps and neighbors) are inherited from parent grids.  This routine passes information about the previous generation of {{{n+1}}} grids to the new grids created by {{{CreateChildrens(n)}}}.  This routine is ''only'' executed on step 1 of the {{{AMR()}}} execution loop.
- * '''{{{InheritNewNodeOverlapsChildren(n)}}}''' - This inherits the relationships going the other way.  The children of previous level n grids will need to send their data to the children of new level n grids.
- * !InheritNeighborsChildren - Neighbors of children will be children of neighbors
+ * '''{{{InheritNewNodeOverlapsChildren(n)}}}''' -- The children of previous level {{{n}}} grids will also need to send their data to the children of new level {{{n}}} grids.
+ * '''{{{InheritNeighborsChildren(n)}}}''' -- The children of neighboring grids on level {{{n}}} will very likely be neighbors.  This routine passes neighbor information from level {{{n}}} to level {{{n+1}}}.
  * !AdvanceGrids - Performs hyperbolic advance of data structures
  * AMR(n+1) - Launches AMR routine on the child level
@@ -71 +71 @@
  * !SyncFluxes - To enforce mass conservation and DivB constraint - common fluxes used at grid boundaries need to be synchronized.
  * !AccumulateFluxes - We need to accumulate the used fluxes to send back to our parent grids.
+
 * Step 2
  * !UpdateOverlaps - On the second step we don't need to receive overlap data from the previous generation of grids, however we do need to 'ghost' data with our current overlap grids or neighbors.  So we think of our neighbors as our current overlaps. (Note we use the same nodelist but point to it twice with node%neighbors and node%overlaps - this is the reason we have to just !NullifyNeighbors later)