ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:47:06-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/18972active stereo does not work with Qt 5.12.2 on linx2024-03-07T20:47:06-05:00Utkarsh Ayachitactive stereo does not work with Qt 5.12.2 on linxActive stereo does not work with Qt 5.12.2 on linux.
Seems to work fine with Qt 5.11.1 or 5.10.1Active stereo does not work with Qt 5.12.2 on linux.
Seems to work fine with Qt 5.11.1 or 5.10.15.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/17794Catalyst rendering-python edition missing SaveScreenshot proxy.2024-03-07T20:47:45-05:00Utkarsh AyachitCatalyst rendering-python edition missing SaveScreenshot proxy.This is needed to save screenshots from Catalyst runs.This is needed to save screenshots from Catalyst runs.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/16870Cleanup ParaView installations on Linux.2022-07-25T20:54:25-04:00Utkarsh AyachitCleanup ParaView installations on Linux.Refactoring tasks:
* [x] disable shared forwarding by default and use rpaths. All relevant linux systems now support rpath. ParaView executables should have rpath set to `$ORIGIN/../lib`. This will affect how we presently support `--mesa...Refactoring tasks:
* [x] disable shared forwarding by default and use rpaths. All relevant linux systems now support rpath. ParaView executables should have rpath set to `$ORIGIN/../lib`. This will affect how we presently support `--mesa-llvm` etc. Need a workaround for that.
* [x] don't put libraries under `<prefix>/lib/paraview-$version`, instead just use `<prefix>/lib`. This will make it easier with putting together ParaView-based application packages. Those other apps, don't need to separately deal with locating ParaView libraries under the version specific directory.
* [x] all libraries installed under `<prefix>/lib` should be versioned.
* [x] all plugins are installed under `<prefix>/lib/paraview-$version/plugins`. Plugins `so`s are not versioned i.e. don't have ParaView version suffix on them. The plugins configuration file (currently `.plugins`) should be under this directory as well.
* [x] all shared resources e.g. PDFs, config files, icons, appdata etc. should be installed `<prefix>/share/paraview-$version`.
* [x] Python modules including Python-C libraries are installed under `<prefix>/lib/python$pyversion/site-packages`(note the absence of ParaView version number).
* [x] make build and install directories as consistent as possible. It's annoying to have to determine if we are running from the build dir or the install location and then do tasks accordingly. Why can't we have them be the same?
* [ ] add documentation for what goes where so that we can refer developer to it when adding any new install rules.
* [ ] ensure that `make|ninja install` target works when `BUILD_DOCUMENTATION` is `ON`.
Other issues:
* [x] Xdmf install rules are bad (#16871)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22386Color by Scalar broken on Line Width greater 12023-12-07T16:35:46-05:00Johannes GrossColor by Scalar broken on Line Width greater 1OS: macOS 13.0
ParaView Version: 5.11.2
Qt Version: 5.15.2
Description
I am trying to show a mass flow in pipes in the appended file.
When setting to Wireframe and using massflow for the color scheme, the flows are displayed fairly cor...OS: macOS 13.0
ParaView Version: 5.11.2
Qt Version: 5.15.2
Description
I am trying to show a mass flow in pipes in the appended file.
When setting to Wireframe and using massflow for the color scheme, the flows are displayed fairly correct (some pipes do not show the red color although they should) but once the Line Width is set to any number greater 1 the colors are all over the place. Line elements that have value 0 are shown in red, Pipe Elements with higher values are shown in blue. I hope this is not some rookie mistake on my end but the file seems fairly simple and straightforward, could not find any other explanation for the issue. Thank you!
[helloagain2.vtk](/uploads/15fb1563971cc7f65c6a21d91f84f52c/helloagain2.vtk)https://gitlab.kitware.com/paraview/paraview/-/issues/22179Crashing on latest Windows Update2023-06-15T10:12:20-04:00lizlivCrashing on latest Windows UpdateThe latest forced update on Windows 10 (version 22H2 os build 19045.3086) seems to have broken Paraview, it crashes on opening. I deleted and reinstalled 5.11.0 and 5.11.1 and neither of them are able to open. I tried on two different ma...The latest forced update on Windows 10 (version 22H2 os build 19045.3086) seems to have broken Paraview, it crashes on opening. I deleted and reinstalled 5.11.0 and 5.11.1 and neither of them are able to open. I tried on two different machines. The RC1 version I have installed through WSL seems to work, not sure how.https://gitlab.kitware.com/paraview/paraview/-/issues/22161Artefact when rendering with pvbatch and MPI2023-06-06T04:23:51-04:00Eve Le GuillouArtefact when rendering with pvbatch and MPIHi all,
I am using Paraview 5.11.0 and MPI 4.0.3.
I noticed a bug in the produced image when I execute the following pipeline:
Wavelet > MaskPoints(GenerateVertices = 1) > SaveScreenShot
Here is the full pipeline with the visuali...Hi all,
I am using Paraview 5.11.0 and MPI 4.0.3.
I noticed a bug in the produced image when I execute the following pipeline:
Wavelet > MaskPoints(GenerateVertices = 1) > SaveScreenShot
Here is the full pipeline with the visualization details [test.py](/uploads/22433c852033f6932a7178e92ffe2db7/test.py)
Points are shown using the RenderPointsAsSphere option.
When executing the pipeline using the command:
mpirun -n 2 pvbatch test.py
I obtain the following image:
![test](/uploads/bcf02df929f8674d70073fe85180e578/test.jpeg)
Artefacts can be seen on the image. The more processes are used, the more artefacts there are.
The problem doesn't appear when the pipeline is executed using pvserver and the paraview client.https://gitlab.kitware.com/paraview/paraview/-/issues/21836MPI issue while building Paraview on Mac2023-03-26T22:08:36-04:00Muhammad Saad AtiqueMPI issue while building Paraview on MacI am trying to build Paraview on mac. I ran ninja command and got the following error.
![image](/uploads/a31d77a664d3e0f4775c43cd23950f3c/image.png)
![image](/uploads/5df7829ed5026ab8d90eb7706541b1b5/image.png)I am trying to build Paraview on mac. I ran ninja command and got the following error.
![image](/uploads/a31d77a664d3e0f4775c43cd23950f3c/image.png)
![image](/uploads/5df7829ed5026ab8d90eb7706541b1b5/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21820ParaView Simple import into Python fails on Linux2023-03-15T07:04:58-04:00CoryParaView Simple import into Python fails on LinuxWhen trying to import ```paraview.simple``` into my Python script, I get the following error:
```
Traceback (most recent call last):
File "/home/cory/git-repos/MachLine/dev/helper_scripts/paraview_functions.py", line 3, in <module>
...When trying to import ```paraview.simple``` into my Python script, I get the following error:
```
Traceback (most recent call last):
File "/home/cory/git-repos/MachLine/dev/helper_scripts/paraview_functions.py", line 3, in <module>
import paraview.simple as pvs
File "/home/cory/Paraview/lib/python3.9/site-packages/paraview/simple.py", line 41, in <module>
from paraview import servermanager
File "/home/cory/Paraview/lib/python3.9/site-packages/paraview/servermanager.py", line 60, in <module>
from paraview.modules.vtkRemotingApplication import *
ImportError: /lib/x86_64-linux-gnu/libp11-kit.so.0: undefined symbol: ffi_type_pointer, version LIBFFI_BASE_7.0
```
I am running Linux Mint 20.2 Cinnamon 64-bit.https://gitlab.kitware.com/paraview/paraview/-/issues/21697Loading identical .py state and .pvsm states give inconsistent results2022-12-14T12:59:12-05:00Alankar DuttaLoading identical .py state and .pvsm states give inconsistent resultsI’m having a ParaView state saved as .pvsm gives correct position of colorbars and other elements. However, when the same state is stored and loaded as a .py script the colorbars get misplaced. What is the issue? (version: ParaView 5.10....I’m having a ParaView state saved as .pvsm gives correct position of colorbars and other elements. However, when the same state is stored and loaded as a .py script the colorbars get misplaced. What is the issue? (version: ParaView 5.10.1)
I’m putting in the relevant images.
Loading .pvsm state:
![image](/uploads/f697316d154c68a0ded8584968661408/image.png)
Misplaced colorbars on loading .py state produced at the same time in the GUI:
![image](/uploads/3ce703f37ba4df837afdffce2eb48bab/image.png)
The placement of the colorbars become consistent when the .py script is loaded and generated in ParaView 5.11.0 version compared to the inconsistencies in 5.10.1 version. However, the font sizes are still in-consistent and don’t give identical results. The same happens if I change the orientation axes position (not shown in these images), the python saved state keeps the orientation axes at the default lower left position but the .pvsm file works correctly and puts the orientation axes at the changed location. As a result of the font size inconsistency, parts of the text get cut off at the edges. Also, most likely because of this, same issues happen for Catalyst python states as well. Can someone more experienced in the community help me fix this issue?
Here is the screenshot of what happens on loading the .py state script in ParaView 5.11.0:
![image](/uploads/332b62d3e3627864ecc00e6785e68159/image.png)
Related: https://discourse.paraview.org/t/loading-identical-py-state-and-pvsm-states-give-inconsistent-results/10939https://gitlab.kitware.com/paraview/paraview/-/issues/21696Crash using Explicit Structured Grid Slice and Cells Extractor filter (from E...2023-06-15T10:45:39-04:00Francois MazenCrash using Explicit Structured Grid Slice and Cells Extractor filter (from Explicit Structured Grid ParaView Plugin)Using Explicit Structured Grid Slice and Cells Extractor filter triggers crashes ParaView (master branch).
Steps to reproduce:
- Load the ExplicitStructuredGrid plugin
- Create Explicit Structured Grid Generator Source, Apply
- Creat...Using Explicit Structured Grid Slice and Cells Extractor filter triggers crashes ParaView (master branch).
Steps to reproduce:
- Load the ExplicitStructuredGrid plugin
- Create Explicit Structured Grid Generator Source, Apply
- Create Explicit Structured Grid Slice and Cells Extractor, Apply
- Crash!
Call stack (relevant part only):
```
6 0x7fc01708a63d vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 199
5 0x7fc01708ca36 vtkExplicitStructuredGridAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 92
4 0x7fbfd06571f0 vtkExplicitStructuredGridPythonExtractor::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 488
3 0x7fc0164a1db7 vtkExplicitStructuredGrid::DeepCopy(vtkDataObject*) + 237
2 0x7fc0163bfbd1 vtkCellArray::DeepCopy(vtkCellArray*) + 129
1 0x7fc01633cdee /home/francois/dev/paraview/build_paraview/bin/../lib/libvtkCommonDataModel-pv5.11.so.1(+0x13cdee) [0x7fc01633cdee]
0 0x7fc01e7a2a00 /usr/lib/libc.so.6(+0x38a00) [0x7fc01e7a2a00]
( 132.129s) [paraview ] :0 FATL| Signal: SIGSEGV
```
Reproduced with master branch. Do not crash with official release 5.11.0, 5.10.1 nor 5.9.1.https://gitlab.kitware.com/paraview/paraview/-/issues/21532Animated clip flickering in 5.11 RC 12023-06-15T09:38:04-04:00Nicolas VuailleAnimated clip flickering in 5.11 RC 1Steps to reproduce:
* Sphere
* Clip
* AnimationView: add track for Clip1 / Clip type - Offset
* configure track: value go from -1 to 1
* play animation
It happens to have some random flickering. See also attached video.
![animated...Steps to reproduce:
* Sphere
* Clip
* AnimationView: add track for Clip1 / Clip type - Offset
* configure track: value go from -1 to 1
* play animation
It happens to have some random flickering. See also attached video.
![animatedClipFlicker](/uploads/211fd0334165159aa6d4b7436ee3fc12/animatedClipFlicker.mp4)
Tested on linux with official binaries of 5.11 RC 1. GPU: NVIDIA GeForce RTX 3070 Mobile
Also seen on Windows (off. binaries of RC1 too)
Not able to reproduce on master, nor in my own build of 5.11 RC1https://gitlab.kitware.com/paraview/paraview/-/issues/20880Background issues in exported image with headless pvpython2021-08-10T15:28:46-04:00Argonaut-JBackground issues in exported image with headless pvpythonWhen building Paraview (headless) with the non-default options listed below, the following issues occur in some background properties when running a `pvpython` script that exports an image:
1. `Background()` method is ignored, i.e. the...When building Paraview (headless) with the non-default options listed below, the following issues occur in some background properties when running a `pvpython` script that exports an image:
1. `Background()` method is ignored, i.e. the setting the color of the background does not work.
1. `TransparentBackground=1` parameter in `SaveScreenshot()` is ignored, i.e. background is not exported transparently.
Building Paraview 5.9.1 is done on a Linux Mint Xfce 20.2 machine with installed packages `libosmesa6-dev` `libgl1-mesa-dev` and `libxt-dev`, which succeeds with 116 warnings and no errors, with the following cmake options set:
```
PARAVIEW_USE_PYTHON=ON
PARAVIEW_USE_QT=OFF
PARAVIEW_USE_QTHELP=OFF
PARAVIEW_USE_VTKM=OFF
VTK_USE_X=OFF
VTK_OPENGL_HAS_OSMESA=ON
```
Steps to reproduce:
1. Build paraview with the options above
1. Download the two attached files
1. Run the following code with pvpython (replacing the 2nd and last line if necessary):
```
from paraview.simple import *
xdmf = XDMFReader(FileNames=[online_solution_y.xdmf'])
renderView1 = GetActiveViewOrCreate('RenderView')
xdmfDisplay = Show(xdmf, renderView1)
renderView1.ResetCamera()
renderView1.Background = [0.8333333333333, 0.6666666666666666, 0.0]
renderView1.Update()
SaveScreenshot('image.png', renderView1, ImageResolution=[594, 519], TransparentBackground=0)
```
Now:
1. Check if the background is orange.
1. Set `TransparentBackground=1` in the code above and rerun, check that the background is transparent.
Can you reproduce either non-orange background or non-transparent background or both, in the last two steps?
[online_solution_y.h5](/uploads/c72d4f4d8e7a7a7f4458d0cae4ba9f3b/online_solution_y.h5)
[online_solution_y.xdmf](/uploads/04c2fc1b0c6285fbcf889c5e4544cd50/online_solution_y.xdmf)https://gitlab.kitware.com/paraview/paraview/-/issues/20608Non integer powers of 10 cause segfault when finding2021-04-01T04:22:13-04:00Lorenzo BertiniNon integer powers of 10 cause segfault when findingIn the `Edit->Find Data` window, entering a query comparing a column with a value that has a non-integer power of 10 in the form (1e7.5) causes the program to crash by segmentation fault. It seems the program can't handle such values. I ...In the `Edit->Find Data` window, entering a query comparing a column with a value that has a non-integer power of 10 in the form (1e7.5) causes the program to crash by segmentation fault. It seems the program can't handle such values. I only tested two files, can someone reproduce consistently?
I suggest instead to produce an error message (preferably a window) stating what input values are permitted.https://gitlab.kitware.com/paraview/paraview/-/issues/20597In case of multiple screen, paraview dialogs pop up on the wrong screen2022-05-18T13:21:06-04:00MelanieCarriereIn case of multiple screen, paraview dialogs pop up on the wrong screenThis bug is reproducible on Windows OS (the issue is not on Linux), with multiple screens.
Steps to reproduce the bug :
- Open Paraview 5.9 (on Windows, with at least 2 screens)
- Try to open a dialog ("export spreadsheet", "Open", "Sa...This bug is reproducible on Windows OS (the issue is not on Linux), with multiple screens.
Steps to reproduce the bug :
- Open Paraview 5.9 (on Windows, with at least 2 screens)
- Try to open a dialog ("export spreadsheet", "Open", "Save State", "Load State", ...)
- The dialog should pop up on the same screen as ParaView, close it
- Move Paraview to the other screen
- Try to re-open the dialog
- The dialog will pop up on the previous screenhttps://gitlab.kitware.com/paraview/paraview/-/issues/20554Visualization of Line integral convolution on a surface2021-03-24T09:42:38-04:00Silvia EscayolaVisualization of Line integral convolution on a surfaceHello!!
I am using the desktop 5.9.0 version for windows and when I try to visualize the LIC representation of magnetic currents using the state file (3D-LIC.pvsm) for opening the *vti and *cml files I get weird results. The images looks...Hello!!
I am using the desktop 5.9.0 version for windows and when I try to visualize the LIC representation of magnetic currents using the state file (3D-LIC.pvsm) for opening the *vti and *cml files I get weird results. The images looks like broken and I have no idea how to solve the problem. I am sure that the files are not corrupted because the images look fine in onother computer (I attach both, ugly and nice pictures, they don't correspond to the same system but still the difference between the good ones and the "wrong" is visible). I would be very happy if someone can suggest or share any idea on how to solve that.
This is the correctly visualized system (which I could obtain when v. 5.2.0 was working on my pc):
[s_a0](/uploads/375d0544f3736b539dacc7a7388762cb/s_a0.png)
This is the erroneous:
[image__1_](/uploads/97076606fae1020fb60bdc0bb859866a/image__1_.png)
More details: I use the desktop version for windows. I was using v 5.2.0 and it was working fine, but now when I try to open the state file the program crashes completely. My guess is that the last windows update is the source of the problem. Anyway, I tried versions 5.5.2, 5.6.2 and 5.9.0 and all of them can open the state file but then the images look like the ugly plots attached.
Thanks a lot.
[3D-LIC.pvsm](/uploads/55c99809eb0a8dc4e584c953247c43b0/3D-LIC.pvsm)!
[mol-bohr.cml](/uploads/b994c59318543a2725a0538947cc278a/mol-bohr.cml)
[jvec.rar](/uploads/ebf2fa1230b2a40b27cd951d2c9bb8bf/jvec.rar)https://gitlab.kitware.com/paraview/paraview/-/issues/20535Incorrect visualization of large hex meshes2021-03-24T09:37:05-04:00Stefan JakobssonIncorrect visualization of large hex meshesFor large hex meshes I have had several cases with incorrect visualization. This is exemplified in the screenshot below. The upper left subfigure shows the whole mesh (which should be if cubical shape) where we have some irregularities i...For large hex meshes I have had several cases with incorrect visualization. This is exemplified in the screenshot below. The upper left subfigure shows the whole mesh (which should be if cubical shape) where we have some irregularities in one of the upper corners. The upper right subfigure shows a view created with the threshold filter where I have extracted 12 rods from the mesh. Here we have many spikes which should not be there. In the lower right subfigure I have extracted the rods myself from the same .xmf and .h5 file but outside paraview, written an new .xmf and .h5 file and imported this into paraview. Now all spikes are gone. ![pv3](/uploads/8a56dd432d83adeef87da57c1dfeac72/pv3.PNG)The mesh has around 11 million cells and 20 million points. For smaller meshes I have not had this problem. I suspect that there are some internal overflow errors causing this problem.https://gitlab.kitware.com/paraview/paraview/-/issues/20523TimeValues not updating from OpenFoam reader when using Python interface2021-06-15T17:17:32-04:00chart3388TimeValues not updating from OpenFoam reader when using Python interfaceMight be related to #20418
TimestepValues are not being updated when using the OpenFOAM Reader via Python Shell. I performed these actions via the Pipeline Browser / Properties panel and always got the correct values back. When I wro...Might be related to #20418
TimestepValues are not being updated when using the OpenFOAM Reader via Python Shell. I performed these actions via the Pipeline Browser / Properties panel and always got the correct values back. When I wrote a test case, and then just used the trace mechanism you can see the values are not what are expected. Via Pipeline Browser With Skip Zero Time unchecked I get back
> runfoam.TimestepValues
> [0.0, 1.0, 2.0, 3.0, 4.0, 5.0]
![image](/uploads/d5604913cd42d828aa1f7bcb89d53d53/image.png)
With Skip Zero Time checked I get back
> runfoam.TimestepValues
> [1.0, 2.0, 3.0, 4.0, 5.0]
![image](/uploads/d22e0db892994667b8e0bbe6806ff1c7/image.png)
When I do this via python
```python
# trace generated using paraview version 5.9.0
#### import the simple module from the paraview
from paraview.simple import *
#### disable automatic camera reset on 'Show'
paraview.simple._DisableFirstRenderCameraReset()
# create a new 'OpenFOAMReader'
runfoam = OpenFOAMReader(registrationName='run.foam', FileName='/opt/dev/temp/reconstruct/run.foam')
# get animation scene
animationScene1 = GetAnimationScene()
# update animation scene based on data timesteps
animationScene1.UpdateAnimationUsingDataTimeSteps()
# Properties modified on runfoam
runfoam.SkipZeroTime = 0
# get active view
renderView1 = GetActiveViewOrCreate('RenderView')
# show data in view
runfoamDisplay = Show(runfoam, renderView1, 'UnstructuredGridRepresentation')
# trace defaults for the display properties.
runfoamDisplay.Representation = 'Surface'
# reset view to fit data
renderView1.ResetCamera(False)
# show color bar/color legend
runfoamDisplay.SetScalarBarVisibility(renderView1, True)
# update the view to ensure updated data information
renderView1.Update()
# get color transfer function/color map for 'p'
pLUT = GetColorTransferFunction('p')
# get opacity transfer function/opacity map for 'p'
pPWF = GetOpacityTransferFunction('p')
# get TimestepValues
runfoam.TimestepValues
# Properties modified on runfoam
runfoam.SkipZeroTime = 1
# update the view to ensure updated data information
renderView1.Update()
# get TimestepValues
runfoam.TimestepValues
```
TimestepValues comes back the same
> runfoam.TimestepValues
> [1.0, 2.0, 3.0, 4.0, 5.0]
The only way to get the TimestepValues correct is to utilize the pipeline browser and properties panel and force something to expose the apply button to trigger the operation again.https://gitlab.kitware.com/paraview/paraview/-/issues/20497Wrong fontsize with HiDPI2021-10-07T03:59:46-04:00Guanyang XueWrong fontsize with HiDPIParaView 5.9.0, macOS 11.2.1 (I believe it happens to all versions)
This is the screenshot of ParaView GUI
![Screen_Shot_2021-02-22_at_3.12.40_PM](/uploads/0f34e6a2a5543eaa95d77a6b725dcc47/Screen_Shot_2021-02-22_at_3.12.40_PM.png)
This ...ParaView 5.9.0, macOS 11.2.1 (I believe it happens to all versions)
This is the screenshot of ParaView GUI
![Screen_Shot_2021-02-22_at_3.12.40_PM](/uploads/0f34e6a2a5543eaa95d77a6b725dcc47/Screen_Shot_2021-02-22_at_3.12.40_PM.png)
This is the screenshot exported by ParaView
![1234](/uploads/16eae581f135b5af2de51a16cbd941a7/1234.png)
Currently I'm using a 1920x1080 monitor, with 1680x945 HiDPI(87.5%). The output resolution is absolutely wrong
![Screen_Shot_2021-02-22_at_3.23.09_PM](/uploads/6b4bdf6b5ccf3dbc0aa8a0497440c178/Screen_Shot_2021-02-22_at_3.23.09_PM.png)
So I guess Paraview cannot correctly process a non-integer HiDPI scale factor.https://gitlab.kitware.com/paraview/paraview/-/issues/20486Paraview-5.9.0 on macOS becomes unresponsive when zooming with data axes2023-05-23T17:24:24-04:00Chris TalleyParaview-5.9.0 on macOS becomes unresponsive when zooming with data axesOS: macOS High Sierra (10.13)
ParaView Version: 5.9.0
Qt Version: 5.15.1
Zooming in to a data set feature with Data Axes Grid enabled gets progressively slower the more you zoom in while using more memory until you get the spinning whee...OS: macOS High Sierra (10.13)
ParaView Version: 5.9.0
Qt Version: 5.15.1
Zooming in to a data set feature with Data Axes Grid enabled gets progressively slower the more you zoom in while using more memory until you get the spinning wheel of death. Paraview becomes unresponsive and you must use Force Quit to kill the app. I do not get this problem on version Paraview-5.4.1 on macOS.
My data set consisted of 187500 quad faces read in from a .vtu file. The domain extents were x(-1.687e-5:0.4),y(0:0.102448) with z=0. Paraview became unresponsive when zooming to a rectangle of size approximately 3e-5 while trying to verify a fine geometric feature of the mesh.https://gitlab.kitware.com/paraview/paraview/-/issues/20480Python filter with TemporalShiftScale not working correctly2021-03-24T09:28:10-04:00Jacob MersonPython filter with TemporalShiftScale not working correctlyI see very strange behavior when doing computations with the results from a temporal shift operator. I'm using the temporal shift operator to try to subtract the value of one frame from the next. To do this I apply the temporal shift sca...I see very strange behavior when doing computations with the results from a temporal shift operator. I'm using the temporal shift operator to try to subtract the value of one frame from the next. To do this I apply the temporal shift scale operator with a scale of 1 and post shift of 1. I then use the following equation in my python filter `inputs[0].PointData["Displacement"]-inputs[1].PointData["Displacement"]`. Where `inputs[0]` should be the original data, and `inputs[1]` should be the shifted data.
When I initially apply the filters I get the expected result. However, if I advance the timestep the data immediately goes to zero. If I reapply the python filter, the numerical values return to the expected result.