Changes between Version 14 and Version 15 of ProcessingObjects

Timestamp:

12/13/18 15:59:25 (6 years ago)

Author:

Jonathan

Comment:

—

ProcessingObjects

@@ -3 +3 @@
 
 = Processing Objects =
-There are several processing objects that can be used to ana1lyze the results of simulations.  Each processing object needs to be created inside of the !ProblemModuleInit() routine. 
+There are several processing objects that can be used to ana1lyze the results of simulations - or append calculated quantities to your chombo file.  Each processing object needs to be created inside of the !ProblemModuleInit() routine. 
 
  * Processing will be done during runtime by default
@@ -10 +10 @@
  * Postprocessing will begin at the !RestartFrame
 
+
 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, SpectraObject), or fixed grid data(ProjectionObjects, PdfObjects) at each frame.  Additionally many objects support ShapeObjects that define the region of data to included in the total, histogram, projection, pdf, spectra, etc...
 
-== 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 store various diagnostics within the AMR Mesh are listed below and are utilized by adding the appropriate code to your !ProblemModuleInit() subroutine
+{{{
+USE ProcessingDeclarations
+CALL AddDiagnosticVar(iField, [name])}}}
+}}}
+ * This will add the desired field to the chombo file. 
+ * If you want to provide a custom name you can pass a second argument - otherwise it will be named using the default name for the field
+ * If you add this prior to PostProcessing - you will need to set lReOutput in global_declarations.f90 =.true.
 
 == Those that have there own form of IO ==