feat(dfns): render blocks and components

autotest/dfns/__snapshots__/v2.0.0.dev0/gwe-adv.json

@@ -10,7 +10,7 @@
       "reader": "urword",
       "optional": true,
       "longname": "advective scheme",
-      "description": "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme.",
+      "description": "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme.",
       "valid": "central upstream tvd"
     },
     "ats_percel": {

autotest/dfns/__snapshots__/v2.0.0.dev0/gwe-adv.toml

@@ -9,7 +9,7 @@ type = "string"
 reader = "urword"
 optional = true
 longname = "advective scheme"
-description = "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme."
+description = "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme."
 valid = "central upstream tvd"
 
 [options.ats_percel]

autotest/dfns/__snapshots__/v2.0.0.dev0/gwe-adv.yaml

@@ -9,8 +9,8 @@ options:
     reader: urword
     optional: true
     longname: advective scheme
-    description: scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified,
-      upstream weighting is the default weighting scheme.
+    description: scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If
+      not specified, upstream weighting is the default weighting scheme.
     valid: central upstream tvd
   ats_percel:
     block: options

autotest/dfns/__snapshots__/v2.0.0.dev0/prt-oc.json

@@ -305,6 +305,14 @@
       "longname": "print particle tracking events",
       "description": "print a verbose particle tracking event trace to standard output",
       "mf6internal": "dev_dump_evtrace"
+    },
+    "scratch_buffer": {
+      "block": "options",
+      "type": "keyword",
+      "reader": "urword",
+      "optional": true,
+      "longname": "buffer track events in scratch file instead of memory",
+      "description": "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory."
     }
   },
   "dimensions": {

autotest/dfns/__snapshots__/v2.0.0.dev0/prt-oc.toml

@@ -293,6 +293,14 @@ longname = "print particle tracking events"
 description = "print a verbose particle tracking event trace to standard output"
 mf6internal = "dev_dump_evtrace"
 
+[options.scratch_buffer]
+block = "options"
+type = "keyword"
+reader = "urword"
+optional = true
+longname = "buffer track events in scratch file instead of memory"
+description = "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory."
+
 [dimensions.ntracktimes]
 block = "dimensions"
 type = "integer"

autotest/dfns/__snapshots__/v2.0.0.dev0/prt-oc.yaml

@@ -281,6 +281,19 @@ options:
     longname: print particle tracking events
     description: print a verbose particle tracking event trace to standard output
     mf6internal: dev_dump_evtrace
+  scratch_buffer:
+    block: options
+    type: keyword
+    reader: urword
+    optional: true
+    longname: buffer track events in scratch file instead of memory
+    description: keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer.
+      Particle tracking results calculated during a time step are buffered, and output is deferred, until
+      successful completion of the time step. By default, results are buffered in memory. However, for
+      simulations in which a very large number of track events is generated during a time step, memory
+      limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results
+      in a scratch file until successful completion of the time step. Buffering in a scratch file is typically
+      slower than buffering in memory.
 dimensions:
   ntracktimes:
     block: dimensions

autotest/dfns/__snapshots__/v2.0.0.dev1/gwe-adv.json

@@ -8,7 +8,7 @@
     "options": {
       "scheme": {
         "block": "options",
-        "description": "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme.",
+        "description": "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme.",
         "valid": "central upstream tvd",
         "reader": "urword",
         "optional": true,

autotest/dfns/__snapshots__/v2.0.0.dev1/gwe-adv.toml

@@ -6,7 +6,7 @@ ftype = "ADV"
 
 [blocks.options.scheme]
 block = "options"
-description = "scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not specified, upstream weighting is the default weighting scheme."
+description = "scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If not specified, upstream weighting is the default weighting scheme."
 valid = "central upstream tvd"
 reader = "urword"
 optional = true

autotest/dfns/__snapshots__/v2.0.0.dev1/gwe-adv.yaml

@@ -7,8 +7,8 @@ blocks:
   options:
     scheme:
       block: options
-      description: scheme used to solve the advection term.  Can be upstream, central, or TVD.  If not
-        specified, upstream weighting is the default weighting scheme.
+      description: scheme used to solve the advection term.  Can be upstream, central, TVD, or UTVD.  If
+        not specified, upstream weighting is the default weighting scheme.
       valid: central upstream tvd
       reader: urword
       optional: true

autotest/dfns/__snapshots__/v2.0.0.dev1/prt-oc.json

@@ -264,6 +264,14 @@
         "mf6internal": "dev_dump_evtrace",
         "longname": "print particle tracking events",
         "type": "keyword"
+      },
+      "scratch_buffer": {
+        "block": "options",
+        "description": "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory.",
+        "reader": "urword",
+        "optional": true,
+        "longname": "buffer track events in scratch file instead of memory",
+        "type": "keyword"
       }
     },
     "dimensions": {

autotest/dfns/__snapshots__/v2.0.0.dev1/prt-oc.toml

@@ -251,6 +251,14 @@ mf6internal = "dev_dump_evtrace"
 longname = "print particle tracking events"
 type = "keyword"
 
+[blocks.options.scratch_buffer]
+block = "options"
+description = "keyword to stage track events in a temporary (scratch) file instead of an in-memory buffer. Particle tracking results calculated during a time step are buffered, and output is deferred, until successful completion of the time step. By default, results are buffered in memory. However, for simulations in which a very large number of track events is generated during a time step, memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer results in a scratch file until successful completion of the time step. Buffering in a scratch file is typically slower than buffering in memory."
+reader = "urword"
+optional = true
+longname = "buffer track events in scratch file instead of memory"
+type = "keyword"
+
 [blocks.dimensions.ntracktimes]
 block = "dimensions"
 description = "is the number of user-specified particle tracking times in the TRACKTIMES block."

autotest/dfns/__snapshots__/v2.0.0.dev1/prt-oc.yaml

@@ -240,6 +240,19 @@ blocks:
       mf6internal: dev_dump_evtrace
       longname: print particle tracking events
       type: keyword
+    scratch_buffer:
+      block: options
+      description: keyword to stage track events in a temporary (scratch) file instead of an in-memory
+        buffer. Particle tracking results calculated during a time step are buffered, and output is deferred,
+        until successful completion of the time step. By default, results are buffered in memory. However,
+        for simulations in which a very large number of track events is generated during a time step,
+        memory limits can be exceeded. In such cases, the SCRATCH_BUFFER option can be invoked to buffer
+        results in a scratch file until successful completion of the time step. Buffering in a scratch
+        file is typically slower than buffering in memory.
+      reader: urword
+      optional: true
+      longname: buffer track events in scratch file instead of memory
+      type: keyword
   dimensions:
     ntracktimes:
       block: dimensions

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-cdb.json

@@ -66,8 +66,7 @@
         "maxbound": {
           "type": "integer",
           "longname": "maximum number of critical depth boundaries",
-          "description": "integer value specifying the maximum number of critical depth boundary cells that will be specified for use during any stress period.",
-          "tagged": false
+          "description": "integer value specifying the maximum number of critical depth boundary cells that will be specified for use during any stress period."
         }
       }
     },

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-cdb.toml

