1. 05 Nov, 2019 1 commit
  2. 31 Oct, 2019 1 commit
  3. 06 Feb, 2019 1 commit
  4. 03 Feb, 2019 1 commit
  5. 05 Dec, 2018 1 commit
    • Mark Olesen's avatar
      ENH: code cleanup for vtk transcription · 98184a9b
      Mark Olesen authored
      - use cellCentres() instead of volField equivalent for vtk conversion
      
      - make looping variables more consistent
      
      - centralize the transcription of OpenFOAM -> vtk tuples
      98184a9b
  6. 25 Jul, 2018 1 commit
    • Mark Olesen's avatar
      ENH: fvMeshSubset improvements (issue #951) · 9b662e70
      Mark Olesen authored
      - what was previously termed 'setLargeCellSubset()' is now simply
        'setCellSubset()' and supports memory efficient interfaces.
      
        The new parameter ordering avoids ambiguities caused by default
        parameters.
      
        Old parameter order:
      
            setLargeCellSubset
            (
                const labelList& region,
                const label currentRegion,
                const label patchID = -1,
                const bool syncCouples = true
            );
      
        New parameter order:
      
            setCellSubset
            (
                const label regioni,
                const labelUList& regions,
                const label patchID = -1,
                const bool syncCouples = true
            );
      
         And without ambiguity:
      
            setCellSubset
            (
                const labelUList& selectedCells,
                const label patchID = -1,
                const bool syncCouples = true
            );
      
      - support bitSet directly for specifying the selectedCells for
        memory efficiency and ease of use.
      
      - Additional constructors to perform setCellSubset() immediately,
        which simplifies coding.
      
        For example,
      
            meshParts.set
            (
                zonei,
                new fvMeshSubset(mesh, selectedCells)
            );
      
        Or even
      
            return autoPtr<fvMeshSubset>::New(mesh, selectedCells);
      9b662e70
  7. 03 Apr, 2018 1 commit
  8. 06 Dec, 2017 1 commit
  9. 02 Aug, 2017 1 commit
  10. 24 May, 2017 1 commit
    • Mark Olesen's avatar
      ENH: paraview reader module with internal caching of the vtk geometries · 8d900264
      Mark Olesen authored
      - The reader module allows two levels of caching.
        The OpenFOAM fvMesh can be cached in memory, for faster loading of
        fields. Additionally, the translated VTK geometries are held in a
        local cache. The cached VTK geometries should incur no additional
        overhead since they use the VTK reference counting for their storage
        management.
      8d900264
  11. 15 May, 2017 1 commit
  12. 14 May, 2017 3 commits
  13. 12 May, 2017 1 commit
  14. 12 Jan, 2017 1 commit
    • Mark Olesen's avatar
      ENH: refactor paraview readers code to avoid duplication · ec944d4b
      Mark Olesen authored
      - as originally intended years ago, but never actually done.
      
      - use 'foamPvCore' instead of 'vtkPVReaders' to avoid potential name
        collisions with any 'vtk*' files and since we may reuse these
        functions in other foam-paraview modules (not just readers).
      
      STYLE: use same font size/colour for patch-names as for point-numbers
      
      BUG: repair issue with single time-step
      
      - paraview time-selector returns '0' as the requested time if there is
        only one time step. However, if we have skipped the 0/ directory,
        this single time step is likely a non-zero value.
      ec944d4b
  15. 11 Nov, 2016 1 commit
  16. 05 Aug, 2016 1 commit
  17. 10 Feb, 2016 1 commit
  18. 17 Jun, 2013 1 commit
  19. 03 May, 2013 1 commit
  20. 05 Apr, 2013 1 commit
  21. 14 Nov, 2012 1 commit
  22. 24 Sep, 2012 1 commit
  23. 14 Aug, 2011 1 commit
  24. 14 Jan, 2011 1 commit
  25. 30 Apr, 2010 1 commit
  26. 29 Mar, 2010 1 commit
  27. 24 Feb, 2010 1 commit
  28. 04 Dec, 2009 1 commit
  29. 23 Nov, 2009 1 commit
    • Mark Olesen's avatar
      Commit Paraview enhancements - quit working on sets/zones frills · 4b82f942
      Mark Olesen authored
      - Include Sets/Zones now scans immediately to refresh the list of available
        mesh parts. Unfortunately, this also causes the object panel to be
        modified, even although the selection doesn't acutally need to change.
        This seems to be due to how the pqNamedWidgets are getting the information
        from the proxy properties. I can't figure if it's possible to acheive what
        I want, but we can probably live with the current implementation.
      
        After IncludeZones, simply us 'Reset' to undo the spurious GUI changes.
        Works fine - just looks a bit silly.
      
      - Added 'Refresh' button to rescan for new times/fields.  Good for
        post-processing ongoing calculations without exiting the reader.
      
      - Added 'Skip Zero Time' checkbox: many (some) calculations have
        data missing at time=0 (eg, rho, lagrangian, etc). This provides
        a convenient way to skip over this time.
      
      - Future?:
        We could probably pick up favourite default values for these switches from
        ~OpenFOAM/controlDict, from a case system/paraview, or simply by making
        the casename.OpenFOAM also be an OpenFOAM dictionary with the settings.
      4b82f942
  30. 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
  31. 31 Dec, 2008 1 commit
  32. 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
  33. 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
  34. 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
  35. 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
  36. 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
  37. 28 Jul, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader reorganization · ad009d0c
      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
      ad009d0c
  38. 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