ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-03-04T14:59:23-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21218HTG Clip and Slice widget doesn't display properly2022-03-04T14:59:23-05:00Yohann Bearzi (Kitware)HTG Clip and Slice widget doesn't display properlyThe clip and slice widgets don't seem to catch the bounding box correctly. Below are screenshots of those widgets on a `Wavelet` and on a `Hyper Tree Grid (random)` source.
HTG plane clip
![htg_clip](/uploads/4b382fd1262938af3a6971d1377...The clip and slice widgets don't seem to catch the bounding box correctly. Below are screenshots of those widgets on a `Wavelet` and on a `Hyper Tree Grid (random)` source.
HTG plane clip
![htg_clip](/uploads/4b382fd1262938af3a6971d1377e65c6/htg_clip.png)
Wavelet plane clip
![wavelet_clip](/uploads/7e4086280bf770628b9aa0c085702423/wavelet_clip.png)
HTG cylinder clip
![htg_cylinder](/uploads/a4bafd26eda1707e6e597accdc917bb4/htg_cylinder.png)
Wavelet cylinder clip
![wavelet_cylinder](/uploads/dbffec98faf30772eff151b64247eb2e/wavelet_cylinder.png)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21216HTG version of PIO reader doesn't render2022-03-04T18:00:12-05:00Yohann Bearzi (Kitware)HTG version of PIO reader doesn't renderWhen loading a file using the PIO reader with checkbox `Use HyperTree Grid (HTG) for AMR Mesh` activated, nothing gets rendered. It seems that it is a consequence of !5462.When loading a file using the PIO reader with checkbox `Use HyperTree Grid (HTG) for AMR Mesh` activated, nothing gets rendered. It seems that it is a consequence of !5462.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21215Crash on PIO reader when resetting session (sometimes)2022-02-07T18:33:20-05:00Yohann Bearzi (Kitware)Crash on PIO reader when resetting session (sometimes)When resetting the session, the PIO reader sometimes crash. Here's how to reproduce:
* Load `simple.pio`
* Apply
* Reset Sessiom
* Load `simple.pio`
* Apply
-> Sometimes crashesWhen resetting the session, the PIO reader sometimes crash. Here's how to reproduce:
* Load `simple.pio`
* Apply
* Reset Sessiom
* Load `simple.pio`
* Apply
-> Sometimes crashesCaitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/21214File dialog issues in client/server mode2022-10-18T09:35:31-04:00Mathieu Westphal (Kitware)File dialog issues in client/server modeThere are multiple issues in client/server mode (with different filesystem).
1. Favorites are not working
Steps to reproduce:
- run pvserver on one filesystem
- run paraview on another filesystem, connect to pvserver
- File -> Open
- ...There are multiple issues in client/server mode (with different filesystem).
1. Favorites are not working
Steps to reproduce:
- run pvserver on one filesystem
- run paraview on another filesystem, connect to pvserver
- File -> Open
- All favorites appears as warning and non existing
- Unable to add/remove/reset favorites
2. Delete empty directory is not working
- run pvserver on one filesystem
- run paraview on another filesystem, connect to pvserver
- Wavelet, apply
- File -> Save
- Creaty empty dir
- Delete empty directory is not working5.10.1 (Winter 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21212Can't set frame rate when saving MP4 animation2022-05-23T14:27:55-04:00S TCan't set frame rate when saving MP4 animationNo matter what frame rate I set in the options, the output is always 15 fps.
![image](/uploads/308d5b3d2e7e4996e02bd2fb139342bb/image.png)
I would be happy if anyone could look into this issue.No matter what frame rate I set in the options, the output is always 15 fps.
![image](/uploads/308d5b3d2e7e4996e02bd2fb139342bb/image.png)
I would be happy if anyone could look into this issue.5.10.1 (Winter 2022)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21210Add camera view2022-02-10T02:52:40-05:00MarcAdd camera viewAdding a **camera view functionality** similar to the [camera view in Blender](https://docs.blender.org/manual/en/latest/editors/3dview/navigate/camera_view.html) could be a good extension of ParaView.
When frequently exporting screensh...Adding a **camera view functionality** similar to the [camera view in Blender](https://docs.blender.org/manual/en/latest/editors/3dview/navigate/camera_view.html) could be a good extension of ParaView.
When frequently exporting screenshots or animations of the same data set, it is desired to keep the same view, dimensions, etc.
The camera settings can be easily stored and loaded, but when changing the viewport size in-between (e.g. over weeks) or when working on different hardware, it's difficult to obtain the very same output again. (At least, I haven't found an easy way by setting the x and y dimensions during the export, yet.)
Although this can be achieved using `pvpython`/`pvbatch` scripts, a "GUI-way" of realizing this would be helpful.https://gitlab.kitware.com/paraview/paraview/-/issues/21209Unresolved Externals Windows when Building v5.102023-06-07T21:51:16-04:00Keith BallardUnresolved Externals Windows when Building v5.10Hello,
I have been building various versions of ParaView on Windows, but I have recently come across an issue with the latest release (v5.10). I am getting many unresolved externals related to the VTK conduit extension.
For example:
...Hello,
I have been building various versions of ParaView on Windows, but I have recently come across an issue with the latest release (v5.10). I am getting many unresolved externals related to the VTK conduit extension.
For example:
![image](/uploads/ed82a8809e5fe6c7a01c22b74920bfa3/image.png)
And other unresolved externals in the DLL causing others to fail:
![image](/uploads/99866b95567cbf7ec98ad5364bc8fb87/image.png)
Any direction would be appreciated. Thanks!
System:
Visual Studio 2019, Python 5.9, Windows 10, QT 5.15.2https://gitlab.kitware.com/paraview/paraview/-/issues/21206PIO reader access to restart block and even/odd checkpoints2022-04-10T15:29:46-04:00Maxwell JacksonPIO reader access to restart block and even/odd checkpoints@patchett2002 @ethan.stam @boonth
For the PIO reader, we want two checkboxes:
One titled “include restart blocks” would, when selected, include the restart block files in the sequence position that they belong.
One checkbox “re...@patchett2002 @ethan.stam @boonth
For the PIO reader, we want two checkboxes:
One titled “include restart blocks” would, when selected, include the restart block files in the sequence position that they belong.
One checkbox “read even/odd restarts would match the even and odd restart files and append them to the file sequence.
In addition a new keyword is needed for the PIO file format: DUMP_FILE = myfile
If DUMP_FILE is defined in the PIO file, only the file on the right of the = should be made available.
If Multiple DUMP_FILE keywords are encountered, the restart files should be ordered as a sequence in the same order they are in the PIO file.
Example names of dump files with a DUMP_BASE_NAME of xA50:
xA50-dmp_even xA50-dmp_odd xA50-dmp047323 xA50-dmp087011
xA50-dmp096220 xA50-dmp100976 xA50-dmp104260
xA50-dmp048392_rb_impact xA50-dmp087438
xA50-dmp096451 xA50-dmp101104 xA50-dmp104373 xA50-dmp057806
xA50-dmp087873 xA50-dmp096668 xA50-dmp101239 xA50-dmp1044905.10.1 (Winter 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21205ParaView installation configuration is incomplete2022-03-04T02:29:01-05:00Timothee ChabatParaView installation configuration is incompleteI ran into 2 unexpected behaviors when building a plugin against an install folder of ParaView :
1. [x] If ParaView was built with Ospray enabled, one must re configure Ospray. Configuration of the plugin outputs
```
CMake Error at /h...I ran into 2 unexpected behaviors when building a plugin against an install folder of ParaView :
1. [x] If ParaView was built with Ospray enabled, one must re configure Ospray. Configuration of the plugin outputs
```
CMake Error at /home/timothee/Dev/PARAVIEW/paraview/INSTALL/lib/cmake/paraview-5.10/vtk/VTK-vtk-module-find-packages.cmake:162 (find_package):
By not providing "Findospray.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "ospray", but
CMake did not find one.
Could not find a package configuration file provided by "ospray"
[...]
```
[SOLVED] see https://gitlab.kitware.com/paraview/paraview/-/issues/21205#note_1135028
2. [x] `vtkSMMessage.h` cannot be included in a source file of a plugin. Compilation error is :
```
In file included from /home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtkprotobuf/src/google/protobuf/stubs/macros.h:34,
from /home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtkprotobuf/src/google/protobuf/stubs/common.h:48,
from /home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtkprotobuf/src/google/protobuf/stubs/casts.h:34,
from /home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtkprotobuf/src/google/protobuf/message.h:122,
from /home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtk_protobuf.h:24,
from /home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtkSMMessage.h:36,
from /home/timothee/Dev/PARAVIEW/paraview/Examples/Plugins/SMMyProxy/Plugin/MyProxy/vtkSMMyElevationProxy.cxx:5:
/home/timothee/Dev/PARAVIEW/paraview/INSTALL/include/paraview-5.10/vtkprotobuf/src/google/protobuf/stubs/port.h:47:10: fatal error: google/protobuf/port_def.inc: No such file or directory
47 | #include <google/protobuf/port_def.inc>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
## Step to reproduce :
- Install ParaView in dir $PVINSTALL
- Apply this [patch](/uploads/f3903854a02449a8a9f9c346a6e32ac5/smmessage.patch) to your paraview repo (this patch will only affect the `ParaView/Examples/Plugins/SMMyProxy` source code by adding an `#include "vtkSMMessage.h"`)
- Build the `ParaView/Examples/Plugins/SMMyProxy` plugin against `$PVINSTALL/lib/cmake/paraview-5.10`
- Get both unexpected behaviors
Both behaviors work as expected when building the plugin against a build directory.https://gitlab.kitware.com/paraview/paraview/-/issues/21204Reader "Change File" error with multiple output ports2022-03-04T18:12:34-05:00Nicolas VuailleReader "Change File" error with multiple output portsFirst loaded `2LYZ.pdb` (from VTK testing data), then `Change File` and select `3GQP.pdb`
This error message raises:
```
ERROR: In /home/nicolas/ParaView/master/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 756
vtkPVDataRe...First loaded `2LYZ.pdb` (from VTK testing data), then `Change File` and select `3GQP.pdb`
This error message raises:
```
ERROR: In /home/nicolas/ParaView/master/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 756
vtkPVDataRepresentationPipeline (0x55fd5faf55f0): Input for connection index 0 on input port index 0 for algorithm vtkMoleculeRepresentation(0x55fd5ce1e350) is of type vtkPolyData, but a vtkMolecule is required.
```
In the RenderView, both files are mixed. In the following, the molecule rep correspond to the `2LYZ` file whereas the polydata comes from `3GQP`.
![image](/uploads/3ed9a4f4a09dc74dad8c73a90dc8551a/image.png)
Also note that in the pipeline browser, only the `Output-0` is visible when both were previously.
Then I tried to undo the file name change, and I obtained more of the same error message and this buggy pipeline:
![changeName](/uploads/268c5bd1c1cef42fc3f803d026cebffc/changeName.png)
I suspect the problem comes from multiple output port.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21201Remove instances of "Whats This" help tool2022-11-01T21:51:50-04:00Stan HammonRemove instances of "Whats This" help tool## General Description
There are three types of user help provided in Qt:
1. `Tool Tips` (shown by hovering the mouse over a widget)
2. `Status Tips` (shown in the Status Bar)
3. `Whats This` tips shown by different methods depending on ...## General Description
There are three types of user help provided in Qt:
1. `Tool Tips` (shown by hovering the mouse over a widget)
2. `Status Tips` (shown in the Status Bar)
3. `Whats This` tips shown by different methods depending on the platform (Windows: using the "?" in the Title Bar - Linux: using a Title Bar menu item)
This screenshot shows the `Whats This` utilization tool for Windows (indicated by red circle)
![Screenshot](/uploads/7b90acb76d7b34331685e9acac8397aa/Screenshot.png)
The proper use of these three tools is described here: https://flylib.com/books/en/2.18.1/tooltips_status_tips_and_whats_this_help.html
The GUI facility for interacting with `Whats This` tips is exposed by default for `QDialog`, and anything that inherits it.
`Whats This` tips are barely used in `Paraview`. They are intended to be more verbose than `Tool Tips`, and are only properly used in a single file (`pqLightsEditor.ui`). In most cases in `Paraview`, they simply duplicate the content of the `Tool Tip`, or would be better suited as a `Tool Tip` (given how short they are).
## Suggested Changes
`Whats This` tips should be removed from the project, and (more importantly) the buttons and menu items that enable `Whats This` tips to be exposed should be removed, as well.
### Hiding Window Title Bar Items
A single line of code hides the UI facility for interacting with the `Whats This` tips:
```dialog->setWindowFlags(dialog->windowFlags() & ~Qt::WindowContextHelpButtonHint);```
This would need to be added everywhere a `QDialog` or `QFileDialog` is used.
### Removing all definitions of `Whats This` tips
There are no uses of `QWidget::setWhatsThis()` in the project, meaning that all `Whats This` tips are defined in `.ui` files. Removing redundant tips, and changing the rest to be `Tool Tips` will fully suffice for all `.ui` except for `pqLightsEditor.ui`. This is the only file where some information will be lost - probably information that was never used by anyone, but information none the less. Twelve `.ui` files will be affected.https://gitlab.kitware.com/paraview/paraview/-/issues/21198IOSS reader performance issue2022-05-04T19:50:11-04:00W. Alan ScottIOSS reader performance issueWe have another performance issue with the IOSS reader. Here is how to replicate.
* The tarball cement_bridge.tar.gz contains two files. One is exampleFile.e, the other is spreader144. Spreader144 will make the dataset.
* Linux
* C...We have another performance issue with the IOSS reader. Here is how to replicate.
* The tarball cement_bridge.tar.gz contains two files. One is exampleFile.e, the other is spreader144. Spreader144 will make the dataset.
* Linux
* Create a sandbox directory, and go into it. "source spreader144"
* 5.9.1, 16 ranks, Linux.
* Load dataset cement_bridge.e.144.*. Leave all variables not loaded. Time the time from hitting the apply button to when the bridge segment appears.
For me, this is about 49 seconds.
* 5.10.0, 16 ranks, Linux.
* Load dataset cement_bridge.e.144.*. Turn off block array loads. Time the time from hitting the apply button to when the bridge segment appears.
For me, this is about 165 seconds.
This 3X to 4X slowdown is impacting my users.
I will pass the dataset cement_bridge.tar.gz to Utkarsh.5.11 (Spring 2022)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/21197Unused private member in vtkSMProxyClipboard2022-03-03T21:40:37-05:00Artem BodrinUnused private member in vtkSMProxyClipboardThere is unused private class member vtkSMProxyClipboard::CopiedState declared here:
https://gitlab.kitware.com/paraview/paraview/-/blob/master/Remoting/Misc/vtkSMProxyClipboard.h#L80
One defined in Internals class used instead.There is unused private class member vtkSMProxyClipboard::CopiedState declared here:
https://gitlab.kitware.com/paraview/paraview/-/blob/master/Remoting/Misc/vtkSMProxyClipboard.h#L80
One defined in Internals class used instead.https://gitlab.kitware.com/paraview/paraview/-/issues/21196List plugins in alphabetical order2022-10-12T12:48:50-04:00W. Alan ScottList plugins in alphabetical orderPlease list the plugins in alphabetical order. Recently, developers have been just dumping plugins at the bottom of the list.Please list the plugins in alphabetical order. Recently, developers have been just dumping plugins at the bottom of the list.5.11 (Spring 2022)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/21193IOSS print statements2022-06-29T10:43:10-04:00W. Alan ScottIOSS print statementsWe are seeing IOSS print statements when datasets with 8 byte integers are being read. I don't have a dataset that can be shared, but could we have this print statement turned off for production?
Print statement is: "IOSS: Input dat...We are seeing IOSS print statements when datasets with 8 byte integers are being read. I don't have a dataset that can be shared, but could we have this print statement turned off for production?
Print statement is: "IOSS: Input database contains 8-byte integers. Setting Ioss to use 8-byte integers." Probably located in: "ParaView5/VTK/ThirdParty/ioss/vtkioss/exodus/Ioex_BaseDatabaseIO.C: line 368"5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21192IOSS reader needs Displacement Magnitude2022-05-04T21:07:19-04:00W. Alan ScottIOSS reader needs Displacement MagnitudeThe Exodus reader in ParaView 5.9.1 has a feature called "Displacement Magnitude". This is found on the Advanced properties tab. This has been lost in the IOSS reader in 5.10.0. Please add it back, as it is being requested by users.The Exodus reader in ParaView 5.9.1 has a feature called "Displacement Magnitude". This is found on the Advanced properties tab. This has been lost in the IOSS reader in 5.10.0. Please add it back, as it is being requested by users.5.11 (Spring 2022)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21191Restart file fails with IOSS reader2022-06-23T15:19:09-04:00W. Alan ScottRestart file fails with IOSS readerThe new IOSS reader is failing with restart files. Restart files are documented on the wiki, here: https://www.paraview.org/Wiki/Restarted_Simulation_Readers. I have a tarball of "can" that has been broken up into restarts. There is ...The new IOSS reader is failing with restart files. Restart files are documented on the wiki, here: https://www.paraview.org/Wiki/Restarted_Simulation_Readers. I have a tarball of "can" that has been broken up into restarts. There is a restartFiles.ex-timeseries file that loads properly with 5.9.1, but fails with 5.10.0. This needs to be fixed.
Tarball attached. Note that I also include three patterns that should read, and correctly do.
5.10.0, builtin server, Linux.5.10.1 (Winter 2022)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/21190Scroll zooms to mouse option2022-04-27T19:44:14-04:00Alexandre MinotScroll zooms to mouse optionHello,
We currently have the option to ZoomToMouse using (ctrl/shift + ) + left/middle/right click + move mouse. Scroll always Zooms. I would like to ZoomToMouse using scroll.
A "scroll ZoomsToMouse" checkbox under the Mouse Wheel Fac...Hello,
We currently have the option to ZoomToMouse using (ctrl/shift + ) + left/middle/right click + move mouse. Scroll always Zooms. I would like to ZoomToMouse using scroll.
A "scroll ZoomsToMouse" checkbox under the Mouse Wheel Factor settings in the Camera pane of the Settings window would cover my need.
Many thanks,
Alex5.11 (Spring 2022)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21189Link camera between 2D and 3D renderview has different interaction than linki...2022-03-14T14:46:52-04:00Ethan StamLink camera between 2D and 3D renderview has different interaction than linking 2D to 2D or 3D to 3D@patchett2002 @cory.quammen @berkgeveci @maxwelljackson002
Windows 10 using ParaView 5.10.0 local client. Also reproduced with 5.9.1 in a parallel client-server connection.
Linking a 2D view to a 3D view has possibly unexpected result...@patchett2002 @cory.quammen @berkgeveci @maxwelljackson002
Windows 10 using ParaView 5.10.0 local client. Also reproduced with 5.9.1 in a parallel client-server connection.
Linking a 2D view to a 3D view has possibly unexpected results. For example, you can zoom in/out on one of the views without affecting the other.
To reproduce:
1. Wavelet (Default options)
2. Slice (Default options)
3. Show only the slice
4. Split renderview and show the slice again in the new view. Should have one 3D view and one 2D view like the screen shot below:
![image](/uploads/522078babbf666c03ca8cfaa1d2f0bbc/image.png)
5. Link camera between the views
6. Try moving the camera in either renderview. Try zooming in/out on one of the renderviews. They should be zooming together.
Maybe the answer is to force 2D/3D based on which view is being linked.5.11 (Spring 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21186Colormap Preset picker does not have priority on MacOS binaries2023-07-07T10:24:43-04:00Ethan StamColormap Preset picker does not have priority on MacOS binaries@cory.quammen @maxwelljackson002 @berkgeveci @patchett2002
Reproduced on multiple MacOS versions. I don't hit this issue on Ubuntu or Windows 10 binaries.
For MacOS binaries, the colormap preset picker window does not have priority ov...@cory.quammen @maxwelljackson002 @berkgeveci @patchett2002
Reproduced on multiple MacOS versions. I don't hit this issue on Ubuntu or Windows 10 binaries.
For MacOS binaries, the colormap preset picker window does not have priority over other panels and can get stuck behind things. This is more an annoyance than anything.
Steps to reproduce:
1. Use MacOS
2. Wavelet -> Color by `RTData` variable
3. Separate a panel from the GUI, the Pipeline Browser for example
4. Open the colormap editor and the colormap preset picker
5. Move the panels so they overlap.
It is expected to be able to switch which panel is on top of the stack. This is possible on Linux and Windows binaries.
![color-presets-on-bottom](/uploads/a5725e4e39392b3b7ee5fc80b2188bbd/color-presets-on-bottom.gif)5.12 (Winter 2023)Aron HelserAron Helser