1. 06 Feb, 2019 1 commit
  2. 03 Feb, 2019 1 commit
  3. 07 Jan, 2019 1 commit
  4. 30 Jul, 2018 1 commit
  5. 03 Apr, 2018 1 commit
  6. 06 Dec, 2017 1 commit
  7. 13 Sep, 2017 1 commit
    • Andrew Heather's avatar
      ENH: Lagrangian - provided backwards compatibility for cases using the · 984f8f00
      Andrew Heather authored
      old "positions" file form
      
      The change to barycentric-based tracking changed the contents of the
      cloud "positions" file to a new format comprising the barycentric
      co-ordinates and other cell position-based info.  This broke
      backwards compatibility, providing no option to restart old cases
      (v1706 and earlier), and caused difficulties for dependent code, e.g.
      for post-processing utilities that could only infer the contents only
      after reading.
      
      The barycentric position info is now written to a file called
      "coordinates" with provision to restart old cases for which only the
      "positions" file is available. Related utilities, e.g. for parallel
      running and data conversion have been updated to be able to support both
      file types.
      
      To write the "positions" file by default, use set the following option
      in the InfoSwitches section of the controlDict:
      
          writeLagrangianPositions 1;
      984f8f00
  8. 02 Aug, 2017 1 commit
  9. 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
  10. 14 May, 2017 2 commits
  11. 12 May, 2017 1 commit
  12. 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
  13. 11 Nov, 2016 1 commit
  14. 05 Aug, 2016 1 commit
  15. 10 Feb, 2016 1 commit
  16. 17 Jun, 2013 1 commit
  17. 08 Apr, 2013 1 commit
  18. 05 Apr, 2013 1 commit
  19. 14 Aug, 2011 1 commit
  20. 14 Jan, 2011 1 commit
  21. 30 Apr, 2010 1 commit
  22. 29 Mar, 2010 1 commit
  23. 24 Feb, 2010 1 commit
  24. 04 Dec, 2009 1 commit
  25. 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
  26. 03 Nov, 2009 1 commit
  27. 05 Oct, 2009 1 commit
  28. 16 Mar, 2009 1 commit
  29. 06 Mar, 2009 1 commit
    • Mark Olesen's avatar
      objectRegistry fixes · 47830f9c
      Mark Olesen authored
      - objectRegistry gets a rename() that also adjusts the dbDir
      - cloud reworked to use static variables subInstance and defaultName.
        This avoids writing "lagrangian" everywhere
      
      string fixes
      - avoid masking of std::string::replace in string.H
      - avoid old strstream in PV3FoamReader
      47830f9c
  30. 31 Dec, 2008 1 commit
  31. 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
  32. 05 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - minor changes · d20b6fe6
      Mark Olesen authored
        - remove TimeRange property from XML. Not needed for discrete time data
        - represent Lagrangian data as VTK_VERTEX for simple visualization
      d20b6fe6
  33. 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
  34. 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
  35. 23 Jul, 2008 1 commit
  36. 25 Jun, 2008 1 commit
  37. 27 May, 2008 1 commit
  38. 09 May, 2008 1 commit
  39. 15 Apr, 2008 1 commit