ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:50-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21496AMReX plotfile of size 68GB or higher grid data shows nan/inf when visualizin...2024-03-07T20:23:50-05:00Revathi JambunathanAMReX plotfile of size 68GB or higher grid data shows nan/inf when visualizing with Paraview 5.10.0We are using Paraview 5.10.0 on the NERSC system to visualize our AMReX plotfile and we also notice the same issue on ALCF resources.
For AMReX plotfiles with grid data size of 68GB and higher, we see that the slice feature shows only ...We are using Paraview 5.10.0 on the NERSC system to visualize our AMReX plotfile and we also notice the same issue on ALCF resources.
For AMReX plotfiles with grid data size of 68GB and higher, we see that the slice feature shows only nan or inf or some really large value.
However, with other visualization tools, such as Visit, we were able to visualize these plotfiles and confirm that there are no NaNs.
This problem is seen for all grid data.
![Screenshot_from_2022-08-08_10-10-59](/uploads/47900600f112a204edf7aad8a2e82530/Screenshot_from_2022-08-08_10-10-59.png)
Notice especially the colorbar
![Screenshot_from_2022-08-08_10-11-32](/uploads/b4c81f58ee0f6951a8b24ceb116c3129/Screenshot_from_2022-08-08_10-11-32.png)
The same issue is also reproduced on a different problem set with 92GB grid data
![Screen_Shot_2022-08-09_at_10.02.22_AM](/uploads/f58350fe4c5dee80566017e814303b85/Screen_Shot_2022-08-09_at_10.02.22_AM.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21495Add ability to create file group in file browser2022-08-09T12:56:57-04:00Kenneth MorelandAdd ability to create file group in file browserThe ParaView file browser looks for files whose name matches a pattern and groups them together. When the group is opened in the file read dialog, the list of files in the group is sent to a single reader where it is interpreted as a tim...The ParaView file browser looks for files whose name matches a pattern and groups them together. When the group is opened in the file read dialog, the list of files in the group is sent to a single reader where it is interpreted as a time series (or other convention based on the reader).
The file browser grouping usually identifies groups of files, but may fail if the pattern is unexpected. In that case, it is impossible to open the collection of files as a group. If you attempt to select them all and open them, ParaView creates a separate pipeline object for each.
There should be a way to select a collection of files and create a custom group out of them so that the group can be loaded into a single reader.
See https://discourse.paraview.org/t/reading-time-series-where-file-name-is-just-number/10105/4 for a discussion on this subject.https://gitlab.kitware.com/paraview/paraview/-/issues/21493PythonAlgorithm plugins: properties are sorted by command attribute2023-03-23T14:21:44-04:00Cory Quammencory.quammen@kitware.comPythonAlgorithm plugins: properties are sorted by command attributeIn the example PythonAlgorithm plugin `Examples/Plugins/PythonAlgorithm/PythonAlgorithmExamples.py`, the properties are sorted by the `command` attribute, which is rather arbitrary and does not offer any control over the ordering of UI e...In the example PythonAlgorithm plugin `Examples/Plugins/PythonAlgorithm/PythonAlgorithmExamples.py`, the properties are sorted by the `command` attribute, which is rather arbitrary and does not offer any control over the ordering of UI elements in the interface. For example, the properties `PythonSuperquadricSource` have this order:
`['GetStrings', 'GetValueRange', 'SetCenter', 'SetPhiResolution', 'SetScale', 'SetString', 'SetThetaResolution', 'SetThickness', 'SetValue']`
which isn't terribly useful, i.e., you can't hack the order by changing the property name, for instance.
Instead, we shoul have an `order` attribute that can be passed to the `smproperty` decorators or something similar to specify how they are ordered in the generated XML.
A possible workaround is to use property groups.Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/21490Files in series named only with numbers are not recognized as a group.2022-08-08T14:51:17-04:00Cory Quammencory.quammen@kitware.comFiles in series named only with numbers are not recognized as a group.From https://discourse.paraview.org/t/reading-time-series-where-file-name-is-just-number/10105/2
```
I’m looking at some older scivis contest data, and the data contains many file time series with files named like 000.vtu, 001.vtu, 002....From https://discourse.paraview.org/t/reading-time-series-where-file-name-is-just-number/10105/2
```
I’m looking at some older scivis contest data, and the data contains many file time series with files named like 000.vtu, 001.vtu, 002.vtu, 003.vtu,…
I expected the ParaView file browser to recognize these files as a series and group them together so that I could load the group and play them as a time series. But I was surprised to find that ParaView does not group files like this. Apparently, if the file is only a number, it will not be grouped.
```
This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/21486Extract Cells By Region should convert voxels to hexahedra2022-07-29T11:47:05-04:00Kenneth MorelandExtract Cells By Region should convert voxels to hexahedraWhen you run `Extract Cells By Region` on a structured type of data (image, rectilinear, curvilinear), it converts the data to an unstructured data. However, it should also convert the cell type to a hexahedron, which has a different poi...When you run `Extract Cells By Region` on a structured type of data (image, rectilinear, curvilinear), it converts the data to an unstructured data. However, it should also convert the cell type to a hexahedron, which has a different point ordering than a voxel. The following replicates the problem.
1. Create a `Wavelet` source. Apply.
2. Add the `Extract Cells By Region` filter. Apply.
3. Create a new `SpreadSheet` view.
4. View the result of `Extract Cells By Region` in the spreadsheet view.
5. Change the `Attribute` to `Cell Data`.
6. Note that the `Cell Type` column shows `Voxel` type for all cells.
Having `Voxel` cells in unstructured data should be avoided because it can lead to problems with some filters that do not handle the order of the points correctly. (See for example #15982 and #21485).https://gitlab.kitware.com/paraview/paraview/-/issues/21485Resample To Image does not work with unstructured grids with voxel cells2022-07-29T16:11:47-04:00Kenneth MorelandResample To Image does not work with unstructured grids with voxel cellsThe `Resample To Image` filter does not work correctly if it is given an unstructured grid with voxel cells as input. To replicate, try the following:
1. Open this file: [ugrid-voxel-cells.vtk](/uploads/a25bbe2403b245f394e82c431b161594/...The `Resample To Image` filter does not work correctly if it is given an unstructured grid with voxel cells as input. To replicate, try the following:
1. Open this file: [ugrid-voxel-cells.vtk](/uploads/a25bbe2403b245f394e82c431b161594/ugrid-voxel-cells.vtk)
2. Add the `Resample To Image`. Apply.
3. Try changing the representation to `Surface` or `Volume`. Nothing is rendered.
The problem is that `Resample To Image` is not correctly locating voxel cells. The resulting "sampled" image identifies all cells as the `HIDDENCELL` attribute in `vtkGhostType`.
This is likely related to #15982.https://gitlab.kitware.com/paraview/paraview/-/issues/21484CI: ColorOpacityTableEditing test is flaky2022-10-07T01:31:45-04:00Mathieu Westphal (Kitware)CI: ColorOpacityTableEditing test is flakyVery occasionnaly, the ColorOpacityTableEditing fails with a SIGSEV:
```
vtkSMTestDriver: client command is:
"/builds/gitlab-kitware-sciviz-ci/build/bin/paraview" "--enable-bt" "--test-script=/builds/gitlab-kitware-sciviz-ci/Clients/Pa...Very occasionnaly, the ColorOpacityTableEditing fails with a SIGSEV:
```
vtkSMTestDriver: client command is:
"/builds/gitlab-kitware-sciviz-ci/build/bin/paraview" "--enable-bt" "--test-script=/builds/gitlab-kitware-sciviz-ci/Clients/ParaView/Testing/XML/ColorOpacityTableEditing.xml" "--test-directory=/builds/gitlab-kitware-sciviz-ci/build/Testing/Temporary" "--test-baseline=/builds/gitlab-kitware-sciviz-ci/build/ExternalData/Clients/ParaView/Testing/Data/Baseline/ColorOpacityTableEditing.png" "--data-directory=/builds/gitlab-kitware-sciviz-ci/build/ExternalData" "--dr" "--exit"
vtkSMTestDriver: starting process client
-------------- client output --------------
hwloc/linux: Ignoring PCI device with non-16bit domain.
Pass --enable-32bits-pci-domain to configure to support such devices
(warning: it would break the library ABI, don't enable unless really needed).
Process started
vtkSMTestDriver: client successfully started.
Process started
Playing: /builds/gitlab-kitware-sciviz-ci/Clients/ParaView/Testing/XML/ColorOpacityTableEditing.xml
Loguru caught a signal: SIGSEGV
Stack trace:
33 0x407dc5 /builds/gitlab-kitware-sciviz-ci/build/bin/paraview() [0x407dc5]
32 0x7f938637e4f0 __libc_start_main + 128
31 0x7f938637e440 /lib64/libc.so.6(+0x40440) [0x7f938637e440]
30 0x40f540 /builds/gitlab-kitware-sciviz-ci/build/bin/paraview() [0x40f540]
29 0x7f93844e9b34 QCoreApplication::exec() + 148
28 0x7f93844e15f2 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 306
27 0x7f9384533f88 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 104
26 0x7f93724c78a3 g_main_context_iteration + 51
25 0x7f937251f308 /lib64/libglib-2.0.so.0(+0xaa308) [0x7f937251f308]
24 0x7f93724ca0af g_main_context_dispatch + 415
23 0x7f9384533bc4 /lib64/libQt5Core.so.5(+0x2f7bc4) [0x7f9384533bc4]
22 0x7f9384533283 QTimerInfoList::activateTimers() + 1059
21 0x7f93844e2be8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 296
20 0x7f938594b443 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 131
19 0x7f938450d2cf QObject::event(QEvent*) + 447
18 0x7f93841f0f9b pqTimer::timerEvent(QTimerEvent*) + 35
17 0x7f9384519a7e QTimer::timeout(QTimer::QPrivateSignal) + 62
16 0x7f9384516820 /lib64/libQt5Core.so.5(+0x2da820) [0x7f9384516820]
15 0x7f9385f7d840 /builds/gitlab-kitware-sciviz-ci/build/bin/../lib64/libpqApplicationComponents-pv5.10.so.1(+0xd2840) [0x7f9385f7d840]
14 0x7f9385ff552c pqCommandLineOptionsBehavior::processCommandLineOptions() + 128
13 0x7f9385ff6905 pqCommandLineOptionsBehavior::processTests() + 469
12 0x7f93841ebf74 pqTestUtility::playTests(QString const&) + 78
11 0x7f93841ec223 pqTestUtility::playTests(QStringList const&) + 635
10 0x7f93841d1d84 pqEventDispatcher::playEvents(pqEventSource&, pqEventPlayer&) + 496
9 0x7f93841d2480 pqEventDispatcher::playEvent(int) + 1418
8 0x7f93841d413e pqEventPlayer::playEvent(QString const&, QString const&, QString const&, int, bool&) + 1078
7 0x7f93841eb0b8 pqTableViewEventPlayer::playEvent(QObject*, QString const&, QString const&, int, bool&) + 130
6 0x7f93841c691b pqAbstractItemViewEventPlayerBase::playEvent(QObject*, QString const&, QString const&, int, bool&) + 1723
5 0x7f9385bc235f QAbstractItemView::setCurrentIndex(QModelIndex const&) + 159
4 0x7f93844a3e0e QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) + 174
3 0x7f93844a27fe QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) + 62
2 0x7f9384516820 /lib64/libQt5Core.so.5(+0x2da820) [0x7f9384516820]
1 0x7f9385bc88ea QAbstractItemView::currentChanged(QModelIndex const&, QModelIndex const&) + 474
0 0x7f9386393350 /lib64/libc.so.6(+0x55350) [0x7f9386393350]
( 2.493s) [paraview ] :0 FATL| Signal: SIGSEGV
vtkSMTestDriver: client0 process exited with an exception: Segmentation fault
```
This is already a FORCE_SERIAL test.
I was not able to reproduce locally by just running the test by I was able to obtain the same sigsev stack by just showing another window on top of ParaView during the test:
```
3134: Loguru caught a signal: SIGSEGV
3134: Stack trace:
3134: 33 0x5572c70e8dd5 /home/glow/dev/paraview/pv1/build/bin/paraview(+0x8dd5) [0x5572c70e8dd5]
3134: 32 0x7f784b62934a __libc_start_main + 138
3134: 31 0x7f784b629290 /usr/lib/libc.so.6(+0x29290) [0x7f784b629290]
3134: 30 0x5572c70f001d /home/glow/dev/paraview/pv1/build/bin/paraview(+0x1001d) [0x5572c70f001d]
3134: 29 0x7f784928fda9 QCoreApplication::exec() + 153
3134: 28 0x7f784928527c QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 300
3134: 27 0x7f78492d732c QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 108
3134: 26 0x7f783d916392 g_main_context_iteration + 50
3134: 25 0x7f783d96f001 /usr/lib/libglib-2.0.so.0(+0xab001) [0x7f783d96f001]
3134: 24 0x7f783d918c6b g_main_context_dispatch + 411
3134: 23 0x7f78492d71b2 /usr/lib/libQt5Core.so.5(+0x2d71b2) [0x7f78492d71b2]
3134: 22 0x7f78492d6b73 QTimerInfoList::activateTimers() + 931
3134: 21 0x7f784928cad8 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 296
3134: 20 0x7f784a978b3c QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
3134: 19 0x7f78492b03e6 QObject::event(QEvent*) + 470
3134: 18 0x7f784afb6893 pqTimer::timerEvent(QTimerEvent*) + 35
3134: 17 0x7f78492bf6ff QTimer::timeout(QTimer::QPrivateSignal) + 63
3134: 16 0x7f78492bd378 /usr/lib/libQt5Core.so.5(+0x2bd378) [0x7f78492bd378]
3134: 15 0x7f784b0d24d4 /home/glow/dev/paraview/pv1/build/bin/../lib/libpqApplicationComponents-pv5.10.so.1(+0xd24d4) [0x7f784b0d24d4]
3134: 14 0x7f784b14eabe pqCommandLineOptionsBehavior::processCommandLineOptions() + 128
```
Running in gdb, I have the following backtrace:
```
(gdb) bt
#0 0x00007ffff71e76ac in QAbstractItemView::currentChanged(QModelIndex const&, QModelIndex const&) () from /usr/lib/libQt5Widgets.so.5
#1 0x00007ffff58bd378 in ?? () from /usr/lib/libQt5Core.so.5
#2 0x00007ffff58510ef in QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) () from /usr/lib/libQt5Core.so.5
#3 0x00007ffff58534b3 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/libQt5Core.so.5
#4 0x00007ffff71d918f in QAbstractItemView::setCurrentIndex(QModelIndex const&) ()
from /usr/lib/libQt5Widgets.so.5
#5 0x00007ffff7b8b09b in pqAbstractItemViewEventPlayerBase::playEvent (this=0x555555b940a0,
object=0x55555c2498e0, command=..., arguments=..., eventType=0,
error=@0x7fffffffdc2a: false)
at /home/glow/dev/paraview/pv1/src/ThirdParty/QtTesting/vtkqttesting/pqAbstractItemViewEventPlayerBase.cxx:239
#6 0x00007ffff7bb021c in pqTableViewEventPlayer::playEvent (this=0x555555b940a0,
object=0x55555c2498e0, command=..., arguments=..., eventType=0,
error=@0x7fffffffdc2a: false)
at /home/glow/dev/paraview/pv1/src/ThirdParty/QtTesting/vtkqttesting/pqTableViewEventPlayer.cxx:60
#7 0x00007ffff7b9920e in pqEventPlayer::playEvent (this=0x555555b9e718, objectString=...,
command=..., arguments=..., eventType=0, error=@0x7fffffffdcd0: false)
at /home/glow/dev/paraview/pv1/src/ThirdParty/QtTesting/vtkqttesting/pqEventPlayer.cxx:199
#8 0x00007ffff7b9737b in pqEventDispatcher::playEvent (this=0x555555b9e6d0, indent=0)
at /home/glow/dev/paraview/pv1/src/ThirdParty/QtTesting/vtkqttesting/pqEventDispatcher.cxx:352
```
Valgrind:
```
==60371== Invalid read of size 4
==60371== at 0x530870B: QAbstractItemView::currentChanged(QModelIndex const&, QModelIndex const&) (in /usr/lib/libQt5Widgets.so.5.15.5)
==60371== by 0x68BF377: void doActivate<false>(QObject*, int, void**) (qobject.cpp:3898)
==60371== by 0x68530EE: QItemSelectionModel::currentChanged(QModelIndex const&, QModelIndex const&) (moc_qitemselectionmodel.cpp:482)
==60371== by 0x68554B2: QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) (qitemselectionmodel.cpp:1416)
==60371== by 0x52FA18E: QAbstractItemView::setCurrentIndex(QModelIndex const&) (in /usr/lib/libQt5Widgets.so.5.15.5)
==60371== by 0x6B7A209: pqAbstractItemViewEventPlayerBase::playEvent(QObject*, QString const&, QString const&, int, bool&) (pqAbstractItemViewEventPlayerBase.cxx:242)
==60371== by 0x6B9F44D: pqTableViewEventPlayer::playEvent(QObject*, QString const&, QString const&, int, bool&) (pqTableViewEventPlayer.cxx:60)
==60371== by 0x6B8843F: pqEventPlayer::playEvent(QString const&, QString const&, QString const&, int, bool&) (pqEventPlayer.cxx:199)
==60371== by 0x6B865AC: pqEventDispatcher::playEvent(int) (pqEventDispatcher.cxx:352)
==60371== by 0x6B85E94: pqEventDispatcher::playEvents(pqEventSource&, pqEventPlayer&) (pqEventDispatcher.cxx:240)
==60371== by 0x6BA0655: pqTestUtility::playTests(QStringList const&) (pqTestUtility.cxx:274)
==60371== by 0x6BA03A2: pqTestUtility::playTests(QString const&) (pqTestUtility.cxx:238)
==60371== Address 0x2faf0e50 is 0 bytes inside a block of size 32 free'd
==60371== at 0x4848B5F: operator delete(void*, unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==60371== by 0x68405E7: UnknownInlinedFun (qabstractitemmodel.cpp:89)
==60371== by 0x68405E7: QPersistentModelIndex::operator=(QModelIndex const&) (qabstractitemmodel.cpp:258)
```
And it correspond to the following xml event:
```
<pqevent object="pqClientMainWindow/colorMapEditorDock/colorMapEditorPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/PropertiesFrame/Properties/ColorOpacityEditor/ColorTable" command="setCurrent" arguments="1.2" />
```
The next step would be to build Qt in debug to understand what is going on.https://gitlab.kitware.com/paraview/paraview/-/issues/21481Point Gaussian doesn't seem to be supported by the MultiBlock Inspector2022-07-27T05:43:14-04:00Lucas GivordPoint Gaussian doesn't seem to be supported by the MultiBlock InspectorAfter loading an multiblock, if we hide some blocks in the MultiBlock Inspector, we always visualize theses hidden block if the representation is set to Point Gaussian.
can.ex2 with the block_2 hidden in Point representation :
![image]...After loading an multiblock, if we hide some blocks in the MultiBlock Inspector, we always visualize theses hidden block if the representation is set to Point Gaussian.
can.ex2 with the block_2 hidden in Point representation :
![image](/uploads/8a89c8768af53aef164c37d1124fc140/image.png)
can.ex2 with the block_2 hidden in Point Gaussian representation :
![image](/uploads/9b5a68449e991efb95d54dd7d1bc4e06/image.png)
Step to reproduce :
- load can.ex2
- open MultiBlock Inspector
- hide block_2
- switch to Point Gaussian representation
Note that we also visualize hidden block in `3D Glyph`.https://gitlab.kitware.com/paraview/paraview/-/issues/21479synchronize time over multiple datasets2023-01-03T12:08:13-05:00Boonthanome Nouanesengsysynchronize time over multiple datasetsI have multiple datasets that I would like to compare at essentially the same simulation times. But each dataset has slightly different simulation times. Sometimes it’s more than slightly different. Is there some way to synchronize the d...I have multiple datasets that I would like to compare at essentially the same simulation times. But each dataset has slightly different simulation times. Sometimes it’s more than slightly different. Is there some way to synchronize the datasets together in time? I’d like to set one dataset as a “master time”, and have all the other datasets be synchronized to it.
I’m aware of the Synchronize Time filter, and that will mostly work, but sometimes the times are far enough apart that I’d like to have a new timestep be generated by interpolating between two timesteps. I do know that the Temporal Interpolator filter will interpolate between timesteps, but it doesn’t really do exactly what I want.
In summary, it would be nice to have a filter:
- accept multiple input datasets that are close together in time
- set one dataset to be the 'master' time that other datasets must sync in time to
- have a threshold
- if the time delta is smaller than the threshold, set the 'master' time as the time (like the Synchronize Time Filter)
- if the time delta is larger than the threshold, interpolate a new timestep (like the Temporal Interpolator Filter)
@patchett2002 @cory.quammen @yohann.bearzihttps://gitlab.kitware.com/paraview/paraview/-/issues/21478ParaView "hangs" when running remotely and using Stream Tracers with Custom S...2024-03-07T20:23:50-05:00Phil SmithParaView "hangs" when running remotely and using Stream Tracers with Custom SourceTested with Linux Remote server. To reproduce the problem:
Here is what I did:
Linux, remote server, master from May
Exodus reader
Open Can.ex2
Cell To Point
View: Select Points Through (rectangular selection of som...Tested with Linux Remote server. To reproduce the problem:
Here is what I did:
Linux, remote server, master from May
Exodus reader
Open Can.ex2
Cell To Point
View: Select Points Through (rectangular selection of some points on CellToPoint)
Extract Selection
Stream Tracer With Custom Source (Input: CellToPoint)
In the popup, pick Seed Source: ExtractSelection
Vectors – Vel
Interpolator Type – Interpolator with point locator
Check box Surface Streamlines
Apply
ParaView hangs
When done locally, on Linux and MacOS nightly, it will not "hang" and be unresponsive. It will just produce no output as expected.
-Phil5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21476Files on network drives lead to crash2022-07-21T15:44:26-04:00Johannes NeumannFiles on network drives lead to crashplatform: Windows 10
version: > 5.9.1
When I load a (XDMF) file from a Windows network drive, Paraview crashes and no message is written to the log with `-log` command line option. The same file can be opened from a local copy or with v...platform: Windows 10
version: > 5.9.1
When I load a (XDMF) file from a Windows network drive, Paraview crashes and no message is written to the log with `-log` command line option. The same file can be opened from a local copy or with version 5.9.1. Newer versions seem to crash.https://gitlab.kitware.com/paraview/paraview/-/issues/21475Crash attempting iso-contour on certain AMReX datasets2023-05-05T13:37:59-04:00Nicholas Brunhart-LupoCrash attempting iso-contour on certain AMReX datasetsHello,
We are experiencing an error/crash when trying to use the iso-contour filter for some datasets generated by AMR-wind. An example of the output is (hopefully) attached [here](/uploads/5472df65d0a1e1d19d3e86f83a5c63e8/error.txt). W...Hello,
We are experiencing an error/crash when trying to use the iso-contour filter for some datasets generated by AMR-wind. An example of the output is (hopefully) attached [here](/uploads/5472df65d0a1e1d19d3e86f83a5c63e8/error.txt). We've done a bit of testing to narrow things down a bit:
- Crash happens when trying to use certain isovalues on certain quantities (like .1 for q-criterion). Seems to be the more geometry generated, the greater chance of crash.
- Crash happens when using PVserver, regardless the number of MPI ranks ( >= 1)
- Does not happen with GUI-mode Paraview with no MPI
- All output files can be read by other tools (like the python YT package) parallel or not, and at all isovalues
- Seems to happen on our supported versions of Paraview; 5.9, 5.10.
- Doesn’t seem to be an out-of-memory issue. Memory usage seems to be just fine and below machine limits. Tried with a lot more MPI ranks across more nodes to be sure; still crashes.
- Seems to start happening from one tilmestep to the next; beginning sets iso-contour just fine, then the next (and all subsequent time steps) will end in a crash. Lends a bit more credence in some kind of geometry issue.
- Nothing significantly different between a working and non-working plt file on-disk structure
The filter chain we use for this case is very simple:
- Pltfile with just one quantity (q-criterion)
- Cell Data to Point Data filter
- Contour
When using these filters at a problematic isovalue, we get a bit of loading, and then the error log fills up; this is then followed by pvserver stalling out.
We're happy to provide an example dataset, though it is several hundred gigabytes in size, so there might be some difficulties there. Happy to provide more details, or run more tests to help figure this out.Corey Wetterer-Nelson (Kitware)Corey Wetterer-Nelson (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21474IOSSReader error causes ParaView to crash when opening certain exodus files2022-07-27T12:38:51-04:00JFihosyIOSSReader error causes ParaView to crash when opening certain exodus filesI’m trying to use ParaView version 5.10.1 to view exodus files created by the MOOSE finite element modelling software, but my application crashes when I try to open certain files. ParaView starts up fine and is able to load certain .e fi...I’m trying to use ParaView version 5.10.1 to view exodus files created by the MOOSE finite element modelling software, but my application crashes when I try to open certain files. ParaView starts up fine and is able to load certain .e files such as those I created during MOOSE’s tutorial: [runs_normally.e](/uploads/3a1e2ca249a98654d580633ceee4acfe/runs_normally.e)
I’ve been running larger simulations in MOOSE (.e files are typically ~50 MB) and ParaView immediately crashes when I try to open them with it. Here's an example of a much smaller .e file from the same code which ParaView still isn't able to run: [crash_example.e](/uploads/d07a74bd8311e5ebe1031194d5c96ffd/crash_example.e)
Apparently this issue is with the IOSSReader. Any help offered is greatly appreciated. Thanks.https://gitlab.kitware.com/paraview/paraview/-/issues/21471Manipulating ModelTransformMatrix on RenderView breaks GPU Based volume mode2024-02-21T15:08:07-05:00Scott WittenburgManipulating ModelTransformMatrix on RenderView breaks GPU Based volume mode## Description
When using `CAVEInteraction` plugin, if I configure vtkVRInteractorStyles that manipulate the `ModelTransformMatrix` property on the `RenderView` proxy, this can result in volume rendering errors. The problem only seems ...## Description
When using `CAVEInteraction` plugin, if I configure vtkVRInteractorStyles that manipulate the `ModelTransformMatrix` property on the `RenderView` proxy, this can result in volume rendering errors. The problem only seems to happen when using the "GPU Based" volume rendering mode.
## Reproducing
This problem can be reproduced simply using the GUI with the "Python Shell" view.
1. Add a `Wavelet` source and set the representation to `Volume`.
2. In the Python editor view, paste or type the following:
```
import math
theta = math.pi / 4
v = GetActiveView()
# For a 45 deg rotation about the y axis
rot_y_matrix = [math.cos(theta), 0, math.sin(theta), 0, 0, 1, 0, 0, -math.sin(theta), 0, math.cos(theta), 0, 0, 0, 0, 1]
v.SetPropertyWithName("ModelTransformMatrix", rot_y_matrix)
Render()
```
That produces the following image:
![volume_wrong](/uploads/e3dabc39c49d38eb4158ca34e3232fe2/volume_wrong.png)
Notice that if I change the "Volume Rendering Mode" from "Smart" to "Ray Cast Only", the problem goes away, like below:
![volume_correct](/uploads/9ccb0e98fdedd57e1d6ea77833f57cfe/volume_correct.png)
Changing the mode back to "Smart" or to "GPU Based" again produces the issue.
## Observations
This makes sense given that the gpu shader based volume mapper depends on the camera position (see [here](https://gitlab.kitware.com/vtk/vtk/-/blob/master/Rendering/VolumeOpenGL2/vtkOpenGLGPUVolumeRayCastMapper.cxx#L3664-3665)) which we circumvent by using the `ModelTransformMatrix`.
I would expect other things that depend on the camera position (e.g. clipping) to be affected when transformations include a translation are applied via the `ModelTransformMatrix` property on the `RenderView` proxy as well.
## System Information
```
$ uname -a
Linux 4.15.0-189-generic #200-Ubuntu SMP Wed Jun 22 19:53:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS"
$ nvidia-smi
Thu Jul 14 19:40:32 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 510.73.05 Driver Version: 510.73.05 CUDA Version: 11.6 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... Off | 00000000:04:00.0 On | N/A |
| 29% 48C P8 23W / 250W | 1247MiB / 11264MiB | 1% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 3230 G /usr/lib/xorg/Xorg 40MiB |
| 0 N/A N/A 3413 G /usr/bin/gnome-shell 119MiB |
| 0 N/A N/A 4316 G /usr/lib/xorg/Xorg 525MiB |
| 0 N/A N/A 4485 G /usr/bin/gnome-shell 73MiB |
| 0 N/A N/A 4927 G /usr/lib/firefox/firefox 157MiB |
| 0 N/A N/A 4937 G ...veSuggestionsOnlyOnDemand 145MiB |
| 0 N/A N/A 19112 G ...w/build_cave/bin/paraview 58MiB |
| 0 N/A N/A 31099 G ...RendererForSitePerProcess 120MiB |
+-----------------------------------------------------------------------------+
```https://gitlab.kitware.com/paraview/paraview/-/issues/21469Exodus file is loaded but showing empty2022-07-27T15:22:20-04:00Gabriele GranelloExodus file is loaded but showing empty [DICe_solution.e](/uploads/b11b28d6abf6713e9b17c56784c72d28/DICe_solution.e) Hey there, thanks for your great work with Paraview. When loading a .e file such as the one attached , it appears empty. The thing that is bizarre to me is t... [DICe_solution.e](/uploads/b11b28d6abf6713e9b17c56784c72d28/DICe_solution.e) Hey there, thanks for your great work with Paraview. When loading a .e file such as the one attached , it appears empty. The thing that is bizarre to me is that if I open and close a few times, it happens to be loaded correctly at some point.
I am currently using version 5.10.1 on Mac with intel chip. Am I doing perhaps something obviously wrong? Just using the command open... Thanks for helping,
Gabrielehttps://gitlab.kitware.com/paraview/paraview/-/issues/21467Ghost Cell Generator create ghost cells between blocks with a multiblock input2022-07-13T03:05:49-04:00Mathieu Westphal (Kitware)Ghost Cell Generator create ghost cells between blocks with a multiblock inputWhen using the GCG on a multiblock input, it will try to create ghost cells between blocks.
While this behavior may be wanted on some cases, it may not be in other cases.
Steps to reproduce:
- mpirun -np 2 ./bin/pvserver
- run paraview...When using the GCG on a multiblock input, it will try to create ghost cells between blocks.
While this behavior may be wanted on some cases, it may not be in other cases.
Steps to reproduce:
- mpirun -np 2 ./bin/pvserver
- run paraview, connect to server
- Unstructured Cell Types, Apply
- Transform, Translate Y : 10, Apply
- Select both sources, GroupDataSet, Apply
- GhostCellGenerator, Apply
- ExtractGhostCells, Apply : result is not expected:
![image](/uploads/4b9474646a6eca8ba1090aba7737c971/image.png)
Note: Using ConvertToPartitionedDataSet fix the issue:
![image](/uploads/00103a5d94826312c7fb4b08014f7894/image.png)
IMO a new property should be added, either to enable/disable this behavior of creating ghost cells, or even better, choose at which the block level to start creating ghost cellls.
FYI @nicolas.vuaille @yohann.bearzihttps://gitlab.kitware.com/paraview/paraview/-/issues/21466ParaView crashes when selecting "Use Window Location" for Text Source positio...2024-03-07T20:23:50-05:00Artem BodrinParaView crashes when selecting "Use Window Location" for Text Source position after a state loadIf Text Source was saved with "AnyLocation" property set, switching it to "Use Window Location" in Display dock after a state load crashes ParaView.
Affected versions: 5.9.1, 5.10.1
![paraview_crash](/uploads/5c1d683f2cdb7dee606b38128...If Text Source was saved with "AnyLocation" property set, switching it to "Use Window Location" in Display dock after a state load crashes ParaView.
Affected versions: 5.9.1, 5.10.1
![paraview_crash](/uploads/5c1d683f2cdb7dee606b38128ef23aa8/paraview_crash.mp4)
One of the possible solutions (no crash):
```c++
//-----------------------------------------------------------------------------
void pqTextLocationWidget::radioButtonLocationClicked()
{
auto button = this->Internals->Ui.buttonGroupLocation->checkedButton();
// --- there can be no checked button after a state loaded
if (!button)
{
button = this->Internals->Ui.toolButtonUL;
button->setChecked(true);
}
QString locationStr(button->property("location").toString());
this->setWindowLocation(locationStr);
}
```
The other one is to set a default checked button in UI file. Did not tested that.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21465Environment Lighting doesn't used the good Background Texture2022-09-03T01:47:01-04:00Lucas GivordEnvironment Lighting doesn't used the good Background Texturewhen we enable `Use environment lighting`, it seems that when you select another background texture and then reuse the first one, the background texture used remains the second one.
Step to reproduce :
- create a sphere
- disable light...when we enable `Use environment lighting`, it seems that when you select another background texture and then reuse the first one, the background texture used remains the second one.
Step to reproduce :
- create a sphere
- disable lightkit
- use pbr in lighting `interpolation`
- switch `Background Color Mode` to Skybox and select an hdr texture
- enable `Use Environment Lighting`
![render0](/uploads/81e07392c72f6457dc52d124e27d5870/render0.png)
- use another hdr texture
![render1](/uploads/aaa7a6b14dfb9f79814ec1dbbe676f02/render1.png)
- and now switch to the first hdr texture
![render2](/uploads/2b77a0726a9644e55ef22f4444b3397d/render2.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21463Filter Extract Time Steps does not save the extract displacement correctly ov...2024-03-07T20:23:50-05:00Phil SmithFilter Extract Time Steps does not save the extract displacement correctly over timeTo re-create the issue:
- File->Open can.ex2 Apply
- Filters->Alphabetical->Extract Time Steps
- Properties -- Selection Mode -- Select time range
- Time Step Range 22-43 Apply ---- Looks good so far
- File->Save Data
- Exodus II File t...To re-create the issue:
- File->Open can.ex2 Apply
- Filters->Alphabetical->Extract Time Steps
- Properties -- Selection Mode -- Select time range
- Time Step Range 22-43 Apply ---- Looks good so far
- File->Save Data
- Exodus II File type
- save in a convenient location and a file name of your choice
-
- Write all Arrays
- Write all Time Steps
-
- OK
-
- Reset Session
Open the file you just created and it is incorrect. It should look like the can that was saved.
-Phil5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21462CI: macOS arm64 test failure - UndoRedo12022-07-12T08:48:09-04:00Thomas GallandCI: macOS arm64 test failure - UndoRedo1XML test fail on this architecture only (Qt-related).
![image](/uploads/092e9371696d9fef32016be299567faa/image.png)
Same for `pv`, `pvcs` and `pvcrs`.
Consequence of this MR: https://gitlab.kitware.com/paraview/paraview/-/merge_reques...XML test fail on this architecture only (Qt-related).
![image](/uploads/092e9371696d9fef32016be299567faa/image.png)
Same for `pv`, `pvcs` and `pvcrs`.
Consequence of this MR: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5791