Changes between Version 4 and Version 5 of ProcessingObjects

Timestamp:

02/28/12 10:42:27 (14 years ago)

Author:

Jonathan

Comment:

—

ProcessingObjects

@@ -10 +10 @@
 There are also two classes of processing objects - those that store values on a cell by cell basis within the AMR mesh and are accessible from the chombo file, and those that output scalars(TotalObject), vectors(HistogramObject), or fixed grid data(ProjectionObjects, PdfObjects) at each frame.
 
-== Those that store various diagnostics within the AMR Mesh are listed below and are utilized by:
- * {{{CALL StoreChildMasks()}}} - Stores child mask of each cell
- * {{{CALL StoreCoolingLength()}}} - Stores cooling length
- * {{{CALL StoreDivergence()}}} - Stores divergence
- * {{{CALL StoreErrFlags()}}} - Stores error flags
- * {{{CALL StoreMPI_IDs()}}} - Stores processor ID
- * {{{CALL StoreTreeAvailability()}}} - Stores what regions of the mesh are known by processor {{{MPI_TRACK=0}}}
+== Those that store various diagnostics within the AMR Mesh are listed below and are utilized by adding the appropriate code to your ProblemModuleInit() subroutine
+ * {{{CALL StoreChildMasks()}}} - Stores child mask of each cell.  You must also add {{{USE ChildMasks}}}
+ * {{{CALL StoreCoolingLength()}}} - Stores cooling length.  You must also add {{{USE CoolingLength}}}
+ * {{{CALL StoreDivergence()}}} - Stores divergence.  You must also add {{{USE Divergence}}} 
+ * {{{CALL StoreErrFlags()}}} - Stores error flags.  You must also add {{{USE ErrFlags}}}
+ * {{{CALL StoreMPI_IDs()}}} - Stores processor ID.  You must also add {{{USE MPI_IDs}}}
+ * {{{CALL StoreTreeAvailability()}}} - Stores what regions of the mesh are known by processor {{{MPI_TRACK=0}}} defined in module {{{TreeAvailability}}}.  You must also add {{{USE TreeAvailability}}}
 
 == Those that have there own form of IO ==