@@ -56,7 +56,6 @@ mode = "filein"
 type = "integer"
 longname = "maximum number of critical depth boundaries"
 description = "integer value specifying the maximum number of critical depth boundary cells that will be specified for use during any stress period."
-tagged = false
 
 [blocks.period.fields.stress_period_data]
 type = "list"

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-cdb.yaml

@@ -67,7 +67,6 @@ blocks:
         longname: maximum number of critical depth boundaries
         description: integer value specifying the maximum number of critical depth boundary cells that
           will be specified for use during any stress period.
-        tagged: false
   period:
     fields:
       stress_period_data:

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-chd.json

@@ -28,8 +28,7 @@
           "type": "string",
           "longname": "name of auxiliary variable for multiplier",
           "description": "name of auxiliary variable to be used as multiplier of CHD head value.",
-          "optional": true,
-          "tagged": false
+          "optional": true
         },
         "boundnames": {
           "type": "keyword",
@@ -85,8 +84,7 @@
         "maxbound": {
           "type": "integer",
           "longname": "maximum number of constant heads",
-          "description": "integer value specifying the maximum number of constant-head cells that will be specified for use during any stress period.",
-          "tagged": false
+          "description": "integer value specifying the maximum number of constant-head cells that will be specified for use during any stress period."
         }
       }
     },

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-chd.toml

@@ -24,7 +24,6 @@ type = "string"
 longname = "name of auxiliary variable for multiplier"
 description = "name of auxiliary variable to be used as multiplier of CHD head value."
 optional = true
-tagged = false
 
 [blocks.options.fields.boundnames]
 type = "keyword"
@@ -73,7 +72,6 @@ mode = "filein"
 type = "integer"
 longname = "maximum number of constant heads"
 description = "integer value specifying the maximum number of constant-head cells that will be specified for use during any stress period."
-tagged = false
 
 [blocks.period.fields.stress_period_data]
 type = "list"

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-chd.yaml

@@ -31,7 +31,6 @@ blocks:
         longname: name of auxiliary variable for multiplier
         description: name of auxiliary variable to be used as multiplier of CHD head value.
         optional: true
-        tagged: false
       boundnames:
         type: keyword
         description: keyword to indicate that boundary names may be provided with the list of constant-head
@@ -82,7 +81,6 @@ blocks:
         longname: maximum number of constant heads
         description: integer value specifying the maximum number of constant-head cells that will be specified
           for use during any stress period.
-        tagged: false
   period:
     fields:
       stress_period_data:

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-cxs.json

