Repository navigation
feat: Remote rendering 5.2b - Render mult-part datasets with per-part color and selection in ParaView mode - #225
Open
LKasianAnsys wants to merge 20 commits into
Conversation
LKasianAnsys
changed the base branch from
main
to
feat/5.2a-paraview-backend-support
November 16, 2026 20:44
LKasianAnsys
force-pushed
the
feat/5.2b-paraview-multiblock-support
branch
from
November 17, 2026 14:17
b480b94 to
8f733c8
Compare
LKasianAnsys
force-pushed
the
feat/5.2b-paraview-multiblock-support
branch
2 times, most recently
from
November 17, 2026 20:06
5d8926f to
5c1a718
Compare
LKasianAnsys
force-pushed
the
feat/5.2b-paraview-multiblock-support
branch
from
November 17, 2026 20:24
5c1a718 to
2f2e293
Compare
LKasianAnsys
marked this pull request as ready for review
November 17, 2026 22:16
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
Allows PARAVIEW mode to render multi-part (composite) datasets such as .vtm and multiblock .vtkhdf. Each part supports visibility, opacity, solid colour, colour-by-variable and selection. Before this PR,
open_sourcerejected composite input.The final design is one composite representation per dataset. Each Visor part is a block inside it, written through ParaView's per-block properties (
BlockSelectors,BlockOpacities,BlockColors,BlockLookupTables, …) by the block's selector. This mapping lives only inParaviewRenderer. The scene graph, registry and part model are unchanged, and so are CLIENT and SERVER.Separately, the camera now no longer renders twice per mouse move, and the rotation pivots at the centre of the data.
Problems found, and how they shaped the design
Most of this design came from problems found while testing against a real pvserver.
GPU texture limit (one representation per part crashed pvserver)
many_blocks.vtm(66 parts), pvserver loggedHardware does not support the number of textures definedand then crashed. The browser canvas went black or red.vtkCompositePolyDataMapperdraws render in one frame. Pure VTK reproduces it: 31 actors render, 32 crash. CLIENT and SERVER use plainvtkPolyDataMapper, which has no limit, so only PARAVIEW is affected.pvserver. ParaView turnsInterpolateScalarsBeforeMappingon by default, which gives each separate map its own color texture.InterpolateScalarsBeforeMapping = 0, so colors are mapped per vertex and textures are not used per map..InterpolateScalarsBeforeMapping = 0is VTK's default setting, used by CLIENT and SERVER mode, so now PARAVIEW mode now colors the same way.Colours didn't match the other modes
LOOKUP_TABLE_HUE_RANGE), discretized the same way.InterpolateScalarsBeforeMappingoff (see above), color interpolation across cells also matches CLIENT and SERVER modes. which have it off by default. (Before turning the setting off, in PARAVIEW mode, the color mapping looked different from the other modes.)Selection and colour changes got slower with every selected part
simple.SelectBlockstakes one selector per call and renders after each one, so selection time grew quadratically. Selecting all 66 parts one at a time took 152 s. Colouring all 66 parts pushed 264 property writes.BlockTablemarks a property list as stale when a part changes, andParaviewCapturecallsflush_writes()before each render, so each list is written once per frame.Selection highlight is set to use wireframe
Camera lag during drags
EnableRenderOnInteraction = 0, so the capture's render is the only one per frame. Rendering stays on pvserver's GPU rather than moving into the pvpython sidecar.Rotation pivoted around the world origin
CenterOfRotation. It now follows the camera's focal point after a reset, a camera write and each gesture, matching SERVER.Making sure each part shows the right block
CompositeBlocksmaps each local leaf to a pvserver selector.VisorAddDatasetErrorwhen sibling blocks share a name, because the selector would then be ambiguous.Changes to shared code (CLIENT/SERVER behaviour unchanged)
ServerAppstreaming quality is now set through the class attributes INTERACTIVE_QUALITY and STILL_QUALITY, soParaviewAppcan override them. No changes to the actual values in SERVER mode, just a refactor.Known limitations
Manual check (similar to the manual check for PR 5.2a, #223)
.pvenvthat ParaView's environment will use.pvserveron port11111as followspvpythonshell as follows:VisorVTKParaviewinstance with a multiblock dataset using the code below.viewer.add_dataset()andviewer.remove_dataset()on the viewer.Python code for creating a
VisorVTKParaviewinstance