ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-02T11:00:31-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22154Missing dlls for cxx tests inside ParaView plugins on Windows2023-06-02T11:00:31-04:00Thomas GallandMissing dlls for cxx tests inside ParaView plugins on WindowsCurrently, the VTK testing framework do not allow to run `cxx` tests written inside ParaView plugins without doing some "hacks".
By default test executables are put in `paraview_build_dir\bin\paraview-X.XX\plugins\MyPlugin` while VTK m...Currently, the VTK testing framework do not allow to run `cxx` tests written inside ParaView plugins without doing some "hacks".
By default test executables are put in `paraview_build_dir\bin\paraview-X.XX\plugins\MyPlugin` while VTK module libraries are in `paraview_build_dir\bin`, so they are not able to find the dlls at runtime.
A workaround is to edit the `PATH` environment variable for these tests specifically, for example:
```
file(TO_NATIVE_PATH "${CMAKE_BINARY_DIR}/${CMAKE_INSTALL_BINDIR}" paraview_libraries_path)
set(test_path "$ENV{PATH};${paraview_libraries_path}")
string(REPLACE ";" "\;" test_path "${test_path}")
foreach(test IN LISTS tests)
string(REPLACE ".cxx" "" test "${test}")
set_tests_properties(MyPlugin::MyModuleCxx-${test} PROPERTIES
ENVIRONMENT "PATH=${test_path}"
)
endforeach()
```
Is there a good way to add `cxx` tests from plugins, that we can add to the testing framework ?
FYI @mwestphal @ben.boeckel @francois.mazenBen BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22153Axis grid is SLOW when zoomed in2023-05-25T10:49:06-04:00W. Alan ScottAxis grid is SLOW when zoomed inThe axis grid is slow when zoomed in. It can be bad enough that it appears to hang. Here is how to replicate.
* 5.11.1, Linux, builtin server.
* Open can.exo. Don't touch it. Apply.
* Axis grid.
* On the left side you will see a coor...The axis grid is slow when zoomed in. It can be bad enough that it appears to hang. Here is how to replicate.
* 5.11.1, Linux, builtin server.
* Open can.exo. Don't touch it. Apply.
* Axis grid.
* On the left side you will see a coordinate of 4 on the y axis. Place your mouse on the edge of the can just to the right of the 4.
* <CTRL>, and now Right mouse button, and pull down. Do down (zoom in) until the axis grid goes away, and then reverse until the axis grid reappears. Let go of the mouse.
ParaView will tend to freeze as a bazillion axis grid labels are calculated. This is very, very bad behavior. We need to fix it.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22151OpenFOAM reader in 5.11.1 selects geometry regions incorrectly if "Read zones...2023-05-23T06:50:20-04:00Åsmund ErvikOpenFOAM reader in 5.11.1 selects geometry regions incorrectly if "Read zones" is enabledI'm encountering a bug in Paraview with the OpenFOAM reader, where ticking the "Read zones" option causes an incorrect selection of mesh regions.
In the first screenshot below, I have selected a single patch (boundary region) of a geome...I'm encountering a bug in Paraview with the OpenFOAM reader, where ticking the "Read zones" option causes an incorrect selection of mesh regions.
In the first screenshot below, I have selected a single patch (boundary region) of a geometry, without "Read zones", and the patch is displayed correctly.
![paraview-read-zones-correct](/uploads/d32cec987ed668cd5883799e1c11554a/paraview-read-zones-correct.png)
If I enable the "Read zones" option **without changing anything else**, the displayed selection of mesh regions changes significantly and gives me something that is obviously wrong, since it includes parts of the interior mesh.
![paraview-read-zones-incorrect](/uploads/7e8f4d16362cfd15aee706442733ff72/paraview-read-zones-incorrect.png)
I'm getting this error on Paraview 5.11.1 on Arch Linux. I don't have an older Paraview install that I can test with, but I think maybe this used to work fine in the past.
The screenshots taken here are from the OpenFOAM v2112 tutorial case "incompressible/pisoFoam/RAS/cavity" such that you have an example for reproducing. I have uploaded also the case folder if that's easier to use: [cavity-read-zones-bug.zip](/uploads/f42b49803bf1a9b23e58b67b30e0005f/cavity-read-zones-bug.zip)https://gitlab.kitware.com/paraview/paraview/-/issues/22150Paraview 5.11.1 cannot read file series with floating point numbers in filename2023-05-23T04:03:01-04:00Hagen LippokParaview 5.11.1 cannot read file series with floating point numbers in filenameI have a series of vtk files with filenames of the pattern: [fixed prefix part]_[floating point number].vtk. The floating point number consists of one or two digits, followed by a decimal separator, followed by a couple of digits represe...I have a series of vtk files with filenames of the pattern: [fixed prefix part]_[floating point number].vtk. The floating point number consists of one or two digits, followed by a decimal separator, followed by a couple of digits representing the decimal places of the number.
In windows explorer I select many of these files. The filenames may be as follows: p_0.000.vtk, p_0.500.vtk, p_1.000.vtk, p_1.500.vtk and so on. Note, that the leading digits vary.
Using Paraview 5.9.0, I can drag and drop the whole selection into the pipeline and they get interpreted as one continuous series (setting the time to integer values which is a wholly different topic to grumble about).
Using Paraview 5.11.1, I can drag and drop the whole selection into the pipeline and they get inserted as multiple series, one series for each of the distinct leading digits.
This behavior can be reproduced with the [File]->[Open...] dialog **in both versions**. So the clustering using the file open dialog is always over distinct leading digits.
I want to argue that the drag and drop behavior of version 5.9.0 is the most convenient, since I obviously have one continuous series of data. Although the number may not be interpreted as a meaningful value in ParaView itself (and although I might want to grumble about it, I probably understand the reasoning for doing so) it adds useful information to the file itself, should I want to open a specific file, because I know what that number signifies.
I thought, that this might be due to the eternal joy that is machine localisation. So I changed the filenames and set the decimal separator to the one dictated by my machines localisation (switched the point for a comma, damn the German number format). The result was the same, so at least there is no assuming of number formats going on.
Could a more consistent and useful approach for file series loading be implemented going forward? I.e.: Drag and drop constitutes always one series (or multiple series for multiple prefixes) and the open dialog at least lets the user toggle between complete series and break series into distinct-leading-digits-groups.https://gitlab.kitware.com/paraview/paraview/-/issues/22147Filter to rename blocks and create/ modify assemblies2023-05-22T03:35:56-04:00W. Alan ScottFilter to rename blocks and create/ modify assembliesWe need to create a filter that can manipulate blocks
* Be able to rename blocks.
* Create assemblies out of a group of blocks.
* Edit assemblies.
* Delete assemblies of blocks
The goal with this filter is for example to prepare an ex...We need to create a filter that can manipulate blocks
* Be able to rename blocks.
* Create assemblies out of a group of blocks.
* Edit assemblies.
* Delete assemblies of blocks
The goal with this filter is for example to prepare an exodus dataset to be written to another exodus dataset. An example would be to load bake.e, create assemblies out of the outer walls, another assembly out of the corners, another out of the heaters and a final one from the cone.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22145TecplotReader issue in GUI with coordinate variables not as first, second and...2023-05-22T03:38:24-04:00Serge ToxopeusTecplotReader issue in GUI with coordinate variables not as first, second and third variableIn the Paraview GUI (5.11), there is an issue when the coordinate values are not the first, second and third variable. For example, if variable 1 is x, variable 2 is y, variable 3 is var and variable 4 is z, you get the option to load th...In the Paraview GUI (5.11), there is an issue when the coordinate values are not the first, second and third variable. For example, if variable 1 is x, variable 2 is y, variable 3 is var and variable 4 is z, you get the option to load the DataArray "z", not "var". Even if you check the "z" variable, you still do not get "var" as point (or cell) variable. In python or the Python Shell, when you say GetActiveSource().DataArrayStatus = ["var"] and then update the pipeline, you get the desired variables, however. So it is just a GUI issue.
Maybe after reading the variables from the file, first the coordinate variables should be determined and all remaining variables should be presented to the user for inclusion in the DataArrayStatus?
An example ASCII tecplot file is attached: [multizone-cubes.dat](/uploads/da06b54c22409ed056f5b6729274bba8/multizone-cubes.dat)https://gitlab.kitware.com/paraview/paraview/-/issues/22144TecplotReader issue with similar named zones2023-05-22T03:38:43-04:00Serge ToxopeusTecplotReader issue with similar named zonesSee also https://discourse.paraview.org/t/reading-zones-with-identical-names-using-tecplotreader-into-paraview/12118/4
When reading an ASCII Tecplot file into Paraview (5.11) where two (or more) zones have identical names (which is allo...See also https://discourse.paraview.org/t/reading-zones-with-identical-names-using-tecplotreader-into-paraview/12118/4
When reading an ASCII Tecplot file into Paraview (5.11) where two (or more) zones have identical names (which is allowed), it is not possible to extract these zones to separate blocks using ExtractBlocks (which now uses block names, instead of indices like previously). If you use the ExtractBlock filter with one of the zones selected, it will outputs still both zones.
Suggestion: if zones have identical name, append the name with an index such that unique block names will be available?
A very simple example of the problem is attached: one Tecplot file and a python script to read it into Paraview illustrating the problem. It also contains the MergeBlocks and Connectivity filters for your convenience.
[multizone-cubes.dat](/uploads/1501b2c5e820b9bf7bf52cf10e1122f7/multizone-cubes.dat)
[multizone-cubes.py](/uploads/f0f5b1fe4aba61ec18c7dc636175d1dc/multizone-cubes.py)https://gitlab.kitware.com/paraview/paraview/-/issues/22141Replace user defined old color maps with new color maps2023-05-15T20:15:25-04:00W. Alan ScottReplace user defined old color maps with new color mapsWhen a user is importing a user defined color map, and the name matches an already loaded map that is not one of the maps bundled with ParaView, please replace the old map with the new map. Currently, the user needs to delete her old ma...When a user is importing a user defined color map, and the name matches an already loaded map that is not one of the maps bundled with ParaView, please replace the old map with the new map. Currently, the user needs to delete her old map and then add the new one. However, do NOT replace any of the defaults. Here is how to test:
* 5.11.1, Linux, builtin server.
* Load can.exo. Apply. ACCL.
* Color map editor.
* Click on the center point. <CR>. Change the point to yellow. Save Preset. Change the name to Ugly. OK.
* Close the Preset dialog.
* Click on the center point. <CR>. Change the point to green. Save Preset. Change the name to Ugly. OK.
1) The preset isn't correct, it should have green in the center.
2) When you click on the Ugly preset, it is still the yellow Ugly map.
3) There is a warning that says:
Generic Warning: In vtkSMTransferFunctionPresets.cxx, line 261
Giving up. Cannot find a unique name for 'Ugly'. Please provide a good prefix.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22140Particle Tracer fails to produce exploitable data in an in situ environment2023-05-17T16:24:53-04:00Yohann Bearzi (Kitware)Particle Tracer fails to produce exploitable data in an in situ environmentThe filter `Particle Tracer` (implementation is mostly in `vtkParticleTracerBase` in VTK) has a parameter `DisableResetCache` which is supposed to allow to run the filter in situ, i.e. a mode where each call to `UpdateTimeStep(double t)`...The filter `Particle Tracer` (implementation is mostly in `vtkParticleTracerBase` in VTK) has a parameter `DisableResetCache` which is supposed to allow to run the filter in situ, i.e. a mode where each call to `UpdateTimeStep(double t)` outputs a dataset at time `t`. However the filter fails to produce satisfactory outputs in this context.
There are a few reasons:
* Instead of relying on `vtkStreamingDemandDrivenPipeline::UPDATE_TIME_STEP()` to acquire the current time step, the filter gets the current timestep through `vtkDataObject::DATA_TIME_STEP()`, which is not correctly populated in the context I was running the filter (I will share the script below)
* When above point is fixed (correctly setting the timestep), one can get the expected output in situ, but there is a memory leak that originates from a mishandling of the attribute `vtkParticleTracer::FirstIteration`. It gets set to true and triggers a memory leaking path. If the attribute is left untouched, the output is wrong once again.
* The handling of `RequestInformation` and `RequestUpdateExtent` is questionable. They are setting a bunch of internal variables with a complicated algorithm which make it hard to untangle.
The Catalyst script [cata.py](/uploads/59ebea8702e3f9c74418441517871335/cata.py) I am using to test this is run using the `CxxFullExample` in ParaView. It runs a pipeline where one traces a particle on a random vector field. The script should output for each file a growing polyline.
Here is the patch [particle_tracer.diff](/uploads/caff78d253386b45e3ec7e69d0c58ee1/particle_tracer.diff) allowing to get a correct output with a leak. It needs to be used on top of vtk/vtk!10104 and paraview/paraview!6292
The filter should be refactored to make it work correctly in situ without leaking. In addition, it should rely on the key `vtkStreamingDemandDrivenPipeline::INCOMPLETE_TIME_STEPS()` instead of the manual parameter `DisableResetCache`.
There might be issues to discuss regarding backward compatibility. I have little faith we would be able to maintain it upon refactoring.https://gitlab.kitware.com/paraview/paraview/-/issues/22139Raytracing: crash when changing the temporal cache size property2023-05-15T04:56:10-04:00Lucas GivordRaytracing: crash when changing the temporal cache size propertyAfter enabling raytracing in ParaView **master** and decrease the value of the property `Temporal Cache Size`, paraview crashs with `malloc(): unsorted double linked list corrupted`.
<details>
<summary>See the gdb stack trace</summary>
...After enabling raytracing in ParaView **master** and decrease the value of the property `Temporal Cache Size`, paraview crashs with `malloc(): unsorted double linked list corrupted`.
<details>
<summary>See the gdb stack trace</summary>
```batch
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007fa77bcdd859 in __GI_abort () at abort.c:79
#2 0x00007fa77bd4826e in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa77be72298 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3 0x00007fa77bd502fc in malloc_printerr (str=str@entry=0x7fa77be74ad8 "malloc(): unsorted double linked list corrupted") at malloc.c:5347
#4 0x00007fa77bd532ec in _int_malloc (av=av@entry=0x7fa77bea7b80 <main_arena>, bytes=bytes@entry=1160) at malloc.c:3744
#5 0x00007fa77bd55299 in __GI___libc_malloc (bytes=1160) at malloc.c:3066
#6 0x00007fa747060210 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#7 0x00007fa74704ca3f in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#8 0x00007fa744c71f34 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#9 0x00007fa746219c46 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#10 0x00007fa746200a91 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#11 0x00007fa746200909 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#12 0x00007fa745ae6006 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#13 0x00007fa744ff1477 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#14 0x00007fa744c367a6 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#15 0x00007fa744c35e4f in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#16 0x00007fa744c35a6d in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#17 0x00007fa75a53c190 in tbb::detail::r1::task_dispatcher::local_wait_for_all<false, tbb::detail::r1::external_waiter>(tbb::detail::d1::task*, tbb::detail::r1::external_waiter&) (this=0x7fa72d7cbc00, t=0x7fa72daa5c00, waiter=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.h:322
#18 0x00007fa75a525b1e in tbb::detail::r1::task_dispatcher::local_wait_for_all<tbb::detail::r1::external_waiter>(tbb::detail::d1::task*, tbb::detail::r1::external_waiter&) (this=<optimized out>, t=<optimized out>, waiter=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.h:463
#19 tbb::detail::r1::task_dispatcher::execute_and_wait(tbb::detail::d1::task*, tbb::detail::d1::wait_context&, tbb::detail::d1::task_group_context&) (t=0x2, wait_ctx=..., w_ctx=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.cpp:168
#20 0x00007fa744c34cdc in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#21 0x00007fa744cb3d23 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#22 0x00007fa744cc0421 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#23 0x00007fa744cbfaef in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#24 0x00007fa744cbf70d in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#25 0x00007fa75a53c190 in tbb::detail::r1::task_dispatcher::local_wait_for_all<false, tbb::detail::r1::external_waiter>(tbb::detail::d1::task*, tbb::detail::r1::external_waiter&) (this=0x7fa72d7cbc00, t=0x7fa72daa6000, waiter=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.h:322
#26 0x00007fa75a525b1e in tbb::detail::r1::task_dispatcher::local_wait_for_all<tbb::detail::r1::external_waiter>(tbb::detail::d1::task*, tbb::detail::r1::external_waiter&) (this=<optimized out>, t=<optimized out>, waiter=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.h:463
#27 tbb::detail::r1::task_dispatcher::execute_and_wait(tbb::detail::d1::task*, tbb::detail::d1::wait_context&, tbb::detail::d1::task_group_context&) (t=0x2, wait_ctx=..., w_ctx=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.cpp:168
#28 0x00007fa744cc0688 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#29 0x00007fa75a53c190 in tbb::detail::r1::task_dispatcher::local_wait_for_all<false, tbb::detail::r1::external_waiter>(tbb::detail::d1::task*, tbb::detail::r1::external_waiter&) (this=0x7fa72d7cbc00, t=0x7fa72daa7100, waiter=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.h:322
#30 0x00007fa75a528a27 in tbb::detail::r1::task_dispatcher::local_wait_for_all<tbb::detail::r1::external_waiter>(tbb::detail::d1::task*, tbb::detail::r1::external_waiter&) (this=<optimized out>, t=<optimized out>, waiter=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.h:463
#31 tbb::detail::r1::task_dispatcher::execute_and_wait(tbb::detail::d1::task*, tbb::detail::d1::wait_context&, tbb::detail::d1::task_group_context&) (t=<optimized out>, wait_ctx=..., w_ctx=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.cpp:168
#32 tbb::detail::r1::wait(tbb::detail::d1::wait_context&, tbb::detail::d1::task_group_context&) (wait_ctx=..., w_ctx=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/task_dispatcher.cpp:126
#33 0x00007fa744cb828b in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#34 0x00007fa75a528e0c in tbb::detail::r1::isolate_within_arena(tbb::detail::d1::delegate_base&, long)::{lambda()#1}::operator()() const (this=<optimized out>)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/arena.cpp:771
#35 tbb::detail::d0::try_call_proxy<tbb::detail::r1::isolate_within_arena(tbb::detail::d1::delegate_base&, long)::{lambda()#1}>::on_completion<tbb::detail::r1::isolate_within_arena(tbb::detail::d1::delegate_base&, long)::{lambda()#2}>(tbb::detail::r1::isolate_within_arena(tbb::detail::d1::delegate_base&, long)::{lambda()#2}) (this=<optimized out>, on_completion_body=...)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/../../include/oneapi/tbb/detail/_template_helpers.h:230
#36 tbb::detail::r1::isolate_within_arena(tbb::detail::d1::delegate_base&, long) (d=..., isolation=140722034230320)
at /localdisk/ci/runner006/intel-innersource/001/_work/libraries.threading.infrastructure.onetbb-ci/libraries.threading.infrastructure.onetbb-ci/onetbb_source_code/src/tbb/arena.cpp:772
#37 0x00007fa744cb2c61 in () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#38 0x00007fa744c5f7fc in rtcCommitScene () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libembree3.so.3
#39 0x00007fa7476c524e in ospray::World::commit() () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libospray_module_cpu.so
#40 0x00007fa7476a3d0d in ospray::api::ISPCDevice::commit(osp::ManagedObject*) () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libospray_module_cpu.so
#41 0x00007fa7682d09c2 in ospCommit () at /home/jafar/deps/OSPRay/ospray-2.9.0.x86_64.linux/lib/libospray.so.2
#42 0x00007fa76f830876 in RTW::OSPRayBackend::Commit(RTWHandle*) (this=0x55d42cf8eca0, object=0x55d4344efcf0) at /home/jafar/dev/paraview/src/VTK/Rendering/RayTracing/RTWrapper/OSPRay/OSPRayBackend.h:323
#43 0x00007fa76f813970 in vtkOSPRayRendererNode::Render(bool) (this=0x55d43356fc80, prepass=false) at /home/jafar/dev/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayRendererNode.cxx:1296
#44 0x00007fa76b1edc7f in vtkViewNode::Apply(int, bool) (this=0x55d43356fc80, operation=3, prepass=false) at /home/jafar/dev/paraview/src/VTK/Rendering/SceneGraph/vtkViewNode.cxx:236
#45 0x00007fa76f812daf in vtkOSPRayRendererNode::Traverse(int) (this=0x55d43356fc80, operation=3) at /home/jafar/dev/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayRendererNode.cxx:1146
#46 0x00007fa76b1ed768 in vtkViewNode::TraverseAllPasses() (this=0x55d43356fc80) at /home/jafar/dev/paraview/src/VTK/Rendering/SceneGraph/vtkViewNode.cxx:165
#47 0x00007fa76f7fa98e in vtkOSPRayPass::RenderInternal(vtkRenderState const*) (this=0x55d4346b9480, s=0x7ffc66dcf940) at /home/jafar/dev/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayPass.cxx:325
#48 0x00007fa76f7fc807 in vtkOSPRayPassInternals::Render(vtkRenderState const*) (this=0x55d4346b9390, s=0x7ffc66dcf940) at /home/jafar/dev/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayPass.cxx:114
#49 0x00007fa7782c7251 in vtkSequencePass::Render(vtkRenderState const*) (this=0x55d4344e1660, s=0x7ffc66dcf940) at /home/jafar/dev/paraview/src/VTK/Rendering/OpenGL2/vtkSequencePass.cxx:71
#50 0x00007fa7780a43a7 in vtkCameraPass::Render(vtkRenderState const*) (this=0x55d4346683d0, s=0x7ffc66dcf940) at /home/jafar/dev/paraview/src/VTK/Rendering/OpenGL2/vtkCameraPass.cxx:145
--Type <RET> for more, q to quit, c to continue without paging--
#51 0x00007fa76f7fa461 in vtkOSPRayPass::Render(vtkRenderState const*) (this=0x55d4346b9480, s=0x7ffc66dcf940) at /home/jafar/dev/paraview/src/VTK/Rendering/RayTracing/vtkOSPRayPass.cxx:271
#52 0x00007fa7780a43a7 in vtkCameraPass::Render(vtkRenderState const*) (this=0x55d4345dafa0, s=0x7ffc66dcf940) at /home/jafar/dev/paraview/src/VTK/Rendering/OpenGL2/vtkCameraPass.cxx:145
#53 0x00007fa77820d937 in vtkOpenGLRenderer::DeviceRender() (this=0x55d42ecbdc00) at /home/jafar/dev/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderer.cxx:285
#54 0x00007fa7775524cd in vtkRenderer::Render() (this=0x55d42ecbdc00) at /home/jafar/dev/paraview/src/VTK/Rendering/Core/vtkRenderer.cxx:385
#55 0x00007fa777570a63 in vtkRendererCollection::Render() (this=0x55d42ec3e470) at /home/jafar/dev/paraview/src/VTK/Rendering/Core/vtkRendererCollection.cxx:52
#56 0x00007fa77752e888 in vtkRenderWindow::DoStereoRender() (this=0x55d42d584480) at /home/jafar/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:356
#57 0x00007fa77752e5f4 in vtkRenderWindow::Render() (this=0x55d42d584480) at /home/jafar/dev/paraview/src/VTK/Rendering/Core/vtkRenderWindow.cxx:316
#58 0x00007fa77820b3c4 in vtkOpenGLRenderWindow::Render() (this=0x55d42d584480) at /home/jafar/dev/paraview/src/VTK/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx:2772
#59 0x00007fa7780fd929 in vtkGenericOpenGLRenderWindow::Render() (this=0x55d42d584480) at /home/jafar/dev/paraview/src/VTK/Rendering/OpenGL2/vtkGenericOpenGLRenderWindow.cxx:220
#60 0x00007fa76fc753a0 in vtkPVRenderView::Render(bool, bool) (this=0x55d42ec4a8e0, interactive=false, skip_rendering=false) at /home/jafar/dev/paraview/src/Remoting/Views/vtkPVRenderView.cxx:1727
#61 0x00007fa76fc73f04 in vtkPVRenderView::StillRender() (this=0x55d42ec4a8e0) at /home/jafar/dev/paraview/src/Remoting/Views/vtkPVRenderView.cxx:1484
#62 0x00007fa77050c204 in vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*)
(arlu=0x55d42c9632c0, ob=0x55d42ec4a8e0, method=0x55d433247f79 "StillRender", msg=..., resultStream=...) at /home/jafar/dev/paraview/build/CMakeFiles/vtkRemotingViewsCS/vtkPVRenderViewClientServer.cxx:277
#63 0x00007fa77893835d in vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&)
(this=0x55d42c9632c0, cname=0x7fa76fe19c1b "vtkPVRenderView", ptr=0x55d42ec4a8e0, method=0x55d433247f79 "StillRender", msg=..., result=...) at /home/jafar/dev/paraview/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:810
#64 0x00007fa778936762 in vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) (this=0x55d42c9632c0, css=..., midx=2) at /home/jafar/dev/paraview/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:424
#65 0x00007fa778935c3a in vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) (this=0x55d42c9632c0, css=..., message=2) at /home/jafar/dev/paraview/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:265
#66 0x00007fa778935abd in vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) (this=0x55d42c9632c0, css=...) at /home/jafar/dev/paraview/src/Remoting/ClientServerStream/vtkClientServerInterpreter.cxx:235
#67 0x00007fa779b2679a in vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) (this=0x55d42c918830, stream=..., ignore_errors=false) at /home/jafar/dev/paraview/src/Remoting/ServerManager/vtkPVSessionCore.cxx:620
#68 0x00007fa779b26553 in vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) (this=0x55d42c918830, location=16, stream=..., ignore_errors=false) at /home/jafar/dev/paraview/src/Remoting/ServerManager/vtkPVSessionCore.cxx:590
#69 0x00007fa779b221a2 in vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) (this=0x55d42d1db720, location=16, stream=..., ignore_errors=false) at /home/jafar/dev/paraview/src/Remoting/ServerManager/vtkPVSessionBase.cxx:165
#70 0x00007fa779ca539e in vtkSMProxy::ExecuteStream(vtkClientServerStream const&, bool, unsigned int) (this=0x55d42e55b780, stream=..., ignore_errors=false, location=16) at /home/jafar/dev/paraview/src/Remoting/ServerManager/vtkSMProxy.cxx:2406
#71 0x00007fa76fdacdd7 in vtkSMViewProxy::StillRender() (this=0x55d42e55b780) at /home/jafar/dev/paraview/src/Remoting/Views/vtkSMViewProxy.cxx:406
#72 0x00007fa77a998be2 in pqView::forceRender() (this=0x55d42ecef010) at /home/jafar/dev/paraview/src/Qt/Core/pqView.cxx:239
#73 0x00007fa77a998b2a in pqView::tryRender() (this=0x55d42ecef010) at /home/jafar/dev/paraview/src/Qt/Core/pqView.cxx:217
#74 0x00007fa77a85ae8f in pqView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x55d42ecef010, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0x7ffc66dd1300) at /home/jafar/dev/paraview/build/Qt/Core/pqCore_autogen/EWIEGA46WW/moc_pqView.cpp:201
#75 0x00007fa77508a1d0 in QMetaObject::activate(QObject*, int, int, void**) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#76 0x00007fa7750973ee in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#77 0x00007fa77a041d1f in pqTimer::timerEvent(QTimerEvent*) (this=0x55d42edc1f48, evt=0x7ffc66dd1650) at /home/jafar/dev/paraview/src/ThirdParty/QtTesting/vtkqttesting/pqTimer.cxx:53
#78 0x00007fa77508abc5 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#79 0x00007fa77b240a66 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#80 0x00007fa77b24a0f0 in QApplication::notify(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#81 0x00007fa77505e80a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#82 0x00007fa7750b5780 in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#83 0x00007fa7750b606c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#84 0x00007fa76d09217d in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#85 0x00007fa76d092400 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#86 0x00007fa76d0924a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#87 0x00007fa7750b6435 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#88 0x00007fa77505d3ab in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#89 0x00007fa775065116 in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#90 0x000055d42b239024 in main(int, char**) (argc=1, argv=0x55d42c7d5730) at /home/jafar/dev/paraview/build/Clients/ParaView/paraview_main.cxx:151
```
</details>
Step to reproduce:
- Open can.ex2
- Enable Raytracing
- set `Temporal Cache Size` to 10
- play the beginning of the animation
- set `Temporal Cache Size` to 0
- paraview crash with the error linked above.
Other informations:
- raytracing with OSPRay (I have this issue with both OSPRay path tracer and raycaster)
- I test it on can.ex2
- my OS is Ubuntu 20.04https://gitlab.kitware.com/paraview/paraview/-/issues/22138smTestDriver: add documentation for features supported2023-05-11T08:55:48-04:00Ben BoeckelsmTestDriver: add documentation for features supportedThe following discussion from !6253 should be addressed:
- [ ] @cory.quammen started a [discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6253#note_1358574): (+1 comment)
> This seems like a reasonable chan...The following discussion from !6253 should be addressed:
- [ ] @cory.quammen started a [discussion](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6253#note_1358574): (+1 comment)
> This seems like a reasonable change to me. There isn't a clear place for documentation for this environment variables (or the previously existing environment variable), so I suggest just merging as is as it adds a useful feature and the lack of documentation does not make anything worse.
---
`smTestDriver` has all kinds of hidden knobs that we should document. Somewhere.https://gitlab.kitware.com/paraview/paraview/-/issues/22137Saving font settings as default doesn't work in charts2023-05-10T04:16:30-04:00Thomas GallandSaving font settings as default doesn't work in chartsWhen saving current view settings as default with charts, text properties are well saved, except of the font.
![image](/uploads/126be81e71e9521c738d9811df824d4f/image.png)
Steps to reproduce:
- Open a `Wavelet`
- Apply the `Plot Over L...When saving current view settings as default with charts, text properties are well saved, except of the font.
![image](/uploads/126be81e71e9521c738d9811df824d4f/image.png)
Steps to reproduce:
- Open a `Wavelet`
- Apply the `Plot Over Line` filter, a new `Line Char View` is created
- In the `View` properties, `Legend Properties` category, change the font to `Courier`
- Hit the `Save current view settings ...` button
- Open a new chart view, show the result of `Plot Over Line` in it
- Font is back to Arial
Notes:
- Concerns all font properties in the view (title, legend, axis).
- Other properties (bold, font color, etc.) are well saved.
- Note that the copy / paste of properties works well with fonts.https://gitlab.kitware.com/paraview/paraview/-/issues/22136Using Time Manager crashes Paraview when connected to Catalyst2023-11-08T21:11:22-05:00Louis GombertUsing Time Manager crashes Paraview when connected to CatalystHello, I have randomly found a crash in Paraview nightly build, which has to do with the time manager.
Here are the steps reproduce the crash :
- Open a time-varying dataset (for example `can.ex2`)
- Click on `Apply` to view it in th...Hello, I have randomly found a crash in Paraview nightly build, which has to do with the time manager.
Here are the steps reproduce the crash :
- Open a time-varying dataset (for example `can.ex2`)
- Click on `Apply` to view it in the main render view
- Display the new time manager (View > Time Manager)
- Start Catalyst (Catalyst > Connect)
- change the time to 0.11111 (for can.ex2) in the Time Manager using the drop-down menu
- manually change the view orientation in the render view using the mouse
- Click on the settings wheel of the time manager on the right of the panel
At this step, Paraview segfaults.
Environment : Linux Mint 21.1 x86_64, on latest binary Paraview nightly build
I can provide more information if needed.https://gitlab.kitware.com/paraview/paraview/-/issues/22135Paraview VTKHDF Reader can not read utf8 strings2023-05-11T16:52:23-04:00lucasbantingParaview VTKHDF Reader can not read utf8 stringsA file with the encoding:
```
HDF5 “test_file.hdf” {
GROUP “/” {
GROUP “VTKHDF” {
ATTRIBUTE “Type” {
DATATYPE H5T_STRING {
STRSIZE 16;
STRPAD H5T_STR_NULLTERM;
CSET H5T_CSET_UTF8;
CTYPE H5T_C_S1;
}
DATASPACE SCALAR
DATA {
(0): “Unstruct...A file with the encoding:
```
HDF5 “test_file.hdf” {
GROUP “/” {
GROUP “VTKHDF” {
ATTRIBUTE “Type” {
DATATYPE H5T_STRING {
STRSIZE 16;
STRPAD H5T_STR_NULLTERM;
CSET H5T_CSET_UTF8;
CTYPE H5T_C_S1;
}
DATASPACE SCALAR
DATA {
(0): “UnstructuredGrid”
}
}
ATTRIBUTE “Version” {
DATATYPE H5T_STD_I64LE
DATASPACE SIMPLE { ( 2 ) / ( 2 ) }
DATA {
(0): 1, 0
}
}
…
}
```
Will not be able to read the 'Type' attribute. I'm not sure if there is a Paraview limitation, or a limitation of the VTK reader.
Related forum post: https://discourse.vtk.org/t/paraview-can-not-find-reader-for-hdf-file-in-windows/11398/3
Tested on Windows 11 using Paraview 1099 with MS-MPI.https://gitlab.kitware.com/paraview/paraview/-/issues/22131Copy and paste properties does not work for Line2023-05-05T03:53:32-04:00Massimiliano LeoniCopy and paste properties does not work for LineI noticed that if I create a Line1 source, set the point coordinates to something, then create a Line2 source, right click on Line1, Copy, right click on Line2, Paste, nothing happens while I would expect the coordinates from Line1 to be...I noticed that if I create a Line1 source, set the point coordinates to something, then create a Line2 source, right click on Line1, Copy, right click on Line2, Paste, nothing happens while I would expect the coordinates from Line1 to be copied over to Line2.https://gitlab.kitware.com/paraview/paraview/-/issues/22130Python Plugin Documentation missing in pop-up window2023-05-05T12:15:14-04:00Julien FaustyPython Plugin Documentation missing in pop-up window## Problem Statement
When using a filter from a loaded python plugin, clicking on the question mark button in the properties panel does not show the documentation associated when that filter.
## Steps to reproduce
* Load this python p...## Problem Statement
When using a filter from a loaded python plugin, clicking on the question mark button in the properties panel does not show the documentation associated when that filter.
## Steps to reproduce
* Load this python plugin: [MyRandomWarp.py](/uploads/2f23cd1959288b97b37c88bb077d0b32/MyRandomWarp.py)
* Create a Sphere
* Apply the "My Random Warp" filter
* Click on the question mark button to open up the documentation windowhttps://gitlab.kitware.com/paraview/paraview/-/issues/22129Gray out plugins that should not be selected2023-05-09T09:16:43-04:00W. Alan ScottGray out plugins that should not be selectedWhen a user has a remote connection she sometimes needs to start a client/server plugin, found in Tools/ Manage Plugins. The natural thing to do is click the plugin from the right list, then the left list. Please invert these two list...When a user has a remote connection she sometimes needs to start a client/server plugin, found in Tools/ Manage Plugins. The natural thing to do is click the plugin from the right list, then the left list. Please invert these two lists so the Local Plugins (the ones you select first) are on the right. Then, please gray out the server side plugins with a matching local plugin until the local plugin is selected. Either solution is acceptable alone, but I would prefer both solutions.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22128Colormap opacity enabled after switch to categorical and back2024-03-07T20:23:57-05:00Aron HelserColormap opacity enabled after switch to categorical and backOn current PV master, 5/3/2023, with the new colormapping UI reorganization, there is an unexpected behavior enabling opacity mapping.
To reproduce:
* load Source .. Data Objects .. HyperTreeGrid (or any dataset with something that can b...On current PV master, 5/3/2023, with the new colormapping UI reorganization, there is an unexpected behavior enabling opacity mapping.
To reproduce:
* load Source .. Data Objects .. HyperTreeGrid (or any dataset with something that can be a categorical color map)
* color by `vtkEdgeFlags`
* show the Color Map Editor. Notice "Enable Opacity Mapping for Surfaces" is disabled
* enable "Interpret Values as Categories". Immediately disable.
* "Enable Opacity Mapping for Surfaces" is now enabled, and my surface has disappeared.
Note that if I now explicitly disable "Enable Opacity Mapping for Surfaces" at this point, it sticks - I can switch to categorical and back without a problem. Maybe this points to default value handling somehow?
I also see that when "Interpret Values as Categories" is on, an "Enable Opacity Mapping for Surfaces" option is present and enabled by default.
CC @jaswant.panchumarti @cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22126Using a programable filter after a scalar clip will not return min/max in a t...2024-03-07T20:23:56-05:00Phil SmithUsing a programable filter after a scalar clip will not return min/max in a table**To reproduce this error perform the following:**
**Manual reproduction:**
- Open spcta_a.0*; Apply
- Select all cell arrays; Apply
- Perform a clip
- Select Scalar
- Select Temperature (ev)
- Select reset using current data values
-...**To reproduce this error perform the following:**
**Manual reproduction:**
- Open spcta_a.0*; Apply
- Select all cell arrays; Apply
- Perform a clip
- Select Scalar
- Select Temperature (ev)
- Select reset using current data values
- Unselect Invert; Apply
- Add a programmable filter:
- Set Output Data Set Type to vtkTable
- Select Copy Arrays
- within the script window use the following:
```
from paraview.vtk.numpy_interface import algorithms as np
input0 = inputs[0]
array = input0.CellData['Mass (g) - 2']
val = np.mean(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (mean)')
val = np.std(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (std)')
val = np.min(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (min)')
val = np.max(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (max)')`
```
- Apply
**I get this error:**
```
Traceback (most recent call last):
File "<string>", line 22, in <module>
File "<string>", line 15, in RequestData
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 399, in min
return _global_func(MinImpl(), array, axis, controller)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 184, in _global_func
res = impl.serial_composite(array, axis)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 387, in serial_composite
res = _apply_func2(algs.min, array, (axis,))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 48, in _apply_func2
res.append(func(a, *args))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 397, in min
ans = numpy.min(narray, axis)
File "<__array_function__ internals>", line 5, in amin
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 2879, in amin
return _wrapreduction(a, np.minimum, 'min', axis, None, out,
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/Snip/lib/python3.9/site-packages/numpy/core/_methods.py", line 44, in _amin
return umr_minimum(a, axis, None, out, keepdims, initial, where)
ValueError: zero-size array to reduction operation minimum which has no identity
```
**As stated above, I have copied the arrays from the clip to the programable filter, but the programable filter does not show the arrays that are in the clip, or a min and max that should be derived from the clip by using this filter. It does show a mean and an std value, so it should show a min and a max. It shouldn't through an error eather. This is wrong.**
In each of the following scripts I have placed 'snip' for the path, so they will have to be modified to be used.
**Here is another way to reproduce an error(Slightly different, but the same idea) using a script:
Run this script(no_min_after_scalarclip). : [no_min_after_scalarclip.py](/uploads/b31330bfc8e98ae9ee76f62b42069bc7/no_min_after_scalarclip.py)
It will not show a T-1 (max) 0r a T-1(min), but will produce these errors:**
```
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x2919f780): Algorithm vtkPVGeometryFilter (0x2917fbe0) returned failure for request: vtkInformation (0x291a0c20)
Debug: Off
Modified Time: 2830306
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x28e04e20): Algorithm vtkPVGeometryFilter (0x28dec3e0) returned failure for request: vtkInformation (0x28e062c0)
Debug: Off
Modified Time: 2830481
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
Traceback (most recent call last):
File "<string>", line 22, in <module>
File "<string>", line 15, in RequestData
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 399, in min
return _global_func(MinImpl(), array, axis, controller)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 184, in _global_func
res = impl.serial_composite(array, axis)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 387, in serial_composite
res = _apply_func2(algs.min, array, (axis,))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 48, in _apply_func2
res.append(func(a, *args))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 397, in min
ans = numpy.min(narray, axis)
File "<__array_function__ internals>", line 5, in amin
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 2879, in amin
return _wrapreduction(a, np.minimum, 'min', axis, None, out,
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/Snip/lib/python3.9/site-packages/numpy/core/_methods.py", line 44, in _amin
return umr_minimum(a, axis, None, out, keepdims, initial, where)
ValueError: zero-size array to reduction operation minimum which has no identity
**However when this script is run: [min_after_planarclip.py](/uploads/da0453a970dba5188d2cab4f63a34774/min_after_planarclip.py), it will produce the min and the max, but will give theses errors:**
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x24a7f3d0): Algorithm vtkPVGeometryFilter (0x24a5f830) returned failure for request: vtkInformation (0x24a80870)
Debug: Off
Modified Time: 2532788
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x249fec80): Algorithm vtkPVGeometryFilter (0x249e5fe0) returned failure for request: vtkInformation (0x24a00120)
Debug: Off
Modified Time: 2532963
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
**This is still wrong, because it should not show theses errors at all.**
**I modified the pipeline for each of the examples above to include the Redistribute Data filter before the programable filter as a work-around. This should not have to be done.**5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22125vtkSMStateVersionController missing animated property update2023-05-02T11:08:08-04:00Mathieu Westphal (Kitware)vtkSMStateVersionController missing animated property updateAs discussed here: https://gitlab.kitware.com/paraview/paraview/-/issues/21782#note_1354051, vtkSMStateVersionController (and _backwards_compatibility_helper.py for that matter) do not take care of update animated properties names, hence...As discussed here: https://gitlab.kitware.com/paraview/paraview/-/issues/21782#note_1354051, vtkSMStateVersionController (and _backwards_compatibility_helper.py for that matter) do not take care of update animated properties names, hence making older state files with animated properties unusable in newer versions of ParaView.
@cory.quammen @thomas.galland