ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-08-01T04:06:10-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22247SPDX: Improve SPDX plugin framework2023-08-01T04:06:10-04:00Mathieu Westphal (Kitware)SPDX: Improve SPDX plugin frameworkWith the addition of SPDX generation in ParaView, we can now create .spdx files for each modules.
However, there is no way to generate a .spdx file for a plugin. Internal module in the plugin are covered but some plugin may not have any...With the addition of SPDX generation in ParaView, we can now create .spdx files for each modules.
However, there is no way to generate a .spdx file for a plugin. Internal module in the plugin are covered but some plugin may not have any, and some plugin may have Qt files with specific license which would not be part of a module.
This should be improved.https://gitlab.kitware.com/paraview/paraview/-/issues/22245SaveScreenshot and ViewSize resolution issue2023-07-31T03:38:45-04:00CapLekSaveScreenshot and ViewSize resolution issueSaveScreenshot method gives me an image with resolution different from requested (launched from Python script, from Paraview UI everything works fine).
Here is a sample code
```
from paraview.simple import *
resolution = [1200, 900]
vi...SaveScreenshot method gives me an image with resolution different from requested (launched from Python script, from Paraview UI everything works fine).
Here is a sample code
```
from paraview.simple import *
resolution = [1200, 900]
view = GetActiveViewOrCreate('RenderView')
view.ViewSize = resolution
SaveScreenshot(filePath, view, ImageResolution=resolution, OverrideColorPalette='WhiteBackground')
```
When running this code block it gives me 1200 x 845 screenshot (while my display has 1920 x 1080). If I comment out the view.ViewSize = resolution line it will give the image of requested resolution, but in that case the color legend for selected field will have wrong scaling spanned all over the image.
Platform: Windows 10
Paraview versions checked: 5.7, 5.9, 5.10.
Link to discussion on [discourse](https://discourse.paraview.org/t/savescreenshot-and-viewsize-resolution-issue/12526).https://gitlab.kitware.com/paraview/paraview/-/issues/22242Catalyst-ParaView implementation crashes with external ptr to GPU memory (CUDA)2023-11-08T21:09:07-05:00Francois MazenCatalyst-ParaView implementation crashes with external ptr to GPU memory (CUDA)When using a conduit node containing values set as an external pointer to a GPU allocated memory, then ParaView-Catalyst implementation crashes.
To reproduce:
- Download and unzip this small project: [catalyst-cuda-master.zip](/uploads...When using a conduit node containing values set as an external pointer to a GPU allocated memory, then ParaView-Catalyst implementation crashes.
To reproduce:
- Download and unzip this small project: [catalyst-cuda-master.zip](/uploads/413e7cfa597cd55db61281b217975d08/catalyst-cuda-master.zip)
- Create a build folder in the source and configure with cmake, then build the software
- Set environment variable `CATALYST_IMPLEMENTATION_NAME=paraview`
- Set environment variable `CATALYST_IMPLEMENTATION_PATHS=/path/to/catalyst/paraview/lib/folder`
- Launch the `catalyst_gpu` executable
- Crash in `vtkDataArrayPrivate::AllValuesMinAndMax` => not OK!
A simple workaround is to use `cudaMallocManaged` instead of `cudaMalloc` on the simulation side, but a generic solution could be implemented on the ParaView side to handle GPU memory pointers and make explicit copy to RAM before processing it. Ascent seems to implement such a logic with their [MagicMemory functions](https://github.com/Alpine-DAV/ascent/blob/f1ecfb3336bc57657a3ced9ab506e43acb202710/src/libs/ascent/runtimes/expressions/ascent_memory_manager.cpp#L451).
Thanks to @jfavre for the initial issue report and @louis.gombert for the minimal test case!https://gitlab.kitware.com/paraview/paraview/-/issues/22241Failure when opening the Spreadsheet View after Temporal Multiplexing filter2023-08-16T09:42:07-04:00Tiffany ChhimFailure when opening the Spreadsheet View after Temporal Multiplexing filter#### Description
ParaView crashes when trying to open a Spreadsheet View for tables with multidimensional arrays (a type of implicit array).
#### Steps to reproduce
* Create Wavelet
* Apply
* Create Temporal Multiplexing filter on Wav...#### Description
ParaView crashes when trying to open a Spreadsheet View for tables with multidimensional arrays (a type of implicit array).
#### Steps to reproduce
* Create Wavelet
* Apply
* Create Temporal Multiplexing filter on Wavelet
* Apply
* Open Spreadsheet View
* **Crash occurs**
#### Backtrace
```cpp
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
0x00007fffcc3249a5 in vtkMultiDimensionalImplicitBackend<float>::mapComponent (this=0x0, tupleIdx=0,
compIdx=0)
at /[...]/ParaView/Plugins/DSP/DataModel/vtkMultiDimensionalImplicitBackend.h:116
116 return this->CurrentArray->GetTypedComponent(tupleIdx, compIdx);
(gdb) backtrace
#0 0x00007fffcc3249a5 in vtkMultiDimensionalImplicitBackend<float>::mapComponent(long long, int) const
(this=0x0, tupleIdx=0, compIdx=0)
at /[...]/ParaView/Plugins/DSP/DataModel/vtkMultiDimensionalImplicitBackend.h:116
#1 0x00007fffcc3227a4 in vtkImplicitArray<vtkMultiDimensionalImplicitBackend<float> >::GetTypedComponentImpl<vtkMultiDimensionalImplicitBackend<float> >(long long, int) const (this=0x555560577c90, idx=0, comp=0)
at /[...]/ParaView/VTK/Common/ImplicitArrays/vtkImplicitArray.h:425
#2 0x00007fffcc31de67 in vtkImplicitArray<vtkMultiDimensionalImplicitBackend<float> >::GetTypedComponent(long long, int) const (this=0x555560577c90, idx=0, comp=0)
at /[...]/ParaView/VTK/Common/ImplicitArrays/vtkImplicitArray.h:206
#3 0x00007fffcc31df45 in vtkGenericDataArray<vtkImplicitArray<vtkMultiDimensionalImplicitBackend<float> >, float>::GetTypedComponent(long long, int) const (this=0x555560577c90, tupleIdx=0, compIdx=0)
at /[...]/ParaView/VTK/Common/Core/vtkGenericDataArray.h:150
#4 0x00007fffcc308e71 in vtkGenericDataArray<vtkImplicitArray<vtkMultiDimensionalImplicitBackend<float> >, float>::GetComponent(long long, int) (this=0x555560577c90, tupleIdx=0, compIdx=0)
at /[...]/ParaView/VTK/Common/Core/vtkGenericDataArray.txx:156
#5 0x00007fffee6187df in vtkDataArrayAccessor<vtkDataArray>::Get(long long, int) const
(compIdx=0, tupleIdx=0, this=<optimized out>)
at /[...]/ParaView/VTK/Common/Core/vtkDataArrayAccessor.h:160
#6 vtk::detail::ConstComponentReference<vtkDataArray, 0>::operator double() const (this=0x7fffffffa600)
at /[...]/ParaView/VTK/Common/Core/vtkDataArrayTupleRange_Generic.h:131
#7 0x00007fffeec77ed9 in std::__copy_move<false, false, std::random_access_iterator_tag>::__copy_m<vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0> >(vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0>) (__first=..., __last=..., __result=...)
at /usr/include/c++/9/bits/stl_algobase.h:342
#8 0x00007fffeec76a9a in std::__copy_move_a<false, vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0> >(vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0>)
#9 0x00007fffeec76536 in std::__copy_move_a2<false, vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0> >(vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0>)
(__first=..., __last=..., __result=...) at /usr/include/c++/9/bits/stl_algobase.h:440
#10 0x00007fffeec762f9 in std::copy<vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0> >(vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ConstComponentIterator<vtkDataArray, 0>, vtk::detail::ComponentIterator<vtkDataArray, 0>)
(__first=..., __last=..., __result=...) at /usr/include/c++/9/bits/stl_algobase.h:474
#11 0x00007fffeec7616d in std::__copy_n<vtk::detail::ConstComponentIterator<vtkDataArray, 0>, int, vtk::detail::ComponentIterator<vtkDataArray, 0> >(vtk::detail::ConstComponentIterator<vtkDataArray, 0>, int, vtk::detail::ComponentIterator<vtkDataArray, 0>, std::random_access_iterator_tag) (__first=..., __n=1, __result=...)
at /usr/include/c++/9/bits/stl_algo.h:782
#12 0x00007fffeec75e9c in std::copy_n<vtk::detail::ConstComponentIterator<vtkDataArray, 0>, int, vtk::detail::ComponentIterator<vtkDataArray, 0> >(vtk::detail::ConstComponentIterator<vtkDataArray, 0>, int, vtk::detail::ComponentIterator<vtkDataArray, 0>) (__first=..., __n=1, __result=...)
at /usr/include/c++/9/bits/stl_algo.h:812
#13 0x00007fffeec7572f in vtk::detail::TupleReference<vtkDataArray, 0>::operator=<vtkDataArray, 0>(vtk::detail::ConstTupleReference<vtkDataArray, 0> const&) (this=0x7fffffffab10, other=...)
at /[...]/ParaView/VTK/Common/Core/vtkDataArrayTupleRange_Generic.h:1067
#14 0x00007fffeebdfdaf in (anonymous namespace)::SetTuplesRangeWorker::operator()<vtkDataArray, vtkDataArray>(vtkDataArray*, vtkDataArray*) const (this=0x7fffffffac30, src=0x555560577c90, dst=0x5555558370a0)
at /[...]/ParaView/VTK/Common/Core/vtkDataArray.cxx:398
#15 0x00007fffeebd6f18 in vtkDataArray::InsertTuples(long long, long long, long long, vtkAbstractArray*)
(this=0x5555558370a0, dstStart=0, n=1, srcStart=0, src=0x555560577c90)
at /[...]/ParaView/VTK/Common/Core/vtkDataArray.cxx:752
#16 0x00007fffeecca35f in vtkGenericDataArray<vtkAOSDataArrayTemplate<float>, float>::InsertTuples(long long, long long, long long, vtkAbstractArray*)
(this=0x5555558370a0, dstStart=0, n=1, srcStart=0, source=0x555560577c90)
at /[...]/ParaView/VTK/Common/Core/vtkGenericDataArray.h:296
#17 0x00007fffeecc7872 in vtkAOSDataArrayTemplate<float>::InsertTuples(long long, long long, long long, vtkAbstractArray*) (this=0x5555558370a0, dstStart=0, n=1, srcStart=0, source=0x555560577c90)
at /[...]/ParaView/VTK/Common/Core/vtkAOSDataArrayTemplate.txx:316
#18 0x00007fffeff2a37f in vtkDataSetAttributes::CopyTuples(vtkAbstractArray*, vtkAbstractArray*, long long, long long, long long) (this=
0x5555585ca1e0, fromData=0x555560577c90, toData=0x5555558370a0, dstStart=0, n=1, srcStart=0)
at /[...]/ParaView/VTK/Common/DataModel/vtkDataSetAttributes.cxx:1185
#19 0x00007fffeff456ac in vtkDataSetAttributesFieldList::CopyData(int, vtkDataSetAttributes*, long long, long long, vtkDataSetAttributes*, long long) const
(this=0x7fffffffafe0, inputIndex=0, input=0x555558ed1e40, inputStart=0, numValues=1, output=0x5555585ca1e0, outStart=0)
at /[...]/ParaView/VTK/Common/DataModel/vtkDataSetAttributesFieldList.cxx:675
#20 0x00007fffe82f285c in vtkPVMergeTables::MergeTables(vtkTable*, std::vector<vtkTable*, std::allocator<vtkTable*> > const&) (output=0x555561718c30, tables=std::vector of length 1, capacity 1 = {...})
at /[...]/ParaView/VTKExtensions/Misc/vtkPVMergeTables.cxx:77
#21 0x00007fffe82f2934 in vtkPVMergeTables::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (this=0x555558256fa0, inputVector=0x555560626fe0, outputVector=0x555557980540)
at /[...]/ParaView/VTKExtensions/Misc/vtkPVMergeTables.cxx:90
#22 0x00007fffebac5a63 in (anonymous namespace)::SpreadSheetViewMergeTables::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) (this=0x555558256fa0, req=
0x5555585c2140, inputVector=0x555560626fe0, outputVector=0x555557980540)
at /[...]/ParaView/Remoting/Views/vtkSpreadSheetView.cxx:170
[...]
```https://gitlab.kitware.com/paraview/paraview/-/issues/22240Set VTK_USE_FUTURE_BOOL and VTK_USE_FUTURE_CONST to ON somewhere on CI2023-07-29T10:28:01-04:00Sean McBrideSet VTK_USE_FUTURE_BOOL and VTK_USE_FUTURE_CONST to ON somewhere on CIRecently, VTK gained two new build options:
- VTK_USE_FUTURE_BOOL
- VTK_USE_FUTURE_CONST
They both default to OFF. One day, hopefully, they can default to ON. If that's ever going to happen, ParaView will certainly need to be able to...Recently, VTK gained two new build options:
- VTK_USE_FUTURE_BOOL
- VTK_USE_FUTURE_CONST
They both default to OFF. One day, hopefully, they can default to ON. If that's ever going to happen, ParaView will certainly need to be able to build against such a VTK. And so: it would be great if ParaView's CI could set them to ON for at least one buildbot.https://gitlab.kitware.com/paraview/paraview/-/issues/22239pvbatch not exiting properly with MPI. Invoking MPI_ABORT or only exiting hea...2023-07-31T03:41:02-04:00pvMasterSqrt4761pvbatch not exiting properly with MPI. Invoking MPI_ABORT or only exiting head process and hanging.Script:
```
import os, sys, time
sys.dont_write_bytecode = True
import paraview
from paraview.simple import *
COMMENTED paraview.servermanager.Finalize()
sys.exit()
```
cmd line: `mpiexec -np 8 pvbatch -u script.py`
I am trying to get...Script:
```
import os, sys, time
sys.dont_write_bytecode = True
import paraview
from paraview.simple import *
COMMENTED paraview.servermanager.Finalize()
sys.exit()
```
cmd line: `mpiexec -np 8 pvbatch -u script.py`
I am trying to get pvbatch to exit a script cleanly without throwing errors. This is needed where a part of the code is reached where the script does not need to carry on due to some criteria being met. This is expected behaviour and thus should not throw errors on exit. However whichever way I try to exit pvbatch either by using sys.exit() or os.kill() or os.system('kill...'), pvbatch always throws mpiexec errors because 1 or more processes did not exit cleanly.
The screenshot below is taken when using a simple sys.exit() without using servermanager.Finalize(). pvbatch was run on 8 processes.
![Screenshot_2023-07-27_111906](/uploads/1d9cefd4686d917055fce5ed12bcdcd2/Screenshot_2023-07-27_111906.png)
You can see here that 7 processes exited improperly leading me to believe that only the head process which is reading the script is the only one exiting properly.
This lead me to use the Finalize() function which I believed would properly terminate each MPI process however I now get a segmentation fault but just on 1 process.
![Screenshot_2023-07-27_112539](/uploads/29bb63db0c5b127d9381b720b6a711b0/Screenshot_2023-07-27_112539.png)
Is there a way for me to exit pvbatch cleanly or is this a deeper issue?https://gitlab.kitware.com/paraview/paraview/-/issues/22234TemporalShift bug2023-07-24T09:41:35-04:00Rupert GladstoneTemporalShift bug
User aims to animate difference between time t and time t+1 using TemporalShiftScale and python calculator. Input is time series of vtu files.
The problem is that after the initial creation of the pipeline, which appears to work as in...
User aims to animate difference between time t and time t+1 using TemporalShiftScale and python calculator. Input is time series of vtu files.
The problem is that after the initial creation of the pipeline, which appears to work as intended, the difference field resets to zero whenever the user moves through time. Mathieu Westphal suggests problem may be a bug in TemporalShift.
More complete discussion of the problem can be found [here](https://discourse.paraview.org/t/animate-relative-change/12566/7).
Paraview state with input files to reproduce the problem can be found [here](https://drive.google.com/file/d/1hGmwxWlGkppA_jwks9pzfMjvMmfdJ1io/view?usp=sharing).https://gitlab.kitware.com/paraview/paraview/-/issues/22233VTPD files not working properly2023-07-25T04:17:47-04:00Andrew BauerVTPD files not working properlyThere seems to be something weird with VTPD files for vtkPartitionedDataSets. I’m not sure yet where the disconnect is but from my understanding a vtkPartitionedDataSet should have the same field arrays for non-empty partitions. When I g...There seems to be something weird with VTPD files for vtkPartitionedDataSets. I’m not sure yet where the disconnect is but from my understanding a vtkPartitionedDataSet should have the same field arrays for non-empty partitions. When I generate one of these VTPD files (attached below) using the Examples/Catalyst2/CxxImageDataExample (run with Examples/Catalyst2/SampleScripts/gridwriter.py)
I get the expected data but not in the expected form. The meta file doesn’t list the point or cell data in the dataset and when I read the data back into both PV v5.11 and master I don’t get the option to choose which cell/point arrays to read in since none are listed even though they’re present.
![weird](/uploads/e5b14f53605a76998f6bea5d3eecf164/weird.png)
[data.tgz](/uploads/24d33a63f2d5adeb6feecd71b46f7e50/data.tgz)https://gitlab.kitware.com/paraview/paraview/-/issues/22232EvenlySpacedStreamlines2D crashes with transient data2023-07-25T04:18:02-04:00Jean M. FavreEvenlySpacedStreamlines2D crashes with transient dataThe attached Python script tested with v5.11.1 and ParaView master (commit a95d4c39d0ea5ac93b27306c7b86cd6bafe26d09) crashes when playing the animation.
[pvEvenlySpacestreamlines.py](/uploads/c36ef659abdbe842b42bfa2ad72fe912/pvEvenlySpac...The attached Python script tested with v5.11.1 and ParaView master (commit a95d4c39d0ea5ac93b27306c7b86cd6bafe26d09) crashes when playing the animation.
[pvEvenlySpacestreamlines.py](/uploads/c36ef659abdbe842b42bfa2ad72fe912/pvEvenlySpacestreamlines.py)
```
4 0x7efcfa122aab vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 91
3 0x7efcf093e987 vtkEvenlySpacedStreamlines2D::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2887
2 0x7efcf094024a bool vtkEvenlySpacedStreamlines2D::ForEachCell<bool (vtkEvenlySpacedStreamlines2D::*)(double*, long long, vtkPoints*, vtkDataArray*, int)>(double*, bool (vtkEvenlySpacedStreamlines2D::*)(double*, long long, vtkPoints*, vtkDataArray*, int), vtkPoints*, vtkDataArray*, int) + 458
1 0x7efcf093fb91 bool vtkEvenlySpacedStreamlines2D::IsTooClose<0>(double*, long long, vtkPoints*, vtkDataArray*, int) + 81
0 0x7efcfdc42520 /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7efcfdc42520]
( 5.625s) [paraview ] :0 FATL| Signal: SIGSEGV
```https://gitlab.kitware.com/paraview/paraview/-/issues/22226Bug with Screenshot While Using Tone Mapping on high resolutions2023-07-25T05:49:53-04:00Carlos del ValleBug with Screenshot While Using Tone Mapping on high resolutionsHi, I'm using Paraview 5.11 in Linux and I encountered a bug while doing an image.
When I select Use Tone Mapping (I'm using OSPRAY PAthtracer) the image comes out like this:
<img src='/uploads/cbd8ec48d69addc0e665195e6ccb2dfd/Paper_F...Hi, I'm using Paraview 5.11 in Linux and I encountered a bug while doing an image.
When I select Use Tone Mapping (I'm using OSPRAY PAthtracer) the image comes out like this:
<img src='/uploads/cbd8ec48d69addc0e665195e6ccb2dfd/Paper_Fig.png' width='500'>
The amount of copies seems to depend on the resolution. If I turn off Tone Mapping I get the proper image:
<img src='/uploads/db14b7fd172f2d740dfd0e6a82b9ba46/Paper_Fig.png' width='500'>https://gitlab.kitware.com/paraview/paraview/-/issues/22225Point Line Interpolator not updating with animation time2023-07-25T07:32:44-04:00Jamie MacLeodPoint Line Interpolator not updating with animation timeFor me an issue exists where the Point Line Interpolator does not appropriately update its result with the animation time. I've searched for any way to get the data to update (I need the plots across a time range), without avail, short o...For me an issue exists where the Point Line Interpolator does not appropriately update its result with the animation time. I've searched for any way to get the data to update (I need the plots across a time range), without avail, short of fully reloading the files which should not be necessary. Considering the SPH interpolator does update with time, it feels like inconsistent behaviour. Also unsure if this issue extends to other point interpolators.
To produce the issue, open the folder attached of an OpenFOAM case, with associated paraview state file set up as I would usually have my interpolator. See that the panels on the right for both plot and spreadsheet to not update as time is altered, but do if file is reloaded in the pipeline or via python command.
[LineInterpTest.zip](/uploads/ae8b1ed7318a86578d7a4118a1d0eb01/LineInterpTest.zip)
Test done with 5.11.0.
Thanks!https://gitlab.kitware.com/paraview/paraview/-/issues/22223Rendering Scene with Ray Tracing Number of Samples per Pixel Problem2023-07-25T05:55:27-04:00Carlos del ValleRendering Scene with Ray Tracing Number of Samples per Pixel ProblemHi, I'm trying to render a scene with ray tracing (OSPRAY pathtracer), and I spotted a problem that Paraview has when using the GUI that's a bit annoying to work around.
When exporting the scene or saving a screenshot or an animation, ...Hi, I'm trying to render a scene with ray tracing (OSPRAY pathtracer), and I spotted a problem that Paraview has when using the GUI that's a bit annoying to work around.
When exporting the scene or saving a screenshot or an animation, the scene is rendered with the number of defined samples per pixel. So, if one wants a high-quality image, one has to select a big number of pixel samples. The problem is that it will take a long time to render the preview, then the program will respond and allow you to take the screenshot. When it takes the screenshot, it will render again. This takes a long time, and it's annoying.
Possible solutions:
1. I think the easiest solution will be to take into account the number of Progressive Passes in the renders. So, when someone is saving an image it will use a lot of points, but this won't make the GUI hard to work with or unresponsive.
2. Another solution is to have the raytracing menu available in the render menus. So, one can have a few points for the preview and increment the number of points only for the render.
If there's already a workaround for this, I would love to hear it.
Best regards.https://gitlab.kitware.com/paraview/paraview/-/issues/22222Both point plane interpolator and SPH plane interpolator can't handle group d...2023-07-25T04:24:04-04:00Erik FaulhaberBoth point plane interpolator and SPH plane interpolator can't handle group datasetsHere is a screenshot of two SPH simulation results (dataset of points) on two neighboring quadratic domains.
In the simulation, the SPH interpolation is including particles from the other set of particles as well. To do the same, I group...Here is a screenshot of two SPH simulation results (dataset of points) on two neighboring quadratic domains.
In the simulation, the SPH interpolation is including particles from the other set of particles as well. To do the same, I grouped the two results with the "Group Datasets" filter.
![grafik](/uploads/cc80b69c5b428617f6c8386a665181b9/grafik.png)
When I now apply the "SPH Plane Interpolator", it is only using particles in one of the results (randomly).
When I change some parameters or reload one of the files (i.e. triggering a re-rendering in ParaView), it randomly switches between the two results, always interpolating only one.
![grafik](/uploads/f17804a9a49a3f8ba03e994fbc10f6e8/grafik.png)
![grafik](/uploads/d2e7e6aa3b96e2b9602be3e3f18fba77/grafik.png)
The same happens with the "Point Plane Interpolator".
I am using ParaView 5.11.1.https://gitlab.kitware.com/paraview/paraview/-/issues/22220Add local min/max option in Find Data2023-07-14T18:19:02-04:00Boonthanome NouanesengsyAdd local min/max option in Find DataSometimes, we would like to find the minimum or maximum value of a variable, but only within a certain block. In the Find Data dialog, there is an option to query for the min/max of a value, and there are `Block Selectors` which lets you...Sometimes, we would like to find the minimum or maximum value of a variable, but only within a certain block. In the Find Data dialog, there is an option to query for the min/max of a value, and there are `Block Selectors` which lets you filter the results, showing only the results within certain blocks.
But when using this configuration, Find Data still searches for the global min/max throughout the entire grid. It would be good to add an option to search for the local min/max, which is the min/max when considering only the selected blocks.
In the below screenshot, I would like to find the minimum density in the `LowP` block, but instead the global minimum value is searched for.
![find_data](/uploads/d04239790d1eaf4fe040b9cc11a79103/find_data.png){width=30%}
@patchett2002 @cory.quammen @yohann.bearziCory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22211GenerateGlobalIds filter causes error in exporting/importing Exodus mesh2023-07-25T04:30:08-04:00Hernan VillanuevaGenerateGlobalIds filter causes error in exporting/importing Exodus meshExodus II mesh files expect global IDs to start at 1.
Here is my situation: I have a mesh representing a quarter of a torus-like structure. I copy and rotate the structure using 3 consecutive Transform filters. Then, I group the Transf...Exodus II mesh files expect global IDs to start at 1.
Here is my situation: I have a mesh representing a quarter of a torus-like structure. I copy and rotate the structure using 3 consecutive Transform filters. Then, I group the Transforms together using the GroupDatasets filter. I then use MergeBlocks and CleantoGrid to merge the duplicate points from the rotation. Finally, I apply GenerateGlobalIds to renumber the IDs because at this point each ID is repeated 3 times from rotating the initial structure.
However, GenerateGlobalIds renumbers the IDs from zero. When I export the data as Exodus, I can't read it back in in ParaView. I get an error that says:
```
( 4.735s) [paraview ] vtkIOSSReader.cxx:2544 ERR| Error reading entity block (or set) named 'block_12' from 'test.exo'; skipping. Details:
ERROR: element mapping routines detected non-positive global id 0 for local id 1 on processor 0, filename 'test.exo'.
```
I think Exodus expects IDs to start at 1, not zero.https://gitlab.kitware.com/paraview/paraview/-/issues/22210Sliders behaving strangely on MacOS2023-07-04T09:03:56-04:00Mathieu Westphal (Kitware)Sliders behaving strangely on MacOSSliders behaving strangely on MacOS
Steps:
- Sphere, advanced options
- Interact with sliders using "two fingers interactions"
- Sliders do stanges things, values are still goodSliders behaving strangely on MacOS
Steps:
- Sphere, advanced options
- Interact with sliders using "two fingers interactions"
- Sliders do stanges things, values are still goodhttps://gitlab.kitware.com/paraview/paraview/-/issues/22209ParallelCoordinates clear selection does not remove selection markers2023-07-10T09:08:14-04:00Julien SchuellerParallelCoordinates clear selection does not remove selection markerson the ParallelCoordinates, the "clear selection" button clears the red lines between the points (they go from red to black),
but not the red vertical selection indicator bars stay unchanged, is that normal ? I would expected them to di...on the ParallelCoordinates, the "clear selection" button clears the red lines between the points (they go from red to black),
but not the red vertical selection indicator bars stay unchanged, is that normal ? I would expected them to disappear
note that I can manually remove them using the minus and rectangle selection buttons
![pv1](/uploads/1daa5971a2c6561e38b648f62c81bb07/pv1.png)
![pv2](/uploads/424fb2e738c47de108800e1a76e3e7f3/pv2.png)
cc @nicolas.vuaille @lucas.givordhttps://gitlab.kitware.com/paraview/paraview/-/issues/22206Unable to read .bp file generated with ADIOS2 v2.9.0 on ParaView 5.11.1 and n...2023-07-12T07:14:51-04:00kastatineUnable to read .bp file generated with ADIOS2 v2.9.0 on ParaView 5.11.1 and nightliesWe are using ParaView as part of an ECP-funded project at ORNL on the OLCF systems. In this project, we are using the [GrayScott.jl miniapp](https://github.com/JuliaORNL/GrayScott.jl) to examine an HPC workflow in Julia. After running th...We are using ParaView as part of an ECP-funded project at ORNL on the OLCF systems. In this project, we are using the [GrayScott.jl miniapp](https://github.com/JuliaORNL/GrayScott.jl) to examine an HPC workflow in Julia. After running the miniapp and generating a .bp file with the latest version of ADIOS2 (v2.9.0), we attempted to open the file in ParaView v5.11.1 by setting the filetype as “All Files (*)” and trying both the “ADIOS2VTXReader” and “FidesReader” readers. ParaView immediately crashes. We have attached the error message displayed when ADIOS2VTXReader is used. We have reproduced this error on WSL, Mac, and HPC (Leconte, a node of Summit) systems.
ParaView is able to render .bp files perfectly fine when they are generated using ADIOS2 v2.8.3 (specific version tag cloned from GitHub), so the issue may be that ParaView’s superbuild is not using the latest ADIOS2 v2.9.
@williamfgc
[error.log](/uploads/1b2b7df9b3d1cc8cea9b2d080b0f81cf/error.log)Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/22204Depth rendering issues when rendering lines close to unstructured meshes2023-07-25T04:32:27-04:00Thomas HilkeDepth rendering issues when rendering lines close to unstructured meshesHi,
I noticed an issue with Paraview 5.11.1 (On Windows 11) when rendering lines (more specifically polylines loaded from a .vtk file) close to an unstructured triangle mesh. The line appear alternatively behind or in front of the trian...Hi,
I noticed an issue with Paraview 5.11.1 (On Windows 11) when rendering lines (more specifically polylines loaded from a .vtk file) close to an unstructured triangle mesh. The line appear alternatively behind or in front of the triangular mesh, depending on the view direction and the zoom level.
Here is a gif demonstrating the issue. Focus on the portion of the line colored in blue:
![Line_render_issue_lq](/uploads/bda079d807168d4b1ed13932c866edd4/Line_render_issue_lq.gif)
I could reproduce the issue to some extend with two sources (a cylinder and a line). Here is the Paraview state file:
[Line_render_issue_minimal_reproduction.pvsm](/uploads/70c98b155e1456800decd68615ee3e66/Line_render_issue_minimal_reproduction.pvsm)
And the demonstration:
![Line_render_issue_minimal](/uploads/a9a6cfbc14b7a5a920d894d0cdb705b0/Line_render_issue_minimal.gif)
As in this case I am most interested in the relative positions of these objects and whether or not they intersect and where, this render issue is a bit disturbing.
Thanks in advance for your time,
Thomashttps://gitlab.kitware.com/paraview/paraview/-/issues/22202[XRInterface][HTC Vive] Interactions are not working as expected2023-07-28T07:39:15-04:00Mathieu Westphal (Kitware)[XRInterface][HTC Vive] Interactions are not working as expectedWith the nightly version of ParaView (ParaView-master-5.11.1-1309-gbb4dcf1d66-MPI-Windows-Python3.9-msvc2017-AMD64), XRInterface interactions are not working as expected.
The grip is not working at all (warnings) and all the interaction...With the nightly version of ParaView (ParaView-master-5.11.1-1309-gbb4dcf1d66-MPI-Windows-Python3.9-msvc2017-AMD64), XRInterface interactions are not working as expected.
The grip is not working at all (warnings) and all the interactions are different from valve index. This should be reworked.