- normal mesh data on port0
  - Lagrangian data on port1
  - no fixed block numbers for dividing internalMesh, patches, zones etc.
    This helps avoid ugly gaps in the multiblock output
  - avoid segfault if Lagrangian fields are converted without positions

  TODO:
  - can we label the output ports?
  - the selection of Lagrangian data and fields is wonky.

  - added printMemory() method to aid debugging memory used
  - call UpdateInformation() if the mesh has changed
  - automatic activation of "internalMesh", "p", "U"
    is suppressed if a fvMesh is cached. Otherwise,
    appearing/disappearing volFields can cause a crash

  Note:
  The message "had to make up a selection value" that sometimes occurs
  seems to be paraview related (see paraview mailing list),

  - vtkPV3Foam get PrintSelf (reduces number of methods)
  - move output data member from vtkPV3Foam -> PV3FoamReader
    in preparation for rewriting output method
  - roughed in code to track mesh/field changes in preparation for rewriting
    output method
  - progress bar with arbitrary values to give the user something to watch

  - Remove paraFoam/Allwmake leftover junk
  - Always attempt make of libccmio to ensure lnInclude/ exists

  - avoid code duplication in vtkPV3Foam.C and checkTimeOption.H
  - can also be used in Time::findClosestTime(), but didn't touch that

  - On the first call, select 'internalMesh' and the 'p', 'U' fields.
    This corresponds to a fairly common default case without loading all
    possible fields etc.
  - Include zones should now work without issuing a FatalError when the
    corresponding files are missing. I must have tried too many things
    at once and didn't notice this before.
  - Use ZoneMesh for zone names if the fvMesh is already cached
    (skips re-reading the same files).
  - Change reader description to "OpenFOAM Reader" to distinguish it a bit
    from the vtkOpenFOAMReader built into paraview/vtk
  - Misc. file and method names reorganized

  - Remaining problem:
    mixing internalMesh and cellZones is clunky since there aren't yet
    interpolated point values for cellSets/cellZones. Paraview complains
    about the mismatch, but extracting a block is still okay.

  TODO:
  - multi-port output for Lagrangian
  - hold all the vtk mesh parts (including multiblock) and just pass the
    reference. With this, the pipeline might notice that the geometry is
    actually identical and skip the PVGeometryFilter that takes so long.