ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-08-01T04:39:51-04:00https://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/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/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/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/22244Offsets for bounding ruler2023-07-28T15:33:14-04:00Phil SmithOffsets for bounding rulerPlease provide a way to provide an offset for the Bounding Ruler filter. If the bounds are close they can overlap and be un-readable. Please see discourse issue [12579](https://discourse.paraview.org/t/offsets-for-bounding-ruler/12579) f...Please provide a way to provide an offset for the Bounding Ruler filter. If the bounds are close they can overlap and be un-readable. Please see discourse issue [12579](https://discourse.paraview.org/t/offsets-for-bounding-ruler/12579) for more information5.13 (Summer 2024)https://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.https://gitlab.kitware.com/paraview/paraview/-/issues/20839volume rendering by vector component/magnitude not working on rectilinear grid2023-07-26T05:24:29-04:00Greg Abramvolume rendering by vector component/magnitude not working on rectilinear gridAttached is a little file that creates a trivial rectilinear grid. Import the result, pass it through the calculator with a result name of 'vector' and an equation containing simply 'coords'. Using the GUI, select volume rendering by ...Attached is a little file that creates a trivial rectilinear grid. Import the result, pass it through the calculator with a result name of 'vector' and an equation containing simply 'coords'. Using the GUI, select volume rendering by a component or by Magnitude and you get errors and no image. Pass the result through the AppendDatasets filter to convert it to an unstructured grid, and you can volume render by either individual component or by Magnitude.[vtr.py](/uploads/96724451404790239d7d54ced5750bbd/vtr.py)
By the way, this is v. 5.9.1 and on a Mac running Big Sur.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/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/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/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/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/22231Programmable Annotation fails for field data2023-07-25T04:18:19-04:00W. Alan ScottProgrammable Annotation fails for field dataThe Programmable Annotation filter fails with field data. Here is what I am looking for.
* We need to be able to annotate different datasets and types of field data. Please use can.ex2 and mb.vtm (dataset from Mathieu - a vtm file of c...The Programmable Annotation filter fails with field data. Here is what I am looking for.
* We need to be able to annotate different datasets and types of field data. Please use can.ex2 and mb.vtm (dataset from Mathieu - a vtm file of can.exo).
* Please add a section to ParaView Reference Manual, section 5.4, showing how to annotate the following. We will use this section for testing.
* A point from point data. For instance, point 100.
* A cell from cell data. For instance, cell 100.
* Field data. For instance title, or QA Records, or NSTEPS.
* Add an example of writing two lines of field data. (Can it be done with one Programmable Annotation, or does it take two? Two is acceptable.)
* There is a known issue accessing field data, documented for the Programmable Filter in #21104. This will need to be fixed.5.13 (Summer 2024)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/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/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/22224File series reader should get time from filename2023-07-24T05:13:43-04:00Kenneth MorelandFile series reader should get time from filenameSeveral file formats that do not directly support time allow a series of similarly named files to be treated as a time progression, which is internally implemented with a `FileSeriesReader` meta reader object. The `FileSeriesReader` naiv...Several file formats that do not directly support time allow a series of similarly named files to be treated as a time progression, which is internally implemented with a `FileSeriesReader` meta reader object. The `FileSeriesReader` naively ignores the name of any file in the list and assigns integer time indices starting at 0.
However, it is common practice to encode the simulation time in the file name. When this happens, ParaView ignores the simulation time, and it can be very challenging to get it back.
The `FileSeriesReader` should check its list of files and see if it follows a pattern that has a common name with a varying number, extract that number from each filename, and use that number for the time value.
It should be possible to turn this feature off (advanced property, default to on).5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22199Spline can not be manipulated with mouse2023-07-19T16:39:20-04:00Phil SmithSpline can not be manipulated with mouseTested with MacOS x86 v5.11.1 Master and Windows v5.11.1 Master. Depending on the zoom and position of your object, you may not even see the spline let alone be able to manipulate it. If the object is zoomed out enough, the spline can b...Tested with MacOS x86 v5.11.1 Master and Windows v5.11.1 Master. Depending on the zoom and position of your object, you may not even see the spline let alone be able to manipulate it. If the object is zoomed out enough, the spline can be seen, but it can not be manipulated with the mouse or the keyboard controls as shown in the spline parameters dialog box.
To reproduce:
- Open can; Apply
- View->Time Manager
- Zoom out until the can is about 2-3x the size if on of the icons in the icon bar(This is so you can at least see the spline)
- Within the time manager select Animations->Camera->Follow Path; click "+"
- Double-Click on the name or timeline to edit
- Double-Click on Path (At this point the dialog box is too narrow)
- Click on camera point and if the position and/or the zoom level is ok, you will see the spline, but if the position and/or zoom level is to close you will not even see the spline. This can be a problem.
- Click on any point on the spline and you will not be able to move it, try the quick keys as stated in the dialog box and the spline will not move. This is a problem.
The only way you can get the spline to move is changing the numbers within the spline chart. Even then you will have to re-size the chart to see what you are modifying.
I have assigned this as a show stopper for 5.12, but it can slip to 5.13, because we are so close to the release of 5.125.13 (Summer 2024)