1. 18 Oct, 2009 1 commit
    • Mark Olesen's avatar
      Cleanup/fixup paraview readers · c57262c2
      Mark Olesen authored
      - remove patch/point text labels upon deletion
      
      - combined client/server plugin instead of separate .so files
        first experiment with adding panel decorations
      
      - directory reorganization
      c57262c2
  2. 05 Oct, 2009 1 commit
  3. 22 Jul, 2009 1 commit
  4. 20 May, 2009 1 commit
  5. 23 Mar, 2009 2 commits
  6. 04 Mar, 2009 1 commit
  7. 20 Feb, 2009 1 commit
  8. 02 Feb, 2009 1 commit
  9. 31 Dec, 2008 1 commit
  10. 21 Nov, 2008 1 commit
  11. 10 Aug, 2008 1 commit
  12. 08 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader gets (single) mesh region handling · 9427a34c
      Mark Olesen authored
        - handling multiple regions require multiple readers
        - a region is currently recognized by the file name, anything after the
          '=' delimiter (eg, "case=region.OpenFOAM") is used to determine the
          mesh region, but might be changed in the future
          eg, 'case%region', 'case^region', 'case~region', 'case{region}' ...
      
      Note:
        - Having a separate reader for each region instead attempting to handle
          all the mesh regions in a single reader is the better solution.
          It is not only simpler, but allows distinct field selections for
          each region
      Todo:
        - Haven't a test for Lagrangian and multi-regions.
      9427a34c
  13. 05 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - minor changes · de195bf1
      Mark Olesen authored
        - remove TimeRange property from XML. Not needed for discrete time data
        - represent Lagrangian data as VTK_VERTEX for simple visualization
      de195bf1
  14. 04 Aug, 2008 1 commit
  15. 03 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - code cleanup · 062bb366
      Mark Olesen authored
       - streamlined code somewhat, minor attempt to reclaim some memory
       - now use "mesh parts" for patches/zones/sets/etc throughout to avoid
         ambiguity with mesh regions
       - collect superCells and addPointCellLabels in a class. The old version
         actually seemed to have overwritten the addPointCellLabels with each
         cellSet/cellZone. This means that part of the pointFields would be trashed
         in the combination of polyhedral cells, cellSets/cellZones and internalMesh
       - polyDecomp information for muitiple mesh regions, but not yet exploited
       - pointFields now working for cellZones/cellSets
       - extroplating fields onto walls also works as expected for interpolated
         pointFields
       - added tooltips to reader GUI
      
      TODO:
       - pointFields (real and interpolated) for faceSets/faceZones
      062bb366
  16. 02 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader improvements · 775ef2c8
      Mark Olesen authored
        - various GUI properties are now animateable="0"
          (meaning they no longer show up on the time-line)
        - move reader switches to the bottom of the GUI
        - move Lagrangian fields above pointFields for better visibility
        - basic support for multiple clouds
        - filter fields based on selection before looping over all the geometry bits
        - mesh conversion functions now return VTK mesh types for easier handling
        - faceZones mesh conversion had points/faces allocation reversed
        - updateInfo with every call to setTime() that changes the timeIndex
          This seems to be the only way to notice Lagrangian fields
        - restore displaying patchnames that got forgotten in the last commit
        - misc reorganization
      775ef2c8
  17. 01 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - neater multiblocks and dual output ports · fa0b0343
      Mark Olesen authored
        - 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.
      fa0b0343
  18. 30 Jul, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader fixes · 5d715694
      Mark Olesen authored
        - 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),
      5d715694
  19. 28 Jul, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader reorganization · f8b27463
      Mark Olesen authored
        - 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
      f8b27463
  20. 25 Jul, 2008 2 commits
    • Mark Olesen's avatar
      static label Time::findClosestTimeIndex(const instantList&, const scalar) · 3cdc8ca0
      Mark Olesen authored
        - avoid code duplication in vtkPV3Foam.C and checkTimeOption.H
        - can also be used in Time::findClosestTime(), but didn't touch that
      3cdc8ca0
    • Mark Olesen's avatar
      PV3FoamReader repaired several misfeatures · 8a2596a0
      Mark Olesen authored
        - 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.
      8a2596a0
  21. 24 Jul, 2008 1 commit
  22. 23 Jul, 2008 1 commit
  23. 22 Jul, 2008 2 commits
  24. 04 Jul, 2008 1 commit
  25. 03 Jul, 2008 2 commits
  26. 25 Jun, 2008 2 commits
  27. 16 Jun, 2008 1 commit
  28. 28 May, 2008 1 commit
  29. 27 May, 2008 1 commit
  30. 08 May, 2008 1 commit