ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T09:39:46-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/13556[git/master] VisItBridge GMVReader ignores Point Array/Cell Array selection w...2023-06-15T09:39:46-04:00Kitware Robot[git/master] VisItBridge GMVReader ignores Point Array/Cell Array selection when reading tracer data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13556). Further discussion may take place here.**
---
Take the sample GMV file "gmvtest.inp" from issue 13553 that traditionally...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13556). Further discussion may take place here.**
---
Take the sample GMV file "gmvtest.inp" from issue 13553 that traditionally shipped with GMV binaries since February 2000, append file extension ".gmv".
Download nightly build ParaViewSuperbuild.
Load "gmvtest.inp.gmv" by means of the VisItBridge GMVReader.
Under "Meshes" untick "mesh", tick "tracers" instead.
Leave all entries under "Materials", "Cell Arrays" and "Point Arrays" unticked.
Apply.
=> Information panel shows that in fact all point and cell data got imported.
Additionally, an error message pops up. Most likely, because the reader tried to assign the 10 tracer cell values to the 14 cells of the unstructured grid definition.https://gitlab.kitware.com/paraview/paraview/-/issues/13555[git/master] VisItBridge GMVReader does not support reading polygonal data2023-06-15T09:39:51-04:00Kitware Robot[git/master] VisItBridge GMVReader does not support reading polygonal data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13555). Further discussion may take place here.**
---
Take the sample GMV file "gmvtest.inp" from issue 13553 that traditionally...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13555). Further discussion may take place here.**
---
Take the sample GMV file "gmvtest.inp" from issue 13553 that traditionally shipped with GMV binaries since February 2000, append file extension ".gmv".
Download nightly build ParaViewSuperbuild
Load "gmvtest.inp.gmv" by means of the VisItBridge GMVReader.
=> Only unstructured grid and tracer data can be loaded when hitting "Apply" next. The polygonal data (6 faces of an axis aligned hexaeder) is ignored.https://gitlab.kitware.com/paraview/paraview/-/issues/13548Wrong CMake dependency in Test definition2020-05-04T05:47:35-04:00Kitware RobotWrong CMake dependency in Test definition**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13548). Further discussion may take place here.**
---
Both of those test are defined in the wrong CMake location as there condit...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13548). Further discussion may take place here.**
---
Both of those test are defined in the wrong CMake location as there condition is not properly set at the first pass.
Plugins-ServerManagerPython
pvcrs.UncertaintyRendering
=== ParaViewCore/ServerManager/Default/Testing/Python/CMakeLists.txt ===
if(PARAVIEW_BUILD_PLUGIN_SurfaceLIC AND PARAVIEW_BUILD_PLUGIN_SLACTools)
list(APPEND PY_TESTS_NO_BASELINE Plugins)
endif()
=== Plugins/UncertaintyRendering/Testing/CMakeLists.txt ===
if(PARAVIEW_CLIENT_RENDER_SERVER_TESTS)
add_client_render_server_tests("pvcrs"
BASELINE_DIR ${PARAVIEW_DATA_ROOT}/Baseline
TEST_SCRIPTS ${UNCERTAINTY_RENDERING_TESTS}
)
endif()https://gitlab.kitware.com/paraview/paraview/-/issues/13399create new domain to enable/disable GUI input properties based on the number ...2020-06-09T21:24:17-04:00Kitware Robotcreate new domain to enable/disable GUI input properties based on the number of components in the selected input array**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13399). Further discussion may take place here.**
---
There should be a domain that allows an input property in the GUI to be en...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13399). Further discussion may take place here.**
---
There should be a domain that allows an input property in the GUI to be enabled/disabled based on the number of components in the selected input array. For example, the vtkGradientFilter has options to compute vorticity and Q criterion but the input array must have exactly 3 components in order to do this. It would be nice if there was an domain for these properties (ComputeVorticity, VorticityArrayName, ComputeQCriterion, and QCriterionArrayName) such that they would be enable or disabled in the GUI if the selected input array had 3 components or not, respectively.https://gitlab.kitware.com/paraview/paraview/-/issues/13392ParaView-Superbuild: Linux: We need to provide option to not build fontconfig...2020-05-04T05:45:01-04:00Kitware RobotParaView-Superbuild: Linux: We need to provide option to not build fontconfig, freetype etc.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13392). Further discussion may take place here.**
---
On Linux, we need to provide option to not build fontconfig, freetype etc....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13392). Further discussion may take place here.**
---
On Linux, we need to provide option to not build fontconfig, freetype etc. Although these are needed for full distributions, these are generally available on machines and we should just use those. https://gitlab.kitware.com/paraview/paraview/-/issues/13391ExtractHistogram filter should support vtkTable inputs2020-06-11T22:47:28-04:00Kitware RobotExtractHistogram filter should support vtkTable inputs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13391). Further discussion may take place here.**
---
ExtractHistogram filter should support vtkTable inputs. Currently, it seem...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13391). Further discussion may take place here.**
---
ExtractHistogram filter should support vtkTable inputs. Currently, it seems, it needs Dataset.https://gitlab.kitware.com/paraview/paraview/-/issues/13356change input causing problems with gui state2020-05-25T17:29:22-04:00Kitware Robotchange input causing problems with gui state**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13356). Further discussion may take place here.**
---
When right clicking (on non-mac platforms) on a filter to change its input...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13356). Further discussion may take place here.**
---
When right clicking (on non-mac platforms) on a filter to change its inputs, the gui state is wrong in that the Apply button isn't activated and neither is the Filters menu.
To reproduce the problem:
1. Create a Wavelet source -> apply
2. Create a Clip filter -> apply
3. Create a Group Datasets filter -> apply
4. Right click on GroupDatasets filter and choose Change inputs
5. Hold the control button and select both Wavelet and Clip and click on OK.
After this both the Apply button in the GroupDatasets filter and the Filters menu are disabled.https://gitlab.kitware.com/paraview/paraview/-/issues/13332pqRenderViewXXX initialization should be cleaned up2020-05-04T05:42:17-04:00Kitware RobotpqRenderViewXXX initialization should be cleaned up**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13332). Further discussion may take place here.**
---
Basically inside pqRenderView::initializeWidgets() we bind the RenderWindo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13332). Further discussion may take place here.**
---
Basically inside pqRenderView::initializeWidgets() we bind the RenderWindow with the widget where instead it should have happened in the createWidget method.
But before doing that, the bug 13331 should be fixed to prevent unwanted createWidget() call.https://gitlab.kitware.com/paraview/paraview/-/issues/13308Plot Over Line Gives Different Results When Server Is Used2020-05-04T05:41:42-04:00Kitware RobotPlot Over Line Gives Different Results When Server Is Used**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13308). Further discussion may take place here.**
---
The plot over line filter appears to give different results depending if P...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13308). Further discussion may take place here.**
---
The plot over line filter appears to give different results depending if ParaView is connected to a server or not. To connect to a server, I run "mpirun -np 3 pvserver" followed by "paraview --server=hostname". To run paraview without a server, I simply run "paraview."
The plot over line filter correctly interpolates the solution without a server running. But if I use the filter while connected to a server, the interpolation takes much longer, about 4x, for a 100 pt line and the results are incorrect. Attached are images of the plot over line filter output on the same data set.https://gitlab.kitware.com/paraview/paraview/-/issues/13288White screen on AMD Radeon HD 66702020-05-04T05:40:28-04:00Kitware RobotWhite screen on AMD Radeon HD 6670**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13288). Further discussion may take place here.**
---
White screen (no 3D view at all) on AMD Radeon HD 6670; Windows7 64-bit;
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13288). Further discussion may take place here.**
---
White screen (no 3D view at all) on AMD Radeon HD 6670; Windows7 64-bit;
Graphic Driver = AMD Catalyst 12.6 (newest)
Paraview 3.14.1 64bit
Tried all combinations of Settings of Paraview & Catalyst; all in vain.
(OpenGL issue?)
https://gitlab.kitware.com/paraview/paraview/-/issues/13278NVIDIA Quadro 2000 problems2023-07-12T22:02:21-04:00Kitware RobotNVIDIA Quadro 2000 problems**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13278). Further discussion may take place here.**
---
We’ve found graphic and memory problems working with ParaView3.14.1 on RHE...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13278). Further discussion may take place here.**
---
We’ve found graphic and memory problems working with ParaView3.14.1 on RHEL5.7 64 bit with a NVIDIA Quadro 2000 graphic card. The uploaded file report the details of this problem.https://gitlab.kitware.com/paraview/paraview/-/issues/13275Add support for negative/descending time values.2020-10-27T20:42:37-04:00Kitware RobotAdd support for negative/descending time values.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13275). Further discussion may take place here.**
---
Add support for negative/descending time values.
From user:
Using geolog...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13275). Further discussion may take place here.**
---
Add support for negative/descending time values.
From user:
Using geological time dependent data. Geological time dependent data are represented by positive numbers in million of years going from the past time to the present time using a descending order (e.g. 93 90 75 39 5.4 0). The example below shows how we can load this kind of data in ParaView. As you can see we had to associate to the time index 0 time step -93, to the time index 1 time step -90 and so on. So we need to set negative time steps in order to fit the ParaView logic used to animate time dependent data from past to present time (times must be stored in ascending order). What we would like to have is the possibility to use positive time step values (93 90 75 39 5.4 0) using a descending order and play animation starting from 93 My to 0 My.
Same problem is present for readers that support file series, where again ParaView logic works considering time in ascending order.https://gitlab.kitware.com/paraview/paraview/-/issues/13273Unstructured grid does not load, slice origin resets to 0.25,0.25,0.25 coordi...2021-03-24T15:56:30-04:00Kitware RobotUnstructured grid does not load, slice origin resets to 0.25,0.25,0.25 coordinate when loading pvsm**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13273). Further discussion may take place here.**
---
Steps needed to recreate bug.
1. Load a legacy VTK file containing an uns...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13273). Further discussion may take place here.**
---
Steps needed to recreate bug.
1. Load a legacy VTK file containing an unstructured grid
2. Create Slice
3. Toggle eye so the unstructured grid and the slices are not rendered
4. Save Paraview state file
5. Disconnect from current session
6. Load .pvsm file created above.
7. Select slice and Review data
Properties tab shows origin of 0.25,0.25,0.25
Information tab indicates number of cells/points/memory: 0/0/0 MB
8. Select unstructured grid layer and review data
Information tab indicates number of cells/points/memory: 0/0/0 MB
It appears as if the unstructured grid does not load when opening a state file if all elements associated with that layer (e.g. slices) are turned off. The user can not do any further processing or visualization of this layer or any subsequent layers.
If the same steps above are repeated, but the eyes are all toggled on before saving the state file, than everything loads correctly when opening the Paraview state file.https://gitlab.kitware.com/paraview/paraview/-/issues/13248Default behaviour for volume rendering between image and unstructured data2020-06-09T21:08:02-04:00Kitware RobotDefault behaviour for volume rendering between image and unstructured data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13248). Further discussion may take place here.**
---
PV does not support client-side volume rendering.
As a result, when run...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13248). Further discussion may take place here.**
---
PV does not support client-side volume rendering.
As a result, when running on parallel, the behaviour of volume rendering is not consistent between image and unstructured data: if the data set is small enough not make the server-side threshold, then the client only renders the outline.
From a user's perspective this is bad for at least 2 reasons:
1. The inconsistency between image and unstructured data cannot be easily figure out, and is counter-intuitive, as one would expect that the easiest case (regular grid) is handled when the hard one is not--but the opposite occurs.
2. The way to fix this behaviour requires relatively advanced knowledge of PV, and is a bad fix because it forces server-side rendering even for small data sets when this is not warranted.
Therefore I suggest that client-side VR be either never, or always (i.e., for both image and unstructured data) permitted.https://gitlab.kitware.com/paraview/paraview/-/issues/13238Problem with 1D plotting on pyramidal mesh2020-05-06T10:07:08-04:00Kitware RobotProblem with 1D plotting on pyramidal mesh**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13238). Further discussion may take place here.**
---
Hi!
I've noticed a bug in the last version of Paraview (3.14.1) on Debi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13238). Further discussion may take place here.**
---
Hi!
I've noticed a bug in the last version of Paraview (3.14.1) on Debian testing amd64. Plot over line in pyramidal mesh doesn't show me the curves (I've checked versions 3.8 and 3.12 -- they're both worked as expected).
I attached an example file. It's a simple pyramidal mesh in a flat quadratic region. Try to create a 1D plot over X-axis ({0.0,3.0}, 1.5, 0.0) and you will see the problem.
-----|-
Gena.https://gitlab.kitware.com/paraview/paraview/-/issues/13236Vertices of quadratic cells (edes, quads ..) should not be merged before rend...2021-09-09T12:51:43-04:00Kitware RobotVertices of quadratic cells (edes, quads ..) should not be merged before rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13236). Further discussion may take place here.**
---
The vertices of the quadratic cells are always merged (in vtkUnstructuredG...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13236). Further discussion may take place here.**
---
The vertices of the quadratic cells are always merged (in vtkUnstructuredGridGeometryFilter) before rendering, i.e., duplicates are removed. This is not the right behaviour. The merging should be turned off.
To test, use the following VTK legacy file description. A correct output should show the two edges in two constant colors and discontinuous at the joint vertex.
-------------------------------------------------------------
# vtk DataFile Version 2.0
Test 1 : disjoints VTK_QUADRATIC_EDGE : one vertex in common
ASCII
DATASET UNSTRUCTURED_GRID
POINTS 6 float
0 0 0
0.5 0 0
1 0 0
1 1 0
.5 0.5 0
0 0 0
CELLS 2 8
3 0 2 1
3 5 3 4
CELL_TYPES 2
21
21
POINT_DATA 6
SCALARS scalars float 1
LOOKUP_TABLE default
1.0
1.0
1.0
0.0
0.0
0.0https://gitlab.kitware.com/paraview/paraview/-/issues/13228Selecting Points with "Select Points On" from vtkUnstructuredGrid consisting ...2020-06-16T21:17:46-04:00Kitware RobotSelecting Points with "Select Points On" from vtkUnstructuredGrid consisting of vtkQuadraticTetra doesn't work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13228). Further discussion may take place here.**
---
Selecting Points with "Select Points On" from vtkUnstructuredGrid consisti...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13228). Further discussion may take place here.**
---
Selecting Points with "Select Points On" from vtkUnstructuredGrid consisting of vtkQuadraticTetra results in the following error:
ERROR: In /Source/ParaView/release/ParaView/ParaViewCore/VTKExtensions/vtkSelectionConverter.cxx, line 224
vtkSelectionConverter (0x118681b70): Could not locate the original ids arrays. Did the geometry not produce them?
https://gitlab.kitware.com/paraview/paraview/-/issues/13216create a filter to remove field data arrays2020-05-27T17:25:30-04:00Kitware Robotcreate a filter to remove field data arrays**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13216). Further discussion may take place here.**
---
For writers in general and coprocessing specifically it would be useful to...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13216). Further discussion may take place here.**
---
For writers in general and coprocessing specifically it would be useful to have a filter to remove arrays that don't need to be written out. https://gitlab.kitware.com/paraview/paraview/-/issues/13215Regression: Position of text source not restored when loading state file2023-07-11T10:56:11-04:00Kitware RobotRegression: Position of text source not restored when loading state file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13215). Further discussion may take place here.**
---
PV 3.14.1 official binaries + git/master as of today, Linux x86_64, builti...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13215). Further discussion may take place here.**
---
PV 3.14.1 official binaries + git/master as of today, Linux x86_64, builtin mode:
Sources - Text - Apply. Move text in render view to non-default position.
File - Save State - foo.pvsm - Ok
File - Disconnect
File - Load State - foo.pvsm - Ok
=> Text appears in default position again.
This used to work since ParaView 3.10.1 and still did in 3.11.0. It is broken since 3.11.1, i.e. since the day the topic 'Collaboration' got merged.
(The same issue got reported for older ParaView versions as issues 8789, 10521 and 11261.)https://gitlab.kitware.com/paraview/paraview/-/issues/13210vtkExodusIIWriter segfaults while attempting to save wavelet source2020-05-04T12:20:33-04:00Kitware RobotvtkExodusIIWriter segfaults while attempting to save wavelet source**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13210). Further discussion may take place here.**
---
Refactoring of Exodus writer in mid May 2012 has introduced a regression i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13210). Further discussion may take place here.**
---
Refactoring of Exodus writer in mid May 2012 has introduced a regression into git/master:
Sources - Wavelet - Apply
File - Save Data - File name: foo.ex2 - Files of type: Exodus II file - Ok
Ok
=> segfault in vtkExodusIIWriter.cxx:1645-1646 due to attempted array out of bounds access as 'numElts' is 0:
if (numNodes == 0)
{
numPoints = blockIter->second.EntityNodeOffsets[numElts - 1]
+ blockIter->second.EntityCounts[numElts - 1];
}
https://gitlab.kitware.com/paraview/paraview/-/issues/13209Surface LIC is distorted when using screenshot2021-03-24T16:59:07-04:00Kitware RobotSurface LIC is distorted when using screenshot**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13209). Further discussion may take place here.**
---
The LIC looks fine in the client but when File > Save Screenshot is used, ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13209). Further discussion may take place here.**
---
The LIC looks fine in the client but when File > Save Screenshot is used, the outputted image is malformed. See attached.https://gitlab.kitware.com/paraview/paraview/-/issues/13207Program crash associated with python macro2023-06-15T08:14:38-04:00Kitware RobotProgram crash associated with python macro**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13207). Further discussion may take place here.**
---
I run a simple python macro.
If I close the Layout and then I close the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13207). Further discussion may take place here.**
---
I run a simple python macro.
If I close the Layout and then I close the builtin, the program crash.
If I delete the macro before close the Layout and/or the builtin, the program crash, too.https://gitlab.kitware.com/paraview/paraview/-/issues/13203slice rep ignores dataset origin in 3.14.x in client-server mode2021-04-16T20:50:23-04:00Kitware Robotslice rep ignores dataset origin in 3.14.x in client-server mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13203). Further discussion may take place here.**
---
in past version of pv slice representation image data has been rendered wi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13203). Further discussion may take place here.**
---
in past version of pv slice representation image data has been rendered with dataset positioned in the scene at it's origin. this changed in 3.14 where in the dataset origin is ignored and the dataset is rendered at 0,0,0. The following datasets illustrate. d1 has an origin of 0,0 spacing of 1,1 and extent is 20 30 20 30, while d2 has an origin of 20 30 spacing of 1,1 and an extent of 0 10 0 10. These should be rendered in the same location, however they are not. Changing from slice to another representation fixes the issue. this only happens in client server mode.https://gitlab.kitware.com/paraview/paraview/-/issues/13189inconsistent cuts from cells with a non-planar quad face2020-05-04T05:18:41-04:00Kitware Robotinconsistent cuts from cells with a non-planar quad face**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13189). Further discussion may take place here.**
---
When a cell has a non-planar face it can give a different cut depending on...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13189). Further discussion may take place here.**
---
When a cell has a non-planar face it can give a different cut depending on the normal (see image). Either could be considered correct but I would consider it a bug that it is not consistent for the same cell.
To reproduce use a "Programmable Source" that outputs vtkUnstructuredGrid with the following script:
8<---------------------------------------------
output = self.GetOutput()
npts = 5
pts = vtk.vtkPoints()
pts.InsertNextPoint(-1.0, -1.0, -1.0)
pts.InsertNextPoint( 1.0, -1.0, -0.5)
pts.InsertNextPoint( 1.0, 1.0, -1.0)
pts.InsertNextPoint(-1.0, 1.0, -0.5)
pts.InsertNextPoint( 0.0, 0.0, 1.0)
output.SetPoints(pts)
output.Allocate(1,1)
ids = vtk.vtkIdList()
for i in range(npts):
ids.InsertId(i,i)
output.InsertNextCell(vtk.VTK_PYRAMID, ids)
--------------------------------------------->8
Now apply "Slice" for Origin (0,0,-0.75) and try Normal of (0,0,-1) and (0,0,1). The output will be different depending on the direction.
https://gitlab.kitware.com/paraview/paraview/-/issues/13185EnSight file reader (*.case) doesn't work properly in parallel2021-04-29T19:15:33-04:00Kitware RobotEnSight file reader (*.case) doesn't work properly in parallel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13185). Further discussion may take place here.**
---
Hi all,
As you can see in the image I've attached, when I loaded my EnSig...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13185). Further discussion may take place here.**
---
Hi all,
As you can see in the image I've attached, when I loaded my EnSight file using standalone ParaView, it worked. Using paraview + pvserver (MPI) it didn't work.
It seems EnSight Reader has some problem when Paraview runs parallel.
Any ideas to solve this problem? Actually, that error is blocking my work now...
Hope somebody can help me.
Thanks in advance.https://gitlab.kitware.com/paraview/paraview/-/issues/13173Painter can report wrong bounds on first check2020-05-04T05:17:20-04:00Kitware RobotPainter can report wrong bounds on first check**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13173). Further discussion may take place here.**
---
When the Renderer first calls ComputeVisiblePropBounds, the poly data pain...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13173). Further discussion may take place here.**
---
When the Renderer first calls ComputeVisiblePropBounds, the poly data painter mapper calls ComputeBounds on its painter, but this happens the first time before setInput has been called on the painter.
This patch fixes it.https://gitlab.kitware.com/paraview/paraview/-/issues/13166stl reader expects characters after endsolid2023-07-07T16:25:49-04:00Kitware Robotstl reader expects characters after endsolid**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13166). Further discussion may take place here.**
---
(I think in)
ParaView-3.14.0-Source/VTK/IO/vtkSTLReader.cxx line 432 it ex...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13166). Further discussion may take place here.**
---
(I think in)
ParaView-3.14.0-Source/VTK/IO/vtkSTLReader.cxx line 432 it explicitly checks for additional characters (fgets) after reading ENDSOLID.
(this check is fine in the SOLID reading block but I don't think it should be in the ENDSOLID)https://gitlab.kitware.com/paraview/paraview/-/issues/13138dataserver+renderserver not able to process data2021-03-29T21:23:08-04:00Kitware Robotdataserver+renderserver not able to process data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13138). Further discussion may take place here.**
---
I run dataserver and renderserver (in simplest case on same machine, but i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13138). Further discussion may take place here.**
---
I run dataserver and renderserver (in simplest case on same machine, but in production we will use cluster for data processing and a few servers to show rendered results) at linux server (cenos 5.7). And connect to them by remote client (linux workstation).
After connection i may see on display of renderserver Paraview screen and may rotate axis.
When i try to add some object in client (sphere, for example) and press apply button nothing changed on renderserver display, but client hangs and not able to do anything.
tcpdump shows that after client connection data and render server not send any data to each other due to client disconnect.
In case of using pvserver instead of pvdataserver+pvrenderserver all works fine.https://gitlab.kitware.com/paraview/paraview/-/issues/13128Tile full screen does not switch between 3D and charts2019-04-24T20:28:54-04:00Kitware RobotTile full screen does not switch between 3D and charts**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13128). Further discussion may take place here.**
---
We observed some issues where the tiles do not switch between rendering th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13128). Further discussion may take place here.**
---
We observed some issues where the tiles do not switch between rendering the 3D display and the charts as expected. This was on master with the scatter-plot-matrix-pc branch during testing of 2x2 arrays (Linux 64 bit with nVidia binary driver).https://gitlab.kitware.com/paraview/paraview/-/issues/13115Memory leaks in StreamTracer2020-05-06T10:53:23-04:00Kitware RobotMemory leaks in StreamTracer**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13115). Further discussion may take place here.**
---
Leaks are reported when the test StreamTracerUpdates is run in parallel.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13115). Further discussion may take place here.**
---
Leaks are reported when the test StreamTracerUpdates is run in parallel.https://gitlab.kitware.com/paraview/paraview/-/issues/13113PV crashes with little endian client / big endian server setup2019-05-23T17:23:56-04:00Kitware RobotPV crashes with little endian client / big endian server setup**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13113). Further discussion may take place here.**
---
I get crashes with the following little endian client / big endian server ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13113). Further discussion may take place here.**
---
I get crashes with the following little endian client / big endian server setup:
Client:
Mac OS X 10.6.8 (Intel)
PV 3.14.1 OS X 64-bit binary downloaded from Kitware
Server:
Fujitsu FX10 (SPARC64 IXfx)
PV 3.14.1 cross-compiled on x86-64 Linux with CMake 2.8.7, FCCpx compiler
Server error messages:
mpiexec ~/fx/20120415/bin/pvserver --use-offscreen-rendering
Waiting for client...
Connection URL: cs://xxxxx:11111
Accepting connection(s): xxxxx:11111
Client connected.
[xxxxx:12678] *** Process received signal ***
[xxxxx:12678] Signal: Bus error (10)
[xxxxx:12678] Signal code: Invalid address alignment (1)
[xxxxx:12678] Failing at address: 0x214037b1
[xxxxx:12678] [ 0] /opt/FJSVxosmmm/lib64/libmpgpthread.so.1(_IO_funlockfile+0x5c) [0xffffffff20809974]
[xxxxx:12678] [ 1] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkParallel.so.pv3.14(_ZN21vtkMultiProcessStream12vtkInternals9SwapBytesEv+0x1e4) [0xffffffff06783b64]
[xxxxx:12678] [ 2] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkParallel.so.pv3.14(_ZN21vtkMultiProcessStream10SetRawDataEPKhj+0x440) [0xffffffff06778b80]
[xxxxx:12678] [ 3] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkPVServerImplementation.so(_ZN18vtkPVSessionServer24OnClientServerMessageRMIEPvi+0x18) [0xffffffff008aec98]
[xxxxx:12678] [ 4] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkPVServerImplementation.so(_ZN46_GLOBAL__N__22_vtkPVSessionServer_cxx_cc8ff48111RMICallbackEPvS0_ii+0xc) [0xffffffff008ac5cc]
[xxxxx:12678] [ 5] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkParallel.so.pv3.14(_ZN25vtkMultiProcessController10ProcessRMIEiPvii+0x3f0) [0xffffffff0676c8b0]
[xxxxx:12678] [ 6] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkParallel.so.pv3.14(_ZN25vtkMultiProcessController11ProcessRMIsEii+0x210) [0xffffffff0676bfd0]
[xxxxx:12678] [ 7] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkPVClientServerCore.so(_ZN26vtkTCPNetworkAccessManager21ProcessEventsInternalEmb+0x3c4) [0xffffffff01116f44]
[xxxxx:12678] [ 8] /xxxxx/fx/20120415/lib/paraview-3.14/libvtkPVClientServerCore.so(_ZN26vtkTCPNetworkAccessManager13ProcessEventsEm+0xc) [0xffffffff01116b4c]
[xxxxx:12678] [ 9] /xxxxx/fx/20120415/lib/paraview-3.14/pvserver [0x102440]
[xxxxx:12678] [10] /xxxxx/fx/20120415/lib/paraview-3.14/pvserver(main+0xc) [0x10250c]
[xxxxx:12678] [11] /lib64/libc.so.6(__libc_start_main+0x194) [0xffffffff2118b81c]
[xxxxx:12678] [12] /xxxxx/fx/20120415/lib/paraview-3.14/pvserver(_start+0x2c) [0x10206c]
[xxxxx:12678] *** End of error message ***
[ERR.] PLE 0017 plexec The process terminated with the signal.(rank=0)(nid=0x01040006)(sig=10)
Client error messages:
> /Applications/ParaView\ 3.14.1.app/Contents/MacOS/paraview
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55627
ERROR: In /Source/ParaView/release/ParaView/ParaViewCore/ServerManager/vtkSMSessionClient.cxx, line 774
vtkSMSessionClient (0x10c6bc1f0): Server failed to gather information.
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55627
ERROR: In /Source/ParaView/release/ParaView/ParaViewCore/ServerManager/vtkSMSessionClient.cxx, line 774
vtkSMSessionClient (0x10c6bc1f0): Server failed to gather information.
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55627
ERROR: In /Source/ParaView/release/ParaView/ParaViewCore/ServerManager/vtkSMSessionClient.cxx, line 774
vtkSMSessionClient (0x10c6bc1f0): Server failed to gather information.
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55629
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55629
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55628
libprotobuf ERROR /Source/ParaView/release/ParaView/Utilities/protobuf/src/google/protobuf/message_lite.cc:123] Can't parse message of type "paraview_protobuf.Message" because it is missing required fields: global_id, location
ERROR: In /Source/ParaView/release/ParaView/ParaViewCore/ServerManager/vtkSMProxy.cxx, line 1874
vtkSMPluginLoaderProxy (0x11be90290): Try to load a state on a proxy which has a different ID(1 != 0)
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55628
libprotobuf ERROR /Source/ParaView/release/ParaView/Utilities/protobuf/src/google/protobuf/message_lite.cc:123] Can't parse message of type "paraview_protobuf.Message" because it is missing required fields: global_id, location
ERROR: In /Source/ParaView/release/ParaView/VTK/Parallel/vtkSocketCommunicator.cxx, line 812
vtkSocketCommunicator (0x10d88b820): Could not receive tag. 55627
ERROR: In /Source/ParaView/release/ParaView/ParaViewCore/ServerManager/vtkSMSessionClient.cxx, line 774
vtkSMSessionClient (0x10c6bc1f0): Server failed to gather information.
https://gitlab.kitware.com/paraview/paraview/-/issues/13099Glyph filter fails on parallel files with Mask Points and Random Mode2020-06-09T21:26:37-04:00Kitware RobotGlyph filter fails on parallel files with Mask Points and Random Mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13099). Further discussion may take place here.**
---
On parallel files (PVTU), if Mask Points is active the random mode is not ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13099). Further discussion may take place here.**
---
On parallel files (PVTU), if Mask Points is active the random mode is not equally balanced between parallel parts.
As a consequence, there is a big density of glyphs in some parts on the domain, and none in some other parts.
This was not the case in previous versions (tested up to 3.12)
Attached screenshots were done on the same result file in paraview 3.8.1 and 3.14.1https://gitlab.kitware.com/paraview/paraview/-/issues/13094Interactive Lightsource Rotation in Qt Client2020-06-11T18:50:20-04:00Kitware RobotInteractive Lightsource Rotation in Qt Client**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13094). Further discussion may take place here.**
---
PROBLEM:
Changing light direction vector requires manual typing values in...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13094). Further discussion may take place here.**
---
PROBLEM:
Changing light direction vector requires manual typing values in dialog. Much more intuitive method would be to use interactive mouse tracking in 3D view.
SOLUTION:
Patch supplied to implement interactive light vector rotation.
patched files: vtkPVTrackballRotate.cxx, vtkRenderer.[h,cxx], pqComponents.qrc, pqCameraToolbar.ui, pqStandardViewFrameActionGroup.cxx, pqCameraToolbar.[h,cxx], pqTrackLight24.png
action: copy vtkPVTrackballRotate.cxx to ParaView-3.14.0/ParaViewCore/VTKExtensions
copy vtkRenderer.[h,cxx] to ParaView-3.14.0/VTK/Rendering
copy pqComponents.qrc to ParaView-3.14.0/Qt/Components/Resources
copy pqCameraToolbar.ui to ParaView-3.14.0/Qt/ApplicationComponents/Resources/UI
copy pqCameraToolbar.[h,cxx] to ParaView-3.14.0/Qt/ApplicationComponents
copy pqTrackLight24.png to ParaView-3.14.0/Qt/Components/Resources/Icons
DESCRIPTION:
Complex geological surfaces and terrains, are often best shown at certain oblique lighting angles, so interactive discovery of best angle is needed. This patch allows user to rotate currently used light sources, in the ParaView scene by using "Track light" option from "Camera Controls" toolbar, and perform their surface investigation with optimally set lighting.
CHANGES: To make this patch, following changes were made (ParaView source patch):
- vtkRenderer.h - Added boolean mTrackLight property to vtkRenderer class and its inspector and mutator routines,
- vtkRenderer.cxx - Added initializing of mTrackLight property at the end of vtkRenderer's constructor routine,
- pqComponents.qrc - Added icon file pqTrackLight24.png to resource file,
- pqCameraToolbar.ui - Added action definition to camera toolbar resource definition file,
- pqCameraToolbar.h - Added onTrackLight() slot routine called whenever "Track Light" toolbar option is selected / deselected,
- pqCameraToolbar.cxx - Added onTrackLight() definition in which is set current renderer's TrackLight flag to state of
"Track Light" toolbar option,
- vtkPVTrackballRotate.cxx - Added new logic of processing mouse move actions in vtkPVTrackballRotate::OnMouseMove()
routine to support when "Track Light" of currently active renderer is turned on.
https://gitlab.kitware.com/paraview/paraview/-/issues/13092Environment Variables in Statefile Data paths, Missing data visual indicator,...2020-05-27T17:15:38-04:00Kitware RobotEnvironment Variables in Statefile Data paths, Missing data visual indicator, scroll long lists**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13092). Further discussion may take place here.**
---
PROBLEM:
Saved state files are written with full data paths, requiring ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13092). Further discussion may take place here.**
---
PROBLEM:
Saved state files are written with full data paths, requiring adjustment if moved. No visible indication if reloaded data paths are valid. If 10+ data files in state file, list becomes too long for screen size, no scrolling facility.
SOLUTION:
Add environment variable support in data path names, making state files portable. Add visual RED/GREEN indicated for valid data paths, add Qt scrollbar.
PATCH:
patched files: pqFixStateFilenamesDialog.[h,cxx], vtkSMStateLoader.cxx
action: copy pqFixStateFilenamesDialog to ParaView-3.14.0\Qt\Components
copy vtkSMStateLoader to ParaView-3.14.0\ParaViewCore\ServerManager
DESCRIPTION: State files with filenames often require to be updated with locations of used files on new machine. Our
patch makes this process easier and faster by allowing pathnames to contain environment variables and by adding
indicators to "Fix Paths in State File" dialog about missing filename or directory. Also, scrolling area is added
to the dialog to handle cases if there is large number of input files specified in state file. In case of environment
variables, supported syntax is %VAR_NAME%, ${VAR_NAME} and $VAR_NAME. In the latest case ($VAR_NAME), VAR_NAME must be
from [a-zA-Z0-9_-]+ language. Beside each filename box in "Fis Paths in State File" dialog is added indicator which
when its green, currently specified file / directory is found on current machine. If it is yellow, it should be checked
because algorithm was unable to check if it is semantically correct, and if it is red, user shoud double-check and
possibly replace content of appropriate text-box. Also, if environment variables are present, they are replaced with
its content (value).
CHANGES: To make this patch, following changes were made (ParaView source patch):
- QMap<pqFileChooserWidget*, QLabel*> IndicatorsMappings parameters is added to pqFixStateFilenamesDialog
class declaration in pqFixStateFilenamesDialog.h,
- QMap, pqFileChooserWidget and QLabel classes are included at the beginning of pqFixStateFilenamesDialog.h,
- At the beginning of the file pqFixStateFilenamesDialog.cxx, new function is added SetIndicator() which
initializes indicator's color for passed content of text-box,
- At the beginning of the file pqFixStateFilenamesDialog.cxx, new function is added ResolveEnvironmentVariables()
which replaces environment variables from input strings with environment variable's contents,
- In pqFixStateFilenamesDialog class constructor, ResolveEnvironmentVariables() is called to resolve environment
variables in every path,
- In pqFixStateFilenamesDialog class constructor, QScrollArea is added and populated by group-boxes,
- In pqFixStateFilenamesDialog class constructor, IndicatorsMappings table is populated and indicators are
initialized and
- In pqFixStateFilenamesDialog::onFileNamesChanged() is added logic for setting indicator green if file exists
or red if file doesn't exist.
- Added ResolveEnvironmentVariables() and TraverseTree() routines at the beginning of vtkSMStateLoader.cxx. Also
added calling of TraverseTree() in vtkSMStateLoader::LoadStateInternal() routine.
https://gitlab.kitware.com/paraview/paraview/-/issues/13075Change display properties of multiple images simultaneously2020-06-09T21:25:50-04:00Kitware RobotChange display properties of multiple images simultaneously**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13075). Further discussion may take place here.**
---
It would be very helpful to be able to select multiple objects in the pipe...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13075). Further discussion may take place here.**
---
It would be very helpful to be able to select multiple objects in the pipeline browser and change their display properties simultaneously.
E.g. select two images, change representation to Slice, change slice #, and set to visible, and have it apply to both of the images. Right now, if this workflow is followed only one of the images has the display properties changed.https://gitlab.kitware.com/paraview/paraview/-/issues/13067extent information is causing problems in coprocessing2023-06-15T11:09:17-04:00Kitware Robotextent information is causing problems in coprocessing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13067). Further discussion may take place here.**
---
When using the vtkPVTrivialProducer() for structured data sets there are p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13067). Further discussion may take place here.**
---
When using the vtkPVTrivialProducer() for structured data sets there are problems with the pipeline information. Run the attached script with pvpython to see the errors.Julien FaustyJulien Faustyhttps://gitlab.kitware.com/paraview/paraview/-/issues/13058VPIC reader crashes since pv 3.12.02020-06-11T20:28:22-04:00Kitware RobotVPIC reader crashes since pv 3.12.0**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13058). Further discussion may take place here.**
---
changes introduced between 3.10.0 and 3.12.0 result in VPIC reader crashin...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13058). Further discussion may take place here.**
---
changes introduced between 3.10.0 and 3.12.0 result in VPIC reader crashing. steps to reproduce: open a vpic dataset with pv version 3.12.0 or newer. VPIC reader needs regression test.https://gitlab.kitware.com/paraview/paraview/-/issues/13053Destroy XYChartViews will crash on Windows debug builds2021-03-24T18:16:53-04:00Kitware RobotDestroy XYChartViews will crash on Windows debug builds**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13053). Further discussion may take place here.**
---
With Windows (win7 VS9) debug build, start paraview, create any xychartvie...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13053). Further discussion may take place here.**
---
With Windows (win7 VS9) debug build, start paraview, create any xychartviews (bar chart or line plot), then close paraview, it will crash at
//----------------------------------------------------------------------------
unsigned long vtkSubjectHelper::GetTag(vtkCommand* cmd)
{
--> vtkObserver *elem = this->Start; // Crash
This seems only to happen with debug build, because the pv chart tests are ok on nightly dashboards.https://gitlab.kitware.com/paraview/paraview/-/issues/13052The paraview.vtk python module is different than the standard vtk python module2020-05-04T05:06:58-04:00Kitware RobotThe paraview.vtk python module is different than the standard vtk python module**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13052). Further discussion may take place here.**
---
The paraview.vtk module is located in the build directory:
Utilities/VT...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13052). Further discussion may take place here.**
---
The paraview.vtk module is located in the build directory:
Utilities/VTKPythonWrapping/site-packages/paraview/vtk
This vtk module is different than the standard vtk module, located in the build directory:
VTK/Wrapping/Python/vtk
Importing these modules yields different functionality, meaning that a script that works for vtkpython probably doesn't work in pvpython.https://gitlab.kitware.com/paraview/paraview/-/issues/13051Slow Rendering Performance when using OpenGL (Hardware Rendering) and MPI2020-05-04T10:30:01-04:00Kitware RobotSlow Rendering Performance when using OpenGL (Hardware Rendering) and MPI**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13051). Further discussion may take place here.**
---
Summery:
When using ParaView in parallel with either MVAPICH2 or OpenMPI...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13051). Further discussion may take place here.**
---
Summery:
When using ParaView in parallel with either MVAPICH2 or OpenMPI and hardware rendering (nVidia Quadro 5000/6000, Tesla C2050 tested), rendering performance drops significantly. Problem reproduced using a VTK test program and when running on a single node with MPI simply linked to the executable (no composting occurring).
Notes:
1) Have ruled out composting as the issue by running on one node with MPI simply linked but not invoked (no mpirun or mpiexec called).
2) No X forwarding or Mesa in play on the systems exhibiting this issue.
3) Immediate mode rendering toggled on and off with no effect when test data set loaded into PV GUI.
To Reproduce:
1) Build ParaView w\ MPI support and OpenGL support for the installed graphics card.
2) Issue a pvbatch job with timer logs to capture run time. Recompile PV w/o MPI and re-time.
3) Convert the pvbatch job to a VTK C++ program. Link against vtkRendering and time execution. Relink program against vtkParallel and time execution.
Results Seen (VTK Program w\ MPI and 4 million triangles):
HP DL585 compute node w\ Quadro 5000, MVAPICH2: ~10 fps
HP Z800 workstation w\ Quadro 6000, OpenMPI: ~4 fps
HP Z800 workstation w\ Tesla C2050, OpenMPI: ~2.5 fps
Results w/o MPI Linked for DL585 Compute Node, 4 million triangles: ~114 fps
https://gitlab.kitware.com/paraview/paraview/-/issues/13047Java wrapping for ParaViewCore and support for ParaView rendering in Eclipse ...2020-05-07T21:42:42-04:00Kitware RobotJava wrapping for ParaViewCore and support for ParaView rendering in Eclipse SWT windows**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13047). Further discussion may take place here.**
---
* Use VTK Java wrapping to wrap the classes in ParaViewCore, specifically ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13047). Further discussion may take place here.**
---
* Use VTK Java wrapping to wrap the classes in ParaViewCore, specifically the classes in ServerManager, to allow ParaView server to be controlled from Java programs.
* Use SWIG (Simplified Wrapper and Interface Generator) to bridge C++ and Java and create a class that permits vtkSMRenderViewProxy to display an interactive render window inside of an Eclipse SWT (Standard Widget Toolkit) window. https://gitlab.kitware.com/paraview/paraview/-/issues/13046Selection tools don't work for images2020-06-29T20:47:02-04:00Kitware RobotSelection tools don't work for images**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13046). Further discussion may take place here.**
---
If I open an image, the "Select points through" type of tools are disabled...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13046). Further discussion may take place here.**
---
If I open an image, the "Select points through" type of tools are disabled. It seems like you should be able to select a rectangular region of an image the same way you would select any other type of points. The benefit is the ability to select and extract a region and then rescale the colors so that the local variation in the region can be more easily interpreted.https://gitlab.kitware.com/paraview/paraview/-/issues/13045Clip on Extract Subset crashes when Extract Subset reduces to a surface2021-03-29T21:39:20-04:00Kitware RobotClip on Extract Subset crashes when Extract Subset reduces to a surface**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13045). Further discussion may take place here.**
---
- Load a structured IJK domain (Tecplot reader or else), indexes I = 0 to ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13045). Further discussion may take place here.**
---
- Load a structured IJK domain (Tecplot reader or else), indexes I = 0 to Imax, J = 0 to Jmax and K = 0 to Kmax
- Add the "Extract subset" filter to get the surface J=0, so subset indexes are I = 0 to Imax, J = 0 to 0 and K = 0 to Kmax
- Add the "Clip" filter with plane Z=something or else => paraview crashes !!!
Workaround: after the "Extract Subset" filter, add the "Extract Surfaces" filter, then the "Clip" filter and clipping is OK !https://gitlab.kitware.com/paraview/paraview/-/issues/13043EnSight Gold nsided elements cause segmentation fault2021-03-24T18:31:43-04:00Kitware RobotEnSight Gold nsided elements cause segmentation fault**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13043). Further discussion may take place here.**
---
the following test case taken from the EnSight Gold documentation causes ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13043). Further discussion may take place here.**
---
the following test case taken from the EnSight Gold documentation causes ParaView 3.14 to crash when clipping.https://gitlab.kitware.com/paraview/paraview/-/issues/13026Static builds of ParaView fail to build external applications2020-05-04T05:02:07-04:00Kitware RobotStatic builds of ParaView fail to build external applications**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13026). Further discussion may take place here.**
---
Refer to the thread:
http://www.paraview.org/pipermail/paraview/2012-Marc...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13026). Further discussion may take place here.**
---
Refer to the thread:
http://www.paraview.org/pipermail/paraview/2012-March/024452.htmlhttps://gitlab.kitware.com/paraview/paraview/-/issues/13023Integrate filter yields different results in client-server mode2021-03-29T21:34:33-04:00Kitware RobotIntegrate filter yields different results in client-server mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13023). Further discussion may take place here.**
---
Using the integrate filter to integrate variables over the volume yields d...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13023). Further discussion may take place here.**
---
Using the integrate filter to integrate variables over the volume yields different results when running in client-server mode with different numbers of server nodes. The results are also changed by integrating after applying the D3 filter.https://gitlab.kitware.com/paraview/paraview/-/issues/13014Missing libraries with INSTALL_THIRD_PARTY_LIBRARIES is set2020-05-25T22:01:10-04:00Kitware RobotMissing libraries with INSTALL_THIRD_PARTY_LIBRARIES is set**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13014). Further discussion may take place here.**
---
The Qt libraries are not installed when building with nmake on windows.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13014). Further discussion may take place here.**
---
The Qt libraries are not installed when building with nmake on windows.https://gitlab.kitware.com/paraview/paraview/-/issues/12995Find Data not working on tables2020-06-11T21:07:19-04:00Kitware RobotFind Data not working on tables**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12995). Further discussion may take place here.**
---
Using the csv file attached I have tried "Query is" and "foo==2" but it do...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12995). Further discussion may take place here.**
---
Using the csv file attached I have tried "Query is" and "foo==2" but it doesn't work. Am I doing something wrong is it not supported?https://gitlab.kitware.com/paraview/paraview/-/issues/12977Add support multi-configurations to fix library links in plugin2023-06-15T08:04:44-04:00Kitware RobotAdd support multi-configurations to fix library links in plugin**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12977). Further discussion may take place here.**
---
The current ParaView build only can fixup library links correctly with Rel...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12977). Further discussion may take place here.**
---
The current ParaView build only can fixup library links correctly with Release configuartion by MSVC compiler in Windows box.
Because the plugin library has located in ${EXECUTABLE_OUTPUT_PATH}/${CMAKE_INSTALL_CONFIG_NAME} folder if use MSVC IDE to compile, and located in ${EXECUTABLE_OUTPUT_PATH} folder if use NMAKE.
Attached please found my patch to support multi-configurations that compiling by MSVC IDE and all configurations that compiling by NMAKE tool.https://gitlab.kitware.com/paraview/paraview/-/issues/12961Add image overlay, similar to text source2020-06-09T21:53:19-04:00Kitware RobotAdd image overlay, similar to text source**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12961). Further discussion may take place here.**
---
It would be nice to be able to show an image overlay on a render view, for...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12961). Further discussion may take place here.**
---
It would be nice to be able to show an image overlay on a render view, for instance to show add a logo to a figure. The functionality I have in mind would be similar to a Text source that can be added by Sources --> Text, and positioned using the window location. Additionally, it would allow the user to resize the image.https://gitlab.kitware.com/paraview/paraview/-/issues/12957Rendering bug with Gaussian Resampling filter2020-05-11T22:25:12-04:00Kitware RobotRendering bug with Gaussian Resampling filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12957). Further discussion may take place here.**
---
1) Start ParaView 3.12.0.
2) Source -> Wavelet -> Apply
3) Filters -...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12957). Further discussion may take place here.**
---
1) Start ParaView 3.12.0.
2) Source -> Wavelet -> Apply
3) Filters -> Alphabetical -> Gaussian Resampling -> Apply
4) Representation Toolbar -> Surface
What happens: only a small corner of the cube I expect to see is visible.
I have reproduced this bug on both the pre-compiled 64-bit Windows and 64-bit Linux versions of ParaView. It has been confirmed on MacOSX as well. I also reproduced it with Win/64/3.14.0-RC2.
https://gitlab.kitware.com/paraview/paraview/-/issues/12949Segfault setting options in 2D view2020-05-20T21:15:20-04:00Kitware RobotSegfault setting options in 2D view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12949). Further discussion may take place here.**
---
To reproduce this (no data needs to be loaded in):
Start ParaView
Chan...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12949). Further discussion may take place here.**
---
To reproduce this (no data needs to be loaded in):
Start ParaView
Change to 2D view
Change an option and apply (e.g show axis)
Change to 3D view
Change back to 2D view
Change an option and apply (e.g show axis)
The segmentation fault happens when apply is clicked.https://gitlab.kitware.com/paraview/paraview/-/issues/12911Wrong "update extent" specified in output's informtation after modifying the ...2021-04-29T20:07:35-04:00Kitware RobotWrong "update extent" specified in output's informtation after modifying the extent inside RequestData**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12911). Further discussion may take place here.**
---
I've managed to run a Paraview based application created with Paraview
3.8...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12911). Further discussion may take place here.**
---
I've managed to run a Paraview based application created with Paraview
3.8.1 using Paraview 3.12, but one of my filters is reporting an error
it didn't before.
My vtkAlgorithm is a sub-class of vtkImageAlgorithm, which as a result
of processing the input data generates a new vtkImageData which is
smaller than the original one.
Using Paraview 3.8.1 I managed to use that filter in my application, but now after updating to Paraview 3.12 I get
the following error:
ERROR: src/ParaView-3.12.0/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx,
line 1009
vtkPVCompositeDataPipeline (0x4c3dca0): The update extent specified in
the information for output port 0 on algorithm
vtkConnectedThresholdImageFilter(0x4c3c8d0) is 0 698 0 535 0 114,
which is outside the whole extent 408 421 86 106 0 1.
Inside my RequestData I've tried changing all possible combinations of
whole extent, update extent and extent for both output and
outputInformation without success.
I attach the vtkAlgorithm which I used with PV3.8.1https://gitlab.kitware.com/paraview/paraview/-/issues/12887TimeKeeper in 3.12 doesn't seem to work properly2020-11-09T19:40:48-05:00Kitware RobotTimeKeeper in 3.12 doesn't seem to work properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12887). Further discussion may take place here.**
---
On the Animation View in "Sequence" (or "Real Time") mode, I'm not able to...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12887). Further discussion may take place here.**
---
On the Animation View in "Sequence" (or "Real Time") mode, I'm not able to use the "TimeKeeper - Time" track to decouple animation from data time. Animation over time-varying data goes anyway, no matter what sequence you define.
It works well in 3.10
I use ParaView for Windows x64https://gitlab.kitware.com/paraview/paraview/-/issues/12886additional erroneous focus point2020-10-27T20:41:22-04:00Kitware Robotadditional erroneous focus point**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12886). Further discussion may take place here.**
---
I animate camera in an orbit mode. I save a session. I delete everything. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12886). Further discussion may take place here.**
---
I animate camera in an orbit mode. I save a session. I delete everything. I re-load the state. Camera has one extra (erroneous) focus point that results in a different animation when saved. Removing this point restores the intended motion.https://gitlab.kitware.com/paraview/paraview/-/issues/12869Feature request: Make coprocessing scripts not to recreate proxies on each ca...2021-03-23T10:38:36-04:00Kitware RobotFeature request: Make coprocessing scripts not to recreate proxies on each call to DoCoProcessing**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12869). Further discussion may take place here.**
---
The current implementation of coprocessing scripts re-creating proxies on ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12869). Further discussion may take place here.**
---
The current implementation of coprocessing scripts re-creating proxies on each call to DoCoProcessing incurs extra setup/teardown processes and unreclaimed memory usage that is not easy to be tracked down. We should be able to keep the proxies alive and re-used on each DoCoProcessing call.
The issue is discussed here: http://markmail.org/message/aajj2c7hwiukdrxohttps://gitlab.kitware.com/paraview/paraview/-/issues/12868Changing time after deleting a layout crashes ParaView2020-05-04T22:05:16-04:00Kitware RobotChanging time after deleting a layout crashes ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12868). Further discussion may take place here.**
---
Git-master, OS X 10.6.8, Qt 4.7.2.
1. Start PV.
2. Sources->Wavelet. App...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12868). Further discussion may take place here.**
---
Git-master, OS X 10.6.8, Qt 4.7.2.
1. Start PV.
2. Sources->Wavelet. Apply.
3. Click the + button at the top of the graphics view to open Layout #2.
4. Click the eye icon at the left of the Wavelet source in the pipeline browser to make it visible.
5. Click "X" in the Layout #2 tab to delete the layout.
6. Click Next Frame.
Then ParaView crashes.https://gitlab.kitware.com/paraview/paraview/-/issues/12867Coprocessing export state from layout #2 crashes ParaView2020-05-04T04:35:04-04:00Kitware RobotCoprocessing export state from layout #2 crashes ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12867). Further discussion may take place here.**
---
Git-master as of today, OS X 10.6.8, Qt 4.7.2.
1. Start PV.
2. Load Copr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12867). Further discussion may take place here.**
---
Git-master as of today, OS X 10.6.8, Qt 4.7.2.
1. Start PV.
2. Load Coprocessing plugin.
3. Click the + button at the top of the graphics view to open Layout #2.
4. Sources->Wavelet. Apply.
5. Coprocessing->Export State.
Then PV crashes leaving the following message on the terminal.
ERROR: In /Volumes/RAID0data/paraview/ParaView/VTK/Filtering/vtkDemandDrivenPipeline.cxx, line 727
vtkCompositeDataPipeline (0x123aa5bb0): Input port 0 of algorithm vtkPNGWriter(0x123aa5050) has 0 connections but is not optional.
ERROR: In /Volumes/RAID0data/paraview/ParaView/VTK/IO/vtkPNGWriter.cxx, line 54
vtkPNGWriter (0x123aa5050): Write:Please specify an input!
Segmentation fault
https://gitlab.kitware.com/paraview/paraview/-/issues/12864Building ParaView with VTK_USE_SYSTEM_HDF5 =ON fails when HDF5 in not install...2020-05-04T22:06:12-04:00Kitware RobotBuilding ParaView with VTK_USE_SYSTEM_HDF5 =ON fails when HDF5 in not installed globally.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12864). Further discussion may take place here.**
---
The problem appears to be that HDF5_INCLUDE_DIR is not set correctly in Pa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12864). Further discussion may take place here.**
---
The problem appears to be that HDF5_INCLUDE_DIR is not set correctly in ParaViewCommon.cmake.
<begin snippet>
#########################################################################
# Configure HDF5
IF(VTK_USE_SYSTEM_HDF5)
SET(PARAVIEW_HDF5_LIBRARIES ${VTK_HDF5_LIBRARIES})
SET(HDF5_INCLUDE_DIR ${VTK_HDF5_INCLUDE_DIRS})
ELSE()
...
ENDIF()
<end snippet>
It seems to be using a VTK_HDF5_INCLUDE_DIRS variable that's never set, it seems.https://gitlab.kitware.com/paraview/paraview/-/issues/12861Unable to ask for user input from within ParaView Python macro2023-06-15T09:16:05-04:00Kitware RobotUnable to ask for user input from within ParaView Python macro**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12861). Further discussion may take place here.**
---
In ParaView 3.8.1, it was possible to write a Python macro that asked the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12861). Further discussion may take place here.**
---
In ParaView 3.8.1, it was possible to write a Python macro that asked the user for input with a dialog window. This was done with the following simple code:
import PyQt4.QtGui
(ret, ok) = PyQt4.QtGui.QInputDialog.getInt(
PyQt4.QtGui.QWidget(), 'T', 'L')
if not ok:
raise Exception('input error')
print ret
Starting with 3.10 and continuing with 3.12.0, this will fail. If there is a good reason to disallow "import PyQt4.QtGui" in ParaView, I understand, but can we implement equivalent functionality to these four static functions
PyQt4.QtGui.QInputDialog.getInt()
PyQt4.QtGui.QInputDialog.getItem()
PyQt4.QtGui.QInputDialog.getDouble()
PyQt4.QtGui.QInputDialog.getText()
from within a ParaView Python macro?https://gitlab.kitware.com/paraview/paraview/-/issues/12844Place all SuperBuild external sources on public2020-05-04T08:24:06-04:00Kitware RobotPlace all SuperBuild external sources on public**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12844). Further discussion may take place here.**
---
This way MD5s won't become invalid when a TPL has a new version released a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12844). Further discussion may take place here.**
---
This way MD5s won't become invalid when a TPL has a new version released and the one we're fixed to is removed.https://gitlab.kitware.com/paraview/paraview/-/issues/12840Threshold filter lowers precision of Points data2020-05-06T09:38:23-04:00Kitware RobotThreshold filter lowers precision of Points data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12840). Further discussion may take place here.**
---
How to reproduce:
1.) Open a file that stores positions in double preci...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12840). Further discussion may take place here.**
---
How to reproduce:
1.) Open a file that stores positions in double precision.
2.) Apply Threshold filter
3.) Look at point data in spreadsheet view
Before the point data in spreadsheet view was double precision, after applying the filter the point data is only in single precision.
I'm not a 100% sure but can this be related to line 40 in VTK/Graphics/vtkThreshold.cxx which reads
this->PointsDataType = VTK_FLOAT;https://gitlab.kitware.com/paraview/paraview/-/issues/12789Plugin changing property after Apply (SurfaceLIC + PointSprite)2020-05-04T22:09:23-04:00Kitware RobotPlugin changing property after Apply (SurfaceLIC + PointSprite)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12789). Further discussion may take place here.**
---
Plugin Qt widget are not supposed to change property value after the apply...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12789). Further discussion may take place here.**
---
Plugin Qt widget are not supposed to change property value after the apply button get clicked.
This induce invalid changes that get pushed to the UndoStack.
To reproduce that: build static or load plugins before executing those steps:
- Create sphere
- Apply
- Mouse over Undo (The tooltip showing the undo name should show "Apply" and not vtkSMRepresentation...)
https://gitlab.kitware.com/paraview/paraview/-/issues/12782Saving EnSight data doesn't support VTK_POLYHEDRON2024-01-22T10:26:14-05:00Kitware RobotSaving EnSight data doesn't support VTK_POLYHEDRON**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12782). Further discussion may take place here.**
---
ParaView 3.12.0 can't write out EnSight data with VTK_POLYHEDRON cell type...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12782). Further discussion may take place here.**
---
ParaView 3.12.0 can't write out EnSight data with VTK_POLYHEDRON cell type. I think the reason is that vtkEnSightWriter doesn't support VTK_POLYHEDRON.
Attached files are test data and patches which I used in order to adjust and test.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/12759Issue with the QDoubleSpinbox on the qtTesting - shift between current and ex...2020-05-07T21:55:11-04:00Kitware RobotIssue with the QDoubleSpinbox on the qtTesting - shift between current and expcted values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12759). Further discussion may take place here.**
---
A long click on the up/down arrow -> just one click even if the value chan...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12759). Further discussion may take place here.**
---
A long click on the up/down arrow -> just one click even if the value change severals times.
Fast click -> Double click -> no effect.
Clik on the up/down arrow just after editing the spin Box -> no effect. https://gitlab.kitware.com/paraview/paraview/-/issues/12758Issue with the QSpinbox on the qtTesting - shift between current and expcted ...2020-05-07T21:45:27-04:00Kitware RobotIssue with the QSpinbox on the qtTesting - shift between current and expcted values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12758). Further discussion may take place here.**
---
A long click on the up/down arrow -> just one click even if the value chan...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12758). Further discussion may take place here.**
---
A long click on the up/down arrow -> just one click even if the value change severals times.
Fast click -> Double click -> no effect.
Clik on the up/down arrow just after editing the spin Box -> no effect. https://gitlab.kitware.com/paraview/paraview/-/issues/12757Crash when loading Ensight Gold files2021-03-23T07:46:06-04:00Kitware RobotCrash when loading Ensight Gold files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12757). Further discussion may take place here.**
---
Paraview 3.12.0 crashes when I load Fluent-generated Ensight Gold ASCII fi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12757). Further discussion may take place here.**
---
Paraview 3.12.0 crashes when I load Fluent-generated Ensight Gold ASCII files on my Windows 7, 64-bit system. Paraview 3.10.1 installed on the same system does not.
Fluent generates Ensight Gold output as an .encas file, which is a text document pointing to other files containing geometry and surface variables. In all versions of Paraview I have tried over the past couple years, Paraview does not recognize .encas files as being associated with Ensight Gold, so when I open the file loader, I must set the filter to "all files" and then select my desired .encas file. Normally, this brings up a next screen which asks me which type of file this is, and I select Ensight Gold, and the file then loads correctly.
In Paraview 3.12.0, once I select the .encas file in the loader, the entire program crashes with no visible error message. I do not get asked what type of file the .encas file is before the crash happens.
Upon request, I would be glad to share a sample dataset that crashes Paraview 3.12.0, but the files are extremely large and so probably not appropriate to provide here.https://gitlab.kitware.com/paraview/paraview/-/issues/12743GatherInformation is not gathering information from pvrenderserver correctly.2021-03-23T10:38:53-04:00Kitware RobotGatherInformation is not gathering information from pvrenderserver correctly.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12743). Further discussion may take place here.**
---
Try using the "memory inspector" in render-server mode to see the issue.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12743). Further discussion may take place here.**
---
Try using the "memory inspector" in render-server mode to see the issue.https://gitlab.kitware.com/paraview/paraview/-/issues/12739import paraview.vtk.geovis imports the common kit2020-05-23T08:31:46-04:00Kitware Robotimport paraview.vtk.geovis imports the common kit**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12739). Further discussion may take place here.**
---
Running "import paraview.vtk.geovis" on pvpython imports the vtkCommon kit...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12739). Further discussion may take place here.**
---
Running "import paraview.vtk.geovis" on pvpython imports the vtkCommon kit.
```
> pvpython
Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49)
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import paraview.vtk.geovis
>>> dir(paraview.vtk.geovis)
['VTK_ARIAL', 'VTK_ARRAY_DATA', 'VTK_BACKGROUND_LOCATION', 'VTK_BIT', 'VTK_BIT_MAX', 'VTK_BIT_MIN', 'VTK_BUILD_SHARED_LIBS', 'VTK_BUILD_VERSION', 'VTK_CHAR', 'V
.........
.........
iLi2EE', 'vtkVector_IiLi3EE', 'vtkVector_IiLi4EE', 'vtkVersion', 'vtkVoidArray', 'vtkWarpTransform', 'vtkWindow', 'vtkWindowLevelLookupTable', 'vtkXMLDataElement', 'vtkXMLFileOutputWindow']
```
Indeed, ParaView-3.12.0/Utilities/VTKPythonWrapping/paraview/vtk/geovis.py reads:
```
from vtkCommonPython import *
```Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/12733pvbatch rendering is different than interactive rendering2020-05-04T22:12:17-04:00Kitware Robotpvbatch rendering is different than interactive rendering**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12733). Further discussion may take place here.**
---
The user starts ParaView, starts tracing as soon as possible. He then does...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12733). Further discussion may take place here.**
---
The user starts ParaView, starts tracing as soon as possible. He then does some post-processing, dumps an image and stops tracing.
when executing the created dump with pvbatch, the image created is different than then one created interactively.
attached is a simple test script.https://gitlab.kitware.com/paraview/paraview/-/issues/12719Add support for interactors in PVPython2020-05-04T22:13:38-04:00Kitware RobotAdd support for interactors in PVPython**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12719). Further discussion may take place here.**
---
Add support for interactors in pvpython**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12719). Further discussion may take place here.**
---
Add support for interactors in pvpythonhttps://gitlab.kitware.com/paraview/paraview/-/issues/12714D3 crashes with option "duplicate cells"2023-06-15T08:55:18-04:00Kitware RobotD3 crashes with option "duplicate cells"**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12714). Further discussion may take place here.**
---
Using more then 8 pvservers (our standard is 12 processes), D3 will crash ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12714). Further discussion may take place here.**
---
Using more then 8 pvservers (our standard is 12 processes), D3 will crash when executing with the Exodus file which you can find at
ftp://ftp.cscs.ch/out/jfavre/bones.ex2.gz
1) Load the data, without the cell or point data (to be faster).
2) Add D3 with "duplicate cells"
3) Hit play button (or crash also immediately)
4) crash
the same file was verified to run correctly with 3.10.1
Jeanhttps://gitlab.kitware.com/paraview/paraview/-/issues/12708Special characters in Text Source produce invalid state files2019-01-21T21:26:45-05:00Kitware RobotSpecial characters in Text Source produce invalid state files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12708). Further discussion may take place here.**
---
When adding a text annotation using Source -> Text that contains the Greek...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12708). Further discussion may take place here.**
---
When adding a text annotation using Source -> Text that contains the Greek letter µ, the annotation shows up correctly in the display window. However, saving the state file (example attached) with this source and loading it again yields the error:
===
ERROR: In /tmp/MWInstaller/src/ParaView/VTK/IO/vtkXMLParser.cxx, line 483
vtkPVXMLParser (0x1181585b0): Error parsing XML in stream at line 217, column 34, byte index 9991: not well-formed (invalid token)
Root does not exist. Either state file could not be opened or it does not contain valid xml
===
The problem seems to be that the character "mu" is stored in the state file and the XML loader can't parse this character.
I compiled from git commit 606c3e5c24b1a54223ceb06935e5ef6859a76844 on Mac OS X Snow Leopard, i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3).
Testing notes:
* ParaView, builtin server
* Add **Text** source
* Set text to µ. Apply.
* Save state.
* Reset session.
* Load previously saved state.
µ should be restored as the text in the **Text** source.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/12697lower level of detail (LOD) rendering for Volume representation does not allo...2020-05-04T22:18:15-04:00Kitware Robotlower level of detail (LOD) rendering for Volume representation does not allow opaque surfaces for speed**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12697). Further discussion may take place here.**
---
When rendering a volume representation that takes 0.5 or more seconds to r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12697). Further discussion may take place here.**
---
When rendering a volume representation that takes 0.5 or more seconds to render, the polygonal lower level of detail representation for interaction is highly necessary.
As it is now, the LOD polygonal rendering is done translucently. This has two problems. First, the default configuration of paraview has depth peeling off (I think). Thus the translucent rendering is wrong due to ordering errors. Second, with depth peeling on, multiple render passes are necessary and for some (many?) cases the speed for the translucent polygonal rendering is unacceptable. (Especially compared to similar handling in VTK applications).
The default LOD rendering for the volume should be opaque polygons, not translucent ones. At the very least, there should be a way to set the LOD rendering to opaque, and as of now there isn't a way to do that.
Right now, the class vtkPVLODVolume is apparently responsible (at a reasonably high level) for this level of detail render handling. Digging down, I find that vtkLODProp3D is the class that is responsible for the rendering at various LODs, and, in the case of the volume rendering, the polygonal LOD is being rendering by a vtkOpenGLActor instance.
Essentially, this Actor needs to be forced to use 1.0 opacity or have some way so that the ultimate parent can request 1.0 opacity.
I hacked in a version of vtkLODProp3D.cxx and vtkLODProp3D.h to get the behavior I desire, which I am attaching. Essentially I just added a flag to decide whether to force a particular opacity value (I didn't add a way to set the flag--it's just on by default), and a particular opacity value (defaulted to 1.0) to force if the flag is true. This achieves my desired behavior. However, we need to determine if opaque is the correct default behavior and we probably need a way to let the user choose the opacity level for the LOD presentation. It seems logical to me to tie the LOD opacity to the opacity used when the component is being rendered as a surface. If this would be the case, the prop opacity would need to be set to the corresponding surface presentation opacity on creation, and any change to the surface rendering opacity would need to be copied to the volume LOD opacity. It might also make sense for the volume LOD to simply be the surface representation, rather than having a separate surface representation in the volume management.
(This bug is related to a couple others also having to do with volume LOD presentation)https://gitlab.kitware.com/paraview/paraview/-/issues/12676PV_FORWARD_PATH_INSTALL not set properly if PV_INSTALL_BIN_DIR and PV_INSTALL...2020-05-07T21:26:35-04:00Kitware RobotPV_FORWARD_PATH_INSTALL not set properly if PV_INSTALL_BIN_DIR and PV_INSTALL_LIB_DIR set**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12676). Further discussion may take place here.**
---
For the Fedora MPI packages of paraview I need to install the binaries int...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12676). Further discussion may take place here.**
---
For the Fedora MPI packages of paraview I need to install the binaries into /usr/lib{,64}/openmpi/bin and the libraries into /usr/lib{,64}/openmpi/lib/paraview which I do with:
-DPV_INSTALL_BIN_DIR:PATH=%{_lib}/openmpi/bin \
-DPV_INSTALL_LIB_DIR:PATH=%{_lib}/openmpi/lib/paraview \
%{_lib} is set to lib/lib64 as needed.
This results in:
Error converting runtime path entry "/usr/lib64/openmpi/bin/../lib64/openmpi/lib/paraview" to real path: No such file or directory
when trying to run pvserver. It seems that there are too many assumptions about shared paths in CMake/ParaViewMacros.cmake when constructing PV_FORWARD_PATH_INSTALL and it does not seem possible to override it. In this case PV_FORWARD_PATH_INSTALL would need to be either ../lib/paraview or ../../../lib64/openmpi/lib/paraview.https://gitlab.kitware.com/paraview/paraview/-/issues/12672Plugin macros override output arguments instead of appending to them2023-06-15T08:38:26-04:00Kitware RobotPlugin macros override output arguments instead of appending to them**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12672). Further discussion may take place here.**
---
Plugin macros override output arguments instead of appending to them, this...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12672). Further discussion may take place here.**
---
Plugin macros override output arguments instead of appending to them, this makes it tedious when adding multiple types of plugins in the same CMakeLists.txt file.https://gitlab.kitware.com/paraview/paraview/-/issues/12666Wrong Extents used by Translator2020-05-12T22:10:56-04:00Kitware RobotWrong Extents used by Translator**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12666). Further discussion may take place here.**
---
The Extent Translator values used by
int vtkStreamingDemandDrivenPipelin...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12666). Further discussion may take place here.**
---
The Extent Translator values used by
int vtkStreamingDemandDrivenPipeline::SetUpdateExtent
can be completely wrong.
Example : Create a wavelet source. Default params. (extent, -10,10...)
Add a Mask Points filter, with vertices enabled. Add a Gaussian resample filter with default params.
On a small piece of the output is generated.
The Update request for the Gaussian resample uses the extent translator that was bound to the Wavelt. It has extents {-10,10,-10,10,-10,10} which are clamped by {0,50,0,50,0,50} to give {0,10,0,10,0,10) and so only 1/5 of the output is generated.
Very nasty to work with mixture of image and polygon datasets.
https://gitlab.kitware.com/paraview/paraview/-/issues/12657Allow readers to be added with pure xml plugin2020-05-05T23:09:32-04:00Kitware RobotAllow readers to be added with pure xml plugin**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12657). Further discussion may take place here.**
---
If a reader is compiled into VTK and isn't exposed you can't write a pure ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12657). Further discussion may take place here.**
---
If a reader is compiled into VTK and isn't exposed you can't write a pure xml plugin to show it, which you can do for filters.https://gitlab.kitware.com/paraview/paraview/-/issues/12634Resampling transient data on grouped sources2020-05-04T02:00:24-04:00Kitware RobotResampling transient data on grouped sources**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12634). Further discussion may take place here.**
---
I satisfied a questionable behaviour of the "group datasets" filter
appli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12634). Further discussion may take place here.**
---
I satisfied a questionable behaviour of the "group datasets" filter
applied to some sources (e.g. cylinders) in combination with resampling
a transient dataset of ensight input files in paraview 3.8.1 and
3.10.1. I wonder if it is a feature or a bug.
By changing the time in paraview the output of the "resample with
dataset" filter of the grouped sources (e.g. two planes) isn't updated
to the current time value. The resampling of a single source is
updating though.
My intention is to get an updated output of the "resample with dataset"
filter for a "group of sources" each time the time has changed.
https://gitlab.kitware.com/paraview/paraview/-/issues/12632Some Dashboard machine do not run pvcrs.FindDataDialog.Flow2020-05-04T04:39:16-04:00Kitware RobotSome Dashboard machine do not run pvcrs.FindDataDialog.Flow**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12632). Further discussion may take place here.**
---
On top of that we are not properly detecting failure on pvcrs.FindDataDial...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12632). Further discussion may take place here.**
---
On top of that we are not properly detecting failure on pvcrs.FindDataDialog.Flow when it run on Windows.
The trace say server exit with code 1.
But the test pass.https://gitlab.kitware.com/paraview/paraview/-/issues/12623Invalid chart capture when the renderer size is bigger than the real Qt view ...2020-05-04T04:38:49-04:00Kitware RobotInvalid chart capture when the renderer size is bigger than the real Qt view size**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12623). Further discussion may take place here.**
---
This happens in the pvcs-collab.Spreadsheet2 test that has been disable fo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12623). Further discussion may take place here.**
---
This happens in the pvcs-collab.Spreadsheet2 test that has been disable for now.https://gitlab.kitware.com/paraview/paraview/-/issues/12617Build Mac Binaries with their own MPI.2020-05-05T23:17:09-04:00Kitware RobotBuild Mac Binaries with their own MPI.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12617). Further discussion may take place here.**
---
OSX 10.7 no longer includes open mpi. For future releases we should just p...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12617). Further discussion may take place here.**
---
OSX 10.7 no longer includes open mpi. For future releases we should just package our own MPI instead of relying on the systerm version.https://gitlab.kitware.com/paraview/paraview/-/issues/12606Snapshot resolution can't be set via script2020-05-04T22:22:34-04:00Kitware RobotSnapshot resolution can't be set via script**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12606). Further discussion may take place here.**
---
There is no way to set or change the snapshot resolution/quality in python...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12606). Further discussion may take place here.**
---
There is no way to set or change the snapshot resolution/quality in python scripts. WriteImage() has no such options. There is no documentation on
it either.
'Recording script' gives nothing during 'save snapshot' dialog manipulation.
https://gitlab.kitware.com/paraview/paraview/-/issues/12579Line chart display bug when loading a statefile2020-06-04T21:28:49-04:00Kitware RobotLine chart display bug when loading a statefile**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12579). Further discussion may take place here.**
---
The "Display" tab in the "Object Inspector" does not populate the "Use Dat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12579). Further discussion may take place here.**
---
The "Display" tab in the "Object Inspector" does not populate the "Use Data Array" combo box in the "X Axis Data" section when it is set up from a state file.
I've attached a script that generates a statefile (saves to /tmp/mystate.pvsm)
Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/12577Parallel Coordinates bug with column visibility on selection2021-04-22T21:21:52-04:00Kitware RobotParallel Coordinates bug with column visibility on selection**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12577). Further discussion may take place here.**
---
The view will reset to showing all columns if you limit the number of colu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12577). Further discussion may take place here.**
---
The view will reset to showing all columns if you limit the number of columns to display using the "Display" tab in the "Object Inspector" and then select a range in the parallel co-ordinates view.https://gitlab.kitware.com/paraview/paraview/-/issues/12564BUNDLE_ICON in build_paraview_client() ignores paths2020-05-21T21:05:29-04:00Kitware RobotBUNDLE_ICON in build_paraview_client() ignores paths**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12564). Further discussion may take place here.**
---
I am building a ParaView based application under Mac OS X 10.6.8.
BUNDLE_...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12564). Further discussion may take place here.**
---
I am building a ParaView based application under Mac OS X 10.6.8.
BUNDLE_ICON is a parameter used in in the function build_paraview_client() specifying where the icon file is. But it ignores the paths that I give it, and it only looks for one place, ${CMAKE_CURRENT_SOURCE_DIR}.
If I copy the icon to ${CMAKE_CURRENT_SOURCE_DIR}, no matter what the paths are, it always finds it. Otherwise, CMake won't let me pass.
https://gitlab.kitware.com/paraview/paraview/-/issues/12560Gradient filter (2D) and (all other Image filters) fail to update display wit...2021-03-24T18:50:13-04:00Kitware RobotGradient filter (2D) and (all other Image filters) fail to update display with results when run on test data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12560). Further discussion may take place here.**
---
Gradient filter (2D) and (all other Image filters) fail to update display ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12560). Further discussion may take place here.**
---
Gradient filter (2D) and (all other Image filters) fail to update display with results when run on 2D test data. Filter is correctly run, since results are correctly displayed if new view window is created and results are shown in new view windows. But results are never displayed correctly in original view window. (it only shows a red square).
Error was introduced in ParaView 3.10 and currently exists in ParaView 3.12 RC-1 as well.
Sample data is attached
Additional information from the original bug:
This only appears with the auto-accept default set to on.
With auto-accept on it will first apply the 3D version of the filter which creates the red square and when changing to 2D version of the filter the correct representation is not shown.
If you have auto-accept off this does not occur as you can apply the 2D version of the filter without first applying the 3D version.
If you manually apply the 3D version of the filter and then apply the 2D version the problem will again manifest.https://gitlab.kitware.com/paraview/paraview/-/issues/12548Table To Structured Grid bugs with x y z, but works as x z y?2020-05-04T01:53:14-04:00Kitware RobotTable To Structured Grid bugs with x y z, but works as x z y?**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12548). Further discussion may take place here.**
---
I have windtunnel data in a table in a csv file.
The data contains x, y...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12548). Further discussion may take place here.**
---
I have windtunnel data in a table in a csv file.
The data contains x, y, z coordinates in each row with some scalar values in other columns. After selecting x as x and y as y and z as z and defining the grid size it outputs a saw-toothed edged plane with the data all distorted.
However, when I specify y as z and z as y it works but of course my data is off 90 degrees so I then apply a transform filter to it.
Why is this happening? Seems odd. Is there a particular requirement in the order of my data for it to work correctly with x as x, y as y and z as z???https://gitlab.kitware.com/paraview/paraview/-/issues/12547Information tab reports the wrong cell and point count in parallel2021-04-22T21:28:44-04:00Kitware RobotInformation tab reports the wrong cell and point count in parallel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12547). Further discussion may take place here.**
---
This can sometimes only show the size for one partition.
To reproduce:
Ru...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12547). Further discussion may take place here.**
---
This can sometimes only show the size for one partition.
To reproduce:
Runs a parallel server with 2 procs
Create a Box source [ cells=12, points=48 ]
Add an array with the calculator [ cells=6, points=24 ]https://gitlab.kitware.com/paraview/paraview/-/issues/12540Probing with PlotOverLine in 2D view2020-05-04T04:37:43-04:00Kitware RobotProbing with PlotOverLine in 2D view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12540). Further discussion may take place here.**
---
The 3D space of the line widget does not map the 2D view of a slice.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12540). Further discussion may take place here.**
---
The 3D space of the line widget does not map the 2D view of a slice.https://gitlab.kitware.com/paraview/paraview/-/issues/12509Extract Subset filter strange behaviour2023-06-15T08:04:13-04:00Kitware RobotExtract Subset filter strange behaviour**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12509). Further discussion may take place here.**
---
I have an image dataset A (1137x716x834) that was created using the
Extrac...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12509). Further discussion may take place here.**
---
I have an image dataset A (1137x716x834) that was created using the
Extract Subset filter from a larger dataset. It is stored in a .pvti +
8*.vti files. The extents of A are
X: 514-1650 (dim 1137), Y: 455-1170 (dim 716), Z: 0:833 (dim 834)
I want to create a subsampled version of A by once again using the
Extract Subset filter, with as VOI the full extents above and setting
its sample rates to 2. But to my surprise the subsampled dataset (using
PV 3.10.1 in standalone mode, btw) ends up having extents
X: 514-825 (312), Y: 455-584 (130), Z: 0-416 (417)
and covers only the upper portion of A, not the whole set. I also don't
understand where the weird reduction in X and Y dimensions comes from
(factors 3.6 and 5.5, resp). See the attached screenshots.https://gitlab.kitware.com/paraview/paraview/-/issues/12508Errors in .desktop file included with paraview2020-05-12T22:06:58-04:00Kitware RobotErrors in .desktop file included with paraview**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12508). Further discussion may take place here.**
---
Desktop file included in paraview is missing:
Exec=paraview
and the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12508). Further discussion may take place here.**
---
Desktop file included in paraview is missing:
Exec=paraview
and the Version key should be:
Version=1.0
i.e. the version of the desktop spec in use, not the version of the program.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/12501PythonCalculator crashes when running on multiple core with mpirun2021-04-16T21:28:17-04:00Kitware RobotPythonCalculator crashes when running on multiple core with mpirun**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12501). Further discussion may take place here.**
---
PythonCalculor causes a crashes when
mpirun -np 2 pvbatch --use-offscree...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12501). Further discussion may take place here.**
---
PythonCalculor causes a crashes when
mpirun -np 2 pvbatch --use-offscreen-rendering pythoncalcmpibug.py
is issued.
without mpirun and with mpirun with only 1 core the scripts works.
------------------- start pythoncalcmpibug.py
from paraview.simple import *
view=CreateRenderView()
view.ViewSize = [400, 400]
view.ResetCamera()
view.Background=[0.7,0.7,0.7]
view.CameraViewUp = [0,1,0]
Sphere(PhiResolution = 1024, ThetaResolution = 1024);
Elevation(LowPoint=[-0.5, -0.5, -0.5],HighPoint=[0.5, 0.5, 0.5])
PythonCalculator(Expression='Elevation*Elevation')
rep = Show()
lut = MakeBlueToRedLT(0,1)
lut.NumberOfTableValues=100
rep.LookupTable=lut
rep.ColorAttributeType='POINT_DATA'
rep.ColorArrayName='Elevation'
bar=CreateScalarBar(LookupTable=lut,Title='Elevation')
bar.TitleColor=[0,0,0]
bar.LabelColor=[0,0,0]
bar.NumberOfLabels=3
view.Representations.append(bar)
view.StillRender()
WriteImage("elevationsphere.png",view=view,Writer="vtkPNGWriter")https://gitlab.kitware.com/paraview/paraview/-/issues/12493Random error with Invalid output port2020-05-04T04:32:18-04:00Kitware RobotRandom error with Invalid output port**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12493). Further discussion may take place here.**
---
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available numb...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12493). Further discussion may take place here.**
---
Invalid output port : pqPipelineSource::getOutputPort( 0 ). Available number of output ports: 0https://gitlab.kitware.com/paraview/paraview/-/issues/12487ComputeDerivative filter crashes in x86, 64 bit linux binaries2023-06-15T08:03:48-04:00Kitware RobotComputeDerivative filter crashes in x86, 64 bit linux binaries**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12487). Further discussion may take place here.**
---
I have installed paraview with Linux x86, 64 bit binaries. When we use Com...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12487). Further discussion may take place here.**
---
I have installed paraview with Linux x86, 64 bit binaries. When we use ComptueDerivative filter to calculate vorticity it crashes with the error segmentation fault. The windows binaries do not have the same problem when I apply this filter to the same database.https://gitlab.kitware.com/paraview/paraview/-/issues/12479AMR Dual Clip produces incorrect results on some datasets.2023-06-15T15:08:19-04:00Kitware RobotAMR Dual Clip produces incorrect results on some datasets.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12479). Further discussion may take place here.**
---
Bug happens when clipping both materials at 0.1.
See attached image**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12479). Further discussion may take place here.**
---
Bug happens when clipping both materials at 0.1.
See attached imagehttps://gitlab.kitware.com/paraview/paraview/-/issues/12478AMR Dual Clip and Contour Accept invalid input datasets2020-06-11T18:54:01-04:00Kitware RobotAMR Dual Clip and Contour Accept invalid input datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12478). Further discussion may take place here.**
---
Both filters accept any composite data set when they should only accept AM...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12478). Further discussion may take place here.**
---
Both filters accept any composite data set when they should only accept AMR data. This causes both filters to crash if they are run on a multiblock dataset.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/12474make ParaView application bundle generation optional2020-05-07T21:27:11-04:00Kitware Robotmake ParaView application bundle generation optional**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12474). Further discussion may take place here.**
---
Add an option to turn off creating an App bundle when building ParaView on...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12474). Further discussion may take place here.**
---
Add an option to turn off creating an App bundle when building ParaView on the Mac. By default this will remain on but when it's off ParaView will be built/installed with a Unix directory structure.https://gitlab.kitware.com/paraview/paraview/-/issues/12471vtkOpenFOAMReader class does not support read of solution files written in AS...2020-04-24T19:00:09-04:00Kitware RobotvtkOpenFOAMReader class does not support read of solution files written in ASCII format**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12471). Further discussion may take place here.**
---
The vtkOpenFOAMReader class supports only binary reading of the OpenFOAM s...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12471). Further discussion may take place here.**
---
The vtkOpenFOAMReader class supports only binary reading of the OpenFOAM solution files if the simulation was run in double precision. If this might be relevant for most cases, this becomes a real pain for single precision simulations, where the binary format used for storing the solution is different from the double precision case. There is unfortunately no simple way to differentiate at the time being single precision binary dumps from double precision ones.
In order to avoid to convert twice the binary dump from single precision binary to ASCII, and then from ASCII to double precision binary, it is much easier to convert the data to ASCII once and for all and let the vtkOpenFOAMReader class do the rest. For this purpose, we have gone through this class and found out that it does not fully support ASCII solution files especially when the field size is 0. This happens for instance in parallel simulation for which do all existing boundaries are declared in all processor directories, but if a processor does not have the boundary lying on its domain, the corresponding boundary patch size and all associated fields are of length 0. This is valid for all ParaView version from v3.8.1 to v3.10.1.
Please find a working patch to the file Paraview-3.10.1/VTK/IO/vtkOpenFOAMReader.cxx
This patch has been tested in parallel on Linux. https://gitlab.kitware.com/paraview/paraview/-/issues/12463Add ability to get notification when a global setting changes2020-04-24T20:24:16-04:00Kitware RobotAdd ability to get notification when a global setting changes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12463). Further discussion may take place here.**
---
There should be a way for objects to be informed when a global setting cha...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12463). Further discussion may take place here.**
---
There should be a way for objects to be informed when a global setting changes through the pqSettings class.