@@ -29,14 +29,12 @@
         "nsections": {
           "type": "integer",
           "longname": "number of reaches",
-          "description": "integer value specifying the number of cross sections that will be defined.  There must be NSECTIONS entries in the PACKAGEDATA block.",
-          "tagged": false
+          "description": "integer value specifying the number of cross sections that will be defined.  There must be NSECTIONS entries in the PACKAGEDATA block."
         },
         "npoints": {
           "type": "integer",
           "longname": "total number of points defined for all reaches",
-          "description": "integer value specifying the total number of cross-section points defined for all reaches.  There must be NPOINTS entries in the CROSSSECTIONDATA block.",
-          "tagged": false
+          "description": "integer value specifying the total number of cross-section points defined for all reaches.  There must be NPOINTS entries in the CROSSSECTIONDATA block."
         }
       }
     },

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-cxs.toml

@@ -21,13 +21,11 @@ optional = true
 type = "integer"
 longname = "number of reaches"
 description = "integer value specifying the number of cross sections that will be defined.  There must be NSECTIONS entries in the PACKAGEDATA block."
-tagged = false
 
 [blocks.dimensions.fields.npoints]
 type = "integer"
 longname = "total number of points defined for all reaches"
 description = "integer value specifying the total number of cross-section points defined for all reaches.  There must be NPOINTS entries in the CROSSSECTIONDATA block."
-tagged = false
 
 [blocks.packagedata.fields.packagedata]
 type = "list"

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-cxs.yaml

@@ -25,13 +25,11 @@ blocks:
         longname: number of reaches
         description: integer value specifying the number of cross sections that will be defined.  There
           must be NSECTIONS entries in the PACKAGEDATA block.
-        tagged: false
       npoints:
         type: integer
         longname: total number of points defined for all reaches
         description: integer value specifying the total number of cross-section points defined for all
           reaches.  There must be NPOINTS entries in the CROSSSECTIONDATA block.
-        tagged: false
   packagedata:
     fields:
       packagedata:

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-dfw.json

@@ -16,15 +16,13 @@
           "type": "double",
           "longname": "length conversion factor",
           "description": "real value that is used to convert user-specified Manning's roughness coefficients from meters to model length units. LENGTH_CONVERSION should be set to 3.28081, 1.0, and 100.0 when using length units (LENGTH_UNITS) of feet, meters, or centimeters in the simulation, respectively. LENGTH_CONVERSION does not need to be specified if LENGTH_UNITS are meters.",
-          "optional": true,
-          "tagged": false
+          "optional": true
         },
         "time_conversion": {
           "type": "double",
           "longname": "time conversion factor",
           "description": "real value that is used to convert user-specified Manning's roughness coefficients from seconds to model time units. TIME_CONVERSION should be set to 1.0, 60.0, 3,600.0, 86,400.0, and 31,557,600.0 when using time units (TIME_UNITS) of seconds, minutes, hours, days, or years in the simulation, respectively. TIME_CONVERSION does not need to be specified if TIME_UNITS are seconds.",
-          "optional": true,
-          "tagged": false
+          "optional": true
         },
         "save_flows": {
           "type": "keyword",

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-dfw.toml

@@ -14,14 +14,12 @@ type = "double"
 longname = "length conversion factor"
 description = "real value that is used to convert user-specified Manning's roughness coefficients from meters to model length units. LENGTH_CONVERSION should be set to 3.28081, 1.0, and 100.0 when using length units (LENGTH_UNITS) of feet, meters, or centimeters in the simulation, respectively. LENGTH_CONVERSION does not need to be specified if LENGTH_UNITS are meters."
 optional = true
-tagged = false
 
 [blocks.options.fields.time_conversion]
 type = "double"
 longname = "time conversion factor"
 description = "real value that is used to convert user-specified Manning's roughness coefficients from seconds to model time units. TIME_CONVERSION should be set to 1.0, 60.0, 3,600.0, 86,400.0, and 31,557,600.0 when using time units (TIME_UNITS) of seconds, minutes, hours, days, or years in the simulation, respectively. TIME_CONVERSION does not need to be specified if TIME_UNITS are seconds."
 optional = true
-tagged = false
 
 [blocks.options.fields.save_flows]
 type = "keyword"

autotest/dfns/__snapshots__/v2.0.0.dev2/chf-dfw.yaml

@@ -21,7 +21,6 @@ blocks:
           when using length units (LENGTH_UNITS) of feet, meters, or centimeters in the simulation, respectively.
           LENGTH_CONVERSION does not need to be specified if LENGTH_UNITS are meters.
         optional: true
-        tagged: false
       time_conversion:
         type: double
         longname: time conversion factor
@@ -31,7 +30,6 @@ blocks:
           in the simulation, respectively. TIME_CONVERSION does not need to be specified if TIME_UNITS
           are seconds.
         optional: true
-        tagged: false
       save_flows:
         type: keyword
         longname: keyword to save DFW flows