ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-03-05T10:37:36-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/12341Static plugins and static executables2019-03-05T10:37:36-05:00Kitware RobotStatic plugins and static executables**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12341). Further discussion may take place here.**
---
Right now, when building statically, the plugins cannot be imported withou...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12341). Further discussion may take place here.**
---
Right now, when building statically, the plugins cannot be imported without changing the code. We need to add mechanism so that the "enabled" plugins are imported automatically in static executables.
https://gitlab.kitware.com/paraview/paraview/-/issues/12340Allow Sources/ Text on 2d windows2020-07-01T07:32:23-04:00Kitware RobotAllow Sources/ Text on 2d windows**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12340). Further discussion may take place here.**
---
Create a sphere, then a Plot over line filter. We should be able to add a...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12340). Further discussion may take place here.**
---
Create a sphere, then a Plot over line filter. We should be able to add a text message on top of this 2d window.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/12339pvvtk-next not working correctly on dashboards2019-03-05T10:37:36-05:00Kitware Robotpvvtk-next not working correctly on dashboards**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12339). Further discussion may take place here.**
---
refer to
http://www.cdash.org/CDash/viewUpdate.php?buildid=1307272
Th...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12339). Further discussion may take place here.**
---
refer to
http://www.cdash.org/CDash/viewUpdate.php?buildid=1307272
The issue is happening because Rob forwarded PVVTK, however the SHA VTK in ParaView referred to was in PVVTK next and since the dashboard does not update pull from pvvtk-remote, it complained.
On amber8, when I manually added the pvvtk remote and did a "git fetch pvvtk", then everything worked.https://gitlab.kitware.com/paraview/paraview/-/issues/12338No lookup table set on a filter when applied on a generic dataset that is hidden2020-04-24T19:38:35-04:00Kitware RobotNo lookup table set on a filter when applied on a generic dataset that is hidden**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12338). Further discussion may take place here.**
---
When the dataset is visible everything is fine but as soon as the dataset ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12338). Further discussion may take place here.**
---
When the dataset is visible everything is fine but as soon as the dataset get hidden either by another filter if we apply a new filter to it, that new filter will miss that lookup table and the default weird VTK one will be created but won't be mentioned in the XML state file.https://gitlab.kitware.com/paraview/paraview/-/issues/12337Ghost cells not handled correct for volume rendering.2019-03-05T10:37:36-05:00Kitware RobotGhost cells not handled correct for volume rendering.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12337). Further discussion may take place here.**
---
Refer to email:
http://markmail.org/thread/tsvh52wogo54g3wk**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12337). Further discussion may take place here.**
---
Refer to email:
http://markmail.org/thread/tsvh52wogo54g3wkhttps://gitlab.kitware.com/paraview/paraview/-/issues/12336ParaView Qt requirement to remain at 4.6.*2019-03-05T10:37:36-05:00Kitware RobotParaView Qt requirement to remain at 4.6.***This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12336). Further discussion may take place here.**
---
ParaView Qt requirement to remain at 4.6.* since the latest stable version...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12336). Further discussion may take place here.**
---
ParaView Qt requirement to remain at 4.6.* since the latest stable version of Debian and other OS's support that version.
We can reconsider this post-octoberhttps://gitlab.kitware.com/paraview/paraview/-/issues/12335Number of visible digits of point data in graphs2019-03-05T10:37:36-05:00Kitware RobotNumber of visible digits of point data in graphs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12335). Further discussion may take place here.**
---
The number of visible digits of data points in the Line Chart is restricte...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12335). Further discussion may take place here.**
---
The number of visible digits of data points in the Line Chart is restricted to three in this version. In version 3.8.0 for example, all digits were shown.
To make it clear: What is meant is, when hovering the mouse cursor over a data point in a Line Chart, the data will appear in a box. And in the newer versions, not all of the data is shown, which makes it impossible to read the data correctly, because it is rounded off.https://gitlab.kitware.com/paraview/paraview/-/issues/12334Single file given with --data= command line option is not loaded if it is par...2019-03-05T10:37:36-05:00Kitware RobotSingle file given with --data= command line option is not loaded if it is part of a file series**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12334). Further discussion may take place here.**
---
PV 3.10.1 official binary release and own build of git master as of now:
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12334). Further discussion may take place here.**
---
PV 3.10.1 official binary release and own build of git master as of now:
$ file Data/FileSeries/blow?.vtk
Data/FileSeries/blow0.vtk: ASCII C program text
Data/FileSeries/blow1.vtk: ASCII C program text
Data/FileSeries/blow2.vtk: ASCII C program text
Data/FileSeries/blow3.vtk: ASCII C program text
Data/FileSeries/blow4.vtk: ASCII C program text
Data/FileSeries/blow5.vtk: ASCII C program text
Data/FileSeries/blow6.vtk: ASCII C program text
Data/FileSeries/blow9.vtk: ASCII C program text
=> The file Data/FileSeries/blow0.vtk does exist. Try to load it into ParaView from the command line:
$ paraview --data=Data/FileSeries/blow0.vtk
=> PV 3.10.1 does not load the file nor reports any error, while
PV nightly build states: Cannot open data file " Data/FileSeries/blow0.vtk "
This is a regression. With PV 3.4.0 (official binary release) either case of
$ paraview --data=Data/FileSeries/blow0.vtk
(to load a single file) and
$ paraview --data=Data/FileSeries/blow..vtk
(to load the complete file series) worked. It stopped working at least with PV 3.6.2.https://gitlab.kitware.com/paraview/paraview/-/issues/12333vtkSocket bug2019-03-05T10:37:36-05:00Kitware RobotvtkSocket bug**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12333). Further discussion may take place here.**
---
Using recent git (yesterday's master). I have noticed that when I use auto...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12333). Further discussion may take place here.**
---
Using recent git (yesterday's master). I have noticed that when I use autoMPI, which I have just tried for the first time, I get
ERROR: In ..\..\..\..\Code\pv-meshless\VTK\Common\vtkSocket.cxx, line 539
vtkSocket (0000000008A2FF10): Socket error in call to close/closesocket. An operation was attempted on something that is not a socket.
every time I run on windows (2 machines both give it).
I poked around and see that in vtkProcessModuleAutoMPI.cxx a call to CloseSocket is not followed by a reset of the socket descriptor
attached is a patch.
JBhttps://gitlab.kitware.com/paraview/paraview/-/issues/12332Client-driven update and delivery requests for views2019-03-05T10:37:36-05:00Kitware RobotClient-driven update and delivery requests for views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12332). Further discussion may take place here.**
---
We need to make the requests for delivering data be triggered from the cli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12332). Further discussion may take place here.**
---
We need to make the requests for delivering data be triggered from the client side. This helps avoid deadlocks or unexpected messages when client A's representation hasn't been modified, by the server-side representation is dirty because of client B.https://gitlab.kitware.com/paraview/paraview/-/issues/12330remove protobuf from coverage2019-03-05T10:37:36-05:00Kitware Robotremove protobuf from coverage**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12330). Further discussion may take place here.**
---
remove protobuf from coverage **This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12330). Further discussion may take place here.**
---
remove protobuf from coverage https://gitlab.kitware.com/paraview/paraview/-/issues/12329Disable testing on Dash12019-03-05T10:37:36-05:00Kitware RobotDisable testing on Dash1**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12329). Further discussion may take place here.**
---
Dash1 is to be used only for build/configure testing and not running the t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12329). Further discussion may take place here.**
---
Dash1 is to be used only for build/configure testing and not running the tests since it has several random failures. We attribute those to being an old machine.https://gitlab.kitware.com/paraview/paraview/-/issues/12327Selection inspector's label mode drop-down lists not updated when creating ne...2019-03-05T10:37:36-05:00Kitware RobotSelection inspector's label mode drop-down lists not updated when creating new data array with calculator**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12327). Further discussion may take place here.**
---
Sources - Wavelet - Apply.
Selection Inspector - Create Selection - Field...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12327). Further discussion may take place here.**
---
Sources - Wavelet - Apply.
Selection Inspector - Create Selection - Field Type: Point - New Value: 1
Selection Inspector - Display Style - Point Label - Check Visible
Selection Inspector - Display Style - Point Label - Label Mode drop-down list contains "Point IDs" and "RTData".
Filters - Calculator - Operation: "coords" - Apply.
Selection Inspector - Display Style - Point Label - Label Mode drop-down list still merely contains "Point IDs" and "RTData". The selection needs to be re-created in order for the new "Result" data array to appear in the drop-down list.
(The list is updated, though, when an existing calculator-created data array gets renamed.)
Tested with ParaView 3.10.1 and git master branch as of now.https://gitlab.kitware.com/paraview/paraview/-/issues/12325Numpy dependencies need to be scanned by fixupbundle2020-04-10T18:32:44-04:00Kitware RobotNumpy dependencies need to be scanned by fixupbundle**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12325). Further discussion may take place here.**
---
liblapack.so and libblas.so aren't being installed which numpy depends on....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12325). Further discussion may take place here.**
---
liblapack.so and libblas.so aren't being installed which numpy depends on. Didn't catch this during testing as testing machines apparently already had system installed versions.https://gitlab.kitware.com/paraview/paraview/-/issues/12324Multiple-viewports involving at least one "3d view (comparative)" doesn't ren...2020-04-10T18:13:55-04:00Kitware RobotMultiple-viewports involving at least one "3d view (comparative)" doesn't render properly to png**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12324). Further discussion may take place here.**
---
Steps to reproduce this bug
1) split viewport
2) make the new viewport "...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12324). Further discussion may take place here.**
---
Steps to reproduce this bug
1) split viewport
2) make the new viewport "3d view (comparative)"
3) Save screenshot to png, making sure to unselect "save only selected view"
The outputted png will have black across half the image.https://gitlab.kitware.com/paraview/paraview/-/issues/12323Remove Tile "Composite Threshold" from Render View Settings2019-04-24T20:29:33-04:00Kitware RobotRemove Tile "Composite Threshold" from Render View Settings**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12323). Further discussion may take place here.**
---
Under "Tile Display Parameters", in the Render View settings dialog, there...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12323). Further discussion may take place here.**
---
Under "Tile Display Parameters", in the Render View settings dialog, there's a slider for "Compositing Threshold". That's no longer applicable. We use Remote Render Threshold now.https://gitlab.kitware.com/paraview/paraview/-/issues/12322Exodus reader does not deal with attributes, but needs to.2020-06-29T20:32:07-04:00Kitware RobotExodus reader does not deal with attributes, but needs to.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12322). Further discussion may take place here.**
---
The Exodus reader needs to fully implement attributes. It is half way the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12322). Further discussion may take place here.**
---
The Exodus reader needs to fully implement attributes. It is half way there, but seems to never have been finished. Attributes are variables that are specific to a block, with no time data. They are basically per cell or point input data to the upstream physics packages that is then passed through. An example would be the thickness of the sheet metal on the blocks representing the skin of a car. As with this example, the engine would not have attributes (the engine has no thickness), but could have other attributes (percent aluminum, or some stress tensor, etc).
ParaView needs to deal with the case where these blocks are split across multiple files, and for files that don't include any cells for a block, there is no attribute data. I have seen cases where the number of attributes is different (but not zero) between blocks.
Please just create a union of all attributes. For blocks that don't have an attribute (for instance an engine and skin thickness), please fill with NaN.
This has already been implemented in EnSight numerous years ago, and is an issue with these people moving to ParaView. See attached screenshot from EnSight. In the attached picture, red is attributes, blue is the underlying color.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/12321Capture image fails with comparative view2024-03-07T20:47:38-05:00Kitware RobotCapture image fails with comparative view**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12321). Further discussion may take place here.**
---
Steps to reproduce:
1. Split view horizontally
2. Select 3D view (compara...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12321). Further discussion may take place here.**
---
Steps to reproduce:
1. Split view horizontally
2. Select 3D view (comparative)
3. File -> Save Screenshot
4. Uncheck "Save only selected view"
5. Click Ok
6. Save File
The image produced is incorrect and places the comparative view in the wrong place.
Platform: Ubuntu Linux 11.04, ParaView 3.11.15.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/12320Setting head and tail is not being updated immediately2020-04-08T07:25:00-04:00Kitware RobotSetting head and tail is not being updated immediately**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12320). Further discussion may take place here.**
---
Setting head and tail is not being updated immediately**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12320). Further discussion may take place here.**
---
Setting head and tail is not being updated immediatelyhttps://gitlab.kitware.com/paraview/paraview/-/issues/12319Show landmark labels in all 3D views2021-03-23T10:39:16-04:00Kitware RobotShow landmark labels in all 3D views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12319). Further discussion may take place here.**
---
Show landmark labels in all 3D views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12319). Further discussion may take place here.**
---
Show landmark labels in all 3D views