1. 24 Jun, 2019 1 commit
  2. 14 May, 2019 1 commit
    • Utkarsh Ayachit's avatar
      stereo cleanup · 8da606c8
      Utkarsh Ayachit authored
      Improve support for stereo screenshots. vtkSMViewProxy now explicitly
      handles the stereo left-right compositing after rendering each eye
      separately. This is required to support stereo captures that need
      tiling. Fixes #18974.
  3. 08 May, 2019 1 commit
    • Utkarsh Ayachit's avatar
      fix `OSMesaMakeCurrent` failed errors. · 463c9ecd
      Utkarsh Ayachit authored
      vtkPVView was calling Window::Initialize to ensure that the shared
      render window is initialized, but that doesn't seem to be adequate for
      certain implementations. Reworking code to call `Render` on the shared
      window before the very first render to overcome the issue.
      ref #18938.
  4. 04 May, 2019 2 commits
    • Utkarsh Ayachit's avatar
    • Utkarsh Ayachit's avatar
      refactoring remote rendering · ced8cf80
      Utkarsh Ayachit authored
      This commit cleans up the code that manages remote rendering.
      This fixes several issues: #15205, #17611, #18940, #18152, #18938,
      and #18937. #17815 is also addressed since its no longer applicable.
      ParaView no longer creates a single render window to use among all
      vtkPVView instances on non-client processes like pvbatch or pvserver,
      pvrenderserver. This shared render window was the root cause of several
      headaches and necessitated classes like vtkPVSynchronizedRenderWindows
      and extra burden on views to re-direct several calls like creating
      windows, resizing windows to vtkPVSynchronizedRenderWindows. This is no
      longer the case. Non-client processes still have a single viewable
      window per proceses (vtkPVProcessWindow). However, this is not the
      window that each view renders into. Instead, each view creates its own
      vtkRenderWindow subclass. However, it's a FBO-based render window which
      shares the context with the process specific render window
      (created in vtkPVProcessWindow). This makes it possible to simply blit
      back the rendering results from each view to the user-viewable window
      when needed (e.g. tile display, cave, etc.).
      `vtkPVSynchronizedRenderWindows` is now obsolete and removed with
      appropriate convenience API now moved over to vtkPVView. This also
      removes the need to initialize each view with a unique ID and hence
      `vtkPVView::Initialze()` API is no longer needed and hence removed.
      vtkIceTCompositePass was fixed to address several issues including tile
      display aspect ratios (#18152, #17611). vtkPVIceTCompositePass is no
      longer needed and hence removed which further simplifies the code.
  5. 24 Jul, 2017 1 commit
  6. 24 Mar, 2017 1 commit
    • Utkarsh Ayachit's avatar
      Adding setting for PPI. · c8fead25
      Utkarsh Ayachit authored
      The settings dialog now has an setting for the Screen PPI. This is
      passed on to all render windows in the application created through
      ParaView views.
  7. 07 Nov, 2016 2 commits
  8. 18 Oct, 2016 1 commit
  9. 20 Sep, 2016 1 commit
  10. 08 Dec, 2015 1 commit
    • Utkarsh Ayachit's avatar
      Make caching state reliable. · 385ca16f
      Utkarsh Ayachit authored
      vtkPVView only passed the UseCache flag to the representations in Update
      for performance reasons. Which meant there were often cases where the
      representations didn't have the update state of this flag and would end
      up clearing their caches unnecessarily e.g. just playing repeatedly
      without looping ended up never using the cache.
      To avoid this issue, we now let the representations directly access the
      caching flags on the view. This resulted in a couple of backwards
      incompatible changes, however, documented in MajorAPIChanges.md.
      1. vtkPVDataRepresentation subclasses must call superclass AddToView and
      RemoveFromView methods in their overrides.
      2. vtkPVDataRepresentation::SetUseCache and
      vtkPVDataRepresentation::SetCacheKey are no longer present.
  11. 22 Oct, 2015 1 commit
    • Andrew Bauer's avatar
      Fixing Catalyst script export, image output and batch interactors · 8817e4ac
      Andrew Bauer authored
      The fixes here include:
      *Fixing segfault when exporting a Catalyst script with a plot view.
      *Fixing batch interactor issue (no need for interactors in batch
       or when using Catalyst).
      The testing was improved with:
      *Adding a full workflow Catalyst test that outputs images.
       Had issue where outputting a chart view caused ParaView to
       segfault and now adding in a test to prevent that from
       happening again. It also outputs 2 images to make sure that
       works as well (the other one is a 3D render view).
      *The Catalyst tests that were run with pvpython as the driver were
       changed to use pvbatch instead which is more like how Catalyst
       is used.
  12. 26 May, 2015 1 commit
    • Utkarsh Ayachit's avatar
      Don't render client-side 3D geometry when remote rendering. · e9f13adc
      Utkarsh Ayachit authored
      Parent commit adds a test that fails to demonstrate the problem
      (TestCompositedGeometryCulling). The issue was that the composited
      renderer always renders the client-side geometries even when remote
      rendering is enabled. This change adds a culler to cull the props which
      will be rendered remotely.
      Also added logic to vtkPVRenderView to robustly say if remote rendering
      is being employed.
  13. 31 Jan, 2015 1 commit
    • Utkarsh Ayachit's avatar
      Refactoring ParaView interaction code. · a5111d41
      Utkarsh Ayachit authored
      ParaView was subclassing vtkRenderWindowInteractor to create
      vtkPVGenericRenderWindowInteractor to handle interaction. That piece of code
      was potentially derrived from an older implementation of
      vtkRenderWindowInteractor and hence did what it did. Current implementation
      of vtkRenderWindowInteractor lets the vtkInteractionStyle (and subclasses)
      do all the heavy lifting. ParaView did that to some extent (since it has a
      vtkPVInteractorStyle), but will was relying on
      vtkPVGenericRenderWindowInteractor, vtkPVRenderViewProxy to propage
      interaction/still renders and other things. This has been refactored.  ParaView no
      longer uses a special vtkRenderWindowInteractor. All logic is handled by observers
      on the standard vtkRenderWindowInteractor.
      This change was done to make it easier to enable interactivity in pvpython.
      Added new API to simple.py to start interact with a view in pvpython.
      Change-Id: I9725be948174b12c7f306c1d2fdbcfaac2d352ee
  14. 24 Oct, 2012 1 commit
    • Utkarsh Ayachit's avatar
      BUG #13533. Fixes state issue with exodus reader. · a9fe4321
      Utkarsh Ayachit authored
      Fixes bug introduced by 74ec34b1. When state files were loaded with timestep 0,
      the time value wasn't being set on vtkPVView. vtkPVView::SetViewTime() compared
      the old time value to the new one without regard for whether VimeTimeValid was
      set. This fixes that issue.
      Added a test that loads Exodus state file (for ParaView 3.14.1 to test backwards
      compatibility as well). The state file is loaded using the command line
      argument for loading state file.
      Change-Id: Ib5c1e237617cfb47a0fa3e948e4be554db89d9ed
  15. 09 Oct, 2012 1 commit
  16. 22 Sep, 2012 1 commit
    • Utkarsh Ayachit's avatar
      Refactors AMR streaming framework. · 52c7392f
      Utkarsh Ayachit authored
      This commit refactors AMR streaming framework and add support for a mechanism
      for streaming composite datasets in general. To try out amr streaming, run all
      executables with "--enable-streaming" flag and open an AMR Flash or Enzo dataset
      and render as "AMR Blocks" or "Volume" (currently, only works in builtin mode,
      but will be supported in other modes soon).
      vtkAMROutlineRepresentation is a example class that demonstrates how a
      representation can leverage the streaming capabailities provided by
      vtkPVRenderView adds support to two new passes: REQUEST_STREAMING_UPDATE() and
      which the representations can update their data pipelines to request a certain
      "piece" of the data. REQUEST_PROCESS_STREAMED_PIECE() is called on
      representations to handle a "piece" just received by the process. This
      separation makes it possible for representations to be agnostic of where the
      data is processed and where it is rendered. It's the reposibility of the view
      (vtkPVDataDeliveryManager in particular) to deliver the data to the
      rendering nodes.
      vtkPVDataDeliveryManager doesn't currently support data delivery for streamed
      pieces, however. That's on the TODO list.
  17. 28 Jun, 2012 1 commit
  18. 18 May, 2012 9 commits
  19. 04 Jan, 2012 1 commit
    • Robert Maynard's avatar
      ENH: Removed the use of vtkstd · 4e3debab
      Robert Maynard authored
      The vtkstd forwarding headers are deprecated, move to using the STL
      headers directly.
      Change-Id: I18b275a283f8a0684536bf844f166f4050d20473
  20. 31 Oct, 2011 1 commit
    • Utkarsh Ayachit's avatar
      Fixed ability to create views on different sessions at the same time. · ee9b9b2e
      Utkarsh Ayachit authored
      vtkPVView now creates a vtkPVSynchronizedRenderWindows instance per session.
      This ensures that multiple views exisiting on different sessions can be created
      Fixed vtkPVSynchronizedRenderWindows to set the name for each VTK-window. Now
      all windows show up with nicer names that make it possible to determine which
      window corresponds to which process.
  21. 05 Jul, 2011 1 commit
  22. 04 Jul, 2011 2 commits
    • Utkarsh Ayachit's avatar
      Cleanup View::Update(). · e57e56d1
      Utkarsh Ayachit authored
      Cleaned up vtkSMViewProxy::Update() and how it interacts with the
      represenations. Ensure that vtkSMViewProxy::NeedsUpdate flag is updated
      correctly when representations are dirty (even for selection changes).
      Additional optimizations in vtkPVRenderView to not do communication unless
    • Utkarsh Ayachit's avatar
      Making delivery request client-driven. · fba4aed7
      Utkarsh Ayachit authored
      Now, representations should not deliver any data to the "rendering nodes"
      unless the driver tells it to. Add a new DELIVERY phase to the renderview
      rendering phases. The DELIVERY phase is called on only those representations
      that the driver thinks need to delivery. Also any representation is required to
      do delivery in this phase (if it does indeed do delivery).
      Updating most render-view representations to use DELIVERY() stage for
  23. 18 May, 2011 1 commit
  24. 11 Apr, 2011 1 commit
  25. 13 Feb, 2011 1 commit
    • Utkarsh Ayachit's avatar
      Directory restructuring of Servers. · d7d21495
      Utkarsh Ayachit authored
      * Created new ParaViewCore directory in place of Servers.
      * Moved classes from old directories to new ones.
      * Removed some obsolete classes that were lingering in Filters/ServerManager.
  26. 30 Nov, 2010 1 commit
  27. 03 Nov, 2010 2 commits
  28. 02 Nov, 2010 1 commit