1. 06 May, 2020 1 commit
    • Mark Olesen's avatar
      ENH: improve installation handling · 59bdcfb3
      Mark Olesen authored
      - uses updated cmake/paraview scripts (1912, patch=200506)
        to support a user-specified installation prefix.
        Reworked the wmake Make/{files,options} files to respect the use
        of CMAKE_INSTALL_PREFIX, or default to FOAM_LIBBIN.
        Similarly the CMakeLists files have been updated to add install
        targets that respect the value of CMAKE_INSTALL_PREFIX.
        For building with paraview-5.7 and 5.8 a "staged" install is used
        to retain the expected output directory structure and to silently
        discard the unneeded static libraries.
  2. 27 Jan, 2020 1 commit
    • Mark Olesen's avatar
      CONFIG: increase cmake requirement for build · 19a4e158
      Mark Olesen authored
      - building paraview-5.7 and later requires cmake >= 3.10 itself
        but cmake-3.8 appears to work adequately for building dependent
  3. 23 Jan, 2020 1 commit
    • Mark Olesen's avatar
      ENH: support plugin building for paraview-5.7 · 26f5a091
      Mark Olesen authored
          For paraview-5.7 (and later?) plugins are built into their own subdirs.
          It also is not possible to suppress creation of static libraries in
          the process.
      The current solution is still a bit ugly
        - install into a local "staged" location (within the build directory)
        - use rsync to relocate to the .so files to the plugin directory
  4. 22 Jan, 2020 1 commit
    • Mark Olesen's avatar
      COMP: reorganized paraview library names for more clarity · 0b0e85b7
      Mark Olesen authored
      - OpenFOAM reader:
           (vtkPVFoam, PVFoamReader_SM)
        => (vtkPVFoamReader, ParaFoamReader)
      - blockMesh reader:
           (vtkPVblockMesh, PVblockMeshReader_SM)
        => (vtkPVblockReader, ParaFoamBlockReader)
      * provides better correspondence between library and module names
  5. 20 Jan, 2020 2 commits
  6. 12 Dec, 2019 1 commit
    • Mark Olesen's avatar
      CONFIG: prefer use of ParaView_MESA_DIR in runTimePostProcessing · e3d971dd
      Mark Olesen authored
      - when using VTK from ParaView sources it can better to tag them as
        such, but simultaneously not mask the ParaView with hardware
        The additional ParaView_MESA_DIR variable allows this.
        The balance of library and path setup is unaffected by this.
      STYLE: cleanup of Allwclean, Allwmake
      CONFIG: remove local version of cmakeVersionedInstall
  7. 11 Nov, 2019 2 commits
    • Mark Olesen's avatar
      ENH: rationalize some string methods. · 06f08f74
      Mark Olesen authored
      - silently deprecate 'startsWith', 'endsWith' methods
        (added in 2016: 2b1436066221), in favour of
        'starts_with', 'ends_with' methods, corresponding to C++20 and
        allowing us to cull then in a few years.
      - handle single character versions of starts_with, ends_with.
      - add single character version of removeEnd and silently deprecate
        removeTrailing which did the same thing.
      - drop the const versions of removeRepeated, removeTrailing.
        Unused and with potential confusion.
      STYLE: use shrink_to_fit(), erase()
    • Mark Olesen's avatar
      COMP: adjust common paraview library name to vtkPVFoamCommon · d1591319
      Mark Olesen authored
      - similar prefixing as the dependent readers, making it easier to
      - add FOAM_API information as server module version
  8. 06 Nov, 2019 1 commit
  9. 05 Nov, 2019 1 commit
  10. 04 Nov, 2019 1 commit
  11. 31 Oct, 2019 1 commit
  12. 04 Oct, 2019 1 commit
    • Mark Olesen's avatar
      CONFIG: adjustments for CMake files · 7eb1ef75
      Mark Olesen authored
      - drop plugin support for Qt4 (old paraview)
      - handle upcoming changes in VTK version naming in CMake files
  13. 06 Feb, 2019 1 commit
  14. 03 Feb, 2019 1 commit
  15. 31 Jan, 2019 1 commit
  16. 23 Jan, 2019 1 commit
  17. 07 Jan, 2019 2 commits
  18. 11 Dec, 2018 1 commit
    • Mark Olesen's avatar
      ENH: use Zero when zero-initializing types · 3d4e4a21
      Mark Olesen authored
      - makes the intent clearer and avoids the need for additional
        constructor casting. Eg,
            labelList(10, Zero)    vs.  labelList(10, 0)
            scalarField(10, Zero)  vs.  scalarField(10, scalar(0))
            vectorField(10, Zero)  vs.  vectorField(10, vector::zero)
  19. 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
  20. 29 Nov, 2018 1 commit
    • Mark Olesen's avatar
      ENH: improve setup for paraview · f88b74a0
      Mark Olesen authored
      - removed reliance on ParaView_INCLUDE_DIR variable for conveying the
        major.minor version information when compiling. This can be somewhat
        fragile and also adds variable that is an unnecessary when running
        (only used when compiling).
        Instead use `have_pvplugin_support` function in paraviewFunctions
        wmake script to determine the maj.min from the PV_PLUGIN_PATH
        since we have already defined the output path there with paraview
        maj.min numbering.
        Can now build with paraview from the operating system,
        provided that it has develop headers available.
        In the etc/config.sh/paraview setup, the maj.min is taken from
        the corresponding `paraview --version` output and used when
        defining the PV_PLUGIN_PATH.
        During the build, the include path taken from `paraview-config`
        for a system installation, from the guess installation root
        of the paraview binary, or ParaView_DIR otherwise.
      NB: using a system ParaView for building runTimePostProcessing is unsupported.
      - these types of builds appear to have various library resolution issues
        (eg, libexpat not being loaded). Additionally, the build logic does
        not yet cover this type of use case.
      CONFIG: add so version to libcatalystFoam
      STYLE: add OpenFOAM/include directory in CMakeLists
      - eg for foamVersion.H
  21. 05 Oct, 2018 1 commit
  22. 30 Jul, 2018 1 commit
  23. 26 Jul, 2018 1 commit
  24. 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
        Old parameter order:
                const labelList& region,
                const label currentRegion,
                const label patchID = -1,
                const bool syncCouples = true
        New parameter order:
                const label regioni,
                const labelUList& regions,
                const label patchID = -1,
                const bool syncCouples = true
         And without ambiguity:
                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,
                new fvMeshSubset(mesh, selectedCells)
        Or even
            return autoPtr<fvMeshSubset>::New(mesh, selectedCells);
  25. 24 Jul, 2018 1 commit
  26. 26 Jun, 2018 1 commit
  27. 30 May, 2018 1 commit
  28. 24 Apr, 2018 1 commit
    • Mark Olesen's avatar
      ENH: improve handling of ThirdParty packages · c794fa0d
      Mark Olesen authored
      - generalize some of the library extensions (.so vs .dylib).
        Provide as wmake 'sysFunctions'
      - added note about unsupported/incomplete system support
      - centralize detection of ThirdParty packages into wmake/ subdirectory
        by providing a series of scripts in the spirit of GNU autoconfig.
        For example,
            have_boost, have_readline, have_scotch, ...
        Each of the `have_<package>` scripts will generally provide the
        following type of functions:
            have_<package>          # detection
            no_<package>            # reset
            echo_<package>          # echoing
        and the following type of variables:
            HAVE_<package>          # unset or 'true'
            <package>_ARCH_PATH     # root for <package>
            <package>_INC_DIR       # include directory for <package>
            <package>_LIB_DIR       # library directory for <package>
        This simplifies the calling scripts:
            if have_metis
                wmake metisDecomp
        As well as reducing clutter in the corresponding Make/options:
            EXE_INC = \
                -I$(METIS_INC_DIR) \
            LIB_LIBS = \
                -L$(METIS_LIB_DIR) -lmetis
        Any additional modifications (platform-specific or for an external build
        system) can now be made centrally.
  29. 12 Apr, 2018 2 commits
  30. 03 Apr, 2018 1 commit
  31. 21 Mar, 2018 1 commit
  32. 31 Jan, 2018 1 commit
  33. 06 Dec, 2017 1 commit
  34. 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;
  35. 06 Sep, 2017 1 commit
  36. 12 Sep, 2017 1 commit