ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:38:17-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/11823Add VTK_USE_SYSTEM_LIBRARIES option2019-03-05T10:38:17-05:00Kitware RobotAdd VTK_USE_SYSTEM_LIBRARIES option**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11823). Further discussion may take place here.**
---
It would be very nice for packaging to have a VTK_USE_SYSTEM_LIBRARIES opt...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11823). Further discussion may take place here.**
---
It would be very nice for packaging to have a VTK_USE_SYSTEM_LIBRARIES option that would be the default value for the different VTK_USE_SYSTEM_$X options. The attached patch appears to work nicely.https://gitlab.kitware.com/paraview/paraview/-/issues/11822Strange install location for Python vtk2019-03-05T10:38:17-05:00Kitware RobotStrange install location for Python vtk**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11822). Further discussion may take place here.**
---
I'm updating the Fedora paraview package to 3.10.0-RC1 and running into a ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11822). Further discussion may take place here.**
---
I'm updating the Fedora paraview package to 3.10.0-RC1 and running into a problem where a bunch of stuff is installed into /usr/bin/Python/vtk/, e.g:
/usr/bin/Python/vtk/__helper.pyhttps://gitlab.kitware.com/paraview/paraview/-/issues/11821(Mars) Prism - autoscaling should differ for multiple surfaces2018-08-28T09:39:50-04:00Kitware Robot(Mars) Prism - autoscaling should differ for multiple surfaces**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11821). Further discussion may take place here.**
---
In prism (both filter and sesame reader), surfaces are rescaled so that th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11821). Further discussion may take place here.**
---
In prism (both filter and sesame reader), surfaces are rescaled so that they have an aspect ratio of 1:1:1 in the three coordinate directions. This is because the coordinates are thermodynamic variables, rather than e.g. length, and are independent and have different units. For a single surface this seems to work fine. However, when two or more surfaces are shown, they are rescaled independently. As a result, the same coordinates on each surface are not at the same location in the view.https://gitlab.kitware.com/paraview/paraview/-/issues/11818saving animation and screenshot in stereo2019-03-05T10:38:17-05:00Kitware Robotsaving animation and screenshot in stereo**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11818). Further discussion may take place here.**
---
When saving animations and sreenshots in stereo, I end up with a black scr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11818). Further discussion may take place here.**
---
When saving animations and sreenshots in stereo, I end up with a black screen in place of the renderview, and the viewpoints are the same for left and right eye.https://gitlab.kitware.com/paraview/paraview/-/issues/11813Render window context menu edit color not working2019-03-05T10:38:17-05:00Kitware RobotRender window context menu edit color not working**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11813). Further discussion may take place here.**
---
When using the context menu edit color it uses the current pipeline browse...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11813). Further discussion may take place here.**
---
When using the context menu edit color it uses the current pipeline browser selection instead of what your mouse is over in the render window.https://gitlab.kitware.com/paraview/paraview/-/issues/11812Memory leak when playing with ScalarBar visibility2019-03-05T10:38:17-05:00Kitware RobotMemory leak when playing with ScalarBar visibility**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11812). Further discussion may take place here.**
---
If you are monitoring the memory consumption of ParaView while you are pla...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11812). Further discussion may take place here.**
---
If you are monitoring the memory consumption of ParaView while you are playing with the visibility of a scalar bar, you will be able to see large chunk of memory allocated each time you set it to visible.
For the first couple of time, the increase in memory is less than 1 KB but after several iteration one iteration can increase the memory of more than 100 MB.https://gitlab.kitware.com/paraview/paraview/-/issues/11811Internal surfaces visible after D3 when opacity < 12019-03-05T10:38:17-05:00Kitware RobotInternal surfaces visible after D3 when opacity < 1**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11811). Further discussion may take place here.**
---
* Client/ remote server. Trunk.
* Open g1s1. All vars on, apply.
* Ch...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11811). Further discussion may take place here.**
---
* Client/ remote server. Trunk.
* Open g1s1. All vars on, apply.
* Change the opacity to 0.5. Notice the processor boundaries.
* D3 filter. Apply. Make sure that the opacity is 0.5. Notice that we still have processor boundaries.https://gitlab.kitware.com/paraview/paraview/-/issues/11802point sprite plugin python trace not functionnal2019-03-05T10:38:17-05:00Kitware Robotpoint sprite plugin python trace not functionnal**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11802). Further discussion may take place here.**
---
Dumping a python script using the trace functionnality creates a script th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11802). Further discussion may take place here.**
---
Dumping a python script using the trace functionnality creates a script that does not reproduce the same result when re-executed, especially when using the texture mode.https://gitlab.kitware.com/paraview/paraview/-/issues/11801On multiple File open only prompt once for each file extension.2019-03-05T10:38:17-05:00Kitware RobotOn multiple File open only prompt once for each file extension.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11801). Further discussion may take place here.**
---
I've just talked to Rob about your problem and explained your point.
Rob ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11801). Further discussion may take place here.**
---
I've just talked to Rob about your problem and explained your point.
Rob is going to report a bug for that.
One solution we were thinking of is when several files are selected in
the OpenFile process, if we already have define a reader for a given
extension, we reuse that same reader and ask for the reader type only
for new extension where concurrent reader exist.
https://gitlab.kitware.com/paraview/paraview/-/issues/11796Smart context menu for outline representation2019-03-05T10:38:17-05:00Kitware RobotSmart context menu for outline representation**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11796). Further discussion may take place here.**
---
The new smart context menus are awesome! The only trouble is, once you swi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11796). Further discussion may take place here.**
---
The new smart context menus are awesome! The only trouble is, once you switch to "outline" view, you cannot right click on the object anymore to change it to something other than outline view - you have to use the old "Display" tab method. It is still possible to select the in wireframe mode (the line are the same thickness as the outline), so it should be possible to select the outline.https://gitlab.kitware.com/paraview/paraview/-/issues/11778Mac install symlinks to server tools2019-03-05T10:38:17-05:00Kitware RobotMac install symlinks to server tools**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11778). Further discussion may take place here.**
---
In 3.10 we now ship the server tools (pvserver, pvpython, pvbatch, ...) in...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11778). Further discussion may take place here.**
---
In 3.10 we now ship the server tools (pvserver, pvpython, pvbatch, ...) in the bin directory of the app bundle instead of as a separate download. To make these more accessible we should add a menu option (like CMake) to install symlinks to the server tools in /usr/bin.https://gitlab.kitware.com/paraview/paraview/-/issues/11777DISPLAY environment variable (from *.pvx files for CAVE) being set after disp...2018-11-28T09:40:46-05:00Kitware RobotDISPLAY environment variable (from *.pvx files for CAVE) being set after display is opened**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11777). Further discussion may take place here.**
---
The error (unable to open display) is occurring before the environment var...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11777). Further discussion may take place here.**
---
The error (unable to open display) is occurring before the environment variables (from the pvx file) for the pvservers is being set. The vtkPVDisplayInformation::CopyFromObject is being called prior to the environment variables being set resulting in vtkSMMultiProcessRenderView::EndCreateVTKObjects setting RemoteRenderAvailable=false. I have not yet figured out how to do it, but the best solution would involve the PVX info being passed to all of the pvservers when they are started (assuming the pvx file is passed to the pvserver command) and if so, then the environment variable(s) should be set immediately - maybe the vtkSMClientServerRenderSyncManagerHelper::InitializeRenderSyncManager should run before testing the displays assuming it is actually telling the pvservers how (and when) to set their environments. I've tested paraview-3.8.1 on our render cluster resulting in same errors. If we had only 1 X screen or X display and only 1 GPU per node, I agree we could set the DISPLAY environment variable. But, being we have 2 GPUs per render nodes in the CAVE and 2 GPUs per compute node in our render cluster, paraview is not working the way it should and it is a bug that should be fixed. Below is some basic output from printf statements I set in various functions to show what is and is not happening. It appears the HOSTNAME variable is not set when the pvservers are started so simply accept that "host: (null)" is a pvserver on one of the render nodes whereas "host:console" is the head node where the client is running.https://gitlab.kitware.com/paraview/paraview/-/issues/117762d axis needs enhancing2018-08-28T09:39:51-04:00Kitware Robot2d axis needs enhancing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11776). Further discussion may take place here.**
---
We need to enhance the 2d axis. I am using sources/ mandlebrot as an exam...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11776). Further discussion may take place here.**
---
We need to enhance the 2d axis. I am using sources/ mandlebrot as an example.
I can think of a few options, such as:
* Lock the axis to reasonable numbers. With mandelbrot, use a Y range from -1.5 to 1.5.
* Let the user to select the range, and thus the size of the axis.
* Allow user to add a grid pattern.
* Allow user to turn on/off different axes (for instance, upper and right.)
https://gitlab.kitware.com/paraview/paraview/-/issues/117752d axis is confusing2018-08-28T09:39:51-04:00Kitware Robot2d axis is confusing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11775). Further discussion may take place here.**
---
It is confusing how to turn on the show axis for a 2d view. Lets add a no...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11775). Further discussion may take place here.**
---
It is confusing how to turn on the show axis for a 2d view. Lets add a note in the display tab, for 2d views, that tells a user to go to the Edit View Options.
An example dataset is sources/ mandlebrot.https://gitlab.kitware.com/paraview/paraview/-/issues/11772vtp and vtk cannot handle more than order 120 million triangles2020-04-10T16:59:24-04:00Kitware Robotvtp and vtk cannot handle more than order 120 million triangles**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11772). Further discussion may take place here.**
---
We think 32 bit integers are used in vtp and vtk files to represent the nu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11772). Further discussion may take place here.**
---
We think 32 bit integers are used in vtp and vtk files to represent the number of coordinates and polygons. In particular, the offset is suspect. In our case, when the number of points and triangles approaches respectively 60 million and 120 million, paraview cannot render the object. We get the following error:
ERROR: In /Users/partyd/Kitware/ParaView-3.8/src/VTK/IO/vtkXMLUnstructuredDataReader.cxx, line 589
vtkXMLPolyDataReader (0x10a504c00): Cannot read cell offsets from Polys in piece 0 because the "offsets" array is not long enough.
Some versions of paraview are able to read the vtp files on unix boxes. It depends on the build. Here is the header of the vtp file:
[dgd]% head test.vtp
<?xml version="1.0"?>
<VTKFile type="PolyData" version="0.1" byte_order="LittleEndian">
<PolyData>
<Piece NumberOfPoints=" 61342156" NumberOfVerts="0" NumberOfLines="0" NumberOfStrips="0" NumberOfPolys=" 118579532">
<Points>
<DataArray type="Float32" NumberOfComponents="3" format="appended" offset="0"/>
</Points>
<Polys>
<DataArray type="Int32" Name="connectivity" format="appended" offset=" 736105876"/>
<DataArray type="Int32" Name="offsets" format="appended" offset=" 2159060264"/>
https://gitlab.kitware.com/paraview/paraview/-/issues/11765Python trace bug for heterogeneous multiblock datasets2020-05-26T21:29:26-04:00Kitware RobotPython trace bug for heterogeneous multiblock datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11765). Further discussion may take place here.**
---
Load a multiblock dataset with only unstructured grid leafs. Paraview see...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11765). Further discussion may take place here.**
---
Load a multiblock dataset with only unstructured grid leafs. Paraview sees a multiblock dataset containing only unstructured grid data, so it creates an unstructured grid display. Next you enable more blocks, so that multiblock dataset now contains unstructured grid and polydata leafs. Save the python trace now. The trace script records volume rendering properties of the unstructured grid display. When the trace script is replayed, paraview sees the multiblock dataset has unstructured grid and polydata leafs, so it creates a geometry display instead of an unstructured grid display. The geometry display lacks the volume rendering properties.
You could reproduce this bug using an extract block filter with an input multiblock dataset that contains unstructured grid and polydata.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/11764Deprecation of VTK XML Inline Binary Option2019-03-05T10:38:17-05:00Kitware RobotDeprecation of VTK XML Inline Binary Option**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11764). Further discussion may take place here.**
---
As we move to Large file support the inline binary option becomes less and...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11764). Further discussion may take place here.**
---
As we move to Large file support the inline binary option becomes less and less attractive. We should deprecate the ability to write and read this type of file, and instead push people to use appended compressed instead.https://gitlab.kitware.com/paraview/paraview/-/issues/11762Xdmf file with hyperslab itemtype crashes Paraview2023-06-15T08:38:35-04:00Kitware RobotXdmf file with hyperslab itemtype crashes Paraview**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11762). Further discussion may take place here.**
---
The attached file, which is supposed to cut a 2x2x2 cube out of a larger 3...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11762). Further discussion may take place here.**
---
The attached file, which is supposed to cut a 2x2x2 cube out of a larger 3x3x3 cube, causes Paraview to crash. ("*** glibc detected *** ... realloc(): invalid next size: 0x0000000008e1a800 ***")
To extract the subgrid [0,1]^3 from the larger [0,2]^3 grid, the start-stride-count in the first DataItem is set to
0 0 0
1 1 1
2 2 2
The same behavior occurs when trying to access the opposite corner [1,2]^3 (the one with values in the [8,15] range) using
1 1 1
1 1 1
2 2 2
instead. The crash can apparently be avoided using ranges whose count values are at least 3 (which should obviously be too large for the 2x2x2 target grid), and even grossly out-of-bound values such as
12 11 321
1 1 1
6 13 13
are accepted without complaints, and result in
1 2 0 3 4 0 0 0
i.e. a copy of the beginning of the source array.https://gitlab.kitware.com/paraview/paraview/-/issues/11759Prism - crash when disconnecting server.2018-08-28T09:39:51-04:00Kitware RobotPrism - crash when disconnecting server.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11759). Further discussion may take place here.**
---
Ask me for my tutorial on Prism, as well as data to run Prism.
ParaView...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11759). Further discussion may take place here.**
---
Ask me for my tutorial on Prism, as well as data to run Prism.
ParaView trunk, local server, Windows.
Disconnect. It will crash.https://gitlab.kitware.com/paraview/paraview/-/issues/11758Prism - Cube axis labels are too small2018-08-28T09:39:51-04:00Kitware RobotPrism - Cube axis labels are too small**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11758). Further discussion may take place here.**
---
Ask me for my tutorial on Prism, as well as data to run Prism.
ParaView...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11758). Further discussion may take place here.**
---
Ask me for my tutorial on Prism, as well as data to run Prism.
ParaView trunk, local server, Windows.
Turn on cube axis on the SESAME surface. Note that the labels are tiny. We need to scale it properly, and further, add the ability to modify the font size and color.