ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-08T07:43:50-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22515Transformation (rotation) of tensor variables2024-03-08T07:43:50-05:00cmorsbachTransformation (rotation) of tensor variablesAs suggested by @mwestphal in https://discourse.paraview.org/t/transformation-of-tensor-variables/14112, I'm opening a ticket for this feature request:
Currently, the _Transform_ filter in ParaView applies the correct transformation (ro...As suggested by @mwestphal in https://discourse.paraview.org/t/transformation-of-tensor-variables/14112, I'm opening a ticket for this feature request:
Currently, the _Transform_ filter in ParaView applies the correct transformation (rotation) to vectors stored as 3-component float arrays. As there is support for Cartesian rank 2 tensors (6-component symmetric and 9-component general) in ParaView, it would be good, if these were transformed as well. Currently (ParaView 5.11), they are not, which leads to an inconsistent dataset when _Transform_ or _AngularPeriodicFilter_ are applied.https://gitlab.kitware.com/paraview/paraview/-/issues/22514polygonal meshes do not get exported correctly to CGNS2024-03-08T07:33:17-05:00Alexandre Minotpolygonal meshes do not get exported correctly to CGNSPolygonal meshes do not get exported correctly to CGNS, at least in 1D. The coordinates and data look right, but there are no elements in the CGNS files. This can be reproduced by creating a line source and saving the result to CGNS. My ...Polygonal meshes do not get exported correctly to CGNS, at least in 1D. The coordinates and data look right, but there are no elements in the CGNS files. This can be reproduced by creating a line source and saving the result to CGNS. My guess is that each segment of the polygon will need to be split into individual BAR elements.
In particular, this means that streamtracer results cannot be saved to CGNS
[line.cgns](/uploads/9f23b0f4a992a80f445f84ee1704b116/line.cgns)
[line.py](/uploads/d544edb3528f433fb10e6c019a5988c8/line.py)https://gitlab.kitware.com/paraview/paraview/-/issues/22513Memory leaks when using ParaView Catalyst2024-03-08T07:27:33-05:00Spiros TsalikisMemory leaks when using ParaView Catalyst```
=================================================================
==17446==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4180894 byte(s) in 2337 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/peo...```
=================================================================
==17446==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 4180894 byte(s) in 2337 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0cad in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0cad in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
Direct leak of 160 byte(s) in 2 object(s) allocated from:
#0 0x5175d8 in operator new(unsigned long) /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:92
#1 0x7fa4bd3bcc2d in catalyst_conduit_node_create (/usr/people/shared/tools/centos/7/catalyst/HPCX/2.0.0/lib64/libcatalyst.so.3+0xedc2d)
#2 0x6080000655d7 (<unknown module>)
Direct leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa4b25470cb (<unknown module>)
Direct leak of 64 byte(s) in 2 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495dd1294 in PyThread_allocate_lock /home/foo/Downloads/Python-3.7.0/build/../Python/thread_pthread.h:257:21
Direct leak of 12 byte(s) in 1 object(s) allocated from:
#0 0x442048 in strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:407
#1 0x7fa4a08f89de in vtkloguru::init(int&, char**, vtkloguru::Options const&) (/usr/people/shared/tools/centos/7/paraview/HPCX/paraview/5.11.0-mesa/lib64/catalyst/libcatalyst-paraview.so+0x87a69de)
Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x442048 in strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:407
#1 0x7fa4a08f93a6 in vtkloguru::set_thread_name(char const*) (/usr/people/shared/tools/centos/7/paraview/HPCX/paraview/5.11.0-mesa/lib64/catalyst/libcatalyst-paraview.so+0x87a73a6)
Direct leak of 1 byte(s) in 1 object(s) allocated from:
#0 0x442558 in __strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:423
#1 0x7fa4b094a7f0 (<unknown module>)
Indirect leak of 1361576 byte(s) in 1124 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0cad in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0cad in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
Indirect leak of 12508 byte(s) in 2 object(s) allocated from:
#0 0x4e0010 in realloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:107
#1 0x7fa495cde4f8 in resize_compact /home/foo/Downloads/Python-3.7.0/build/../Objects/unicodeobject.c:929:31
Indirect leak of 544 byte(s) in 1 object(s) allocated from:
#0 0x4dfba8 in __interceptor_malloc /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:88
#1 0x7fa495cc0edc in PyMem_RawMalloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:503:12
#2 0x7fa495cc0edc in _PyObject_Malloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1560
#3 0x7fa495cc0edc in pymalloc_realloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1882
#4 0x7fa495cc0edc in _PyObject_Realloc /home/foo/Downloads/Python-3.7.0/build/../Objects/obmalloc.c:1901
Indirect leak of 128 byte(s) in 2 object(s) allocated from:
#0 0x5175d8 in operator new(unsigned long) /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:92
#1 0x7fa4bd3412ec in catalyst_conduit::Node::Node() (/usr/people/shared/tools/centos/7/catalyst/HPCX/2.0.0/lib64/libcatalyst.so.3+0x722ec)
#2 0x6080000655d7 (<unknown module>)
Indirect leak of 15 byte(s) in 1 object(s) allocated from:
#0 0x442558 in __strdup /usr/people/shared/tools/centos/6/llvm/build_files/6.0.0/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:423
#1 0x7fa4b254713e (<unknown module>)
SUMMARY: AddressSanitizer: 5555974 byte(s) leaked in 3475 allocation(s).
```
```
cmake /usr/people/shared/tools/centos/7/paraview/installer/src/paraview/Examples -DCMAKE_BUILD_TYPE=ASAN -DOPENGL_xmesa_INCLUDE_DIR:PATH=IGNORE -DOPENGL_gl_LIBRARY:FILEPATH=IGNORE -DOSMESA_INCLUDE_DIR:PATH=$MESA_INC -DOSMESA_LIBRARY:FILEPATH=$MESA_LIB/libOSMesa.so -DCMAKE_INSTALL_PREFIX="/work/foo/cases/053_Catalyst_Standalone/001_Polyhedra/install/"
cd Catalyst2/CxxPolyhedra
make install
```
```
cmake /usr/people/shared/tools/centos/7/paraview/installer/src/paraview/Examples -DCMAKE_BUILD_TYPE=ASAN -DOPENGL_xmesa_INCLUDE_DIR:PATH=IGNORE -DOPENGL_gl_LIBRARY:FILEPATH=IGNORE -DOSMESA_INCLUDE_DIR:PATH=$MESA_INC -DOSMESA_LIBRARY:FILEPATH=$MESA_LIB/libOSMesa.so -DCMAKE_INSTALL_PREFIX="/work/foo/cases/053_Catalyst_Standalone/001_Polyhedra/install/" -DCMAKE_CXX_FLAGS_ASAN="-g -O3 -DNDEBUG -DASAN_ENABLED -fsanitize=address -fno-omit-frame-pointer"
```
```
./build/bin/CxxPolyhedraV2 catalyst_pipeline.py
```
[catalyst_pipeline.py](/uploads/939c786c80b9afd83b0d490c28067551/catalyst_pipeline.py)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22512vtkOverlappingAMR: rendering artifacts with Wireframe and FeatureEdges repres...2024-03-07T08:37:24-05:00Lucas GivordvtkOverlappingAMR: rendering artifacts with Wireframe and FeatureEdges representationIn `Feature Edges` and `Wireframe` representations there are some rendering artifacts when we have overlap between the border of multiple levels:
![image](/uploads/4d5dce5ed815a0cf1220c0b83f48d5ed/image.png)
This issue can be reproduc...In `Feature Edges` and `Wireframe` representations there are some rendering artifacts when we have overlap between the border of multiple levels:
![image](/uploads/4d5dce5ed815a0cf1220c0b83f48d5ed/image.png)
This issue can be reproduce by loading this data and set the level to `2`:
[overlapping_amr_artifacts.vthb](/uploads/6e7797e0f62d8890962a2309fb3954ed/overlapping_amr_artifacts.vthb)https://gitlab.kitware.com/paraview/paraview/-/issues/22511Comparative View Constantly Updating Causing High CPU Usage2024-03-07T07:56:19-05:00Ethan StamComparative View Constantly Updating Causing High CPU Usage@cory.quammen
I am using ParaView 5.11.2 on a Mac x86_64 laptop.
I am getting a problem with the comparative viz view where (in at least one case) it is constantly updating the views.
Steps to reproduce:
1. Launch paraview from comma...@cory.quammen
I am using ParaView 5.11.2 on a Mac x86_64 laptop.
I am getting a problem with the comparative viz view where (in at least one case) it is constantly updating the views.
Steps to reproduce:
1. Launch paraview from command line with `/Applications/ParaView-5.11.2.app/Contents/MacOS/paraview -v=9` to get verbose output
2. Close renderview and open renderview (comparative)
3. View -> Comparative View Inspector
4. File Open disk_out_ref example dataset
5. Apply contour filter with default options
6. In Comparative View Inspector, choose Contour1 and Isosurfaces as the parameter, click the plus icon to add it
After step 6 is where I hit the issue. I didn't spend much time, but I couldn't find another way to reproduce it. I tried other datasets, but didn't get the same result.
![comparative_view](/uploads/e29329840ed69e83da6707b87adb680a/comparative_view.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/22510ParaView v5.12.0 requires an old version of FastFloat, why?2024-03-08T12:48:23-05:00Thierry ThomasParaView v5.12.0 requires an old version of FastFloat, why?Trying to build ParaView 5.12.0 on my workstation, where FastFloat v6.0.0 is installed: it is rejected by CMake:
```
CMake Warning at VTK/CMake/vtkModule.cmake:4958 (find_package):
Could not find a configuration file for package "FastF...Trying to build ParaView 5.12.0 on my workstation, where FastFloat v6.0.0 is installed: it is rejected by CMake:
```
CMake Warning at VTK/CMake/vtkModule.cmake:4958 (find_package):
Could not find a configuration file for package "FastFloat" that is
compatible with requested version "3.9.0".
The following configuration files were considered but not accepted:
/usr/local/share/cmake/FastFloat/FastFloatConfig.cmake, version: 6.0.0
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:5594 (vtk_module_find_package)
VTK/CMake/vtkModule.cmake:5462 (vtk_module_third_party_external)
VTK/ThirdParty/fast_float/CMakeLists.txt:1 (vtk_module_third_party)
CMake Error at VTK/CMake/vtkModule.cmake:4964 (message):
Could not find the FastFloat external dependency.
Call Stack (most recent call first):
VTK/CMake/vtkModule.cmake:5594 (vtk_module_find_package)
VTK/CMake/vtkModule.cmake:5462 (vtk_module_third_party_external)
VTK/ThirdParty/fast_float/CMakeLists.txt:1 (vtk_module_third_party)
```
Note: upstream released [FastFloat v6.1.0](https://github.com/fastfloat/fast_float/releases/tag/v6.1.0) some days ago.
Does ParaView really need such an old version?https://gitlab.kitware.com/paraview/paraview/-/issues/22509Python wrapping needs to pull in all wrapped targets in static builds2024-03-07T07:57:53-05:00Alexander NeumannPython wrapping needs to pull in all wrapped targets in static buildsSo I am trying to build PV 5.12 with external VTK (https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6375?full_index=1) statically and ran into (after removing a cycle in the target deps):
```
CMake Error at E:/vcpkg_folders...So I am trying to build PV 5.12 with external VTK (https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6375?full_index=1) statically and ran into (after removing a cycle in the target deps):
```
CMake Error at E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/VTK-targets.cmake:967 (set_target_properties):
The link interface of target "VTK::RenderingOpenVR" contains:
OpenVR::OpenVR
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/vtk-config.cmake:143 (include)
E:/vcpkg_folders/paraview/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:65 (find_package)
CMake Error at E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/VTK-targets.cmake:1265 (set_target_properties):
The link interface of target "VTK::pegtl" contains:
PEGTL::PEGTL
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/vtk-config.cmake:143 (include)
E:/vcpkg_folders/paraview/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:65 (find_package)
CMake Error at E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/VTK-targets.cmake:1584 (set_target_properties):
The link interface of target "VTK::IOGDAL" contains:
GDAL::GDAL
but the target was not found. Possible reasons include:
* There is a typo in the target name.
* A find_package call is missing for an IMPORTED target.
* An ALIAS target is missing.
Call Stack (most recent call first):
E:/vcpkg_folders/paraview/installed/x64-windows-static-md-release/share/vtk/vtk-config.cmake:143 (include)
E:/vcpkg_folders/paraview/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:65 (find_package)
```
The target chain is:
```
OpenVR::OpenVR
-> VTK::RenderingOpenVR
-> VTK::vtkRenderingOpenVRPython
-> VTK::vtkpythonmodules
-> ParaView::PythonInitializer or pvincubatorpythonmodules or pvpythonmodules
```
(similar for GDAL)
The problem is that the `find_package` call added for external VTK is not pulling in the required VTK COMPONENTS which have been wrapped.
The calculated find_package call is:
`find_package(VTK CONFIG REQUIRED COMPONENTS CommonCore;CommonDataModel;IOImage;IOParallelXML;ParallelMPI;RenderingCore;RenderingOpenGL2;CommonExecutionModel;PythonInterpreter;ParallelCore;WrappingPythonCore;FiltersGeneral;FiltersHybrid;vtksys;mpi;RenderingParallelLIC;Python;RenderingMatplotlib;AcceleratorsVTKmFilters;IOXdmf2;IOCGNSReader;DomainsChemistry;FiltersAMR;FiltersCore;FiltersExtraction;FiltersFlowPaths;FiltersGeneric;FiltersGeometry;FiltersHyperTree;FiltersModeling;FiltersOpenTURNS;FiltersParallel;FiltersParallelDIY2;FiltersParallelVerdict;FiltersSources;FiltersStatistics;FiltersTensor;FiltersTexture;FiltersVerdict;ImagingCore;ImagingFourier;ImagingGeneral;ImagingHybrid;ImagingSources;IOAsynchronous;IOChemistry;IOGeometry;IOInfovis;IOLegacy;IOParallel;IOPLY;IOVPIC;IOXML;IOAMR;IOCityGML;IOCONVERGECFD;IOFDS;IOIOSS;IOH5part;IOH5Rage;IONetCDF;IOOggTheora;IOOMF;IOParallelExodus;IOParallelLSDyna;IOPIO;IOHDF;IOSegY;IOTRUCHAS;IOVeraOut;IOTecplotTable;IOFLUENTCFF;RenderingFreeType;ParallelMPI4Py;FiltersParallelFlowPaths;FiltersParallelGeometry;FiltersParallelMPI;IOMPIImage;IOParallelNetCDF;WrappingTools;CommonMisc;CommonSystem;CommonTransforms;hdf5;netcdf;zlib;CommonMath;opengl;FiltersPython;FiltersPoints;IOCore;cgns;IOEnSight;FiltersParallelStatistics;FiltersProgrammable;GUISupportQt;IOExportGL2PS;jsoncpp;nlohmannjson;ChartsCore;pugixml;cli11;TestingRendering;IOImport;FiltersGeometryPreview;IOMovie;CommonComputationalGeometry;IOExport;fmt;RenderingAnnotation;RenderingContext2D;RenderingCellGrid;RenderingParallel;ViewsContext2D;ViewsCore;CommonColor;DomainsChemistryOpenGL2;FiltersCellGrid;InteractionStyle;RenderingContextOpenGL2;RenderingLICOpenGL2;RenderingLabel;RenderingVolumeAMR;lz4;RenderingVolume;FiltersImaging;doubleconversion;loguru )`
And does not contain the required COMPONENTS to activate the lookup of the additional dependencies.
CC @ben.boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/22508Unstructured Mesh Contour Filter Rendering Glitch2024-03-05T14:41:27-05:00Johannes NeumannUnstructured Mesh Contour Filter Rendering GlitchHello,
I'm encountering a glitch with the new version. I hope, my description below helps:
* I'm rendering an unstructured grid with scalar point values.
* It's surface is visualised with a colour map that has a transparency gradient....Hello,
I'm encountering a glitch with the new version. I hope, my description below helps:
* I'm rendering an unstructured grid with scalar point values.
* It's surface is visualised with a colour map that has a transparency gradient.
![grafik.png](/uploads/7016572ec1100001c511f68ec5eb44cb/grafik.png){width=262 height=216}
![grafik.png](/uploads/28ff54461b3d4774edbc3e66bc3d141f/grafik.png)
* I apply a contour filter with three levels which inherit the semi-transparent colour map.
![grafik.png](/uploads/808864016c9ac3cf37a0e84ccc63815c/grafik.png){width=268 height=210}
![grafik.png](/uploads/4dd43e7e112a1c614972b12e90516640/grafik.png)
* I reenable the original data in the pipeline browser as well and I get a glitch
![grafik.png](/uploads/5662ac49cdb19057e9cb27a3cc71227c/grafik.png){width=275 height=206}
![grafik.png](/uploads/7aa12de73b8e8f1521d6989515509bbf/grafik.png)
Depth peeling is turned off
Version: Paraview 5.12 MPI from the MSI installer on Windows 11 (Intel UHD Graphics 620)
This worked on Paraview 5.11.1
The glitch persists until both are hidden and only the initial data set is unhidden again or only the initial data set is hidden.
Please let me know if you want more information or if you want me to test something.https://gitlab.kitware.com/paraview/paraview/-/issues/22507Triangulated slice does not have components2024-03-07T20:31:42-05:00Richard KellnbergerTriangulated slice does not have componentsWhen adding the file [u2000000.vtk](/uploads/649370f9ede77f0db301e29fed9f846e/u2000000.vtk) (contains 3D SCALARS) and clicking the slice button in the toolbar, the resulting slice has the component dropdown disabled since 5.11<br>
When I...When adding the file [u2000000.vtk](/uploads/649370f9ede77f0db301e29fed9f846e/u2000000.vtk) (contains 3D SCALARS) and clicking the slice button in the toolbar, the resulting slice has the component dropdown disabled since 5.11<br>
When I remove the check from “Triangulate the slice” click off the slice in the Pipeline Browser and back on, the dropdown reappears.
This did not happen in earlier versions and is probably not intentional?5.12.1 (Spring 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22506Add polyhedra source in ParaView2024-03-04T12:28:50-05:00Alexandre MinotAdd polyhedra source in ParaViewWe should add a polyhedra source in the data sources of ParaView. See discourse here: https://discourse.paraview.org/t/adding-a-polyhedra-source/14084We should add a polyhedra source in the data sources of ParaView. See discourse here: https://discourse.paraview.org/t/adding-a-polyhedra-source/14084https://gitlab.kitware.com/paraview/paraview/-/issues/22505OSPRay: support PDC data2024-03-13T10:46:29-04:00Ben BoeckelOSPRay: support PDC dataIt looks like OSPRay doesn't support PDC data yet. Given the future of MultiBlocks, we should add this support.
Cc: @demarle @spiros.tsalikis @cory.quammen @sankheshIt looks like OSPRay doesn't support PDC data yet. Given the future of MultiBlocks, we should add this support.
Cc: @demarle @spiros.tsalikis @cory.quammen @sankheshSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/22504Colorbar titles should accept multiline and support \n as classic annotations do2024-03-03T00:55:42-05:00GregVernonColorbar titles should accept multiline and support \n as classic annotations doSee Discourse discussion here ([specifically, @mwestphal's response](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059/2)).
The title below is: `$Very\ long\ text\ ...See Discourse discussion here ([specifically, @mwestphal's response](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059/2)).
The title below is: `$Very\ long\ text\ but\ this\ is\ still\ a\ bug\ to\ fix$`
![image](/uploads/9f27ba992488c4deb9488f0a843832a1/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22503Vertical color legends with horizontal title clash with the Use Above Range C...2024-03-01T23:24:41-05:00GregVernonVertical color legends with horizontal title clash with the Use Above Range ColorSee [Discourse discussion here](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059).
As shown in the image below, when using a vertical colorbar with a horizontal tit...See [Discourse discussion here](https://discourse.paraview.org/t/vertical-color-legends-with-horizontal-title-clash-with-the-use-above-range-color/14059).
As shown in the image below, when using a vertical colorbar with a horizontal title, if the `Use Above Color Range` option results in the title overlapping the colorbar:
![image](/uploads/1876982796e4865fea44a46e3b5600d2/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22502Add Method to Legacy Ghost Cells Generator to match Ghost Cells Generator for...2024-03-13T15:09:35-04:00John PatchettAdd Method to Legacy Ghost Cells Generator to match Ghost Cells Generator for setting ghost levelThe legacy ghost cells generator needs to have the same method for setting ghost levels so that if the two are swapped, the methods don't also have to be swapped.
So LegacyGCG::MinimumNumberOfGhosts(int) should wrap LegacyGCG::.Minimum...The legacy ghost cells generator needs to have the same method for setting ghost levels so that if the two are swapped, the methods don't also have to be swapped.
So LegacyGCG::MinimumNumberOfGhosts(int) should wrap LegacyGCG::.MinimumNumberOfGhostLevels(int)
This will alleviate a ton of headache for users needing to swap between the two GCGs.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22501File -> SaveAnimation does not work with non temporal dataset2024-03-07T04:22:54-05:00Mathieu Westphal (Kitware)File -> SaveAnimation does not work with non temporal dataset - Wavelet, Apply
- Slice, Apply
- TimeManager -> Animate Slice Offset values
- File -> SaveAnimation
- Only one image saved
It is possible to work around it using GenerateTimeSteps filter, but that should not be needed. - Wavelet, Apply
- Slice, Apply
- TimeManager -> Animate Slice Offset values
- File -> SaveAnimation
- Only one image saved
It is possible to work around it using GenerateTimeSteps filter, but that should not be needed.https://gitlab.kitware.com/paraview/paraview/-/issues/22500GLTF format validation issue when using export scene2024-03-11T09:37:49-04:00Loïc GaillardGLTF format validation issue when using export sceneWhen generating a simple data using the wavelet source from paraview and then exporting the scene to the gltf format, the exported file isn't compliant with the [gltf validator](https://github.khronos.org/glTF-Validator/).
Here is the p...When generating a simple data using the wavelet source from paraview and then exporting the scene to the gltf format, the exported file isn't compliant with the [gltf validator](https://github.khronos.org/glTF-Validator/).
Here is the paraview scene right before exporting it :
![image](/uploads/4f61c05361fdcafa4867d866b39c4090/image.png)
Here is the corresponding [gltf file](/uploads/7c9105c1f1f386a5102a8f355c825277/dummy.gltf).
It seems to be a texture mapping issue, the generated texture seems incorrect since it has the color map in a single 256px line and another line full of yellow :
![texture_image](/uploads/f7fe923465402d2439ae843a6b9e5a9e/export_img0.png)
This incorrect texture leads to some texture clipping in other device using gltf data generated from paraview :
![image](/uploads/7129ab6256add4c2d2738c36913ef3c4/image.png)
Here is a an example on PowerPoint but it also appears on other softwares such as MeshLab.Loïc GaillardLoïc Gaillardhttps://gitlab.kitware.com/paraview/paraview/-/issues/22499Expose Grow and Shrink selection operations in paraview.selection2024-02-28T15:19:32-05:00Cory Quammencory.quammen@kitware.comExpose Grow and Shrink selection operations in paraview.selection5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22498XML tests CMakeLists improvements2024-02-28T07:15:35-05:00Nicolas VuailleXML tests CMakeLists improvementsThe XML client tests are added in the CMakeLists of this [directory](https://gitlab.kitware.com/paraview/paraview/-/tree/master/Clients/ParaView/Testing/XML?ref_type=heads).
I see different issue with this CMakeLists:
1. it is really b...The XML client tests are added in the CMakeLists of this [directory](https://gitlab.kitware.com/paraview/paraview/-/tree/master/Clients/ParaView/Testing/XML?ref_type=heads).
I see different issue with this CMakeLists:
1. it is really big
* harder to find something or the correct place for new entry
* code duplication (like `if` branches and `append` statements)
2. tests without baseline are not added to client-server test suite.
3. tests are added at some place, options defined elsewhere later (like _DISABLE_CS, THRESHOLD or so)https://gitlab.kitware.com/paraview/paraview/-/issues/22497Log Viewer - Export Log broken2024-02-28T03:53:09-05:00Scott WittenburgLog Viewer - Export Log brokenThis bug prevents the export of log data to a file using the Log Viewer. To reproduce, open the the Log Viewer, and update some categories or verbosity level. Then interact with paraview (e.g. create a Cone), and hit the "Refresh" butt...This bug prevents the export of log data to a file using the Log Viewer. To reproduce, open the the Log Viewer, and update some categories or verbosity level. Then interact with paraview (e.g. create a Cone), and hit the "Refresh" button in the Log Viewer. If there are log entries, then click the "Export Log" button, provide a filename in the resulting dialog, and click Ok. Instead of a log file, some errors appear in the Output Messages window.
![client_log_file](/uploads/8b56f975475ad15d776ca69fbc218dc0/client_log_file.png)
![pv_export_log_error](/uploads/78e523feff6e40b94095723e5531b986/pv_export_log_error.png)
As indicated in the screenshot above, this error happened with the 5.12 RC3 release candidate downloaded from the website. The machine is an x86_64 running Ubuntu 20.04.https://gitlab.kitware.com/paraview/paraview/-/issues/22496Mesh geometry corrupted by Temporal Interpolator with Xdmf3 readers2024-03-01T05:26:48-05:00Maxime RenaultMesh geometry corrupted by Temporal Interpolator with Xdmf3 readersHere is what my geometry becomes after a few timesteps when reading HDF5/XDMF3 files and applying Temporal Interpolation:
![Capture_d_écran_du_2024-02-27_08-00-29](/uploads/a5f0a57c39f1d2cffbbda9ce403c3b62/Capture_d_écran_du_2024-02-27_0...Here is what my geometry becomes after a few timesteps when reading HDF5/XDMF3 files and applying Temporal Interpolation:
![Capture_d_écran_du_2024-02-27_08-00-29](/uploads/a5f0a57c39f1d2cffbbda9ce403c3b62/Capture_d_écran_du_2024-02-27_08-00-29.png)
[Here](https://drive.google.com/drive/folders/1nBibQJRCW-EyKmJGWXFLc7noqpwECgNx?usp=sharing) are the data to reproduce.
I’m using ParaView 5.11.2 on Ubuntu 22.04.4. Here are the steps to follow :
1. Open xdmf file with Xdmf3Reader (S or T) and Apply.
2. Apply TemporalInterpolator to it, and choose any resample factor >1 (tried 2, 5, 10 and 100).
3. Click play. It will go through a few timesteps with no problem then the geometry will disappear, or change position, or completely collapse.
The issue only occurs on interpolated timesteps.
XDMF Reader doesn't show this behavior, but the fields are all wrong. An example of pressure fields: left is correct, read by Xdmf3ReaderS, and right is wrong, read by Xdmf Reader.
![Capture_d_écran_du_2024-02-27_15-48-46](/uploads/2ab8c7f6c118a6db68bcbfa1bd8075b6/Capture_d_écran_du_2024-02-27_15-48-46.png)