ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-08-24T07:08:22-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21500Slice filter does not work with cell data on OverlappingAMR2022-08-24T07:08:22-04:00Håkon Strandenesh.strandenes@km-turbulenz.noSlice filter does not work with cell data on OverlappingAMRI just tried a recent nightly build of Paraview (`ParaView-master-5.10.1-1596-g107be2e19c-MPI-Linux-Python3.9-x86_64`) and discovered a bug that have appeared since 5.10.
When using the _Slice_ filter on an AMR dataset the cell data is ...I just tried a recent nightly build of Paraview (`ParaView-master-5.10.1-1596-g107be2e19c-MPI-Linux-Python3.9-x86_64`) and discovered a bug that have appeared since 5.10.
When using the _Slice_ filter on an AMR dataset the cell data is not part of the output as before. Sometimes they are absent and sometimes they show as _(Partial)_.
Steps to reproduce:
1. Open Paraview
2. AMR Gaussian Source, default settings, Apply
3. Slice in for instance Z direction, Apply
4. Observe that the cell-centered values "Centroid" and "Gaussian-Pulse" is not present in the slice
On 5.10 this worked flawlessly. See screenshot with 5.10 (working) to the left, nightly build as mentioned to the right:
![Screenshot_from_2022-08-11_10-41-09](/uploads/a012a80c3434ce451dca6907fac1e3c1/Screenshot_from_2022-08-11_10-41-09.png)
Here is a screenshot from a "real" AMR dataset where the cell-centered `P_RMS` shows up as _(Partial)_, but without any apparent data on the slice:
![Screenshot_from_2022-08-11_10-50-00](/uploads/9e9b7fde29d118b7937efa051407bf60/Screenshot_from_2022-08-11_10-50-00.png)5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/20294Please document PBR2022-08-25T16:10:47-04:00W. Alan ScottPlease document PBRPlease add documentation for PBR to ParaView. At least, add a blog post, and add PBR into the ParaView guide.
OK to assign to Sandia, if needed.Please add documentation for PBR to ParaView. At least, add a blog post, and add PBR into the ParaView guide.
OK to assign to Sandia, if needed.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/21516Surface with Edges after clipping is different before - It creates additional...2022-08-25T20:30:25-04:00Leila SaberiSurface with Edges after clipping is different before - It creates additional edges or removes some edgesI am using Paraview 10.1 and I have a grid that looks fine before clipping (like the first figure), but after I clip it, there are extra lines in the grid when I choose "surface with edges" (second figure) or sometimes it deletes some of...I am using Paraview 10.1 and I have a grid that looks fine before clipping (like the first figure), but after I clip it, there are extra lines in the grid when I choose "surface with edges" (second figure) or sometimes it deletes some of the edges. Could someone helps me with this issue? What I am doing is simply using the clip and then choosing the representation to be "surface with edges". Thanks.
![1](/uploads/3f23669179b9ba73c94bac4df4c74a83/1.PNG)
![2](/uploads/f111f1c26e4a9424c8fd5520b68374d5/2.PNG)https://gitlab.kitware.com/paraview/paraview/-/issues/21470loading a state file in the GUI from the --state command line argument causes...2022-08-27T18:50:03-04:00Andrew Bauerloading a state file in the GUI from the --state command line argument causes issues with recent filesUsing PV master (6369ae9cdec0e3243e9e5a6d475cddabf786a4ce), if a user loads a .pvsm state file into the gui from the command line, e.g. `./paraview --state=<mystatefile.pvsm>` and then closes ParaView. The next time the user runs ParaVie...Using PV master (6369ae9cdec0e3243e9e5a6d475cddabf786a4ce), if a user loads a .pvsm state file into the gui from the command line, e.g. `./paraview --state=<mystatefile.pvsm>` and then closes ParaView. The next time the user runs ParaView that file is shown in `File->Recent Files` but when the user tries to access it through that menu they get the following error:
```
[acbauer@oa debug]$ bin/paraview
critical: In /home/acbauer/Code/ParaView/ParaView/Qt/ApplicationComponents/pqStandardRecentlyUsedResourceLoaderImplementation.cxx, line 112
critical: State file no longer exists: ' "/fromcommandlineargs.pvsm" '
```Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/20216Running tests to build examples is confusing2022-08-27T18:50:04-04:00Utkarsh AyachitRunning tests to build examples is confusingTime and time again people are confused that PARAVIEW_BUILD_EXAMPLES doesn't really build the examples, but instead add tests that you're supposed to run to build those examples. We need to add some mechanism to build the examples during...Time and time again people are confused that PARAVIEW_BUILD_EXAMPLES doesn't really build the examples, but instead add tests that you're supposed to run to build those examples. We need to add some mechanism to build the examples during standard build to avoid this confusion.
cc: @ben.boeckelBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/21512Incomplete scipy installation2022-08-30T14:50:52-04:00Dean ThomasIncomplete scipy installation
The SciPy installation on Paraview 5.10.1 seems to be incomplete. When I try to load scipy's solve_ivp, I receive the following error message.
```
from scipy.integrate import solve_ivp
Traceback (most recent call last):
File "<conso...
The SciPy installation on Paraview 5.10.1 seems to be incomplete. When I try to load scipy's solve_ivp, I receive the following error message.
```
from scipy.integrate import solve_ivp
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/Applications/ParaView-5.10.1.app/Contents/Python/scipy/integrate/__init__.py", line 94, in <module>
from ._bvp import solve_bvp
File "/Applications/ParaView-5.10.1.app/Contents/Python/scipy/integrate/_bvp.py", line 8, in <module>
from scipy.sparse.linalg import splu
File "/Applications/ParaView-5.10.1.app/Contents/Python/scipy/sparse/linalg/__init__.py", line 114, in <module>
from .eigen import *
File "/Applications/ParaView-5.10.1.app/Contents/Python/scipy/sparse/linalg/eigen/__init__.py", line 9, in <module>
from .arpack import *
File "/Applications/ParaView-5.10.1.app/Contents/Python/scipy/sparse/linalg/eigen/arpack/__init__.py", line 20, in <module>
from .arpack import *
ModuleNotFoundError: No module named 'scipy.sparse.linalg.eigen.arpack.arpack'
```
I get the same error on Paraview 5.9.1. But I am able to successfully import solve_ivp on my Anaconda python installation from the command line.
Here is the information from my Paraview installation on an Intel Mac, MacOS 12.5.1
```
Client Information:
Version: 5.10.1
VTK Version: 9.0.20210922
Qt Version: 5.15.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: /Applications/ParaView-5.10.1.app/Contents/Libraries/lib/python3.9
Python Library Version: 3.9.5 (default, Mar 14 2022, 15:46:44) [Clang 12.0.0 (clang-1200.0.32.29)]
Python Numpy Support: On
Python Numpy Path: /Applications/ParaView-5.10.1.app/Contents/Python/numpy
Python Numpy Version: 1.21.1
Python Matplotlib Support: On
Python Matplotlib Path: /Applications/ParaView-5.10.1.app/Contents/Python/matplotlib
Python Matplotlib Version: 3.2.1
Python Testing: Off
MPI Enabled: On
ParaView Build ID: superbuild 6dd132601dbb2a9ebdc0d31825989f5b92595b76 (!969)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 8
OpenGL Vendor: ATI Technologies Inc.
OpenGL Version: 4.1 ATI-4.8.101
OpenGL Renderer: AMD Radeon Pro 560 OpenGL Engine
Connection Information:
Remote Connection: No
```
```
print(sys.path)
['/Applications/ParaView-5.10.1.app/Contents/Python', '/Applications/ParaView-5.10.1.app/Contents/Libraries/lib/python39.zip', '/Applications/ParaView-5.10.1.app/Contents/Libraries/lib/python3.9', '/opt/glr/paraview/paraview-ci/build/install/lib/lib-dynload']
```https://gitlab.kitware.com/paraview/paraview/-/issues/21521Building ParaView v4.0.02022-08-31T07:12:32-04:00saulo1131Building ParaView v4.0.0I need to use Paraview on an old machine that has old OpenGL. So I tried installing an older version of Paraview, eg v4.0.0. But when I do git submodule update --init --recursive, it returns some errors to clone some submodules. can anyb...I need to use Paraview on an old machine that has old OpenGL. So I tried installing an older version of Paraview, eg v4.0.0. But when I do git submodule update --init --recursive, it returns some errors to clone some submodules. can anybody help me, please?https://gitlab.kitware.com/paraview/paraview/-/issues/20890SIGABRT triggered when using the Append Location Attributes filter2022-09-02T09:09:29-04:00Pierre CrepierSIGABRT triggered when using the Append Location Attributes filterHello,
I have a post-processing pipeline that makes use of the Append Location Attributes in order to get access to the cell center coordinates.
Unfortunately, the pileline sometimes crashes without being reproducible consitently. (the ...Hello,
I have a post-processing pipeline that makes use of the Append Location Attributes in order to get access to the cell center coordinates.
Unfortunately, the pileline sometimes crashes without being reproducible consitently. (the pipeline crashed once in 30 runs this morning, but then ran fine when re-running it for the faulty case)
Paraview gives a stack trace:
```
realloc(): invalid old size
Loguru caught a signal: SIGABRT
Stack trace:
19 0x155554aece83 clone + 67
18 0x15554f5962de /lib64/libpthread.so.0(+0x82de) [0x15554f5962de]
17 0x15554f34d196 /cm/shared/apps/paraview/5.9.0/bin/../lib/libtbb.so.2(+0x1d196) [0x15554f34d196]
16 0x15554f34d206 /cm/shared/apps/paraview/5.9.0/bin/../lib/libtbb.so.2(+0x1d206) [0x15554f34d206]
15 0x15554f35156f /cm/shared/apps/paraview/5.9.0/bin/../lib/libtbb.so.2(+0x2156f) [0x15554f35156f]
14 0x15554f353760 /cm/shared/apps/paraview/5.9.0/bin/../lib/libtbb.so.2(+0x23760) [0x15554f353760]
13 0x15554f3595ea /cm/shared/apps/paraview/5.9.0/bin/../lib/libtbb.so.2(+0x295ea) [0x15554f3595ea]
12 0x15552f88918e /cm/shared/apps/paraview/5.9.0/bin/../lib/../lib/libvtkFiltersCore-pv5.9.so.1(+0x12418e) [0x15552f88918e]
11 0x155550f7c31e vtkUnstructuredGrid::GetCell(long long, vtkGenericCell*) + 750
10 0x155550ec7408 vtkPolyhedron::SetFaces(long long*) + 392
9 0x15554f9c9cec vtkAbstractArray::SetNumberOfValues(long long) + 44
8 0x15554f9b425b /cm/shared/apps/paraview/5.9.0/bin/../lib/libvtkCommonCore-pv5.9.so.1(+0x20625b) [0x15554f9b425b]
7 0x15554fb66c3b vtkAOSDataArrayTemplate<long long>::ReallocateTuples(long long) + 283
6 0x155554a7706b realloc + 827
5 0x155554a75edc /lib64/libc.so.6(+0x84edc) [0x155554a75edc]
4 0x155554a71fdc /lib64/libc.so.6(+0x80fdc) [0x155554a71fdc]
3 0x155554a6b897 /lib64/libc.so.6(+0x7a897) [0x155554a6b897]
2 0x155554a12b25 abort + 295
1 0x155554a2870f gsignal + 271
0 0x155554a28790 /lib64/libc.so.6(+0x37790) [0x155554a28790]
( 66.528s) [ A3BFE700] :0 FATL| Signal: SIGABRT
error: exception occurred: Child aborted
```
The dataset is a multiblock dataset from a cgns file.
I'll try to see if the problem is solved when using a merged multiblock dataset (so single block instead of multi block)5.11 (Spring 2022)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21527Text Annotation not in Filter Menu2022-09-02T10:45:56-04:00Phil SmithText Annotation not in Filter MenuThe Text Annotation is not in the filter menu. It can be selected via the search tool, so I know it is implemented, but it is just not in the menu. I looked in the alphabetical menu as well as the Annotation menu
Tested on Mac OS Monter...The Text Annotation is not in the filter menu. It can be selected via the search tool, so I know it is implemented, but it is just not in the menu. I looked in the alphabetical menu as well as the Annotation menu
Tested on Mac OS Monterey x86 5.11.0-RC1 master. The can.ex2 was used.https://gitlab.kitware.com/paraview/paraview/-/issues/21465Environment Lighting doesn't used the good Background Texture2022-09-03T01:47:01-04:00Lucas GivordEnvironment Lighting doesn't used the good Background Texturewhen we enable `Use environment lighting`, it seems that when you select another background texture and then reuse the first one, the background texture used remains the second one.
Step to reproduce :
- create a sphere
- disable light...when we enable `Use environment lighting`, it seems that when you select another background texture and then reuse the first one, the background texture used remains the second one.
Step to reproduce :
- create a sphere
- disable lightkit
- use pbr in lighting `interpolation`
- switch `Background Color Mode` to Skybox and select an hdr texture
- enable `Use Environment Lighting`
![render0](/uploads/81e07392c72f6457dc52d124e27d5870/render0.png)
- use another hdr texture
![render1](/uploads/aaa7a6b14dfb9f79814ec1dbbe676f02/render1.png)
- and now switch to the first hdr texture
![render2](/uploads/2b77a0726a9644e55ef22f4444b3397d/render2.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21528Using the TIFF writer followed by the TIFF reader flips image along Y axis2022-09-03T16:04:30-04:00Dan LipsaUsing the TIFF writer followed by the TIFF reader flips image along Y axisWriting a screenshot or data with the TIFF writer and loading it with the TIFF reader (or with the GLDAL TIFF reader) flips the image along the Y axis. Loading the TIFF in QGIS does not flip it.
See the attached paraview state file and ...Writing a screenshot or data with the TIFF writer and loading it with the TIFF reader (or with the GLDAL TIFF reader) flips the image along the Y axis. Loading the TIFF in QGIS does not flip it.
See the attached paraview state file and TIFF file produced by writing the data produced by Resample To Image.
The state file renders the following:
![all](/uploads/557213c3abd0b3d3a7b71f6fdb3e5ee6/all.png)
[arrow.pvsm](/uploads/647a82cd9b2510af99f3bc89f1d060ee/arrow.pvsm)
[arrow.tif](/uploads/177a8c5cff6204a8a272bdf25a5ec59e/arrow.tif)https://gitlab.kitware.com/paraview/paraview/-/issues/15099Save state misses Show Plane state2022-09-06T19:10:39-04:00Kitware RobotSave state misses Show Plane state**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15099). Further discussion may take place here.**
---
Save State (or Load State, for that matter) don't properly remember the Sh...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15099). Further discussion may take place here.**
---
Save State (or Load State, for that matter) don't properly remember the Show Plane state.
* Linux, 4.2.0, local server.
* Load disk_out_ref.exo. Apply.
* Slice. Turn off Show Plane. Apply.
* Save State.
* Reset Session
* Load State.
* Be sure to click on the Slice filter in the Pipeline Browser, giving it focus.
The plane tool will be visible. This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/21525Slice filter: copy+paste properties does not paste "show plane"2022-09-07T05:56:30-04:00Menno Deij - van RijswijkSlice filter: copy+paste properties does not paste "show plane"It would be nice if "Show plane" property is also copied and pasted. I keep turning off the planes...It would be nice if "Show plane" property is also copied and pasted. I keep turning off the planes...https://gitlab.kitware.com/paraview/paraview/-/issues/21522Artifacts displaying with clip filter and different Arrays2022-09-07T08:21:38-04:00Phil SmithArtifacts displaying with clip filter and different ArraysTested MAC Monterey 12.4 x86, local, 5.11.0-RC1 nightly
To Reproduce:
- Open can.ex2 --Apply
- Color by displacement
- select clip --apply
- Color by Vel
- Show both the can and the clip
- The clip will have artifacts shown on it. Rota...Tested MAC Monterey 12.4 x86, local, 5.11.0-RC1 nightly
To Reproduce:
- Open can.ex2 --Apply
- Color by displacement
- select clip --apply
- Color by Vel
- Show both the can and the clip
- The clip will have artifacts shown on it. Rotate it around and they will vary.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/215405.11-RC1: Elevation range not correct2022-09-08T03:19:42-04:00Menno Deij - van Rijswijk5.11-RC1: Elevation range not correctIn the attached data and state file, the elevation is computed along the Y-axis. The range in elevation values should be `[0.198755 .. 0.2]` but the data reports `[0..1]` and so does the color bar.
@mwestphal
[elevation.zip](/uploads/...In the attached data and state file, the elevation is computed along the Y-axis. The range in elevation values should be `[0.198755 .. 0.2]` but the data reports `[0..1]` and so does the color bar.
@mwestphal
[elevation.zip](/uploads/25cde13855519c8f98508c1e31e85419/elevation.zip)
![image](/uploads/e3483a161bc74f22e13e09b35adfdc80/image.png)5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20898Enable easier 3DConnexion device usage by ParaView2022-09-08T15:47:10-04:00Cory Quammencory.quammen@kitware.comEnable easier 3DConnexion device usage by ParaViewCurrently ParaView supports interaction via 3DConnexion devices (e.g. SpaceNavigator) through the VRPlugin. Using this plugin requires a somewhat complex configuration procedure, and requires that the 3DConnexion system drivers not be pr...Currently ParaView supports interaction via 3DConnexion devices (e.g. SpaceNavigator) through the VRPlugin. Using this plugin requires a somewhat complex configuration procedure, and requires that the 3DConnexion system drivers not be present on the system. Please provide an alternative implementation that does not require the VRPlugin that works with the 3DConnexion system drivers.5.11 (Spring 2022)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/215365.11.0-RC1 Hierarchical Fractal source has rendering artifacts with Ghost Lev...2022-09-08T15:54:37-04:00Ethan Stam5.11.0-RC1 Hierarchical Fractal source has rendering artifacts with Ghost Levels enabled@cory.quammen @patchett2002 @maxwelljackson002
Using 5.11.0-RC1 on MacOS and Windows, when rendering the surface of the heirarchical fractal source with ghost levels enabled, the rendering is messed up.
Steps to reproduce:
1. Sources ...@cory.quammen @patchett2002 @maxwelljackson002
Using 5.11.0-RC1 on MacOS and Windows, when rendering the surface of the heirarchical fractal source with ghost levels enabled, the rendering is messed up.
Steps to reproduce:
1. Sources -> hierarchical fractal -> default values -> apply
2. Change renderview from 2D to 3D
3. Color by depth and choose the surface representation.
4. Reset zoom to data and rotate the dataset
![Screen_Shot_2022-09-06_at_2.58.45_PM](/uploads/02c24472e29703d8647ac94a61e5b371/Screen_Shot_2022-09-06_at_2.58.45_PM.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21537Cell Vertex Ordering is wrong for a Y=0 Slice of a HyperTreeGrid2022-09-09T06:00:04-04:00Julien FaustyCell Vertex Ordering is wrong for a Y=0 Slice of a HyperTreeGrid# Description
When slicing a `vtkHyperTreeGrid` using a plane normal to the Y direction the generated PolyData has cells with bad vertex ordering. This does not occur when the direction is X or Z.
![screenshot_issue](/uploads/650630b76...# Description
When slicing a `vtkHyperTreeGrid` using a plane normal to the Y direction the generated PolyData has cells with bad vertex ordering. This does not occur when the direction is X or Z.
![screenshot_issue](/uploads/650630b76f22f85102aed17befdaf4ec/screenshot_issue.png)
# Steps to reproduce
1. Generate a random HyperTreeGrid using the "RandomHyperTreeGridSource" filter
2. Slice the data with a Y = 0 plane
State file: [y_slice_issue_htg.pvsm](/uploads/7f90067cd7242ab4f830a0fe6b708039/y_slice_issue_htg.pvsm)https://gitlab.kitware.com/paraview/paraview/-/issues/21545Memory usage explodes when generating global Ids for 1024^3 dataset2022-09-09T12:03:07-04:00Eve Le GuillouMemory usage explodes when generating global Ids for 1024^3 datasetHello all,
I use Paraview 5.10.1.
I would like to create in sequential a dataset that is 1024^3 that has global ids.
For this, I use the following Pipeline:
Wavelet > ResampleToImage > GenerateGlobalIds
To create the 1024^3, I s...Hello all,
I use Paraview 5.10.1.
I would like to create in sequential a dataset that is 1024^3 that has global ids.
For this, I use the following Pipeline:
Wavelet > ResampleToImage > GenerateGlobalIds
To create the 1024^3, I set the option of the second filter to:
resampleToImage1.SamplingDimensions = [1024,1024,1024]
Here is the complete pipeline I use: [prepare_wavelet_1024.py](/uploads/0a9f6d4cfa4886462f0cec47b1d7b7e4/prepare_wavelet_1024.py)
This pipeline always crashes due to a lack of RAM. If I instead use GenerateIds, then the Pipeline executes without any issue. This was tested on several computers, including one that has 128GB of RAM, which should be enough. The problem appears to happen when creating the kd-tree during GenerateGlobalIds.
Many thanks,https://gitlab.kitware.com/paraview/paraview/-/issues/21547Rescale same field name on different data with two renderviews2022-09-12T02:14:00-04:00Eloise BRescale same field name on different data with two renderviewsHello,
I have a question about the "normal" behavior of paraview:
I have two data and both have a the same field (let's say distance) but on different units (one in millimeter and other in kilometer). I want to compare them, so I load ...Hello,
I have a question about the "normal" behavior of paraview:
I have two data and both have a the same field (let's say distance) but on different units (one in millimeter and other in kilometer). I want to compare them, so I load both data and display each data in a renderview (not linked) and for both, I displayed the distance field.
Both renderviews have the same scale and it's not confortable to compare (as one scale is higher with a 6 factor). I rescale the first data and it's all right: I have my two data with different scales on the same field. But when my mouse hover the second renderview, there is an update in the second renderview and the scale change and become the same as the first renderview.
Is it normal that the scale are synchronized each time my mouse hover on the non active renderview ? I find this behavior a bit weird: If it's desynchronized, it should not be updated, and if it is synchronized, shouldn't it be directly synchronized when triggered in the first renderview ?
Ideally, I would like have desynchronized scale for each renderview, Is there some option to do this ?
I tried this with a paraview in the master branch (not the commit in mind sorry)
Thanks for your help,
Regards,
Eloïse