ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-11-05T12:32:18-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21062Internal GLEW build does not disable X symbol usage2021-11-05T12:32:18-04:00Robert Manson-SawkoInternal GLEW build does not disable X symbol usageHello,
I am building ParaView 5.9.1 with Catalyst support on an x86 machine but without X11 libraries. There are NVIDIA drivers and OpenGL on this machine as well as Mesa and I intend to use it with the former. Unfortunately I am runnin...Hello,
I am building ParaView 5.9.1 with Catalyst support on an x86 machine but without X11 libraries. There are NVIDIA drivers and OpenGL on this machine as well as Mesa and I intend to use it with the former. Unfortunately I am running into a linking issue:
```bash
[ 95%] Linking CXX executable ../../../bin/vtkProbeOpenGLVersion-pv5.9 [9/9431]
cd /lustre/scafellpike/local/HT04121/aas01/shared/software/build-5.9.1/VTK/Rendering/OpenGL2 && /netfs/smain01/scafellpike/local/apps/hierarchy/core/cmake/3.21
.1/bin/cmake -E cmake_link_script CMakeFiles/vtkProbeOpenGLVersion.dir/link.txt --verbose=2
/lustre/scafellpike/local/apps/hierarchy/core/gcc/6.5.0/bin/g++ -O2 -g -DNDEBUG -Wl,-lc -Wl,-lc -Wl,-rpath=/lustre/scafellpike/local/apps/hierarchy/compiler/
gcc/6.5/openmpi/4.1.1-ucx/lib CMakeFiles/vtkProbeOpenGLVersion.dir/vtkProbeOpenGLVersion.cxx.o -o ../../../bin/vtkProbeOpenGLVersion-pv5.9 -Wl,-rpath,"\$ORIG
IN/../lib64::::::::" ../../../lib64/libvtkRenderingOpenGL2-pv5.9.so.5.9 ../../../lib64/libvtkRenderingUI-pv5.9.so.5.9 ../../../lib64/libvtkRenderingCore-pv5.9.
so.5.9 ../../../lib64/libvtkFiltersGeneral-pv5.9.so.5.9 ../../../lib64/libvtkFiltersCore-pv5.9.so.5.9 ../../../lib64/libvtkglew-pv5.9.so.5.9 /usr/lib64/libOpen
GL.so ../../../lib64/libvtkCommonExecutionModel-pv5.9.so.5.9 ../../../lib64/libvtkCommonDataModel-pv5.9.so.5.9 ../../../lib64/libvtkCommonTransforms-pv5.9.so.5
.9 ../../../lib64/libvtkCommonMisc-pv5.9.so.5.9 ../../../lib64/libvtkCommonMath-pv5.9.so.5.9 ../../../lib64/libvtkCommonCore-pv5.9.so.5.9 -lpthread ../../../li
b64/libvtksys-pv5.9.so.5.9 -ldl -Wl,-rpath-link,/lustre/scafellpike/local/HT04121/aas01/shared/software/build-5.9.1/lib64
../../../lib64/libvtkglew-pv5.9.so.5.9: undefined reference to `glXQueryVersion'
../../../lib64/libvtkglew-pv5.9.so.5.9: undefined reference to `glXGetProcAddressARB'
../../../lib64/libvtkglew-pv5.9.so.5.9: undefined reference to `glXGetClientString'
```
I believe this problem to be identical to [this post](https://discourse.paraview.org/t/undefined-reference-to-glxqueryversion-with-paraview-5-7-0rc1-and-egl-combination/2196), which was at version 5.7 and @ben.boeckel advised then that the problem is GLEW not disabling the X11 symbols. Is it possible that this is still happening?
I also submitted [a post](https://discourse.paraview.org/t/linking-issues-with-glx-for-pv5-9-with-egl/8262) to discourse, but I think now I understand the issue better and that's why I decided to put it here. Please advise.
For reference this is my cmake invocation:
```bash
cmake \
-DCMAKE_BUILD_TYPE=RelWithDebInfo \
-DBUILD_TESTING=OFF \
-DPARAVIEW_USE_MPI=YES \
-DVTK_PYTHON_OPTIONAL_LINK=OFF \
-DVTK_MODULE_ENABLE_ParaView_Catalyst=YES \
-DVTK_MODULE_ENABLE_ParaView_PythonCatalyst=YES \
-DVTK_MODULE_ENABLE_VTK_FiltersParallel=YES \
-DVTK_MODULE_ENABLE_ParaView_VTKExtensionsExtraction=YES \
-DVTK_MODULE_ENABLE_ParaView_VTKExtensionsExtractionPython=YES \
-DVTK_MODULE_ENABLE_VTK_FiltersExtraction=YES \
-DPARAVIEW_USE_PYTHON=NO \
-DVTK_USE_X=NO \
-DVTK_RENDERING_BACKEND=OpenGL2 \
-DPARAVIEW_USE_QT=OFF \
-DEGL_LIBRARY=/usr/lib64/libEGL_nvidia.so.0 \
-DCMAKE_INSTALL_PREFIX=${INSTALL_DIR} \
../ParaView-v${VERSION} 2>&1 | tee $LOGFILE
```https://gitlab.kitware.com/paraview/paraview/-/issues/21061Paraview build fails in windows2021-11-06T08:36:56-04:00wl23321Paraview build fails in windowsI built the paraview step by step according to the method in the official website,and it showed error just as the same question mensioned in the official website,and it recommend to report the problem here.I will show the cmakeout.log an...I built the paraview step by step according to the method in the official website,and it showed error just as the same question mensioned in the official website,and it recommend to report the problem here.I will show the cmakeout.log and the error file here.I use the msvc 2017 instead of msvc2015,I think that will be ok,didn't it?
[CMakeError.log](/uploads/cae0bee0f5cdd757bab2b80a9cff1012/CMakeError.log)
[CMakeOutput.log](/uploads/8bc1464acd883b9383716a4c92903778/CMakeOutput.log)[erro_show_in_native_tool.txt](/uploads/2db09781d5c3cfc3fbb4a9188d266715/erro_show_in_native_tool.txt)https://gitlab.kitware.com/paraview/paraview/-/issues/21059Crash slice view2021-11-09T12:47:44-05:00W. Alan ScottCrash slice viewSlice View is crashing. Here is how to replicate:
* 5.10.0-RC1, Linux, builtin server.
* Open can.exo. Apply.
* Right click the view titlebar, convert to slice view.
* Create a slice at X=0, Y=0 and Z=0.
* Turn on the eyeball.
Crash....Slice View is crashing. Here is how to replicate:
* 5.10.0-RC1, Linux, builtin server.
* Open can.exo. Apply.
* Right click the view titlebar, convert to slice view.
* Create a slice at X=0, Y=0 and Z=0.
* Turn on the eyeball.
Crash.
@cory.quammen @utkarsh.ayachit5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21057IOSS Writer: Exodus2023-06-08T10:34:20-04:00Utkarsh AyachitIOSS Writer: ExodusThis issue documents requirements for the new IOSS writer to generate Exodus datasets. Our objective is to ensure that if someone opened an Exodus file and saved it out again as Exodus via this new writer, the input and output files shou...This issue documents requirements for the new IOSS writer to generate Exodus datasets. Our objective is to ensure that if someone opened an Exodus file and saved it out again as Exodus via this new writer, the input and output files should largely be identical. The difficulty arises from the fact that any data operations in ParaView may make that difficult. Here we document some challenges and then potential solutions.
* File-per-rank: initially, we follow the file-per-rank approach. IOSS is not MPI-aware in VTK/ParaView yet and hence using this approach is the easiest.
* Consolidated node-block: with Exodus, there's only 1 node block. If global node ids are present, then it's easy. We can generate a global node-block with ease. However, if they are not present, we can't simply generate them since that may cause point-fields to be clobbered. In that case, we will create a single nodeblock with duplicated points.
* set-blocks: sets rely on global element/node ids together with special array called "element_side". If required arrays are present, they will be saved appropriately as sets. Otherwise, we simply treat them as element blocks.
* blocks with mixed element types: exodus blocks only have 1 element type. However, vtkUnstructuredGrid supports mixed elements. To handle that case, the writer will have to globally determine if its necessary to split an element-block into multiple. Note, since blocknames need to be unique, we'll need to come up with some strategy when splitting a block.5.12 (Winter 2023)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21056StreamTracer crashes when source is distributed2021-11-15T20:49:41-05:00Timothee ChabatStreamTracer crashes when source is distributedIf source is ditributed and big enough, stream tracer crashes.
Steps to reproduce :
- connect to a server launched with at least 2 MPI ranks
- `Wavelet`, Apply
- `Random Vectors`, Apply
- Open a big enough distributed dataset (~ 20...If source is ditributed and big enough, stream tracer crashes.
Steps to reproduce :
- connect to a server launched with at least 2 MPI ranks
- `Wavelet`, Apply
- `Random Vectors`, Apply
- Open a big enough distributed dataset (~ 2000 cells and points)
- `StreamTracer with Custom Source`, input is Random Vectors, seed source is the dataset, Apply
- ParaView crasheshttps://gitlab.kitware.com/paraview/paraview/-/issues/21055MaterialEditor makes ParaView-5.10.0-RC1 crash when setting colors on Mac2023-09-14T03:14:47-04:00Estelle DirandMaterialEditor makes ParaView-5.10.0-RC1 crash when setting colors on MacWhen using the MaterialEditor of ParaView-5.10.0-RC1 on Mac (Big Sur 11.5.2), ParaView crashes when double clicking on the color value of baseColor/attenuationColor or other parameters that ask a color RGB value.
Instead of showing the ...When using the MaterialEditor of ParaView-5.10.0-RC1 on Mac (Big Sur 11.5.2), ParaView crashes when double clicking on the color value of baseColor/attenuationColor or other parameters that ask a color RGB value.
Instead of showing the Select Color window, ParaView crashes with the following trace.
Setting other types of parameters works fine.
To reproduce it, just create a new material on the MaterialEditor, with a principled base for instance, choose the baseColor parameter and double click on the RGB value.
```
---------
Loguru caught a signal: SIGABRT
Stack trace:
57 0x7fff20405f3d start + 1
56 0x1086bbd61 main + 497
55 0x10a01a042 QCoreApplication::exec() + 130
54 0x10a015acf QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 431
53 0x12c72962f QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2495
52 0x7fff22cd9c69 -[NSApplication run] + 586
51 0x7fff22ce7945 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1364
50 0x7fff22ce9172 _DPSNextEvent + 864
49 0x7fff28727583 _BlockUntilNextEventMatchingListInModeWithFilter + 70
48 0x7fff287276b6 ReceiveNextEventCommon + 284
47 0x7fff28727a83 RunCurrentEventLoopInMode + 292
46 0x7fff204e161c CFRunLoopRunSpecific + 563
45 0x7fff204e205c __CFRunLoopRun + 893
44 0x7fff204e3634 __CFRunLoopDoSources0 + 242
43 0x7fff204e38b4 __CFRunLoopDoSource0 + 180
42 0x7fff204e394c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
41 0x12c72a9c8 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 40
40 0x12c72a260 QCocoaEventDispatcherPrivate::processPostedEvents() + 320
39 0x10979ed7b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 219
38 0x1097b9e2e QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 3534
37 0x10a019a34 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
36 0x108a99e11 QApplication::notify(QObject*, QEvent*) + 497
35 0x108a989ea QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266
34 0x108af06e9 QWidgetWindow::event(QEvent*) + 233
33 0x108af2022 QWidgetWindow::handleMouseEvent(QMouseEvent*) + 3266
32 0x108a99310 QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 896
31 0x10a019a34 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
30 0x108a9b755 QApplication::notify(QObject*, QEvent*) + 6965
29 0x108a989ea QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266
28 0x108c7e40f QToolButton::event(QEvent*) + 319
27 0x108ad2dfd QWidget::event(QEvent*) + 445
26 0x108c7dc4f QToolButton::mouseReleaseEvent(QMouseEvent*) + 15
25 0x108b8320f QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 271
24 0x108b82059 QAbstractButtonPrivate::click() + 233
23 0x108b821df QAbstractButtonPrivate::emitClicked() + 111
22 0x10a04d0d5 void doActivate<false>(QObject*, int, void**) + 1477
21 0x1096dbc35 pqColorChooserButton::chooseColor() + 117
20 0x108c92afc QColorDialog::getColor(QColor const&, QWidget*, QString const&, QFlags<QColorDialog::ColorDialogOption>) + 460
19 0x108c98da9 QDialog::exec() + 281
18 0x12c75e7ee QCocoaColorDialogHelper::exec() + 30
17 0x12c75e3b6 -[QNSColorPanelDelegate runApplicationModalPanel] + 86
16 0x10a019f27 QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 39
15 0x12c729591 QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2337
14 0x12c72a259 QCocoaEventDispatcherPrivate::processPostedEvents() + 313
13 0x10a01ad79 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 809
12 0x10a019a34 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
11 0x108a99e11 QApplication::notify(QObject*, QEvent*) + 497
10 0x108a989ea QApplicationPrivate::notify_helper(QObject*, QEvent*) + 266
9 0x108c7e40f QToolButton::event(QEvent*) + 319
8 0x108ad3e9a QWidget::event(QEvent*) + 4698
7 0x10a04488e QObject::event(QEvent*) + 158
6 0x1096d009e pqColorChooserButton::~pqColorChooserButton() + 14
5 0x108ac1cae QWidget::~QWidget() + 1006
4 0x10a044164 QObjectPrivate::deleteChildren() + 228
3 0x7fff202222aa malloc_report + 151
2 0x7fff2021f165 has_default_zone0 + 0
1 0x7fff2033f406 abort + 125
0 0x7fff20404c26 dyld_stub_binder + 282
( 46.460s) [paraview ] :0 FATL| Signal: SIGABRT
Abort trap: 6
```https://gitlab.kitware.com/paraview/paraview/-/issues/21054Parametric Surfaces plugin - some updates needed2021-11-10T19:48:42-05:00Andrew MacleanParametric Surfaces plugin - some updates neededSome minor changes are needed here, namely:
- It is there as a plugin but not enabled by default.
- Could you please add a checkbox for `Generate Texture Coordinates` as in the original xml file? My feeling is to leave this checked becau...Some minor changes are needed here, namely:
- It is there as a plugin but not enabled by default.
- Could you please add a checkbox for `Generate Texture Coordinates` as in the original xml file? My feeling is to leave this checked because if people use PBR they will automatically need it. If this is enabled, the parametric surfaces will automatically build the texture coordinates.
- The `Clockwise Ordering` checkbox should be unchecked.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21052v5.10-RC1 SPH Interpolator GUI needs rework2022-05-16T14:07:00-04:00Jean M. Favrev5.10-RC1 SPH Interpolator GUI needs reworkas discussed in https://discourse.paraview.org/t/sphvolumeinterpolator-with-cutoff-array/3119, the GUI panel for Array Selections lets the user select a Cut-off Array from a list of PointData arrays available in the source point cloud. T...as discussed in https://discourse.paraview.org/t/sphvolumeinterpolator-with-cutoff-array/3119, the GUI panel for Array Selections lets the user select a Cut-off Array from a list of PointData arrays available in the source point cloud. This is wrong, since the Cutt-off array should be taken from the input point data. As such, the definition of the probes (Line, Plane, volume) does not enable the definition of a Cutt-off array.
An alternative would be to use the SPHDatasetInterpolator, with an added probe (e.g Plane) defined elsewhere, with its own Cutoff array. This does not work either, the GUI marks the array as "Cutoff (?)". pvbatch also fails. Here is an attached Python script to demonstrate the use of an SPHPlaneInterpolator vs. an SPHDatasetInterpolator.
[pvSimpleTestSPHInterpolator.v510.py](/uploads/e2d0db4575bf7e16fc5c0861d4ab741b/pvSimpleTestSPHInterpolator.v510.py)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21050Change Python Script Editor "Scripts > Use as current script..." Menu Item Label2022-05-19T16:23:49-04:00Theodore BaltisChange Python Script Editor "Scripts > Use as current script..." Menu Item LabelCurrent wording might imply to some that the selected script is to be executed
Change to something more explicit like "Load into current tab..."
Idea initially supported by @mwestphal on discourse: [https://discourse.paraview.org/t/par...Current wording might imply to some that the selected script is to be executed
Change to something more explicit like "Load into current tab..."
Idea initially supported by @mwestphal on discourse: [https://discourse.paraview.org/t/paraview-python-script-editor/8224/4](https://discourse.paraview.org/t/paraview-python-script-editor/8224/4)https://gitlab.kitware.com/paraview/paraview/-/issues/21048VelodyneAMRReader Crashes in 5.10.0-RC12021-12-22T15:17:00-05:00Theodore BaltisVelodyneAMRReader Crashes in 5.10.0-RC1VelodyneAMRReader crashes with "SegmentationFault" upon loading a file with the associated format (.xamr)
The attached file opens without issue in 5.9
[velodyne_amr.00004.xamr](/uploads/2ae25fa005d27dd10be0ec39df3b9030/velodyne_amr.000...VelodyneAMRReader crashes with "SegmentationFault" upon loading a file with the associated format (.xamr)
The attached file opens without issue in 5.9
[velodyne_amr.00004.xamr](/uploads/2ae25fa005d27dd10be0ec39df3b9030/velodyne_amr.00004.xamr)
@aandreyev5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/21046Play backwards button2022-04-14T14:49:55-04:00Boonthanome NouanesengsyPlay backwards buttonIt would be nice to have a button that acts like the Play button, but goes backwards in time instead of forwards. I understand there are ways to do this, like using the `Temporal Shift Scale` filter, but a button in the same location as ...It would be nice to have a button that acts like the Play button, but goes backwards in time instead of forwards. I understand there are ways to do this, like using the `Temporal Shift Scale` filter, but a button in the same location as the other VCR buttons would be nice.
@patchett2002 @cory.quammen @utkarsh.ayachitJaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21045vtkSMDataTypeDomain no longer supports custom VTK objects (v5.10.0)2021-10-26T04:57:21-04:00Lutz HofmannvtkSMDataTypeDomain no longer supports custom VTK objects (v5.10.0)In ParaView v5.9.1 and earlier, it was possible to provide custom VTK objects through a plugin, and specify them as DataType in a DataTypeDomain of an InputProperty.
By a recent change (tested with ParaView v5.10.0-RC1), vtkSMDataTypeDo...In ParaView v5.9.1 and earlier, it was possible to provide custom VTK objects through a plugin, and specify them as DataType in a DataTypeDomain of an InputProperty.
By a recent change (tested with ParaView v5.10.0-RC1), vtkSMDataTypeDomain only accepts types that are known to `vtkDataObjectTypes`. This means that the only way to specify filters that require custom VTK objects as inputs is to provide an empty DataTypeDomain, which matches every data type including the custom VTK objects.
This makes it also no longer possible to use subclasses of known types in the ParaView pipeline. For example, in v5.9.1 it was possible to subclass vtkPolyData to attach a custom data structure, but still use most filters and representations that work with vtkPolyData on the custom data object.
**Minimal example**: [paraview-custom-objects.zip](/uploads/edfa5d3f76f60dc1ac28350c3f87c12e/paraview-custom-objects.zip)
* A subclass vtkMyObject of vtkPolyData is defined (an instance is created by MySource)
* MyAlgorithm takes vtkMyObject as input and outputs down-cast vtkPolyData
* MyTransformer casts vtkPolyData to vtkMyObject
**ParaView 5.9.1**
* the pipeline `Box -> MyTransformer -> Python Calculator -> MyAlgorithm` is valid and the underlying poly data of MyTransformer can be displayed by a Surface Representation
**ParaView 5.10.0-RC1**
* MyAlgorithm can be applied to anything in the pipeline
* vtkMyObject cannot be used by filters or representation that would take vtkPolyData (e.g. pipeline `Box -> MyTransformer`)
* prints `vtkSMDataTypeDomain.cxx:242 ERR| vtkSMDataTypeDomain (0x55a9f27ff1f0): 'vtkMyObject' not a known data object type!` when parsing the plugin XMLhttps://gitlab.kitware.com/paraview/paraview/-/issues/21044Error reading large VTK files in the Windows version2023-06-28T03:03:03-04:00vmajorError reading large VTK files in the Windows versionI have large (3.5 Gb+) VTK files generated by our CFD software running on Ubuntu (WSL2 in Windows 11 in fact).
Paraview 5.10.0-RC1 running on Ubuntu WSL2 opens the file correctly, albeit the Nvidia virtualised driver tends to crash so I...I have large (3.5 Gb+) VTK files generated by our CFD software running on Ubuntu (WSL2 in Windows 11 in fact).
Paraview 5.10.0-RC1 running on Ubuntu WSL2 opens the file correctly, albeit the Nvidia virtualised driver tends to crash so I cannot actually use this method. Previously using previous versions of Paraview I successfully worked with the results files in native Ubuntu. The point is that our results files are not corrupted or faulty.
Paraview 5.10.0-RC1 running on Windows 11 while opening the same files reports the errors previously reported by others in other threads on the Paraview support forum and seems related to the issue #16019:
```
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XMLParser\vtkXMLDataParser.cxx, line 655
vtkXMLDataParser (0000021A1A785910): Error reading uncompressed binary data header. Read 0 of 4 bytes.
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLStructuredDataReader.cxx, line 345
vtkXMLImageDataReader (0000021A067EEAB0): Error reading extent 1 597 1 309 1 285 from piece 0
ERROR: In C:\glr\builds\paraview\paraview-ci\build\superbuild\paraview\src\VTK\IO\XML\vtkXMLDataReader.cxx, line 410
vtkXMLImageDataReader (0000021A067EEAB0): Cannot read point data array "vorticityNorm" from PointData in piece 0. The data array in the element may be too short.
```
Summary of the issue:
- Linux ParaView is on ext4.
- Our native Linux CFD solver is on ext4 and the results directory is on ext4.
- Linux software and partitions are running and mounted under WSL2 on Windows 11.
- Windows ParaView is on an ntfs partition on the same Windows 11 machine that is running WSL2
- Linux ParaView can read and visualize the results data. Windows ParaView cannot read and visualize the results data.
Windows ParaView throws up errors with the large domain file (the 3.5 Gb one) when I try to read it from the ext4, or when I copy this file to an ntfs partition. Both files show the same error reading the file and the result cannot be visualized.
Windows ParaView can read the smaller 162 Mb file both from ext4 and the ntfs partitions.
Here is the download link for the 3.5 Gb file (zipped to 2.48Gb): https://velocite-public.s3.fr-par.scw.cloud/domain_00010000.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=SCW4RPBSRG82A0JQQSTB%2F20211019%2Ffr-par%2Fs3%2Faws4_request&X-Amz-Date=20211019T054859Z&X-Amz-Expires=3596&X-Amz-Signature=f9ed586080046ca85380cfe70218dc5c1df575efba945601c56462b31814dd4d&X-Amz-SignedHeaders=hosthttps://gitlab.kitware.com/paraview/paraview/-/issues/21042Allow multiple filters to be deleted at the same time2023-02-28T11:10:55-05:00W. Alan ScottAllow multiple filters to be deleted at the same timePlease add the ability to delete numerous filters from the pipeline at a time. This should be enabled in the Pipeline Browser, right click. Maybe use "delete filter tree" or somesuch.
Here is an example pipeline that shows the problem...Please add the ability to delete numerous filters from the pipeline at a time. This should be enabled in the Pipeline Browser, right click. Maybe use "delete filter tree" or somesuch.
Here is an example pipeline that shows the problem. Lets say a user wants to delete v4, then add a new dataset and filters.
![E862B30A](/uploads/3d8dab4a60e29928f17ed570fdb16ec7/E862B30A.PNG)5.12 (Winter 2023)Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/21041Eyeball doesn't show properly mixing GUI and Python commands2022-10-12T12:42:35-04:00W. Alan ScottEyeball doesn't show properly mixing GUI and Python commandsWe seem to have an issue showing the hidden eyeball when running python commands against a datset read with the ParaView GUI. Here is how to replicate:
* 5.10.0-RC1, builtin server, MacOS
* Open can.exo. Apply.
* View/ Python Shell.
* ...We seem to have an issue showing the hidden eyeball when running python commands against a datset read with the ParaView GUI. Here is how to replicate:
* 5.10.0-RC1, builtin server, MacOS
* Open can.exo. Apply.
* View/ Python Shell.
* Type: clip=Clip()
The eyeball won't show on the clip. It should show, grayed out.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21040Make nightlies sort by date2021-10-18T13:49:57-04:00W. Alan ScottMake nightlies sort by dateSomehow, please make the nightlies on paraview.org/downloads sort by date. Many people, including me, have been confused by the funny sort order (effectively by release then git sha).Somehow, please make the nightlies on paraview.org/downloads sort by date. Many people, including me, have been confused by the funny sort order (effectively by release then git sha).https://gitlab.kitware.com/paraview/paraview/-/issues/21039OK doesn't work for opening multifile datasets.2021-11-09T14:35:33-05:00W. Alan ScottOK doesn't work for opening multifile datasets.The OK is not enabled for opening multiple file datasets. Here are the details:
* Master Oct 13 (v5.10.0-RC1-120-g110d43f265), Linux, Alan Built using Superbuild, builtin server. (I believe this has to be one of your builds, not a nig...The OK is not enabled for opening multiple file datasets. Here are the details:
* Master Oct 13 (v5.10.0-RC1-120-g110d43f265), Linux, Alan Built using Superbuild, builtin server. (I believe this has to be one of your builds, not a nightly…)
* Try to open a multifile Exodus dataset. An example is g1s1.e.16. Another example is can.e.4.* The OK button stays grayed out. If you then say show me All Files (*), then you can click on OK, and it asks what you want to read with. If you choose IOSS, this reader works fine.
I tried a Mac nightly and Linux nightly from today, and they work correctly. I tried 5.10.0-RC1, and it is good.
As this is in master, not RC1, I am marking as Required, but putting it off for 5.11. it needs to be fixed Really Soon, however.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/21035Too many Slice filters in ParaView2022-07-27T12:13:25-04:00Mathieu Westphal (Kitware)Too many Slice filters in ParaViewThere is too many slice filters in ParaView:
* Slice
* Slice (Demand Driven Composite) (non fonctionnal?)
* Slice AMR Data
* Slice Along Polyline
* Slice Generic Data
* Slice with plane
* AMR Cut Plane
Most of these should be put into...There is too many slice filters in ParaView:
* Slice
* Slice (Demand Driven Composite) (non fonctionnal?)
* Slice AMR Data
* Slice Along Polyline
* Slice Generic Data
* Slice with plane
* AMR Cut Plane
Most of these should be put into the first Slice filter similar to the HTG integration, SliceWithPlane should also be integrated, see here: #21033Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21033Use SMP accelerated Slice in ParaView2022-08-09T11:29:00-04:00Mathieu Westphal (Kitware)Use SMP accelerated Slice in ParaViewDefault Slice filter should use SMP accelerated contour in ParaView when possible.
Current status:
- HTG && plane && axis aligned : uses vtkHyperTreeGridAxisCut (Non-SMP)
- HTG && plane : uses vtkHyperTreeGridPlaneCutter (Non-SMP)
- UG ...Default Slice filter should use SMP accelerated contour in ParaView when possible.
Current status:
- HTG && plane && axis aligned : uses vtkHyperTreeGridAxisCut (Non-SMP)
- HTG && plane : uses vtkHyperTreeGridPlaneCutter (Non-SMP)
- UG && **complex conditions* : uses vtk3DLinearGridPlaneCutter (SMP)
- Image : uses vtkSynchronizedTemplatesCutter3D (Non-SMP)
- StructGrid: uses vtkGridSynchronizedTemplates3D (Non-SMP)
- RectGrid: uses vtkRectilinearSynchronizedTemplates (Non-SMP)
- Other: DataSetCutter() from vtkCutter (Non-SMP)
Should be used:
- HTG && plane && axis aligned : uses vtkHyperTreeGridAxisCut (Non-SMP)
- HTG && plane : uses vtkHyperTreeGridPlaneCutter (Non-SMP)
- **Plane && Any dataset type && conditions : vtkPVPlaneCutter + Merge into polydata** (SMP)
- NonPlane && UG && **complex conditions* : uses vtk3DLinearGridPlaneCutter (SMP)
- NonPlane && Image : uses vtkSynchronizedTemplatesCutter3D (Non-SMP)
- NonPlane && StructGrid: uses vtkGridSynchronizedTemplates3D (Non-SMP)
- NonPlane && RectGrid: uses vtkRectilinearSynchronizedTemplates (Non-SMP)
- Other: DataSetCutter() from vtkCutter (Non-SMP)
This make the SliceWithPlane filter irrelevant in ParaViewSpiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21032Replace `Extract Level` with `Extract Block` in the common filters2021-11-15T17:53:57-05:00Kenneth MorelandReplace `Extract Level` with `Extract Block` in the common filtersThe `Extract Level` filter (currently given the icon <img src="/uploads/e85795ce849854eb20c435ab9ce63d22/pqGroupExtract.svg" width="25px" />) should be removed from the common filters menu.
There are a couple of problems with this filte...The `Extract Level` filter (currently given the icon <img src="/uploads/e85795ce849854eb20c435ab9ce63d22/pqGroupExtract.svg" width="25px" />) should be removed from the common filters menu.
There are a couple of problems with this filter as is. First, the icon <img src="/uploads/e85795ce849854eb20c435ab9ce63d22/pqGroupExtract.svg" width="25px" /> clearly suggests that it should be able to invert the `Group Datasets` filter, which has the similar icon <img src="/uploads/0d3d8b30d992a3271943b10b24e32b1a/pqGroup.svg" width="25px" />. However, these filters cannot inverse each other. If you group some input with `Group Datasets`, the `Extract Level` filter is still grayed out. In fact, in over 15 years of using ParaView, I cannot recall a single dataset I had or generated that worked with this filter. I think it's safe to say that this is not a "common" filter.
The `Extract Level` filter should be replaced with the `Extract Block`. The `Extract Block` filter is much more general and able to pull blocks out of any multi-block data set. This makes it much more appropriate for the common filters toolbar. First, it is actually a common operation. Second, it can do the implied inversion of the `Group Datasets` filter.5.10 (Fall 2021)