ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-24T08:09:47-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/20066Axis Rotation Lock when using Shift2021-03-24T08:09:47-04:00Mathieu Westphal (Kitware)Axis Rotation Lock when using ShiftThere is different Axis rotation mechanism in ParaView
Pressing Shift will lock the rotation in the front back axis when clicking and moving the mouse
Pressing [X|Y|Z] will lock the rotation in the [X|Y|Z] axis when clicking and moving ...There is different Axis rotation mechanism in ParaView
Pressing Shift will lock the rotation in the front back axis when clicking and moving the mouse
Pressing [X|Y|Z] will lock the rotation in the [X|Y|Z] axis when clicking and moving the mouse
However, the following input will lock the rotation and then can't be unlocked
* Press shift and click/mouve the mouse : front-back axis lock, expected
* Keep shift pressed and press X and click/mouve the mouse : front-back axis lock, expected I supose
* Keep X pressed and release shift : front-back axis lock, unexpected
* Release X : X Axis lock, **bug**.
* There is no way to unlock the view
@utkarsh.ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/20050ParaView 5.8.0 crashes if you close render view immediately after hitting app...2021-03-24T07:58:04-04:00chart3388ParaView 5.8.0 crashes if you close render view immediately after hitting apply buttonWas able to crash ParaView when rendering a new piece of geometry after hitting the apply button and then hitting the X on the render view.I used a larger piece of geometry (150MB OBJ) so it takes a few moments for it to import.
Step...Was able to crash ParaView when rendering a new piece of geometry after hitting the apply button and then hitting the X on the render view.I used a larger piece of geometry (150MB OBJ) so it takes a few moments for it to import.
Steps to reproduce:
Launch ParaView -> File -> Open -> Select File -> Properties -> Apply then immediately click X in Layout 1.
```
Loguru caught a signal: SIGSEGV
Stack trace:
53 0x407e29 /opt/paraview-5.8.0/bin/paraview() [0x407e29]
52 0x7ffb0b25e830 __libc_start_main + 240
51 0x40eb1d /opt/paraview-5.8.0/bin/paraview() [0x40eb1d]
50 0x7ffb06718d30 QCoreApplication::exec() + 128
49 0x7ffb067102ea QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 234
48 0x7ffb06768e3f QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 95
47 0x7ffaf80eb49c g_main_context_iteration + 44
46 0x7ffaf80eb3f0 /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4a3f0) [0x7ffaf80eb3f0]
45 0x7ffaf80eb197 g_main_context_dispatch + 679
44 0x7ffadca56cba /opt/Qt5.12.4/5.12.4/gcc_64/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0x6bcba) [0x7ffadca56cba]
43 0x7ffb06d6a76b QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 203
42 0x7ffb06d8d125 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 261
41 0x7ffb06d8b9c9 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1161
40 0x7ffb06d8bb73 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1587
39 0x7ffb06711a28 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 264
38 0x7ffb075eaaa0 QApplication::notify(QObject*, QEvent*) + 688
37 0x7ffb075e39ac QApplicationPrivate::notify_helper(QObject*, QEvent*) + 156
36 0x7ffb0763ddbb /opt/Qt5.12.4/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x1badbb) [0x7ffb0763ddbb]
35 0x7ffb0763b121 /opt/Qt5.12.4/5.12.4/gcc_64/lib/libQt5Widgets.so.5(+0x1b8121) [0x7ffb0763b121]
34 0x7ffb075e9fba QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) + 506
33 0x7ffb06711a28 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 264
32 0x7ffb075eb07f QApplication::notify(QObject*, QEvent*) + 2191
31 0x7ffb075e3985 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 117
30 0x7ffb067117bd QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 141
29 0x7ffb0a8e3c83 pqTabbedMultiViewWidget::eventFilter(QObject*, QEvent*) + 317
28 0x7ffb0a8e37af pqTabbedMultiViewWidget::closeTab(int) + 209
27 0x7ffb0a81c560 pqMultiViewWidget::destroyAllViews() + 260
26 0x7ffb0a0bcca6 pqObjectBuilder::destroy(pqView*) + 120
25 0x7ffb094cc760 vtkSMParaViewPipelineController::UnRegisterProxy(vtkSMProxy*) + 474
24 0x7ffb094ca07c vtkSMParaViewPipelineController::UnRegisterViewProxy(vtkSMProxy*, bool) + 1718
23 0x7ffb09540ff0 vtkSMSessionProxyManager::UnRegisterProxy(char const*, char const*, vtkSMProxy*) + 326
22 0x7ffb08756951 vtkObject::InvokeEvent(unsigned long, void*) + 61
21 0x7ffb0875642c /opt/paraview-5.8.0/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x80942c) [0x7ffb0875642c]
20 0x7ffb0856dcd9 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 67
19 0x7ffb09b06c1e /opt/paraview-5.8.0/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x5cc1e) [0x7ffb09b06c1e]
18 0x7ffb09b06c8f /opt/paraview-5.8.0/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x5cc8f) [0x7ffb09b06c8f]
17 0x7ffb09b1998c /opt/paraview-5.8.0/bin/../lib/libvtkGUISupportQt-pv5.8.so.1(+0x6f98c) [0x7ffb09b1998c]
16 0x7ffb0673d4e9 QMetaObject::activate(QObject*, int, int, void**) + 1625
15 0x7ffb0a14183d /opt/paraview-5.8.0/bin/../lib/libpqCore-pv5.8.so.1(+0x15d83d) [0x7ffb0a14183d]
14 0x7ffb0a1160cd pqServerManagerObserver::proxyUnRegistered(vtkObject*, unsigned long, void*, void*, vtkCommand*) + 263
13 0x7ffb0a141f60 pqServerManagerObserver::proxyUnRegistered(QString const&, QString const&, vtkSMProxy*) + 126
12 0x7ffb0673d4e9 QMetaObject::activate(QObject*, int, int, void**) + 1625
11 0x7ffb0a13f96e /opt/paraview-5.8.0/bin/../lib/libpqCore-pv5.8.so.1(+0x15b96e) [0x7ffb0a13f96e]
10 0x7ffb0a1119c2 pqServerManagerModel::onProxyUnRegistered(QString const&, QString const&, vtkSMProxy*) + 968
9 0x7ffb0a140bea pqServerManagerModel::proxyRemoved(pqProxy*) + 86
8 0x7ffb0673d4e9 QMetaObject::activate(QObject*, int, int, void**) + 1625
7 0x7ffb0a90b28a /opt/paraview-5.8.0/bin/../lib/libpqComponents-pv5.8.so.1(+0x30c28a) [0x7ffb0a90b28a]
6 0x7ffb0a81acda pqMultiViewWidget::proxyRemoved(pqProxy*) + 156
5 0x7ffb0352d494 vtkSMViewLayoutProxy::RemoveView(vtkSMViewProxy*) + 356
4 0x7ffb0352b5ab vtkSMViewLayoutProxy::UpdateState() + 1047
3 0x7ffb0334d18c /opt/paraview-5.8.0/bin/../lib/libvtkRemotingViews-pv5.8.so.1(+0x21118c) [0x7ffb0334d18c]
2 0x7ffb08756951 vtkObject::InvokeEvent(unsigned long, void*) + 61
1 0x7ffb08756292 /opt/paraview-5.8.0/bin/../lib/libvtkCommonCore-pv5.8.so.1(+0x809292) [0x7ffb08756292]
0 0x7ffb0b2734b0 /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7ffb0b2734b0]
( 72.172s) [paraview ] :0 FATL| Signal: SIGSEGV
```https://gitlab.kitware.com/paraview/paraview/-/issues/20026Unstructured grid volume rendering: volume disappears with "Bunyk ray cast" m...2021-03-24T08:08:58-04:00Cory Quammencory.quammen@kitware.comUnstructured grid volume rendering: volume disappears with "Bunyk ray cast" mapperThe volume often disappears when interacting with the view. Steps to reproduce:
* Run ParaView, built-in server
* Add **Unstructured Cell Types** source. Change the **Cell Type** to "Tet".
* Change representation to **Volume**
* Change ...The volume often disappears when interacting with the view. Steps to reproduce:
* Run ParaView, built-in server
* Add **Unstructured Cell Types** source. Change the **Cell Type** to "Tet".
* Change representation to **Volume**
* Change the **Select Mapper** to "Bunyk ray cast"
The volume will appear and disappear.https://gitlab.kitware.com/paraview/paraview/-/issues/20025Unstructured grid volume rendering: volume disappears with "Z sweep" mapper2021-03-24T07:50:04-04:00Cory Quammencory.quammen@kitware.comUnstructured grid volume rendering: volume disappears with "Z sweep" mapperThe volume often disappears when interacting with the view. Steps to reproduce:
* Run ParaView, built-in server
* Add **Unstructured Cell Types** source. Change the **Cell Type** to "Tet".
* Change representation to **Volume**
* Change ...The volume often disappears when interacting with the view. Steps to reproduce:
* Run ParaView, built-in server
* Add **Unstructured Cell Types** source. Change the **Cell Type** to "Tet".
* Change representation to **Volume**
* Change the **Select Mapper** to "Z sweep"
The volume will appear and disappear.https://gitlab.kitware.com/paraview/paraview/-/issues/20015vtkSMRrepresentedArrayListDomain duplicates array2021-03-24T07:50:52-04:00Paul LafoixvtkSMRrepresentedArrayListDomain duplicates array![bugDuplicationNone](/uploads/3a4f369749895d44b42853856a32a05c/bugDuplicationNone.gif)
After investigation, it seems that the vtkPVDataInformation returned in **vtkSMRepresentedArrayListDomain::GetExtraDataInformation()** contains wron...![bugDuplicationNone](/uploads/3a4f369749895d44b42853856a32a05c/bugDuplicationNone.gif)
After investigation, it seems that the vtkPVDataInformation returned in **vtkSMRepresentedArrayListDomain::GetExtraDataInformation()** contains wrong ArrayAttributeType (for example for Tangents, the attribute type can be -1 or 2 (normals)), whereas in the previous dataInformation, the ArrayAttributeType were well defined (8 for Tangents, 2 for Normals, and no -1). As the Array is now considered different, in **vtkSMArrayListDomain::Update()**, the resulting std::set is filled with duplicates :
`
vtkPVDataInformation* extraInfo = this->GetExtraDataInformation();
if (extraInfo)
{
this->ALDInternals->BuildArrayList(set, this, fieldDataSelection, iad, extraInfo);
}`
What I tried :
* In **vtkSMRepresentedArrayListDomain::GetExtraDataInformation()**, return null (this fixes the bug obviously but do not take care of parent proxy)
* Modify **vtkSMArrayListDomainArrayInformation::operator<()** to not take care of *this->ArrayAttributeType* for the ordering (as 2 elements a and b are different if !(a < b) && !(b < a)). Infortunately, the sorting will be impacted.
I guess we should resolve the problem in *GetExtraDataInformation*, but I can't figure out howhttps://gitlab.kitware.com/paraview/paraview/-/issues/20003Overlapping AMR and Slice representation2021-03-24T07:51:25-04:00Utkarsh AyachitOverlapping AMR and Slice representation* Open [plt.tar.gz](/uploads/2abc1b40b03625d05907bdb1c1a466f5/plt.tar.gz). Choose AMReX/BoxLib Grid Reader.
* Select all "Cell Arrays", Apply
* Now select "Slice" from the representation type selection combo-box in the toolbar. You'll g...* Open [plt.tar.gz](/uploads/2abc1b40b03625d05907bdb1c1a466f5/plt.tar.gz). Choose AMReX/BoxLib Grid Reader.
* Select all "Cell Arrays", Apply
* Now select "Slice" from the representation type selection combo-box in the toolbar. You'll get the following error:
```
ERROR: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx, line 154
vtkPVDataRepresentationPipeline (0x55c2c2bf5df0): Can not execute simple algorithm without output ports
```
This is a bug. Slice representation should work with Overlapping AMR datasets.https://gitlab.kitware.com/paraview/paraview/-/issues/19996Crash in RedistributeDataForOrderedCompositing when transparency is used.2021-03-24T07:53:14-04:00Charles GueunetCrash in RedistributeDataForOrderedCompositing when transparency is used.archive: [bugOrderCompos.tgz](/uploads/1f654407c68eca86a5a9e34cb74c06d1/bugOrderCompos.tgz)
# Description
I have a crash using **pvbatch**. Trying to save a screenshot of a contour computed
on a data set, shown with transparency, the e...archive: [bugOrderCompos.tgz](/uploads/1f654407c68eca86a5a9e34cb74c06d1/bugOrderCompos.tgz)
# Description
I have a crash using **pvbatch**. Trying to save a screenshot of a contour computed
on a data set, shown with transparency, the execution exit with:
```
terminate called after throwing an instance of 'std::runtime_error'
what(): -1 2.77602 2.79778
Loguru caught a signal: SIGABRT
```
The stacktrace include the following lines:
```
30 0x154b839eb2d6 vtkPVRenderView::StillRender() + 258
29 0x154b839ebb0e vtkPVRenderView::Render(bool, bool) + 1666
28 0x154b839f8692 vtkPVRenderViewDataDeliveryManager::RedistributeDataForOrderedCompositing(bool) + 1616
27 0x154b8082ca23 vtkDIYKdTreeUtilities::GenerateCuts(std::vector<vtkDataObject*> const&, int, bool, vtkMultiProcessController*, double const*) + 609
26 0x154b8082d469 vtkDIYKdTreeUtilities::GenerateCuts(std::vector<vtkSmartPointer<vtkPoints>, std::allocator<vtkSmartPointer<vtkPoints> > > const&, int, vtkMultiProcessController*, double const*) + 1627
25 0x154b8082f94d /home/charles/Software/install/paraview/bin/../lib/libvtkFiltersParallelDIY2-pv5.8.so.1(+0x2a94d) [0x154b8082f94d]
```
Here is the [full version](/uploads/4ccdd4afd474766eeefe995b9a872b2c/stacktrace)
From GDB, the last interesting context is on the following line:
**paraview/VTK/ThirdParty/diy2/vtkdiy2/include/vtkdiy2/detail/algorithms/kdtree.hpp**
```
380 if (loc < 0)
>381 throw std::runtime_error(fmt::format("{} {} {}", loc, x, link->core().min[dim]));
```
# Step to reproduce
1. Extract the archive given in the first line of this issue
2. Execute: `mpirun -np 2 pvbatch kitwareScriptContour.py`
The bug occurs only in specific conditions:
* The script is executed using pvbatch
* MPI is set up to use 2 cores (also bug with 5)
* Transparency is used (see the content of `kitwareScriptContour.py`)
# System
* Linux
* Gcc 10.1.0
* ParaView [master](https://gitlab.kitware.com/paraview/paraview/-/tree/5c5c6d2e803289dec30dd46edd8466272d773917)
@utkarsh.ayachit can you help me with this one ?
@jpouderoux FYIhttps://gitlab.kitware.com/paraview/paraview/-/issues/19991MultiComponent mapping volume rendering force coloring with a non existent po...2021-03-24T07:53:30-04:00Mathieu Westphal (Kitware)MultiComponent mapping volume rendering force coloring with a non existent point dataSteps to reproduces:
* Run ParaView
* Open [a.vtk](/uploads/f372eebfc461bddc91b568cd4beb1c7b/a.vtk), Apply,
* Color by [CellData] Scalars
* Select volume rendering
* Check the "Multi component mapping" checkbox
* A non-existent [P...Steps to reproduces:
* Run ParaView
* Open [a.vtk](/uploads/f372eebfc461bddc91b568cd4beb1c7b/a.vtk), Apply,
* Color by [CellData] Scalars
* Select volume rendering
* Check the "Multi component mapping" checkbox
* A non-existent [PointData] Scalars array become selected for coloring
* Selecting [CellData] Scalars again seems to fix the issue
@michael.migliore : FYIhttps://gitlab.kitware.com/paraview/paraview/-/issues/19956Selection tracing not working correctly with certain filters2024-03-07T20:47:14-05:00Mathieu Westphal (Kitware)Selection tracing not working correctly with certain filtersPlotSelectionOverTime and FFTOfSelectionOverTime are failing to generate a trace line when they are created if a selection exists.
If no selection exists, the trace is as follows: `plotSelectionOverTime1 = PlotSelectionOverTime(Input=str...PlotSelectionOverTime and FFTOfSelectionOverTime are failing to generate a trace line when they are created if a selection exists.
If no selection exists, the trace is as follows: `plotSelectionOverTime1 = PlotSelectionOverTime(Input=stress00, Selection=None)`, so, imo, the Selection being not traced correctly yet prevent the creation of the filter.
Steps to reproduce :
* Wavelet, Apply
* Select cells on
* Tools -> Start trace -> incremental
* PlotSelectionOverTime
* no line for creating the filter.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19954VTM reader does not show array selection correctly2021-03-24T14:23:26-04:00Utkarsh AyachitVTM reader does not show array selection correctlyParaView 5.8/master
* open [dataset.vtm](/uploads/f4866ed1b41d694840edc4068eda1ec1/dataset.zip), properties panel shows <br/>
![image](/uploads/9b27ab3eb3646cf407dc6a1a3d8f29fa/image.png)
* hit apply, information panel shows <br/>
![...ParaView 5.8/master
* open [dataset.vtm](/uploads/f4866ed1b41d694840edc4068eda1ec1/dataset.zip), properties panel shows <br/>
![image](/uploads/9b27ab3eb3646cf407dc6a1a3d8f29fa/image.png)
* hit apply, information panel shows <br/>
![image](/uploads/774d944ba790fd46929accc47cbca264/image.png)
Result0 was not listed in the properties panel.https://gitlab.kitware.com/paraview/paraview/-/issues/19951vtkIossReader::ReadMesh gets called even after vtkIossReader::ReadMetaData re...2021-08-17T11:18:14-04:00Utkarsh AyachitvtkIossReader::ReadMesh gets called even after vtkIossReader::ReadMetaData returns failureSteps:
* Edit `TestIossExodus` to not specify any filename.
* Run the test. The output shows two errors about missing file coming from REQUEST_INFORMATION and REQUEST_DATA passes. If REQUEST_INFORMATION fails, I don't think REQUEST_DATA ...Steps:
* Edit `TestIossExodus` to not specify any filename.
* Run the test. The output shows two errors about missing file coming from REQUEST_INFORMATION and REQUEST_DATA passes. If REQUEST_INFORMATION fails, I don't think REQUEST_DATA should ever get called. What's going on?https://gitlab.kitware.com/paraview/paraview/-/issues/19943python animation script called before view is created when loading state file2021-03-24T07:49:12-04:00Dan Lipsapython animation script called before view is created when loading state fileFor the attached state file, the python animation script embedded is called before the view is created.
To reproduce, load the attached pvsm on the attached data. This prints:
Warning: tick() called before view is created
[allFrames.p...For the attached state file, the python animation script embedded is called before the view is created.
To reproduce, load the attached pvsm on the attached data. This prints:
Warning: tick() called before view is created
[allFrames.pvsm](/uploads/0bf62404c190de4d23fe3c6f7c64f77f/allFrames.pvsm)
The data is at:
https://drive.google.com/file/d/1MZUzCbjTtEcMzDDpR6L7KRf84Z_KYjFN/view?usp=sharing
ref: [discourse](https://discourse.paraview.org/t/animation-python-script-error-when-loaded-from-state-file/4375/7)https://gitlab.kitware.com/paraview/paraview/-/issues/19935pvbatch has issues with sys.argv in parallel2021-01-06T08:50:34-05:00Andrew Bauerpvbatch has issues with sys.argv in parallelThe following with `pvbatch` run with more than a single MPI process hangs:
```
import sys
print("sys.argv is ", sys.argv)
```
i.e. `mpirun -np 2 pvbatch <name of script above> 1 2 3 4`
A workaround for now is to do:
`mpirun -np 2 pvb...The following with `pvbatch` run with more than a single MPI process hangs:
```
import sys
print("sys.argv is ", sys.argv)
```
i.e. `mpirun -np 2 pvbatch <name of script above> 1 2 3 4`
A workaround for now is to do:
`mpirun -np 2 pvbatch -sym <name of script above> 1 2 3 4`
Most users won't know to do this though.https://gitlab.kitware.com/paraview/paraview/-/issues/19922axis aligned slice2020-05-18T09:53:42-04:00Kurt Sansomaxis aligned sliceI importing a quadrilateral based shape that comes from a ascii xml vtu format file.
when I apply a slice at the origin the slice doesn't have a fully connected line as I would expect, when move the slice plane slightly over the gap goe...I importing a quadrilateral based shape that comes from a ascii xml vtu format file.
when I apply a slice at the origin the slice doesn't have a fully connected line as I would expect, when move the slice plane slightly over the gap goes away. I am thinking it has to do with the floating point precision around slicing exactly on the edge that it can't `cut` between the edge and so it gets lost.
I am running on windows 10, latest release from the zip file, ParaView-5.8.0-Windows-Python3.7-msvc2015-64bit. I haven't tested on other platforms yet.
[clipped_test.vtu](/uploads/756186620b220e3f834c4d863c31c6f5/clipped_test.vtu)
![image](/uploads/29eb9d5f9a17b110e8c0fb2fc7d9ba8f/image.png)
![image](/uploads/71364d39f160cdcf92ae71cb0c90829c/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19915Side set rendering issues for Exodus polyhedral elements2020-05-11T22:20:22-04:00Daniel LivingstonSide set rendering issues for Exodus polyhedral elements## Issue
When trying to render side sets for a general polyhedra mesh, ParaView will either crash or throw an error (log at bottom of issue). The mesh geometry itself is rendered fine. Mesh attached.
![ats_four_polyview_noclip](/upload...## Issue
When trying to render side sets for a general polyhedra mesh, ParaView will either crash or throw an error (log at bottom of issue). The mesh geometry itself is rendered fine. Mesh attached.
![ats_four_polyview_noclip](/uploads/118142b635a187b6ccd6d7ea78a0650f/ats_four_polyview_noclip.png)
![ats_four_polyview_clip](/uploads/298ed0e4027360e520250a51b2e7b462/ats_four_polyview_clip.png)
## Files
* [four_polygon.exo](/uploads/7271a9fe151c5f88aad392d16279cabc/four_polygon.exo)
* [basic_ats_example.exo](/uploads/8737033efb79ad0dd9e1cef6a135c714/basic_ats_example.exo)
----
### System Information
* Paraview v5.8
* macOS 10.14.6
### Potentially related issues
* #19404
* #16123
* #18783
----
## Traceback
```
ERROR: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 2672
vtkExodusIIReaderPrivate (0x7ff1e3d310f0): Unable to fetch side set "bottom" (1) node list
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 1465
vtkExodusIIReaderPrivate (0x7ff1e3d310f0): Set wasn't present in file? Working around it. Expect trouble.
ERROR: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 2672
vtkExodusIIReaderPrivate (0x7ff1e3d310f0): Unable to fetch side set "surface" (2) node list
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 1465
vtkExodusIIReaderPrivate (0x7ff1e3d310f0): Set wasn't present in file? Working around it. Expect trouble.
ERROR: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 2672
vtkExodusIIReaderPrivate (0x7ff1e3d310f0): Unable to fetch side set "external_sides" (3) node list
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/IO/Exodus/vtkExodusIIReader.cxx, line 1465
vtkExodusIIReaderPrivate (0x7ff1e3d310f0): Set wasn't present in file? Working around it. Expect trouble.
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51cd630): Cell array ObjectId with 1 components, has 4 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51cd630): Cell array SourceElementId with 1 components, has 4 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51cd630): Cell array SourceElementSide with 1 components, has 4 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51ce110): Cell array ObjectId with 1 components, has 4 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51ce110): Cell array SourceElementId with 1 components, has 4 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51ce110): Cell array SourceElementSide with 1 components, has 4 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51d2230): Cell array ObjectId with 1 components, has 110 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51d2230): Cell array SourceElementId with 1 components, has 110 tuples but there are only 0 cells
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/DataModel/vtkDataSet.cxx, line 476
vtkUnstructuredGrid (0x7ff1e51d2230): Cell array SourceElementSide with 1 components, has 110 tuples but there are only 0 cells
```https://gitlab.kitware.com/paraview/paraview/-/issues/19906Volume Rendering a 2D Image crash Xorg server2021-03-24T07:37:53-04:00Mathieu Westphal (Kitware)Volume Rendering a 2D Image crash Xorg serverSteps to reproduce :
* run paraview
* Open foot.mha ([foot.mha](/uploads/5122faf6000948cd854a2937490cb260/foot.mha) [foot.raw](/uploads/4559a1a4e9633b9d1b83e52b54d3ae5e/foot.raw))
* Switch to volume rendering
Xorg freeze completell...Steps to reproduce :
* run paraview
* Open foot.mha ([foot.mha](/uploads/5122faf6000948cd854a2937490cb260/foot.mha) [foot.raw](/uploads/4559a1a4e9633b9d1b83e52b54d3ae5e/foot.raw))
* Switch to volume rendering
Xorg freeze completelly.
Can't be reproduce with a png or with a 2D wavelet.
A simple fix for this would be to disable volume rendering for 2D image data.https://gitlab.kitware.com/paraview/paraview/-/issues/19888Doing volume rendering while connected to a pvdataserver segfaults2020-06-09T21:18:07-04:00Mathieu Westphal (Kitware)Doing volume rendering while connected to a pvdataserver segfaultsSteps to reproduce :
* run pvdataserver
* run ParaView, connect to server
* Wavelet, Apply
* Volume
```
( 15.164s) [pvdatserver ]vtkSocketCommunicator.c:852 ERR| vtkSocketCommunicator (0x174b300): Tag mismatch: got 10, expecti...Steps to reproduce :
* run pvdataserver
* run ParaView, connect to server
* Wavelet, Apply
* Volume
```
( 15.164s) [pvdatserver ]vtkSocketCommunicator.c:852 ERR| vtkSocketCommunicator (0x174b300): Tag mismatch: got 10, expecting 1.
( 15.164s) [pvdatserver ]vtkTCPNetworkAccessMana:297 ERR| vtkTCPNetworkAccessManager (0x142b980): Some error in socket processing.
( 14.221s) [paraview ] vtkOutputWindow.cxx:76 ERR| ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 852
vtkSocketCommunicator (0x174b300): Tag mismatch: got 10, expecting 1.
```https://gitlab.kitware.com/paraview/paraview/-/issues/19877Preselection and remote/local rendering can crash ParaView2020-04-29T03:23:22-04:00Mathieu Westphal (Kitware)Preselection and remote/local rendering can crash ParaViewIt is possible to segfault ParaView with a tag mismatch when playing with Remote Render treshold and preselection.
unrelated to !4034
Steps to reproduce :
* default settings
* run pvserver
* run paraview, connect to pvserver
* Uns...It is possible to segfault ParaView with a tag mismatch when playing with Remote Render treshold and preselection.
unrelated to !4034
Steps to reproduce :
* default settings
* run pvserver
* run paraview, connect to pvserver
* UnstructuredCellTypes, Apply
* Interactive Select cells on, mouve the mouse around to show a preselection
* Edit -> Settings -> Render View -> Remote Render Treshold -> set to 0;
* ParaView is now remote rendering
* mouve the mouse on the dataset
```
( 37.850s) [paraview ] vtkOutputWindow.cxx:76 ERR| ERROR: In /home/glow/work/paraview/paraviewFirst/paraview/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 846
vtkSocketCommunicator (0x55d887071920): Tag mismatch: got 1, expecting 10.
( 38.309s) [paraview ]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x56441a50a080): Could not receive tag. 188969
```
FYI : @michael.migliorehttps://gitlab.kitware.com/paraview/paraview/-/issues/19865Silo format mesh rendering issue2020-04-24T09:29:38-04:00Philip BlakelySilo format mesh rendering issueOur custom CFD code is capable of outputting Silo format files, some of which do not render correctly in Paraview version 5.8.0 (or any previous version I've tried, e.g. 5.6.0 or 5.7.0).
I think the issue is with how Paraview detects wh...Our custom CFD code is capable of outputting Silo format files, some of which do not render correctly in Paraview version 5.8.0 (or any previous version I've tried, e.g. 5.6.0 or 5.7.0).
I think the issue is with how Paraview detects which (rectilinear) mesh patches are adjacent to each other.
An example plot is:
![PV_bad_screenshot](/uploads/4d6470f32ee78078077e45b2ca23a622/PV_bad_screenshot.png)
(Use Surface With Edges on variable Air_rho). Clearly the top of the mesh is missing.
The resolution of the full domain is 71x71x71 cells with spatial extent 10.0x10.0x10.0
I found that if I scale all coordinate values in this file by 1/0.71, then the grid renders correctly:
![PV_good_screenshot](/uploads/82aab88862270fbbcfb4fd527aba2261/PV_good_screenshot.png)
The Silo files include a Multi-mesh Adj object called Domain_Decomposition, which I thought should help Paraview work out some issues. It may be because the domain decomposition includes patches of width 1 cell.
For what it's worth, VisIt 3.0.2 renders the file correctly:
![Visit_screenshot.png0000](/uploads/5f484286e74fbfa0f8db9cf2b930c4dd/Visit_screenshot.png0000.png)
(I only mention this because I know the Silo reading interface is virtually the same as VisIt's.)
I've attached a zip of the two .silo files, the original (Output_bad.silo) and the 1/0.71 scaled one (Output_good.silo).
Any suggestions on how to solve this would be helpful (including what information we might have failed to output correctly to the .silo files, or any further hints I can give Paraview.)
Thank you very much.
[Output.zip](/uploads/e2d2abaaa5b590fc091f5c216a4aadb8/Output.zip)https://gitlab.kitware.com/paraview/paraview/-/issues/19843Connect to pvserver after connecting to catalyst does not remove builtin2021-03-24T07:30:14-04:00Nicolas VuailleConnect to pvserver after connecting to catalyst does not remove builtinSteps:
- start ParaView
- Catalyst/connect
- start pvserver
- File / Connect
observation: new server is added to the pipeline, but builtin server is still there.
Tested on master (b326c89fae)Steps:
- start ParaView
- Catalyst/connect
- start pvserver
- File / Connect
observation: new server is added to the pipeline, but builtin server is still there.
Tested on master (b326c89fae)