ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-02-10T02:52:40-05:00https://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/21233cannot configure a plugin with a superbuild (5.10.0) install2022-02-15T08:57:58-05:00Jean M. Favrecannot configure a plugin with a superbuild (5.10.0) installwhen using a superbuild install to compile an external plugin, I have a number of undefined *_DIR because they refer to the build tree (to which I have no read access). The superbuild was done with PARAVIEW_RELOCATABLE_INSTALL=OFF, yet t...when using a superbuild install to compile an external plugin, I have a number of undefined *_DIR because they refer to the build tree (to which I have no read access). The superbuild was done with PARAVIEW_RELOCATABLE_INSTALL=OFF, yet the file vtk-find-package-helpers.cmake shows the following list (embree_DIR, ADIOS2_DIR, OpenImageDenoise_DIR, ospray_DIR, TBB_ROOT), pointing to the build tree, instead of somewhere on the install path.
Steps to replicate:
0) do a superbuild with 5.10.0. Set CMAKE_INSTALL_PREFIX where you want it installed.
1) The file <install-path>/lib/cmake/paraview-5.10/vtk/vtk-find-package-helpers.cmake contains reference to the build tree, which in our case, is built by a robot, and no more accessible after installation has completed.
P.S. other variables are completely missing from the vtk-find-package-helpers.cmake file (for example nlohmann_json_DIR, rkcommon_DIR, openvkl_DIR)https://gitlab.kitware.com/paraview/paraview/-/issues/21239ParaView master with VTK master fails at configure2022-02-17T09:29:40-05:00Ethan StamParaView master with VTK master fails at configure@patchett2002 @cory.quammen @berkgeveci @maxwelljackson002
When using VTK master to build ParaView master, we are getting this error:
```
CMake Error at VTK/CMake/vtkCompilerExtraFlags.cmake:55 (target_compile_options):
Cannot speci...@patchett2002 @cory.quammen @berkgeveci @maxwelljackson002
When using VTK master to build ParaView master, we are getting this error:
```
CMake Error at VTK/CMake/vtkCompilerExtraFlags.cmake:55 (target_compile_options):
Cannot specify compile options for target "vtkbuild" which is not built by
this project.
Call Stack (most recent call first):
CMakeLists.txt:98 (include)
```
I'm guessing this will pop up later when ParaView catches up to current VTK master. Steps to reproduce:
```console
git clone https://gitlab.kitware.com/paraview/paraview.git src
cd src
git checkout f463550cb254eb7cd8ea650489061ee1b68bbdcb # current paraview master commit
git submodule update --init --recursive
cd VTK
git checkout 50b91bab86e4951dab0e0331a5c3f093d5b5c30c # latest change in VTK/CMake/vtkCompilerExtraFlags.cmake
cd ../../
mkdir build
cd build
cmake -DPARAVIEW_USE_QT:BOOL=OFF ../src
```https://gitlab.kitware.com/paraview/paraview/-/issues/21252Memory leaks and crashes when saving animations2022-02-23T00:35:01-05:00SO 1291Memory leaks and crashes when saving animations## Summary:
Paraview 5.10 crashes when saving animations from OpenFOAM cases.
## Steps:
* Load OpenFOAM case.
* File -> Export Animation
* Monitoring the memory usage indicates high usage and increases up to 100% when the progress ba...## Summary:
Paraview 5.10 crashes when saving animations from OpenFOAM cases.
## Steps:
* Load OpenFOAM case.
* File -> Export Animation
* Monitoring the memory usage indicates high usage and increases up to 100% when the progress bar reaches only 8%
* Paraview crashes. On the terminal it shows the following error messages: `error: exception occurred: Subprocess killed`.
## System information:
```
Ubuntu 20.04.4 LTS
RAM: 16GB
CPU: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
Client Information:
Version: 5.10.0
VTK Version:
Qt Version: 5.12.9
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /home/user/Apps/Paraview/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/lib/python3.9
Python Library Version: 3.9.5 (default, Dec 22 2021, 22:21:42) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]
Python Numpy Support: On
Python Numpy Path: /home/user/Apps/Paraview/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/lib/python3.9/site-packages/numpy
Python Numpy Version: 1.21.1
Python Matplotlib Support: On
Python Matplotlib Path: /home/user/Apps/Paraview/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/lib/python3.9/site-packages/matplotlib
Python Matplotlib Version: 3.2.1
Python Testing: Off
MPI Enabled: On
ParaView Build ID: superbuild 8ec820e478df782e5b6694c88237b77ea04fdf54 (!950)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 4
OpenGL Vendor: Intel
OpenGL Version: 4.6 (Core Profile) Mesa 21.2.6
OpenGL Renderer: Mesa Intel(R) HD Graphics 520 (SKL GT2)
Connection Information:
Remote Connection: No
```https://gitlab.kitware.com/paraview/paraview/-/issues/21245AttributeError2022-02-24T04:33:43-05:00Zaher BITARAttributeErrorHi,
I am using paraview version 5.6.0.
I am getting the following error when i execute the pvpython script generated by a trace.
I am post-processing results for an openfoam case, and i am trying to plot the pressure at the cells adjace...Hi,
I am using paraview version 5.6.0.
I am getting the following error when i execute the pvpython script generated by a trace.
I am post-processing results for an openfoam case, and i am trying to plot the pressure at the cells adjacent to the wall in a cylinder at a specific slice (plane), by choosing the filter "plot on intersection curves". The slice type used in this filter is a sphere of a center [0.0, 0.0, 1.595] and a radius r=0.072. The intersection curve between the slice plane and the slice sphere is the needed output.
What can i do to eliminate this error?[bliba_123.py](/uploads/aaa700fd8d99ec049ebeca257c82f4cd/bliba_123.py)[bliba_123.py](/uploads/44202a7947ea09f9c55a67c71340dd59/bliba_123.py)
Kindly find attached the script.
Traceback (most recent call last):
File "bliba_123.py", line 160, in <module>
plotOnIntersectionCurves1.SliceType.Center = [0.0, 0.0, 1.595]
File "/opt/paraviewopenfoam56/lib/python2.7/site-packages/paraview/servermanager.py", line 459, in __setattr__
"to add this attribute.")
AttributeError: Attribute Center does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.https://gitlab.kitware.com/paraview/paraview/-/issues/21241Bug2022-02-24T04:35:41-05:00salman ahmedBugOS: Windows 10 Version 2009
ParaView Version: 5.10.0
Qt Version: 5.15.2
DescriptionOS: Windows 10 Version 2009
ParaView Version: 5.10.0
Qt Version: 5.15.2
Descriptionhttps://gitlab.kitware.com/paraview/paraview/-/issues/21240multiple problems2022-02-24T04:36:10-05:00H Gmultiple problemsIgnoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
VisRTX 0.1.6, using devices:
0: Quadro P2200 (...Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
VisRTX 0.1.6, using devices:
0: Quadro P2200 (Total: 5.3 GB, Available: 4.8 GB)
/home/charikleia/ParaView-5.10.0-MPI-Linux-Python3.9-x86_64/lib/python3.9/site-packages/pandas/compat/__init__.py:124: UserWarning: Could not import the lzma module. Your installed Python is incomplete. Attempting to use lzma compression will result in a RuntimeError.
warnings.warn(msg)
ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/Plugins/CDIReader/Reader/vtkCDIReader.cxx, line 1105
vtkCDIReader (0x1ae8ce90): Couldn't open file: No such file or directory
ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/Plugins/CDIReader/Reader/vtkCDIReader.cxx, line 1105
vtkCDIReader (0x1ae8ce90): Couldn't open file: No such file or directory
ERROR: In /builds/gitlab-kitware-sciviz-ci/build/superbuild/paraview/src/Plugins/CDIReader/Reader/vtkCDIReader.cxx, line 1105
vtkCDIReader (0x1ae8ce90): Couldn't open file: No such file or directory
and then it crasheshttps://gitlab.kitware.com/paraview/paraview/-/issues/21259Failed CUDA compile on ParaView 5.10.02022-02-25T11:56:46-05:00BTemp1282020Failed CUDA compile on ParaView 5.10.0Hello,
I am compiling ParaView 5.10.0 on Ubuntu 20.04 LTS with CCmake 3.22.2, OpenMPI 4.0.3, and CUDA Toolkit 11.6. I have tried compiling with both ninja and make.
During the make compile, I get the following error:
/opt/paraview/VTK/...Hello,
I am compiling ParaView 5.10.0 on Ubuntu 20.04 LTS with CCmake 3.22.2, OpenMPI 4.0.3, and CUDA Toolkit 11.6. I have tried compiling with both ninja and make.
During the make compile, I get the following error:
/opt/paraview/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/Algorithm.h:111:69: error: incomplete type ‘vtkm::cont::DeviceAdapterAlgorithm<vtkm::cont::DeviceAdapterTagCuda>’ used in nested name specifier
/opt/paraview/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/vtkm/cont/Algorithm.h: In instantiation of ...
This error includes many "required from" calls; as such, it fills the terminal window in short order. If you'd like a full log file, I can redirect the output but it will likely get rather large.
Possible additional relevant CUDA information: sm_37, compute_37
I previously modified paraview/VTK/ThirdParty/vtkm/vtkvtkm/vtk-m/CMake/VTKmDeviceAdapters.cmake so that it would not attempt to compile sm_30 through sm_35 (and corresponding through compute_35) when given the Kepler architecture flag. I did not change any names, I only removed the lower sm nvcc compile calls/flags in the switch statement.
Please let me know if more if more information would be helpful,
CollinVicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21271Pipeline MPI failed tests not reported in summary2022-03-02T08:50:57-05:00Menno Deij - van RijswijkPipeline MPI failed tests not reported in summaryCheck this pipeline https://gitlab.kitware.com/mennodeij1/paraview/-/jobs/6657337
There are many failed tests due to MPI issues with memory, **but these failed tests are not in the summary at the end**
This makes it very hard to see w...Check this pipeline https://gitlab.kitware.com/mennodeij1/paraview/-/jobs/6657337
There are many failed tests due to MPI issues with memory, **but these failed tests are not in the summary at the end**
This makes it very hard to see what is going on. To start with, it would seem that the MPI tests are running into limitations on the (virtual?) machines they are running on?
Take for example a test I'm interested in:
```
220/227 Test #129: ParaView::VTKExtensionsPCGNSWriterCxx-MPI-TestPartitionedDataSetCollection ........................***Failed 0.24 sec
[1646213770.863287] [runner-juxqemm-project-375-concurrent-0:14076:0] mm_posix.c:164 UCX ERROR Not enough memory to write total of 4292720 bytes. Please check that /dev/shm or the directory you specified has more available memory.
[1646213770.863288] [runner-juxqemm-project-375-concurrent-0:14078:0] mm_posix.c:164 UCX ERROR Not enough memory to write total of 4292720 bytes. Please check that /dev/shm or the directory you specified has more available memory.
[1646213770.863606] [runner-juxqemm-project-375-concurrent-0:14078:0] uct_mem.c:149 UCX ERROR failed to allocate 4292720 bytes using md posix for mm_recv_desc: Out of memory
[1646213770.863621] [runner-juxqemm-project-375-concurrent-0:14078:0] mpool.c:193 UCX ERROR Failed to allocate memory pool (name=mm_recv_desc) chunk: Out of memory
[1646213770.863626] [runner-juxqemm-project-375-concurrent-0:14078:0] mm_iface.c:673 UCX ERROR failed to get the first receive descriptor
[1646213770.863639] [runner-juxqemm-project-375-concurrent-0:14076:0] uct_mem.c:149 UCX ERROR failed to allocate 4292720 bytes using md posix for mm_recv_desc: Out of memory
[1646213770.863644] [runner-juxqemm-project-375-concurrent-0:14076:0] mpool.c:193 UCX ERROR Failed to allocate memory pool (name=mm_recv_desc) chunk: Out of memory
[1646213770.863648] [runner-juxqemm-project-375-concurrent-0:14076:0] mm_iface.c:673 UCX ERROR failed to get the first receive descriptor
Abort(1615503) on node 1 (rank 1 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack:
MPIR_Init_thread(138)........:
MPID_Init(1139)..............:
MPIDI_OFI_mpi_init_hook(1626):
create_endpoint(2284)........: OFI endpoint open failed (ofi_init.c:2284:create_endpoint:Invalid argument)
Abort(1615503) on node 3 (rank 3 in comm 0): Fatal error in PMPI_Init: Other MPI error, error stack:
MPIR_Init_thread(138)........:
MPID_Init(1139)..............:
MPIDI_OFI_mpi_init_hook(1626):
create_endpoint(2284)........: OFI endpoint open failed (ofi_init.c:2284:create_endpoint:Invalid argument)
```
This is the list of failed tests:
```
The following tests FAILED:
16 - ParaView::RemotingApplicationPython-GenerateIdScalarsBackwardsCompatibility (Failed)
24 - ParaView::RemotingApplicationPython-ProgrammableFilterProperties (Failed)
40 - ParaView::RemotingApplicationPython-RepresentationTypeHint (Failed)
42 - ParaView::RemotingApplicationPython-SaveScreenshot (Failed)
43 - ParaView::RemotingApplicationPython-ScalarBarActorBackwardsCompatibility (Failed)
77 - ParaView::RemotingApplicationPython-MPI-Batch-SymmetricTestFetchData (Failed)
89 - ParaView::RemotingApplicationPython::Module::pvbatch::paraview.tests (Failed)
106 - SurfaceLIC-OfficeVSlice-Batch (Failed)
167 - Catalyst::MPI::WaveletMiniApp.package_test_zip (Failed)
173 - Catalyst::FileDriverMiniApp::Wavelet.ValidateChangingTime (Failed)
```https://gitlab.kitware.com/paraview/paraview/-/issues/21172IOSS reader is slow with small, parallel dataset2022-03-03T06:34:13-05:00W. Alan ScottIOSS reader is slow with small, parallel datasetThe IOSS reader is being slow reading a dataset with a lot of files, variables, many timesteps, numerous blocks but very, very few cells and points. I am comparing between 5.9.1 and 5.10.0. 5.10.0 is about 5 to 10 times slower. Here i...The IOSS reader is being slow reading a dataset with a lot of files, variables, many timesteps, numerous blocks but very, very few cells and points. I am comparing between 5.9.1 and 5.10.0. 5.10.0 is about 5 to 10 times slower. Here is how to replicate:
* I am giving you two files, spreader32 and exampleFile.e. Create a directory work. Move spreader32 and exampleFile.e into work. "source spreader32". You should now see a dataset called exampleDataset.e.32.[00-31].
* 5.10.0, Linux, remote server. I'm using 16 ranks, I don't know what 2 would do.
* 5.9.1, Linux, remote server. I'm using 16 ranks, I don't know what 2 would do.
* With 5.9.1 open exampleDataset.e.32.*. Apply.
* With 5.10.0 open exampleDataset.e.32.*. BE SURE TO TURN ALL VARIABLES OFF. Apply.
* Now, step forward in time with 5.9.1. Count seconds to next timestep. Should be 2 seconds to 5 seconds (on Chama)
* Now, step forward in time with 5.10.0. Count seconds to next timestep. Should be about 30 or more seconds (on Chama)
Spread, we should have around 5,000 cells and points. 100 timesteps. 13 blocks. No variables turned on (but lots of variables, maybe 100 or so).
5.10.0 is about 5 to 10 times slower than 5.9.1. This is a critical bug.
* Just to see how horrible loading all the variables is, on 5.10.0, turn all the variables on and hit apply. On Chama this takes minutes.
I will send exampleFile.e and spreader32 to Utkarsh.
OK to slip to 5.11 if the fix isn't easy or safe.
@utkarsh.ayachit5.10.1 (Winter 2022)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17963Changing axis data scale causes axes to grow out of view-able area2022-03-03T17:14:07-05:00wspearChanging axis data scale causes axes to grow out of view-able areaThis error occurred both with my data set and this simple test.csv example. The attached python trace shows the steps I used to see the error. In summary I loaded the data, ran 'table to points' on it (and set up the x/y/z coordinates), ...This error occurred both with my data set and this simple test.csv example. The attached python trace shows the steps I used to see the error. In summary I loaded the data, ran 'table to points' on it (and set up the x/y/z coordinates), ran 'warp by scalar' on it and set the scaling factor to .00001. I set the data to render as 3D glyph cubes. I then turned on the Axes Grid and went to the advanced Axes Grid editing interface. When I set the Z data scaling factor to .00001 to match the warp scaling factor the Axes Grid expanded out of view. Even using smaller scaling factors seems to cause the entire grid to grow in a way that doesn't seem consistent with the intended results of using this feature.
This axis scaling behavior seems to occur even without changing the point rendering to 3D or using the 'warp by scalar' filter.
[AxisWarpBug.py](/uploads/278d38574505a223d43dde8c4d5298c4/AxisWarpBug.py)
[test.csv](/uploads/9bc6541919ce7806ca39c970bfb291af/test.csv)https://gitlab.kitware.com/paraview/paraview/-/issues/21235pio reader seg faults on warnings for client-server2022-03-03T17:48:24-05:00Boonthanome Nouanesengsypio reader seg faults on warnings for client-serverThe PIO Reader will output a warning for various reasons, for example, when it cannot find any data files in a directory. When you are on a client-server connection and a warning appears, it kills the client-server connection, and Paravi...The PIO Reader will output a warning for various reasons, for example, when it cannot find any data files in a directory. When you are on a client-server connection and a warning appears, it kills the client-server connection, and Paraview seg faults. When a warning is displayed when trying to load data locally, the warning appears, but does not crash Paraview.
I am using Paraview 5.9.1, and using a client-server connection with 16 processes.
Example dataset: [todd2_bad.pio](/uploads/d8efafd0a79e7f931694a1a78df00d1b/todd2_bad.pio)
The example pio file points to a directory that does not exist, so trying to load it will always generate a warning message.
To reproduce:
1. create a client-server connection
2. try to load the example dataset
3. the ssh connection will be killed, and Paraview will seg fault
Below is the output I get when trying to load the file, and Paraview seg faults. Note the last part about an error in `vtkSocketCommunicator`. In the PIO Reader, warnings are generated using `vtkGenericWarningMacro()`. Is there something special needed in order for `vtkGenericWarningMacro()` to work in parallel?
```
( 79.349s) [paraview ] vtkOutputWindow.cxx:86 WARN| Generic Warning: In /tmp/pflarr/paraview-builds/toss3/snow/server/5.9.1-osmesa_intel-19.1.3_openmpi-3.1.6_python-system3/superbuild/paraview/src/VTK/IO/PIO/PIOAdaptor.cxx, line 244
Dump directory does not exist: /users/boonth/scratch/eap/pio_datasets/todd2/dumpsnothere
( 79.389s) [paraview ] vtkOutputWindow.cxx:76 ERR| ERROR: In /tmp/pflarr/paraview-builds/toss3/snow/server/5.9.1-osmesa_intel-19.1.3_openmpi-3.1.6_python-system3/superbuild/paraview/src/VTK/IO/PIO/vtkPIOReader.cxx, line 130
vtkPIOReader (0x30b7ee0): Error in pio description file
( 79.394s) [paraview ] vtkOutputWindow.cxx:76 ERR| ERROR: In /tmp/pflarr/paraview-builds/toss3/snow/server/5.9.1-osmesa_intel-19.1.3_openmpi-3.1.6_python-system3/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkPVCompositeDataPipeline (0x30b5d80): Algorithm vtkPIOReader(0x30b7ee0) returned failure for request: vtkInformation (0x30b7b30)
Debug: Off
Modified Time: 95448
Reference Count: 1
Registered Events: (none)
Request: REQUEST_INFORMATION
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
( 79.479s) [paraview ]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x7ffb48c7bba0): Could not receive tag. 55627
```
@cory.quammen @patchett20025.10.1 (Winter 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21074Client information does not show VTK version.2022-03-03T20:34:40-05:00Jaswant PanchumartiClient information does not show VTK version.It would help if the VTK version was populated. I noticed it in the latest rc binary from paraview.org but I remember it also happens with older versions of ParaView (5.9.0 for example).
![image](/uploads/8d2af3646a9db0d660c1d925a5ed597...It would help if the VTK version was populated. I noticed it in the latest rc binary from paraview.org but I remember it also happens with older versions of ParaView (5.9.0 for example).
![image](/uploads/8d2af3646a9db0d660c1d925a5ed597e/image.png)
```bash
Client Information:
Version: 5.10.0-RC1
VTK Version:
Qt Version: 5.12.9
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /home/ITER/jspanchu/Downloads/ParaView-5.10.0-RC1-MPI-Linux-Python3.9-x86_64/lib/python3.9
Python Library Version: 3.9.5 (default, Sep 24 2021, 21:29:01) [GCC 7.3.1 20180303 (Red Hat 7.3.1-5)]
Python Numpy Support: On
Python Numpy Path: /home/ITER/jspanchu/.local/lib/python3.9/site-packages/numpy
Python Numpy Version: 1.21.2
Python Matplotlib Support: On
Python Matplotlib Path: /home/ITER/jspanchu/.local/lib/python3.9/site-packages/matplotlib
Python Matplotlib Version: 3.4.3
Python Testing: Off
MPI Enabled: On
ParaView Build ID: superbuild 804a787c9ac8f9b0f8abc7c3001d1e61eeb15208 (!922)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 16
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 3.2.0 NVIDIA 440.95.01
OpenGL Renderer: Tesla T4/PCIe/SSE2
Connection Information:
Remote Connection: No
```5.10.1 (Winter 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21170pqPythonUtils.h not installed2022-03-03T20:39:43-05:00Charles GueunetpqPythonUtils.h not installedIf your ParaView plugin try to include "pqPythonUtils.h" or any file that tries to include it, you may have an error like the following one:
```
In file included from /home/charles/Software/install/paraview/include/paraview-5.10/pqPytho...If your ParaView plugin try to include "pqPythonUtils.h" or any file that tries to include it, you may have an error like the following one:
```
In file included from /home/charles/Software/install/paraview/include/paraview-5.10/pqPythonScriptEditor.h:38,
from /home/charles/Local/Software/sources/paraview/plugins/...[hidden]:
/home/charles/Software/install/paraview/include/paraview-5.10/pqPythonEditorActions.h:36:10: fatal error: pqPythonUtils.h: No such file or directory
36 | #include "pqPythonUtils.h"
``5.10.1 (Winter 2022)Charles GueunetCharles Gueunethttps://gitlab.kitware.com/paraview/paraview/-/issues/21105ParaView 5.10.0-RC2: SaveExtract volumetric cinema database crash2022-03-03T20:58:54-05:00Jean M. FavreParaView 5.10.0-RC2: SaveExtract volumetric cinema database crashSteps to reproduce:
0) download ParaView-5.10.0-RC2-MPI-Linux-Python3.9-x86_64.tar.gz
1) Create a simple source (Superquadric). Apply
2) Create an Extractor (Cinema Volumetric PNG). Apply
3) Click on Save Extracts. Apply.
4) the applica...Steps to reproduce:
0) download ParaView-5.10.0-RC2-MPI-Linux-Python3.9-x86_64.tar.gz
1) Create a simple source (Superquadric). Apply
2) Create an Extractor (Cinema Volumetric PNG). Apply
3) Click on Save Extracts. Apply.
4) the application seg-faults
this explains perhaps the issue documented in https://discourse.paraview.org/t/createextractor-cinemavolumetricpng-crash/84895.10.1 (Winter 2022)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21182paraview_add_client macro without a APPLICATION_XMLS fails to create any proxy2022-03-03T21:39:55-05:00Mathieu Westphal (Kitware)paraview_add_client macro without a APPLICATION_XMLS fails to create any proxyUsing paraview_add_client macro without a APPLICATION_XMLS result in a non fonctionning application unable to create any proxy
The following CMakeLists would not work
```
# The main cmake macro to create a paraview based application
par...Using paraview_add_client macro without a APPLICATION_XMLS result in a non fonctionning application unable to create any proxy
The following CMakeLists would not work
```
# The main cmake macro to create a paraview based application
paraview_client_add(
NAME spreadsheet_paraview
VERSION "1.0.1"
SOURCES ${sources} ${ui_files}
MAIN_WINDOW_CLASS SpreadSheetMainWindow
ORGANIZATION "Kitware SAS."
TITLE "Spreadsheet ParaView")
target_link_libraries(spreadsheet_paraview
PRIVATE
ParaView::RemotingSettings)
```
![image](/uploads/176210773d46ad1075b988150efc9c46/image.png)
Find a full example here: [Spreadsheet.tgz](/uploads/6d9e117b35eb0d26e041df6a60e4cc4b/Spreadsheet.tgz)https://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/21139File Dialog 'Look In' combo box wrongly set the first time2022-03-03T22:01:52-05:00Timothee ChabatFile Dialog 'Look In' combo box wrongly set the first timeWhen opening the file dialog for the first time in a ParaView session, the 'look in' combobox and the file explorer are not synced.
'Look In' is always set to `/` and the file explorer to the current directory (see screenshot).
Cannot r...When opening the file dialog for the first time in a ParaView session, the 'look in' combobox and the file explorer are not synced.
'Look In' is always set to `/` and the file explorer to the current directory (see screenshot).
Cannot reproduce with 5.10
![filedialog](/uploads/9bed4fdf1018f9e37e00e50ed42b3a6e/filedialog.png)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21157Add button to control columns visibility in FindData panel2022-03-03T22:26:02-05:00Lucas GivordAdd button to control columns visibility in FindData panelIn the FindData panel, we want to be able to choose the array to be shown in the spreadsheet showing the data, similar to the spreadhsheet view.In the FindData panel, we want to be able to choose the array to be shown in the spreadsheet showing the data, similar to the spreadhsheet view.Lucas GivordLucas Givordhttps://gitlab.kitware.com/paraview/paraview/-/issues/21168build.md should mention if Qt6 is supported or not2022-03-03T22:29:10-05:00Sean McBridebuild.md should mention if Qt6 is supported or notbuild.md says "optional dependencies: Qt5, Version 5.12 or newer"
When saying "Qt5", is this exclusionary to Qt6? Or is the document older and it means to exclude Qt4?
For people like me that are building Paraview for the first time, ...build.md says "optional dependencies: Qt5, Version 5.12 or newer"
When saying "Qt5", is this exclusionary to Qt6? Or is the document older and it means to exclude Qt4?
For people like me that are building Paraview for the first time, and know absolutely nothing about Qt and its version scheme, it would be nice to add a sentence to address Qt6 compatibility.