Repository navigation
feat: Remote rendering 5.2c - Wire ParaView mode in VISOR - #226
Open
LKasianAnsys wants to merge 4 commits into
Open
LKasianAnsys wants to merge 4 commits into
LKasianAnsys wants to merge 4 commits into
Conversation
LKasianAnsys
changed the base branch from
main
to
feat/5.2b-paraview-multiblock-support
November 16, 2026 20:52
LKasianAnsys
force-pushed
the
feat/5.2c-wire-paraview-mode-in-visor
branch
from
November 16, 2026 21:07
6690ee0 to
4302aef
Compare
LKasianAnsys
force-pushed
the
feat/5.2c-wire-paraview-mode-in-visor
branch
from
November 17, 2026 14:17
4302aef to
2438d01
Compare
LKasianAnsys
force-pushed
the
feat/5.2c-wire-paraview-mode-in-visor
branch
from
November 17, 2026 17:41
2438d01 to
9134bcc
Compare
LKasianAnsys
force-pushed
the
feat/5.2c-wire-paraview-mode-in-visor
branch
from
November 17, 2026 20:06
9134bcc to
54099b5
Compare
LKasianAnsys
force-pushed
the
feat/5.2c-wire-paraview-mode-in-visor
branch
from
November 17, 2026 20:25
54099b5 to
34e4391
Compare
LKasianAnsys
marked this pull request as ready for review
November 18, 2026 17:25
LKasianAnsys
force-pushed
the
feat/5.2c-wire-paraview-mode-in-visor
branch
from
November 18, 2026 19:02
34e4391 to
c5a4021
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Addresses #34
Summary
Wires up PARAVIEW mode in VISOR, connecting to an existing pvserver session in a subprocess.
ParaView's Python modules (e.g.
paraview.simple) need to run inside ParaView's own interpreter,pvpython, not in VISOR's normal Python environment (.venv). So each PARAVIEW session runs in a separatepvpythonprocess:VisorParaviewHandleis whatVisor(rendering_mode="PARAVIEW")returns, and what the API caches. It starts the child process and passes each Visor call to it.session_main.pybuildsVisorVTKParaviewinside the child process and runs the calls it receives.session_process.pystarts and stops the child process.session_channel.pyis the connection between the two processes.close()or/stop<log_dir>/visor_paraview_session_<port>.log. Error messages point to that file.Considerations:
ParaviewSessionError. If the child process hangs, the call hangs too. Calls to one session are also handled one at a time.UnsupportedInModeError):pvserveropens files itselfupdate_variablesCtrl+C: the child process runs in its own process group, soCtrl+Creaches only the parent. The parent then shuts the child process down cleanly. If the child process exits on its own during a blocking start, it raisesParaviewSessionError.VisorCache.delete_instancenow callsclose()on the instance it removes.close()does nothing for CLIENT and SERVER.Visor(...)andVisorVTKaccept apvserverkwarg. Passing an address in any mode other than PARAVIEW raisesValueError.paraview_pvpythonandparaview_venvmust be set in .visor. If they are not set, aParaviewNotConfiguredErroris raised.Diagrams
Inheritance:
Visorhas two subclasses:VisorVTKandVisorParaviewHandle.VisorVTKhas three subclasses:VisorVtkLocal,VisorVtkServer, andVisorVtkParaview.Instantiation (dispatch + processes): The
Visorclass's__new__()method is a factory that returns a class based on the providedrendering_engineandrendering_modearguments. Until now, it has returned aVisorVtkLocalfor CLIENT mode, andVisorVtkServerfor SERVER mode. In this PR we introduce PARAVIEW mode, which cannot return aVisorVtkParaviewinstance directly:VisorVtkParaviewneeds ParaView dependencies to run, which currently clash with Visor's dependencies (VTK version, Python verison).Instead, for PARAVIEW rendering mode, Visor's factory returns a
VisorParaviewHandle, aVisorsubclass that lives in the main process within the main.venv. That handle creates theVisorVtkParaviewinstance within a child process using ParaView'spvpython, which uses ParaView's VTK and the.pvenvvirtualenv that has the minimal required dependencies. TheVisorParaviewHandlecommunicates with theVisorVtkParaviewinstance that runs in the child process, which itself communicates with the pvserver session, which is in its own separate process.Manual check
Below are two manual checks, to test launching VISOR in PARAVIEW mode in two ways: 1. through
visor-cliand 2. through the PythonVisorclass withrendering_mode="PARAVIEW".Prerequisites
These prerequisites are needed for both manual checks.
.pvenvthat ParaView's environment will use.pvserveron port11111as followsManual check via
visor-cliCheck that PARAVIEW mode is now wired through the CLI
Manual check via Python
Check that PARAVIEW mode is dispatched through the
Visorclass withVisor(rendering_mode="PARAVIEW").