1. 11 Nov, 2016 1 commit
  2. 05 Aug, 2016 1 commit
  3. 25 Apr, 2016 1 commit
  4. 10 Feb, 2016 1 commit
  5. 10 Jan, 2016 1 commit
  6. 02 Dec, 2015 1 commit
  7. 17 Jun, 2013 1 commit
  8. 05 Apr, 2013 1 commit
  9. 14 Aug, 2011 1 commit
  10. 14 Jan, 2011 1 commit
  11. 29 Mar, 2010 1 commit
  12. 24 Feb, 2010 1 commit
  13. 18 Oct, 2009 1 commit
    • Mark Olesen's avatar
      Cleanup/fixup paraview readers · 7b6547ba
      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
      7b6547ba
  14. 03 Nov, 2009 1 commit
  15. 23 Mar, 2009 1 commit
    • Mark Olesen's avatar
      PV3FoamReader fix · b1a15105
      Mark Olesen authored
      - using a filter such as clip-plane on a multi-port source causes
        inconsistent UPDATE_TIME_STEPS() on each port. This looks like a
        VTK/Paraview bug to me.
        Workaround: check both ports and take the first one that has a value
        different than the last time set.
      b1a15105
  16. 31 Dec, 2008 1 commit
  17. 08 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader gets (single) mesh region handling · d8369415
      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.
      d8369415
  18. 03 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - code cleanup · 3277463f
      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
      3277463f
  19. 02 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader improvements · 3db5f133
      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
      3db5f133
  20. 01 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - neater multiblocks and dual output ports · cf9019f8
      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.
      cf9019f8
  21. 30 Jul, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader fixes · 321a91f4
      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),
      321a91f4
  22. 25 Jul, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader repaired several misfeatures · 18976c15
      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.
      18976c15
  23. 23 Jul, 2008 1 commit
  24. 03 Jul, 2008 1 commit
  25. 25 Jun, 2008 1 commit
  26. 27 May, 2008 1 commit
  27. 01 May, 2008 1 commit
  28. 15 Apr, 2008 1 commit