ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:53:57-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/2655SNL: Client/server state saved wrong2019-03-05T10:53:57-05:00Kitware RobotSNL: Client/server state saved wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2655). Further discussion may take place here.**
---
When in client server mode, critical commands are missing in the pvs files ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2655). Further discussion may take place here.**
---
When in client server mode, critical commands are missing in the pvs files written when "Save Session State" is selected. In standalone mode, the first few lines to set the state of glyphs looks something like this:
<pre>
# Glyph Sources
set kw(vtkTemp876) [$kw(vtkTemp2) GetPVSource GlyphSources Arrow0]
set kw(vtkTemp877) [$kw(vtkTemp876) GetPVWidget {TipResolution}]
$kw(vtkTemp877) SetValue 6
set kw(vtkTemp883) [$kw(vtkTemp876) GetPVWidget {TipRadius}]
$kw(vtkTemp883) SetValue 0.1
set kw(vtkTemp889) [$kw(vtkTemp876) GetPVWidget {TipLength}]
$kw(vtkTemp889) SetValue 0.35
set kw(vtkTemp895) [$kw(vtkTemp876) GetPVWidget {ShaftResolution}]
$kw(vtkTemp895) SetValue 6
set kw(vtkTemp901) [$kw(vtkTemp876) GetPVWidget {ShaftRadius}]
$kw(vtkTemp901) SetValue 0.03
$kw(vtkTemp876) AcceptCallback
</pre>
When you save the state in client/server mode, the set kw(vtkTemp*) commands are missing.
<pre>
$kw(vtkTemp893) SetValue 6
$kw(vtkTemp899) SetValue 0.1
$kw(vtkTemp905) SetValue 0.35
$kw(vtkTemp911) SetValue 6
$kw(vtkTemp917) SetValue 0.03
$kw(vtkTemp892) AcceptCallback
</pre>
I found this bug because I just submitted a bunch of pvs files in bug reports that will probably not work for others because these set commands are missin.https://gitlab.kitware.com/paraview/paraview/-/issues/2581SNL: Client/Server connection improvements2019-03-05T10:54:03-05:00Kitware RobotSNL: Client/Server connection improvements**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2581). Further discussion may take place here.**
---
When the server dies the client should beep three times (max), and a dialog...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2581). Further discussion may take place here.**
---
When the server dies the client should beep three times (max), and a dialog box should pop up on the client explicitly saying "lost server..."https://gitlab.kitware.com/paraview/paraview/-/issues/3279SNL: Change composite threshold defualt to 3MB2019-03-05T10:53:10-05:00Kitware RobotSNL: Change composite threshold defualt to 3MB**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3279). Further discussion may take place here.**
---
We have gotten burned so many times on this. Please change this composite t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3279). Further discussion may take place here.**
---
We have gotten burned so many times on this. Please change this composite threshold to be 1MB be default. :)https://gitlab.kitware.com/paraview/paraview/-/issues/3262SNL: Cell centered probing2019-03-05T10:53:10-05:00Kitware RobotSNL: Cell centered probing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3262). Further discussion may take place here.**
---
Right now all the probing tools only allow a user to probe on node centered...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3262). Further discussion may take place here.**
---
Right now all the probing tools only allow a user to probe on node centered data. It would be nice to have the same thing for cell centered data.https://gitlab.kitware.com/paraview/paraview/-/issues/2684SNL: Cell centered isosurfaces2019-03-05T10:53:57-05:00Kitware RobotSNL: Cell centered isosurfaces**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2684). Further discussion may take place here.**
---
Currently to do isosurfaces of cell centered data you must first to 'CellTo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2684). Further discussion may take place here.**
---
Currently to do isosurfaces of cell centered data you must first to 'CellToPoint' and then run the isosurface. We would like to have the isocontour filter show cell centered array and then automatically invoke CellToPoint on just the selected array and then isosurface.https://gitlab.kitware.com/paraview/paraview/-/issues/3686SNL: Cannot Save Animation After Reading Trace File2019-03-05T10:52:36-05:00Kitware RobotSNL: Cannot Save Animation After Reading Trace File**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3686). Further discussion may take place here.**
---
When save as images or as mpg says:
# Error or warning: There was a VTK Er...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3686). Further discussion may take place here.**
---
When save as images or as mpg says:
# Error or warning: There was a VTK Error in file: /home/eschenbe/PV/Src2.4.4/Servers/ServerManager/vtkSMAnimationSceneProxy.cxx (271)
vtkSMAnimationSceneProxy (0xc426700): Unknown extension , try: jpg, tif or png.E
No problem when don't first read a trace file.
Version 2.4.4 compiled from source. FC4. Pentium 4.https://gitlab.kitware.com/paraview/paraview/-/issues/2721SNL: Camera animation + large object + client/server = zbuffer fighting2019-03-05T10:53:51-05:00Kitware RobotSNL: Camera animation + large object + client/server = zbuffer fighting**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2721). Further discussion may take place here.**
---
Start with a large object (about 1000 units along any axis) with a polygon ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2721). Further discussion may take place here.**
---
Start with a large object (about 1000 units along any axis) with a polygon surface. Make an animation where the camera completely spins around it. Now animate the camera.
If you are in client/server mode and the composite flag in the view properties is on, you should see some artifacts appear in the animation. (Note, you really only need 1 process on the server. Actual compositing need not occur, only rendering on the server.)
The artifacts appear to be zbuffer fighting. I am guessing that for some reason during animation the near plane of the camera is set to close to the viewpoint. Once you see the artifacts, they remain after you turn the animation off and use the mouse to change the camera. The artifacts go away if you hit the reset view button and return if you go to any time step.https://gitlab.kitware.com/paraview/paraview/-/issues/3576SNL: Calculator error reporting is broken2019-03-05T10:52:43-05:00Kitware RobotSNL: Calculator error reporting is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3576). Further discussion may take place here.**
---
When running the calculator, if the formula isn't perfect, the display just...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3576). Further discussion may take place here.**
---
When running the calculator, if the formula isn't perfect, the display just goes blank.
Open can.exo.
Turn all node variables on. Hit accept.
Click Calculator.
Vectors, "DISPL", Accept. All is well.
Type "+1" after the DISPL, hit Accept. Everything just goes blank.
It is also reported that if you hand type in the data into the formula window, it doesn't work. I suspect that this is just an error in typed input, and the user can't tell.
Example: type in DISPL, hit accept. It works.
Type in DISLP, it doesn't. Type in =DISPL, it also doesn't work. Get rid of the =, it now works.
There is a red ! at the bottom, if you look carefully. Message is pretty generic.https://gitlab.kitware.com/paraview/paraview/-/issues/3725SNL: Better information on the help tab2019-03-05T10:52:30-05:00Kitware RobotSNL: Better information on the help tab**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3725). Further discussion may take place here.**
---
It would be useful to have information on the help tab such as: MPI/noMPI, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3725). Further discussion may take place here.**
---
It would be useful to have information on the help tab such as: MPI/noMPI, Mesa/OpenGL, ???
alanhttps://gitlab.kitware.com/paraview/paraview/-/issues/2312SNL: Better error handling when out of memory2019-03-05T10:54:10-05:00Kitware RobotSNL: Better error handling when out of memory**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2312). Further discussion may take place here.**
---
Paraview should give an error message about being out of memory when it tri...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2312). Further discussion may take place here.**
---
Paraview should give an error message about being out of memory when it tries and fails to allocate memory during file opening.https://gitlab.kitware.com/paraview/paraview/-/issues/3439SNL: Bad path in linking commands on Mac2019-03-05T10:52:50-05:00Kitware RobotSNL: Bad path in linking commands on Mac**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3439). Further discussion may take place here.**
---
This applies to a cvs checkout.
I discovered this bug because my own per...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3439). Further discussion may take place here.**
---
This applies to a cvs checkout.
I discovered this bug because my own personal script for launching paraview kept disappearing. I have paraview built in ~/util/src/ParaView-datestring-build. I have a script in ~/util/bin that launches a particular build of paraview. When I build a new paraview, my script disappeared.
I've tracked it down to the linking command. The actual link command cds into GUI/Client and then builds the executable at ../../bin. Before the link command executes, the previous binary is removed. But it uses the same path without cd'ing
first and ends up trying delete the binary somewhere outside of the build directory. Yikes!
And hence, my poor little script which happens to be at ../../bin gets killed.
This problem showed up between 5/4 and 6/23.
Below are the linking commands.
Linking CXX executable ../../bin/paraview
/Users/wkoegle/util/bin/cmake -E remove -f ../../bin/paraview
cd /Users/wkoegle/util/src/ParaView/GUI/Client && c++ -Wno-deprecated -noprebind -g -fPIC "CMakeFiles/paraview.dir/ParaView.o" -o ../../bin/paraview -Lhttps://gitlab.kitware.com/paraview/paraview/-/issues/3394SNL: Automatic reload of Exodus files2019-03-05T10:53:03-05:00Kitware RobotSNL: Automatic reload of Exodus files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3394). Further discussion may take place here.**
---
It would be nice if you could reload the exodus file you're currently viewi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3394). Further discussion may take place here.**
---
It would be nice if you could reload the exodus file you're currently viewing, while staying in Paraview.
It would be ideal if this could be automated (if Paraview would check if the exodus file had been updated every x seconds).https://gitlab.kitware.com/paraview/paraview/-/issues/3072SNL: Arbitrary surface 'probing'2019-03-05T10:53:31-05:00Kitware RobotSNL: Arbitrary surface 'probing'**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3072). Further discussion may take place here.**
---
We would like the ability to probe an arbitrary surface with the probe. The...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3072). Further discussion may take place here.**
---
We would like the ability to probe an arbitrary surface with the probe. The easiest thing to do is have the cutplane intersection with the dataset define the vtkPolyData that will be used for the probing data.https://gitlab.kitware.com/paraview/paraview/-/issues/1551SNL: Annotation Improvements2019-03-05T10:54:23-05:00Kitware RobotSNL: Annotation Improvements**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=1551). Further discussion may take place here.**
---
It would be nice to be able to select font size and hide annotations and la...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=1551). Further discussion may take place here.**
---
It would be nice to be able to select font size and hide annotations and labels. For example the node numbers displayed by pick can cover most of the neighboring cells for high resolution displays and closely spaced nodes. If the user could change size or hide this display, they could see to pick adjacent nodes.https://gitlab.kitware.com/paraview/paraview/-/issues/4136SNL: Allow PT in interactive volume render.2019-03-05T10:51:29-05:00Kitware RobotSNL: Allow PT in interactive volume render.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4136). Further discussion may take place here.**
---
The PT volume renderer is sometimes faster than the HAVS volume renderer. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4136). Further discussion may take place here.**
---
The PT volume renderer is sometimes faster than the HAVS volume renderer. That is probably the case when the user selects PT over HAVS.
The logic for the interactive rendrer should select PT if the data is small enough and PT is the still renderer.https://gitlab.kitware.com/paraview/paraview/-/issues/2699SNL: Add vtkSNL Gradient filter to ParaView GUI2019-03-05T10:53:57-05:00Kitware RobotSNL: Add vtkSNL Gradient filter to ParaView GUI**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2699). Further discussion may take place here.**
---
Please add the vtkGradientFilter in vtkSNL to ParaView's GUI.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2699). Further discussion may take place here.**
---
Please add the vtkGradientFilter in vtkSNL to ParaView's GUI.https://gitlab.kitware.com/paraview/paraview/-/issues/2791SNL: Add Material/Shader support to ParaView2019-03-05T10:53:51-05:00Kitware RobotSNL: Add Material/Shader support to ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2791). Further discussion may take place here.**
---
Allow users to apply library and possibly repository materials through Para...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2791). Further discussion may take place here.**
---
Allow users to apply library and possibly repository materials through ParaView's 'Display' gui tab.https://gitlab.kitware.com/paraview/paraview/-/issues/4391SNL: 2.6: Fatal crash: servers bad X server connection.2019-03-05T10:50:56-05:00Kitware RobotSNL: 2.6: Fatal crash: servers bad X server connection.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4391). Further discussion may take place here.**
---
When running ParaView 2.6, Client/Server on a server that doesn't have a gr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=4391). Further discussion may take place here.**
---
When running ParaView 2.6, Client/Server on a server that doesn't have a grapics card, I get the following error:
Process id: 0 >> ERROR: In /projects/viz/paraview/src/ParaView/2.6/ParaView/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 497
vtkXOpenGLRenderWindow (0xcec7e00): bad X server connection. DISPLAY=:0
Process id: 0 >> ERROR: In /projects/viz/paraview/src/ParaView/2.6/ParaView/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 319
vtkXOpenGLRenderWindow (0xcec7e00): bad X server connection. DISPLAY=:0
This is probably the same error as reported on an e-mail listed as PV2.6 Crashes. I am including that e-mail here:
I'm using the released PV2.6 and seeing some strange crashes.
I'm using the Windows Version you guys compiled for the pvclient, and running the PVServer on a linux Cluster. I compiled the server myself with OSMesa ( 6.4.2) & MPI (OpenMPI 1.1.1-1)support, and i'm running it on multiple processors (the number doesn't matter). When I compiled it, I seeded CMake with the following cache:
BUILD_DOCUMENTATION:BOOL=OFF
BUILD_EXAMPLES:BOOL=OFF
BUILD_SHARED_LIBS:BOOL=ON
BUILD_TESTING:BOOL=OFF
CMAKE_BUILD_TYPE:STRING=Release
CMAKE_CXX_COMPILER:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/bin/mpicxx
CMAKE_C_COMPILER:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/bin/mpicc
CMAKE_INSTALL_PREFIX:PATH=/viz/home/rhand/local/pv-2.4
//Path to a file.
MPI_INCLUDE_PATH:PATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1 /include
MPI_LIBRARY:FILEPATH=/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/lib64/libmpi.so
OPENGL_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OPENGL_gl_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libVTKMesaGL.so
OPENGL_glu_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libVTKMesaGLU.so
OPENGL_xmesa_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OSMESA_INCLUDE_DIR:PATH=/viz/home/rhand/local/include
OSMESA_LIBRARY:FILEPATH=/viz/home/rhand/local/lib/libOSVTKMesa.so
VTK_OPENGL_HAS_OSMESA:BOOL=ON
VTK_USE_64BIT_IDS:BOOL=ON
VTK_USE_MPI:BOOL=ON
VTK_USE_RPATH:BOOL=OFF
Problem #1:
If I load an ImageData dataset (VTI) and then attempt to use the Clip filter on it, it crashes every time. Also, I get no ghost cells so when I extract an isosurface the process boundaries are clearly visible. I place the Clip Filter at roughly 45-degrees (eyeballed, not much precision) so that it gives me the lower-left half of the data, and when it crashes I get a trace like the following:
Connected to client
Process id: 0 >> ERROR: In /viz/home/rhand/src/pv- 2.6/comp/PV/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 497
vtkXOpenGLRenderWindow (0x5362f50): bad X server connection. DISPLAY=Process id: 0 >> ERROR: In /viz/home/rhand/src/pv- 2.6/comp/PV/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 319
Signal:11 info.si_errno:0(Success) si_code:1(SEGV_MAPERR)
Failing at addr:0x10
[0] func:/usr/local/ofed/mpi/gcc/openmpi-1.1.1-1/lib64/libopal.so.0 [0x2a9bf15dd5]
[1] func:/lib64/tls/libpthread.so.0 [0x3dd910c430]
[2] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow13CreateAWindowEv+0x216) [0x2a984e13f6]
[3] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow16WindowInitializeEv+0x12) [0x2a984e21d2]
[4] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow5StartEv+0xd) [0x2a984e249d]
[5] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow14DoStereoRenderEv+0x10) [0x2a98452160]
[6] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow10DoFDRenderEv+0x36b) [0x2a984520fb]
[7] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow10DoAARenderEv+0x46b) [0x2a98451d3b]
[8] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN15vtkRenderWindow6RenderEv+0x149) [0x2a98451439]
[9] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN22vtkXOpenGLRenderWindow6RenderEv+0x1c) [0x2a984e437c]
[10] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN25vtkOpenGLExtensionManager20ReadOpenGLExtensionsEv+0xc0) [0x2a984ab450]
[11] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkRendering.so.pv2.6(_ZN25vtkOpenGLExtensionManager6UpdateEv+0x52) [0x2a984aac12]
[12] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN32vtkPVOpenGLExtensionsInformation14CopyFromObjectEP9vtkObject+0xf9) [0x2a955b0bf9]
[13] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN17vtkSelfConnection17GatherInformationEjP16vtkPVInformation17vtkClientServerID+0x83) [0x2a955dc163]
[14] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN20vtkMPISelfConnection17GatherInformationEjP16vtkPVInformation17vtkClientServerID+0x64) [0x2a9559e684]
[15] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN19vtkClientConnection15SendInformationER21vtkClientServerStream+0x1d5) [0x2a9558ff65]
[16] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_Z39vtkClientConnectionGatherInformationRMIPvS_ii+0x48) [0x2a955900b8]
[17] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkParallel.so.pv2.6(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x9e) [0x2a9707ef6e]
[18] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkParallel.so.pv2.6(_ZN25vtkMultiProcessController11ProcessRMIsEii+0xa0) [0x2a9707f3b0]
[19] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN19vtkRemoteConnection20ProcessCommunicationEv+0x14) [0x2a955d9fb4]
[20] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN33vtkProcessModuleConnectionManager18MonitorConnectionsEm+0x2d9) [0x2a955d81d9]
[21] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN16vtkProcessModule11StartServerEm+0x76) [0x2a955cb676]
[22] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVServerCommon.so(_ZN16vtkProcessModule5StartEiPPc+0x24d) [0x2a955ce8cd]
[23] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/libvtkPVFilters.so(_ZN9vtkPVMain3RunEP12vtkPVOptions+0x7b) [0x2a95857b7b]
[24] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/pvserver-real(main+0xc2) [0x402482]
[25] func:/lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x3dd881c3fb]
[26] func:/viz/home/rhand/local/pv2.6/lib/paraview-2.6/pvserver-real(__gxx_personality_v0+0x5a) [0x40232a]
*** End of error message ***
If I load the same ImageData Dataset & apply the D3 filter, then attempt to use the Clip filter, it works. I have alot of rendering artifacts (I think due to the Structured->Unstructured conversion) and it takes ALOT of memory, but it works.https://gitlab.kitware.com/paraview/paraview/-/issues/2966SNL: "Split Parts" filter request2019-03-05T10:53:44-05:00Kitware RobotSNL: "Split Parts" filter request**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2966). Further discussion may take place here.**
---
Not sure how difficult this is. Our users would like to be able to 'fan out...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=2966). Further discussion may take place here.**
---
Not sure how difficult this is. Our users would like to be able to 'fan out' parts based on part ids in their datasetshttps://gitlab.kitware.com/paraview/paraview/-/issues/3479SNL: We need to be able to color blocks differently2019-03-05T10:52:50-05:00Kitware RobotSNL: We need to be able to color blocks differently**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3479). Further discussion may take place here.**
---
We need to be able to color blocks differently - using a different color ma...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=3479). Further discussion may take place here.**
---
We need to be able to color blocks differently - using a different color map per block. For instance, if a user wants to select block number 30, and turn it red while leaving the rest of an object colored by tempurature. Or, a user may want ALL blocks blue, except for wanting block number 3000 to be red.