1. 30 Jan, 2018 1 commit
    • luz paz's avatar
      Misc. typos · 5bff56a1
      luz paz authored
      Some are user-facing and some aren't user-facing. Found via `codespell -q 3 -D ~/Documents/diff-experiment/dictionary.txt --skip="./ThirdParty,./Qt" -I ../paraview-whitelist.txt`
      whitelist contents were
      ```
      ans
      behaviour
      cas
      dum
      initialise
      initialisation
      lod
      nd
      ot
      pres
      wont
      ```
      5bff56a1
  2. 15 Dec, 2017 1 commit
  3. 19 Sep, 2017 1 commit
  4. 13 Jun, 2017 1 commit
    • Mathieu Westphal's avatar
      Adding OpenTURNS feature · 2a926af3
      Mathieu Westphal authored
      This commits adds multiple OpenTURNS related
      features, including
       * A new PARAVIEW_USE_OPENTURNS cmake option to turn on to use these features
       * A dedicated xml for some OpenTURNS filters
       * An extension to the PlotMatrixView for DensityMap capabilities
       * vtkPVHistogramView changes to support the display of OpenTurns filter output in it
       * vtkPVPlotMatrixRepresentation changes to support OpenTURNS features
       * Correction to vtkPVHistogramRepresentation to handle CenterBinAndAroundMax
       * Changes in PlotMatrixRepresentation default values to improve its look and feel
       * Modifications in Chart Management to display automatically line chart in the correct corner
       * Adding a ShowOneRepresentationAtATime xml hint
       * Adding related tests
      2a926af3
  5. 27 May, 2017 1 commit
  6. 07 Apr, 2017 1 commit
    • Ken Martin's avatar
      add in support for Send To OpenVR to ParaView · 9a08944c
      Ken Martin authored
      This topic adds support to take a View in paraview and
      send its actors to OpenVR (e.g. HTC Vive) Currently
      volumes and Actor2D are not sent to VR. This feature
      is off by default but can be turned on with the
      PARAVIEW_USE_OPENVR CMake option
      9a08944c
  7. 29 Mar, 2017 1 commit
  8. 03 Feb, 2017 1 commit
  9. 15 Jan, 2017 1 commit
  10. 23 Dec, 2016 1 commit
  11. 20 Dec, 2016 2 commits
  12. 22 Apr, 2016 1 commit
    • David E. DeMarle's avatar
      Expose the new OSPRay rendering module in ParaView · 374e8370
      David E. DeMarle authored
      Essentially this just exposes a new render pass for the data layer of all
       vtkPVRenderViews that render pass happens to not use GL.
      
      The GUI changes hide the controls when ospray is not compiled in since it
      is a lot harder to do it purely from the XML.
      374e8370
  13. 09 Feb, 2016 1 commit
  14. 29 Oct, 2015 1 commit
  15. 27 Mar, 2015 1 commit
  16. 14 Jan, 2015 1 commit
  17. 17 Sep, 2014 1 commit
    • Utkarsh Ayachit's avatar
      Fix detection of X. · 28ce06c0
      Utkarsh Ayachit authored
      ParaView was using obsolete PARAVIEW_USE_X flag. That flag was removed
      during modularization changes. Fixed to use the proper VTK_USE_X flag to
      check if we should use X API.
      
      This now fixes the detection of a valid display on the server nodes.
      
      Change-Id: I9478f991f81825fd3809895a311a0d3ce4e82043
      28ce06c0
  18. 22 Aug, 2014 1 commit
  19. 11 Jul, 2014 1 commit
  20. 12 Dec, 2013 1 commit
    • Cory Quammen's avatar
      Added Python view that enables plotting data with matplotlib · 797ae3a1
      Cory Quammen authored
      This view is compiled only if Python is enabled.
      
      The Python view accepts a Python script that can be used to plot
      data in a matplotlib figure. The script must contain two functions
      described below:
      
      - setup_data(view)
      
        The setup_data function supplies the current Python view as an
        argument. This is the native VTK object on which all methods that
        have been wrapped in Python may be called. The Python view supplies
        some methods that can be used to select which data arrays to
        transfer from the server side to the client side (all rendering is
        performed on the client). No arrays are selected by default.
      
      - render(view, figure):
      
        The render function supplies the current Python view as the first
        argument and a matplotlib FigureCanvasAgg as the second argument.
        The render function is typically expected to create one or more
        subplots in the figure that will be used for rendering.
      
      The functions setup_data and render may be defined in the script
      (e.g., when defined through the GUI settings for the Python View) or
      in the global Python interpreter (e.g. when defined in a script run by
      pvpython). They are invoked when needed by the Python view when
      rendering is needed.
      
      Removed unused saveImage() method from various views.
      
      Updated VTK to origin/master
      
      Change-Id: I882fa8eeacc81e8120762bf1312f568523559b09
      797ae3a1
  21. 30 Sep, 2013 1 commit
    • Utkarsh Ayachit's avatar
      Initialize MPI regardless of process type. · 45740191
      Utkarsh Ayachit authored
      Added a mechanism to initialize MPI on all processes, even client processes to
      simplify development of readers/plugins that use MPI.
      
      The client processes (paraview, pvpython) now take a command line arguments
      --mpi, --no-mpi that can be used to request enabling/disabling of calling
      MPI_Init() on those processes during startup.
      
      A CMake flag, PARAVIEW_INITIALIZE_MPI_ON_CLIENT can be used to control th
      default, used when the new command line arguments are not used.
      PARAVIEW_INITIALIZE_MPI_ON_CLIENT is OFF by default. When set to ON, the
      ParaView client executables will init MPI when no arguments are specified.
      They command line argumnets (--mpi/--no-mpi) can still override the default and
      hence provide a mechanism at runtime to change this.
      
      Change-Id: Iff90ed3d65358b6e940f8d8be59f98d0ca861684
      45740191
  22. 25 Jun, 2013 1 commit
    • Utkarsh Ayachit's avatar
      BUG #14147. Improve process initialization times. · 5959549f
      Utkarsh Ayachit authored
      - In static builds, we don't need to locate plugins. That is now avoided. This
        saves on several unnecessary filesystem accesses which should improve startup
        time on HPC systems.
      - Also avoiding setup of sys.path to find ParaView modules when
        PARAVIEW_FREEZE_PYTHON is true. Since ParaView modules will be frozen, we
        don't need to find site-packages. This avoids further more filesystem
        accesses.
      
      Change-Id: Ib208d5c2308f60b5ecead9bc63ad2a95315788c1
      5959549f
  23. 22 May, 2013 2 commits
    • Utkarsh Ayachit's avatar
      Cleanup OggTheora support. · 6230007d
      Utkarsh Ayachit authored
      ParaView wasn't detecting that OggTheora was enabled when using
      system-oggtheora since we were checking for the present of a target which is
      only created when not using system OggTheora. This fixes that issue.
      
      Change-Id: I643cb2bd1c18b9abc0e695c856b6786970a0ea5f
      6230007d
    • Utkarsh Ayachit's avatar
      Cleaning up enabling of FFMPEG. · b61e99df
      Utkarsh Ayachit authored
      FFMPEG support was not getting enabled due to buggy logic. Cleaned that up. Now,
      when PARAVIEW_ENABLE_FFMPEG is ON, we require VTK's FFMPEG support modules and
      enable *.avi support. This replaces VTK_HAS_FFMPEG_SUPPORT with
      PARAVIEW_ENABLE_FFMPEG in vtkPVConfig.h.
      
      Change-Id: I047f1143857468542a448d90a0dc58b1be8a0d1a
      b61e99df
  24. 14 Mar, 2013 1 commit
    • Utkarsh Ayachit's avatar
      Restructuring CoProcessing/Catalyst modules. · d582543b
      Utkarsh Ayachit authored
      To make it easier to develop adaptors externally, as well as add ability to
      enable/disable Python capabilities in Catalyst, we refactored the CoProcessing
      modules.
      
      Two new modules were added vtkPVCatalyst and vtkPVPythonCatalyst. These two
      libraries/module provide the Catalyst components necessary for coprocessing.
      These also provide a C/Fortran API (through CAdaptorAPI/FortranAdaptorAPI or
      the Python enabled CPythonAdaptorAPI/FortranPythonAdaptorAPI headers) that can
      be used within C/Fortran simulation codes.
      
      Adaptors are now moved to CoProcessing/Adaptors. They have now been updated to
      be able to built outside of ParaView build directory i.e. users can directly
      point CMake to ParaView/CoProcessing/Adaptors/CTHAdaptor as the source directory
      to build the CTH-Adaptor. They will have to point to an existing ParaView build,
      of course, like any other ParaView dependent project.
      
      ParaView-build builds these adaptors as a separate project (similar to the way
      we build examples). This can be disabled by using the advanced cmake variable
      PARAVIEW_BUILD_CATALYST_ADAPTORS.
      
      Also, fix static Python modules initialization. Added a new module in
      Utilities/PythonInitializer which exposes a C function to
      initialize Python modules for static executables. All executables now simply
      link against this one and call the initialization function to init Python.
      
      Change-Id: Icaacdf8a0d32e03742fbc302008c4ab45c40a22a
      d582543b
  25. 28 Jan, 2013 1 commit
  26. 29 Nov, 2012 1 commit
  27. 27 Nov, 2012 1 commit
  28. 21 Sep, 2012 1 commit
  29. 20 Sep, 2012 1 commit
  30. 15 Aug, 2012 1 commit
  31. 09 Aug, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Reenabling most of ParaView examples. · 303939a8
      Utkarsh Ayachit authored
      Reenabling most of ParaView examples and updates CMake files to make them work.
      spreadsheet example no longer installs using the branding cmake since we have
      deprecating providing cpack rules for applications. applications are expected to
      do that on their own.
      
      Change-Id: I9149ff9bcbc300b29c0c167b56dd2f24b4adea98
      303939a8
  32. 07 May, 2012 1 commit
    • Chris Harris's avatar
      Replace VTK_USE_X with PARAVIEW_USE_X · bb809432
      Chris Harris authored
      Rather than use VTK_USE_X create new cache entry PARAVIEW_USE_X
      that can be added to vtkPVConfig.h
      
      Change-Id: I0b75e09126d0d365967e35555a6edf6f7f019fc7
      bb809432
  33. 03 May, 2012 1 commit
  34. 22 Aug, 2011 1 commit
    • Utkarsh Ayachit's avatar
      Fixed BUG #12311. Changed ParaView version number policy. · f744f457
      Utkarsh Ayachit authored
      We now use "git describe" to determine the version for ParaView. Thus we no
      longer have to use minor/major version number trick for releases. "git describe"
      returns a string such as "v3.10.1-1701-g427f2839". The version is then set as
      follows:
      Major: 3
      Minor: 10
      Patch: 1
      Full : 3.10.1-1701-g427f2839
      
      If Full=="Major.Minor.Patch", then it's treated as a release.
      
      Release candidates can be tagged as "x.y.z-rcN" and the version will be set
      correctly.
      
      If git cannot determine the source version correctly, then
      "CMake/.paraview.version" file is searched for and we try to parse the version
      string from this file. It's a fatal error is both these approaches fail.
      f744f457
  35. 13 Apr, 2011 1 commit
  36. 30 Nov, 2010 1 commit
    • Robert Maynard's avatar
      BUG: Fix state files not having enough precision. · 45a45887
      Robert Maynard authored
      fixes bug 7073 where double values with more than 6 digits of precision where getting rounded down. The solution was setting the defualt precision in vtkSMDoubleVectorProperty. Also had to change pqDoubleRangeWidget to support display doubles with high precision.
      45a45887
  37. 29 Oct, 2010 2 commits