Simple test for extruding the boundary in 2D

domain/extrudeBoundaryTest.yaml

---
test:
  # a unique test name for this integration tests
  name: extrudeBoundaryTest
  # create a default assert that compares the log file
  assert: "inputs/domain/extrudeBoundaryTest.txt"

# metadata for the simulation
environment:
  title: _extrudeBoundaryTest
  tagDirectory: false
# global arguments that can be used by petsc
arguments:
  # ask petsc to label the boundary values
  dm_plex_separate_marker: ""
# set up the time stepper responsible for marching in time
timestepper:
  # for this example there are no time stepper arguments (empty simulation)
  arguments: { }
  # create a simple box mesh for simulation
  domain: !ablate::domain::BoxMesh
    name: extrudedMesh
    # keep the mesh simple with only 4 faces in each direction
    faces: [ 4, 4 ]
    # range the mesh between 0.0, 0.0 to 1.0, 1.0
    lower: [ 0, 0 ]
    upper: [ 1, 1 ]
    options:
      # output the result label for interior cells
      dm_label_view: interiorCells
    # create a dummy example fild
    fields:
      - name: exampleFVField
        components: [ "xx", "yy" ]
        type: FVM
    modifiers:
      # extrude the boundary cells crea
      - !ablate::domain::modifiers::ExtrudeLabel
        # use the labels defined by the dm_plex_separate_marker option
        regions:
          - name: marker
            value: 1 # this is the bottom boundary value
          - name: marker
            value: 4 # this is the left boundary value
        # define a region for the new interface between the originalRegion and extrudedRegion
        boundaryRegion:
          name: boundaryRegion
        # for all cells/faces/points that were in the original mesh before extrusion
        originalRegion:
          name: interiorCells
        # for all cells/faces/points that were extruded.  This does include overlap faces that are in the boundaryRegion, originalRegion, and extrudedRegion regions
        extrudedRegion:
          name: boundaryCells
      # the DmViewFromOptions "modifier" does not modify the dm but outputs. See [PetscOptionsCreateViewer](https://petsc.org/release/docs/manualpages/Viewer/PetscOptionsCreateViewer.html) for more details
      - !ablate::monitors::DmViewFromOptions
        options: ascii
      - !ablate::monitors::DmViewFromOptions
        options: ascii::ascii_info_detail
      - !ablate::monitors::DmViewFromOptions
        options: ":$OutputDirectory/mesh.tex:ascii_latex"
      # the $OutputDirectory is a special keyword that gets parsed by ablate to update to the output directory
      - !ablate::monitors::DmViewFromOptions
        options: "hdf5:$OutputDirectory/dm.h5"
  initialization:
    - fieldName: "exampleFVField"
      field: "x, y"

# this is a test input file with no solvers
solvers: [ ]