ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-08-23T14:50:36-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22277Add regression test for LAMMPS dump reader (in VisItBridge) for multiple time...2023-08-23T14:50:36-04:00Kenneth MorelandAdd regression test for LAMMPS dump reader (in VisItBridge) for multiple time stepsThe LAMMPS dump format supports holding multiple timesteps, and the VisIt reader can read through these timesteps. There was a bug in the VisIt Bridge that prevented all but the first timestep to be read. This problem was fixed in MRs !6...The LAMMPS dump format supports holding multiple timesteps, and the VisIt reader can read through these timesteps. There was a bug in the VisIt Bridge that prevented all but the first timestep to be read. This problem was fixed in MRs !6454 and https://gitlab.kitware.com/paraview/visitbridge/-/merge_requests/101. The regression test currently only tests a file with one timestep. A regression test to test for multiple time steps should be added.
Here is a small, simple LAMMPS dump file with 2 timesteps.
[lammps-multitime.dump](/uploads/9df3b301f5bf33766c7c99a28c94483d/lammps-multitime.dump)https://gitlab.kitware.com/paraview/paraview/-/issues/22275Volume rendering and Ray Tracing are SLOW2023-08-24T16:51:24-04:00W. Alan ScottVolume rendering and Ray Tracing are SLOWVolume rendering and ray tracing are painfully, ridiculously slow. Here is how to replicate.
* ParaView 5.11.1, Linux, builtin server.
* Settings/ Advanced/ RenderView/ Show Annotation. All we need is the framerates.
* Open g1s1-10fps...Volume rendering and ray tracing are painfully, ridiculously slow. Here is how to replicate.
* ParaView 5.11.1, Linux, builtin server.
* Settings/ Advanced/ RenderView/ Show Annotation. All we need is the framerates.
* Open g1s1-10fps.e.16.[0-15] Apply. Color by ids. Note dataset is only 20,000 cells and 28,000 points. Not sure if that is relevant.
* > Frame rate on my workstation is about 560 fps. Way nice.
* Volume Render.
* > Frame rate on my workstation is about 16 fps. Usable, but ouch.
* Turn off Volume Rendering, turning on Surface. Turn on Ray Tracing.
* > Frame rate on my workstation is about 22 fps. Usable, but ouch - especially as we are only ray tracing the outside surface.
* Change Surface to Volume Rendering.
* > Frame rate on my workstation is about 3-4 fps. Not really usable.
For real datasets with many, many more cells this would be basically unusable. I believe we would multiply time spent by the area (which isn't impacted by cell count) and depth (which would be impacted by cell count).
The other issue is that these renders happen every time someone changes something in state, such as changes visibility of filters.https://gitlab.kitware.com/paraview/paraview/-/issues/22267vtkPVPostFilterExecutive (0x1e3ecaa0): The update extent specified in the inf...2023-08-22T06:46:29-04:00baloevtkPVPostFilterExecutive (0x1e3ecaa0): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter (0x1f196a90)When creating a programmable filter from two inputs with different extents I get the following, very annoying error message.
```
(5977.475s) [paraview ]vtkStreamingDemandDrive:878 ERR| vtkPVPostFilterExecutive (0x1b7cbb80): Th...When creating a programmable filter from two inputs with different extents I get the following, very annoying error message.
```
(5977.475s) [paraview ]vtkStreamingDemandDrive:878 ERR| vtkPVPostFilterExecutive (0x1b7cbb80): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter(0x7f6488011cf0) is 0 2304 0 127 0 202, which is outside the whole extent 0 0 0 127 0 202.
```
Within the programmable filter I do take care of the fact that the discretizations of the two inputs don't match and am well aware of the fact that the discretization of the output corresponds to that of the first input.
Here is a very basic example:
```python
# trace generated using paraview version 5.11.1
#import paraview
#paraview.compatibility.major = 5
#paraview.compatibility.minor = 11
from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
renderView1 = GetActiveViewOrCreate('RenderView')
wavelet1 = Wavelet(registrationName='Wavelet1')
wavelet1.WholeExtent = [-10, 10, -10, 10, -10, 10]
wavelet1Display = Show(wavelet1, renderView1, 'UniformGridRepresentation')
wavelet2 = Wavelet(registrationName='Wavelet2')
wavelet2.WholeExtent = [-10, 10, -10, 10, 0, 0]
wavelet2Display = Show(wavelet2, renderView1, 'UniformGridRepresentation')
programmableFilter1 = ProgrammableFilter(registrationName='ProgrammableFilter1', Input=[wavelet1, wavelet2])
programmableFilter1Display = Show(programmableFilter1, renderView1, 'UniformGridRepresentation')
renderView1.Update()
```https://gitlab.kitware.com/paraview/paraview/-/issues/22262Multi block volumes with gaps do not render correctly2023-10-19T17:54:31-04:00Jaswant Panchumarti (Kitware)Multi block volumes with gaps do not render correctlyWhen a multiblock image data is rendered with Volume representation, there is a visible glitch that appears to flip the ordering of the volumes every frame. To reproduce:
1. Create Wavelet source.
2. Apply.
3. Create another Wavelet sou...When a multiblock image data is rendered with Volume representation, there is a visible glitch that appears to flip the ordering of the volumes every frame. To reproduce:
1. Create Wavelet source.
2. Apply.
3. Create another Wavelet source.
4. For the second wavelet, adjust the extent values for the x-axis. Choose values such that the wavelet does not overlap or touch the first wavelet. Ex: 40, 60
![image](/uploads/1e81f184b3602d032f6743557950e635/image.png)
5. Apply
6. Create a Group DataSets filter.
7. Select Wavelet1 and Wavelet2 using Ctrl + click and create a new GroupDatasets filter.
8. Apply
9. Change Representation to Volume and Color by RTData.
10. Move mouse in the render view.
11. See flicker.
Here's how the bug looks:
![ezgif.com-video-to-gif](/uploads/438494c0f9e6c8939627dfa4da2824f2/ezgif.com-video-to-gif.gif)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22261Filter/Source Snap to Mesh Keyboard Shortcut Not Working in LICs Visualization2023-08-16T08:16:46-04:00Elio XhemalajFilter/Source Snap to Mesh Keyboard Shortcut Not Working in LICs VisualizationWhen creating a new filter or source that has snap / snap to mesh capabilities using keyboard shortcuts ('1'/Ctrl+1','2'/Ctrl+2', or 'P'), pressing the keyboard shortcut does not work when representation is set to Surface LIC to define P...When creating a new filter or source that has snap / snap to mesh capabilities using keyboard shortcuts ('1'/Ctrl+1','2'/Ctrl+2', or 'P'), pressing the keyboard shortcut does not work when representation is set to Surface LIC to define Point1/Point2.
- Issue seen with creating line sources, clip, and slice
Reverting the source to Surface, Surface with Edges, or any other representation works as intended. Surface LICs is the only representation that generates the issue.
Tested on ParaView 5.11.1 on Windows 10.https://gitlab.kitware.com/paraview/paraview/-/issues/22258Streamlines not all rendering on MacOS-arm architecture2023-08-16T08:18:00-04:00Julien FaustyStreamlines not all rendering on MacOS-arm architectureUsing the script and data in this archive: [missing_streamlines_macos_arm.tar.gz](/uploads/f48555666f40576d48199c3e00db9150/missing_streamlines_macos_arm.tar.gz), some streamlines that render on linux and MacOS-x86 don't appear when rend...Using the script and data in this archive: [missing_streamlines_macos_arm.tar.gz](/uploads/f48555666f40576d48199c3e00db9150/missing_streamlines_macos_arm.tar.gz), some streamlines that render on linux and MacOS-x86 don't appear when rendering on MacOS-arm.
Reference image:
![image](/uploads/59c503376229ce5e803b813af745452f/image.png)
MacOS-arm image:
![image](/uploads/5c534fce5f5be188a1b57d2debc77ef3/image.png)
## Steps to reproduce
* `cd missing_streamlines_macos_arm/script`
* `pvbatch missing_streamlines_macos_arm.py`
* look at the images generated in `missing_streamlines_macos_arm/output`https://gitlab.kitware.com/paraview/paraview/-/issues/22255Custom axes titles are not working consistently2023-08-16T08:23:14-04:00Utkarsh AyachitCustom axes titles are not working consistentlyversion: 5.11.0
os: windows 11
Steps:
* Start ParaView in builtin mode. Load **NonOrthogonalSource** plugin.
* Create "Sheared Wavelet" source from Sources menu
* Check **Enable Axis Titles** on the `Properties` panel.
* Hit **Apply*: w...version: 5.11.0
os: windows 11
Steps:
* Start ParaView in builtin mode. Load **NonOrthogonalSource** plugin.
* Create "Sheared Wavelet" source from Sources menu
* Check **Enable Axis Titles** on the `Properties` panel.
* Hit **Apply*: what was expected that is that the X/Y/Z labels on the orientation widget would reflect the chosen axes labels. They dont.
* Turn no **Axes Grid**: correctly shows axes labels. Turn off to avoid overlap with next step.
* Turn on **Data Axes Grid**: incorrectly shows axes labels.https://gitlab.kitware.com/paraview/paraview/-/issues/22253Sample over Line artifacts for P3 tets2023-08-03T15:25:50-04:00Jed BrownSample over Line artifacts for P3 tets`Sample Uniformly` yields no data (#22252 ).
## `Sample at Cell Boundaries`
![image](/uploads/c896531d73d9e78cdfb701467754524d/image.png)
## `Sample at Segment Centers`
![image](/uploads/f4f110d1709e250954ab50f06b879751/image.png)
...`Sample Uniformly` yields no data (#22252 ).
## `Sample at Cell Boundaries`
![image](/uploads/c896531d73d9e78cdfb701467754524d/image.png)
## `Sample at Segment Centers`
![image](/uploads/f4f110d1709e250954ab50f06b879751/image.png)
## With tetrahedralize filter (suggested by @dcthomp )
![image](/uploads/bed31cdaccd63ed05ecc26b85c0f0327/image.png)
https://drive.google.com/file/d/1XLpKZ_YGDQynpOqBPcfipF4NVhDxL8JY/view?usp=drive_link
Cc: @c.wetterer-nelsonhttps://gitlab.kitware.com/paraview/paraview/-/issues/22252Plot over line with Sample Uniformly yields no data for high order elements2023-08-03T15:25:50-04:00Jed BrownPlot over line with Sample Uniformly yields no data for high order elementsThis uses Q3 quad elements. The `Sample at Cell Boundaries` and `Sample at Segment Centers` behaves correctly (but loses high order information).
![image](/uploads/f8964a6a0758ed019543c7e015cd3e5b/image.png)
https://drive.google.com/fi...This uses Q3 quad elements. The `Sample at Cell Boundaries` and `Sample at Segment Centers` behaves correctly (but loses high order information).
![image](/uploads/f8964a6a0758ed019543c7e015cd3e5b/image.png)
https://drive.google.com/file/d/1r5EEL4Yke4eyR-g1-QcTF_ump_mQywT1/view?usp=drive_linkhttps://gitlab.kitware.com/paraview/paraview/-/issues/22249Move all relevant information from the wiki to the documentation and bring it...2023-08-23T13:12:04-04:00Mathieu Westphal (Kitware)Move all relevant information from the wiki to the documentation and bring it downTime and time again, the wiki keeps popping up on discourse, misguidded user keep using it as a reliable source of information, which it is not.
However, it does contains interesting sources of information that we may not want to loose.
...Time and time again, the wiki keeps popping up on discourse, misguidded user keep using it as a reliable source of information, which it is not.
However, it does contains interesting sources of information that we may not want to loose.
Let migrate all relevant information from the Wiki to the paraview docs and bring it down for good!
First, we will need to list all relevant pages we may want to extract information from, then we need to do it.
Once all is done, just ask sys admins to hide the wiki from the public.
Here is a list of relevant pages:
- [ ] https://www.paraview.org/Wiki/ParaView_Release_Notes: All release notes should be added to a dedicated blog post
- [ ] https://www.paraview.org/Wiki/ParaView_Nightly_Binaries: Should be added somewhere in docs.paraview.org
- [ ] https://www.paraview.org/Wiki/ParaView_And_Mesa_3D: Should be updated and reposted on discourse as a tips and tricks
- [ ] https://www.paraview.org/Wiki/Configuring_Server_Environment_Using_*.pvx_XML_Files: Should be ported to docs.paraview.org
- [ ] https://www.paraview.org/Wiki/Statistical_analysis: Should be ported to docs.paraview.org
- [ ] https://www.paraview.org/Wiki/Writing_Custom_Applications: Should be ported to markdown doc
- [ ] https://www.paraview.org/Wiki/Camera_and_Property_Linking: Should be ported to docs.paraview.org
- [ ] https://www.paraview.org/Wiki/Related_Publications: Should be added to https://www.paraview.org/resources/
- [ ] https://www.paraview.org/Wiki/Testing_design: Relevant information should be ported to md doc
- [ ] https://www.paraview.org/Wiki/Restarted_Simulation_Readers: Should be ported to docs.paraview.org, see below comment to improve the doc.
- [ ] https://www.paraview.org/Wiki/Python_recipes: Put some in discourse tips and tricks
To generate this list, I started from https://www.paraview.org/Wiki/ParaView and followed the site tree map and ensure every link goes purple.
All page not listed here have equivalent in docs.paraview.org, md doc or are not relevant at all.
The effort needed is small and the community will gain a lot to not have misinformation about ParaView lying around.
@cory.quammen @ben.boeckel @wascott
Related to:
https://gitlab.kitware.com/paraview/paraview/-/issues/19078
https://gitlab.kitware.com/paraview/paraview/-/issues/19080
https://gitlab.kitware.com/paraview/paraview/-/issues/18788
https://gitlab.kitware.com/paraview/paraview/-/issues/20725
https://gitlab.kitware.com/paraview/paraview/-/issues/18709
https://gitlab.kitware.com/paraview/paraview/-/issues/17936
https://gitlab.kitware.com/paraview/paraview/-/issues/17543https://gitlab.kitware.com/paraview/paraview/-/issues/22248SPDX: VTK module spdx file points to a wrong PackageDownloadLocation2023-08-01T04:39:51-04:00Mathieu Westphal (Kitware)SPDX: VTK module spdx file points to a wrong PackageDownloadLocationWhen generating SPDX file for ParaView, VTK modules SPDX points to a wrong location:
```
SPDXVersion: SPDX-2.2
DataLicense: CC0-1.0
SPDXID: SPDXRef-DOCUMENT
DocumentName: vtkFiltersFlowPaths
DocumentNamespace: https://paraview.org/spdx/...When generating SPDX file for ParaView, VTK modules SPDX points to a wrong location:
```
SPDXVersion: SPDX-2.2
DataLicense: CC0-1.0
SPDXID: SPDXRef-DOCUMENT
DocumentName: vtkFiltersFlowPaths
DocumentNamespace: https://paraview.org/spdx/vtkFiltersFlowPaths
Creator: Tool: CMake
Created: 2023-07-31T07:53:49Z
##### Package: vtkFiltersFlowPaths
PackageName: vtkFiltersFlowPaths
SPDXID: SPDXRef-Package-vtkFiltersFlowPaths
PackageDownloadLocation: https://gitlab.kitware.com/vtk/vtk/-/tree/master/VTK/Filters/FlowPaths
FilesAnalyzed: True
PackageLicenseConcluded: BSD-3-Clause
PackageLicenseDeclared: BSD-3-Clause
PackageCopyrightText: <text>
Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
Copyright (c) 1997-2009 John Biddiscombe
</text>
Relationship: SPDXRef-DOCUMENT DESCRIBES SPDXRef-Package-vtkFiltersFlowPaths
```
`PackageDownloadLocation: https://gitlab.kitware.com/vtk/vtk/-/tree/master/VTK/Filters/FlowPaths` is just wrong, it should be: `https://gitlab.kitware.com/vtk/vtk/-/tree/master/Filters/FlowPaths`
There is no mechanism to control that yet, it should be designed and added.https://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
```