Changes between Version 6 and Version 7 of GlobalDataExplained

Timestamp:

06/03/11 16:53:49 (14 years ago)

Author:

Brandon Shroyer

Comment:

—

GlobalDataExplained

@@ -59 +59 @@
 == IOData ==
 
+The {{{IOData}}} namelist contains control flags that affect the way input and output are processed/produced.
+
+ * '''{{{iDataFileType}}}''':  Indicates the kind of output file AstroBEAR should produce.  We currently only support Chombo-formatted [http://www.hdfgroup.org HDF5] files, so this flag should be left at {{{0}}}.
+
 == !DomainData ==
 
+Contains information about the various user-defined domains in AstroBEAR.  AstroBEAR stores domain info in {{{Domain}}} objects which it reads in from this namelist.  For most problems, only one domain is necessary, so there will be only one {{{Domain}}} object.
+
+ * '''{{{Domain%mGlobal}}}''':  The global cell indices for a domain.  For a single-domain problem, {{{Domain%mGlobal}}} should be {{{1, 1, 1, GmX(1), GmX(2), GmX(3)}}}.  A two-domain, 64 x 64 x 64 problem might have mGlobals of {{{[1, 1, 1, 64, 32, 64}}} and {{{1, 33, 1, 64, 64, 64}}}.
+
+ For two-dimensional problems, {{{Domain%mGlobal(3)}}} and {{{Domain%mGlobal(6)}}} should always be set to {{{1}}}.
+
+ * '''{{{Domain%mthbc}}}''':  The boundary condition tags for a domain.  For a single-domain problem, {{{Domain%mthbc}}} will be the same as {{{Gmthbc}}} (see [GlobalDataExplained#GlobalData GlobalData], above).  For a multi-domain problem, however, the there will be some domains who share a common boundary.  For these domains, you use the [InternalBoundaryCondition internal] boundary condition code of {{{999}}}.
+
+ Again, for two dimensional problems, {{{Domain%mthbc(3)}}} and {{{Domain%mthbc(6)}}} should be set to {{{1}}}.
+
+[[BR]]
 == !PoissonData ==
+
+This namelist will only be present in elliptic problems.  {{{PoissonData}}} contains variables that control the behavior both of the elliptic solver and the underlying