ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-08-24T17:05:50-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19859DataAssembly in Information Tab2021-08-24T17:05:50-04:00Utkarsh AyachitDataAssembly in Information TabOpen an exodus file using the Ioss reader. The information tab shows this:
![image](/uploads/51a9eb8716fdefd7e8c2deb25116d32e/image.png)
While this is useful, it doesn't show the logical groupping of blocks/sets etc which is provided a...Open an exodus file using the Ioss reader. The information tab shows this:
![image](/uploads/51a9eb8716fdefd7e8c2deb25116d32e/image.png)
While this is useful, it doesn't show the logical groupping of blocks/sets etc which is provided as a `vtkDataAssembly`.
Solution:
* Make this top part on the information tab a tabbed widget which shows the assembly in one tab and the raw hierarchy in another.
* If the data doesn't have an assembly, only the hierarchy tab should be visible.
* clicking on items in the assembly tree should correctly update to show array information for the selected subset (similar to how it does in the hierarchy view)5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19824vtkXMLPMultiBlockDataWriter does not support vtkPartitionedDataSet2021-11-15T19:18:56-05:00Jeff MauldinvtkXMLPMultiBlockDataWriter does not support vtkPartitionedDataSetI read in a .cgns file, did an extract subset with seed filter. I tried to write out the resulting dataset as .vtm (vtkMultiblock) data. I got the error:
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-r...I read in a .cgns file, did an extract subset with seed filter. I tried to write out the resulting dataset as .vtm (vtkMultiblock) data. I got the error:
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/IO/ParallelXML/vtkXMLPMultiBlockDataWriter.cxx, line 175
vtkXMLPMultiBlockDataWriter (0xa32d160): Unsupported composite dataset type: vtkPartitionedDataSet
and
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_superbuild/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 753
vtkPVCompositeDataPipeline (0x9c79760): Algorithm vtkXMLPMultiBlockDataWriter(0xa32d160) returned failure for request: vtkInformation (0x174cd4d0)5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19805extract block filter should work by block name as well as index for catalyst2021-08-25T16:09:19-04:00Jeff Mauldinextract block filter should work by block name as well as index for catalystWhen you save an "extract block" filter in a catalyst script, the selected blocks for extraction are saved by an index (which appears to be generated as/during a depth-first traverse of the multiblock datastructure).
Unless the data to ...When you save an "extract block" filter in a catalyst script, the selected blocks for extraction are saved by an index (which appears to be generated as/during a depth-first traverse of the multiblock datastructure).
Unless the data to which the catalyst script is applied has an identical block structure, the extract block filter will fail. User expectations are such that if they specify an extract block filter by clicking the names of the blocks in the gui, the extract block filter will extract the blocks with those names regardless of the block structure which the catalyst script is applied to.
In my own python scripts I have gotten around this by doing the search on the block structure myself in python and finding the required indexes that way before creating the extract block filter. However, I think the appropriate interface for the filter would be to specify included/exclued blocks by block name, not by index. I realize that in some cases blocks might not have names, but we could either allow both methods of specifying block filters, or we could set a default name of a string equal to the block index in cases where no name has been supplied.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19690Change default in File Open from OK to Navigate2021-08-24T21:59:04-04:00W. Alan ScottChange default in File Open from OK to NavigatePlease change the default for directories in the File Open dialog from OK to Navigate. Currently, it is totally obnoxious. Further, OK should be very rare for directories.
* In your home directory mkdir the directory aaaaa.
* Open P...Please change the default for directories in the File Open dialog from OK to Navigate. Currently, it is totally obnoxious. Further, OK should be very rare for directories.
* In your home directory mkdir the directory aaaaa.
* Open ParaView.
* File/ Open. Change directory to /.
* Now, highlight Home (or User), `Enter`. Type in your name. `Enter` Now, the top folder (aaaaa) should be highlighted, but isn't in the File Name input box. Just hit `Enter`. We try to open this directory as a datset. It should default to Navigate. Note, if you click on Navigate, it does what you expect. Further, the Open dialog then closes! We get a useless message that File ' "" ' cannot be read.
This is obnoxious enough that I have marked it important.5.10 (Fall 2021)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19680CompositeDataSetIndex property set in python is not updated correctly in GUI ...2021-11-09T15:18:40-05:00Mathieu Westphal (Kitware)CompositeDataSetIndex property set in python is not updated correctly in GUI widgetRelated to #17175
* Open `can.ex2`, Apply
* Close active view, and show data in spreadsheet view
* Now in python shell, do this and observer the changes to the **Composite Data Set Index** widget on the Display properties after each pro...Related to #17175
* Open `can.ex2`, Apply
* Close active view, and show data in spreadsheet view
* Now in python shell, do this and observer the changes to the **Composite Data Set Index** widget on the Display properties after each property change
```python
a = GetDisplayProperties()
a.CompositeDataSetIndex = [ 0 ] # correct
a.CompositeDataSetIndex = [ 1 ] # correct
a.CompositeDataSetIndex = [] # incorrect
```
Note : Spreadsheet is never updated, requires a Render.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19677Watney Master Issues for 5.9.02022-09-21T13:12:56-04:00W. Alan ScottWatney Master Issues for 5.9.0Here are the list of Watney issues that are targetting 5.9.0. These are generally speaking enhancing ParaView/ Catalyst's ability to do quantitative analysis. This is onging development.
Milestone 5.8.0 Watney bugs are here: https://...Here are the list of Watney issues that are targetting 5.9.0. These are generally speaking enhancing ParaView/ Catalyst's ability to do quantitative analysis. This is onging development.
Milestone 5.8.0 Watney bugs are here: https://gitlab.kitware.com/paraview/paraview/issues/19126.
At Watney's request, I am reordering them by functional group.
* Selection. This is a limiting factor in everything we are doing for getting numbers out of ParaView, and highly coupled to the next item (Internal) because selection is how we identify objects.
- [x] #19676 Extend Extract Cells by Region to include line or splice source - Important
- [x] #19406 Sources/ Ellipse misses one segment - Important
- [ ] #19649 Select cells through in parallel does not trace correctly
* Internal to ParaView. How are objects labeled and referenced? Objects are cells and points, but also objects that ParaVew and VTK define or create such as streamlines. How do I find indices, what do they mean, and how can I use them to apply selection and filters to the desired objects?
- [x] #19128 cgns reader block ids messed up - Required
- [ ] #19170 Document all of the block and id names - Required (should slip post 5.8 release)
- [x] #19661 Append Location Attributes filter crashes in Catalyst with muliblock dataset where leaves are structured - On Sandia's plate.
- [x] #19117 CGNS bad in parallel with D3 filter - Important (probable slip to 5.9)
- [ ] #19234 Clarifications and modifications to Global Ids - Important
* Reading and Writing from/to files. For now, the mechanism is writing csv files through either File/SaveData or Export on the Spreadsheet view, but a much more expansive interface should be developed.
- [x] #19073 Save data products on the client, or server, side - Nice to have
- [x] #19454 add cgns reader globbing for batch
- [x] #20664 optionally add automatic displacements in CGNS
* Scripting issues. Critical for doing anything in Catalyst, and selections are not implemented in scripting so we can’t even get started on this area.
* Other, self explanatory
- [ ] #19161 StreamTracer path length seems suspect - Important
* Build support. This includes Catalyst bugs and features, and SuperBuild support.
- [ ] Superbuild - https://gitlab.kitware.com/paraview/paraview-superbuild/issues/142 Add ability to compile LLVM static. - Important
- [x] #19669 CMAKE_INSTALL_PREFIX not propogated properly in Superbuild.
- [x] #19565 External use of hdf5 not easy to implement, and doesn't work.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19675Please add assemblies to the new Exodus reader2021-08-12T15:35:41-04:00W. Alan ScottPlease add assemblies to the new Exodus readerPlease add assemblies to the new Exodus reader. Here are details from a user:
--snip-customer-- have recently funded SNL (Greg Sjaardema) to add in assemblies support to the Exodus file format. Greg is about halfway through these modi...Please add assemblies to the new Exodus reader. Here are details from a user:
--snip-customer-- have recently funded SNL (Greg Sjaardema) to add in assemblies support to the Exodus file format. Greg is about halfway through these modifications which includes updating key Secas tools. I believe Greg has already documented the new features he has added to Exodus. Naturally to make use of this new important capability the pre and post processing tools which support Exodus need to have support added for this assembly capability. Please can you explore if the proposed re-write to the Exodus readers in Paraview could also include adoption of the new assemblies feature in Exodus. The point of contact at SNL for this will be Greg himself. I believe he has about 40 more hours of effort to complete his task with the IOSS before handing over to the STK team to do their bits before the assembly feature can be supported by the wider Sierra codes.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19669CMAKE_INSTALL_PREFIX not propogated properly in superbuild2021-05-17T19:42:10-04:00Jeff MauldinCMAKE_INSTALL_PREFIX not propogated properly in superbuildI am trying to build catalyst for linking against SPARC. When I set the CMAKE_INSTALL_PREFIX argument in the superbuild, that command is not propagated down to paraview (or, for that matter, python if built, osmesa, and maybe not llvm)....I am trying to build catalyst for linking against SPARC. When I set the CMAKE_INSTALL_PREFIX argument in the superbuild, that command is not propagated down to paraview (or, for that matter, python if built, osmesa, and maybe not llvm).
cmake runs find, and the build happens, but all the results are placed in the default install directory (parallel to the 'superbuild' directory) in my building directory.
When I look at the CMakeCache.txt file in .../superbuild/paraview/build I see that the CMAKE_INSTALL_PREFIX is NOT set to what I set CMAKE_INSTALL_PREFIX to in the CMakeCache.txt for the overall superbuild.
I believe I can overcome this for paraview by passing cmake arguments down into paraview, but I'm not sure I can fix it for osmesa, python, and llvm. It does look like the llvm libraries get installed into the install lib directory as desired, but no paraview directories, and there is no <install>/lib/cmake subdirectory which is supposed to contain the paraview cmake config file for SPARC to use to find paraview during it's cmake configuration.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19660SPHVolumeInterpolator and PointVolumeInterpolator have their 3D Bounding Box ...2021-08-11T12:23:00-04:00Jean M. FavreSPHVolumeInterpolator and PointVolumeInterpolator have their 3D Bounding Box widget offset from the input dataEasy to reproduce for V5.8-RC2:
Wavelet + CleanToGrid + SPHVolumeInterpolator
the 3D cuboid widget is not centered over the volume, but appears to be centered on the 0-th point of the grid
N.B. The SPHLine- and SPHPlane- interpolators...Easy to reproduce for V5.8-RC2:
Wavelet + CleanToGrid + SPHVolumeInterpolator
the 3D cuboid widget is not centered over the volume, but appears to be centered on the 0-th point of the grid
N.B. The SPHLine- and SPHPlane- interpolators are correctly centered over the volume5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19538ParaView should find VTK with components2022-06-08T13:00:04-04:00Ben BoeckelParaView should find VTK with componentsVTK (in particular, external VTK) may be built with many more components than ParaView wants. The set of required VTK components from the requested set of ParaView components should be requested from VTK (plumbing `COMPONENTS` and `OPTIO...VTK (in particular, external VTK) may be built with many more components than ParaView wants. The set of required VTK components from the requested set of ParaView components should be requested from VTK (plumbing `COMPONENTS` and `OPTIONAL_COMPONENTS` based on the ParaView component status).
Cc: @utkarsh.ayachit
See #195375.10 (Fall 2021)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19478Master has debug prints remote server.2021-11-08T21:02:44-05:00W. Alan ScottMaster has debug prints remote server.Master is putting out debug prints remote server. I think it was also crashing, but after deleting my configuratin files, and rebuilding, I no longer see the crash. Could be I was fooling myself, thinking there was a crash, but just ge...Master is putting out debug prints remote server. I think it was also crashing, but after deleting my configuratin files, and rebuilding, I no longer see the crash. Could be I was fooling myself, thinking there was a crash, but just get lots of warning verbiage. Here is how to replicate:
* Master (), Linux, remote server. I am using 16 ranks, but I bet it happens with 1 or 2.
* Edit/ Settings/ Render View/ Remote Render Threshold == 0. OK.
* Now, kill and restart ParaView. You will see the following warning (the full version was sent to Ken Martin, and Kitware):
* This error will occur any time you redraw the main window, such as moving the Output Messages window to the side.
* Also happens if you run Sources/ Wavelet/ Apply.
This is a showstopper for Watney development.
```
12.726s) [paraview ] vtkOutputWindow.cxx:86 WARN| Generic Warning: In /snip/VTK/Rendering/OpenGL2/vtkOpenGLState.cxx, line 229
Error in cache state for GL_DRAW_BUFFER got 1028 expected1026
( 12.755s) [paraview ] vtkOutputWindow.cxx:86 WARN| Generic Warning: In /snip/VTK/Rendering/OpenGL2/vtkOpenGLState.cxx, line 275
at stack loc
0x2aaab427f81f : ??? [(???) ???:-1]
0x2aaab427a922 : vtksys::SystemInformation::GetProgramStack(int, int) [(libvtksys-pv5.7.so.1) ???:-1]
0x2aaac454f3f4 : vtkOpenGLState::CheckState() [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac455042a : vtkOpenGLState::vtkBindFramebuffer(unsigned int, vtkOpenGLFramebufferObject*) [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac449da50 : vtkOpenGLFramebufferObject::Bind(unsigned int) [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac449d9fd : vtkOpenGLFramebufferObject::Bind() [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac44a1b6d : vtkOpenGLFramebufferObject::PopulateFramebuffer(int, int, bool, int, int, bool, int, int, bool) [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac452f5cb : vtkOpenGLRenderWindow::CreateOffScreenFramebuffer(int, int) [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac452cb9d : vtkOpenGLRenderWindow::Start() [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaac82cf03b : vtkRenderWindow::DoStereoRender() [(libvtkRenderingCore-pv5.7.so.1) ???:-1]
0x2aaac82cef32 : vtkRenderWindow::Render() [(libvtkRenderingCore-pv5.7.so.1) ???:-1]
0x2aaac45302c7 : vtkOpenGLRenderWindow::Render() [(libvtkRenderingOpenGL2-pv5.7.so.1) ???:-1]
0x2aaab769bf11 : vtkPVProcessWindow::PrepareForRendering() [(libvtkPVClientServerCoreRendering-pv5.7.so.1) ???:-1]
0x2aaab76c9b98 : ??? [(???) ???:-1]
0x2aaab76b0a7f : vtkPVRenderView::Render(bool, bool) [(libvtkPVClientServerCoreRendering-pv5.7.so.1) ???:-1]
0x2aaab76afbbd : vtkPVRenderView::StillRender() [(libvtkPVClientServerCoreRendering-pv5.7.so.1) ???:-1]
0x2aaaab32926c : ??? [(???) ???:-1]
0x2aaaad971199 : vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) [(libvtkClientServer-pv5.7.so.1) ???:-1]
0x2aaaad96f91f : vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) [(libvtkClientServer-pv5.7.so.1) ???:-1]
0x2aaaad96ef4f : vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) [(libvtkClientServer-pv5.7.so.1) ???:-1]
0x2aaaad96edfd : vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) [(libvtkClientServer-pv5.7.so.1) ???:-1]
0x2aaaace2b332 : vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) [(libvtkPVServerImplementationCore-pv5.7.so.1) ???:-1]
0x2aaaace2b138 : vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) [(libvtkPVServerImplementationCore-pv5.7.so.1) ???:-1]
0x2aaaace27b2e : vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) [(libvtkPVServerImplementationCore-pv5.7.so.1) ???:-1]
0x2aaaace37baa : vtkPVSessionServer::OnClientServerMessageRMI(void*, int) [(libvtkPVServerImplementationCore-pv5.7.so.1) ???:-1]
0x2aaaace36902 : ??? [(???) ???:-1]
0x2aaab1175186 : vtkMultiProcessController::ProcessRMI(int, void*, int, int) [(libvtkParallelCore-pv5.7.so.1) ???:-1]
0x2aaab1174d9b : vtkMultiProcessController::ProcessRMIs(int, int) [(libvtkParallelCore-pv5.7.so.1) ???:-1]
0x2aaaad1fcd7d : vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) [(libvtkPVClientServerCoreCore-pv5.7.so.1) ???:-1]
0x2aaaad1fc90e : vtkTCPNetworkAccessManager::ProcessEvents(unsigned long) [(libvtkPVClientServerCoreCore-pv5.7.so.1) ???:-1]
0x401a0a : ??? [(???) ???:-1]
0x401acc : ??? [(???) ???:-1]
0x2aaaaacf1545 : __libc_start_main [(libc.so.6) ???:-1]
0x401609 : ??? [(???) ???:-1]
```5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19395Find Data breaks when running with mpiexec pvserver2021-08-25T17:16:16-04:00Shuhao WuFind Data breaks when running with mpiexec pvserverI'm currently trying to find a node where `U == max(U)` using the Find Data dialog. Paraview is connected to a pvserver instance running with np=4. The source filter has 3388 cells and 1794 nodes and is a polygonal mesh (comes from a sl...I'm currently trying to find a node where `U == max(U)` using the Find Data dialog. Paraview is connected to a pvserver instance running with np=4. The source filter has 3388 cells and 1794 nodes and is a polygonal mesh (comes from a slice of a structured grid).
Once I hit Run Selection Query, the UI freezes and the server emits the following error:
```
Error: Failed to evaluate Expression 'U == max(U)'. The following exception stack should provide additional developer specific information. This typically implies a malfor
med expression. Verify that the expression is valid.
( 38.351s) [pvserver.0 ] vtkPythonSelector.cxx:76 WARN| vtkPythonSelector (0x88ca890): Could not invoke 'python_selector.execute()'
Traceback (most recent call last):
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/python_selector.py", line 79, in execute
Error: Failed to evaluate Expression 'U == max(U)'. The following exception stack should provide additional developer specific information. This typically implies a malfor
med expression. Verify that the expression is valid.
( 38.351s) [pvserver.3 ] vtkPythonSelector.cxx:76 WARN| vtkPythonSelector (0x51a89c0): Could not invoke 'python_selector.execute()'
Traceback (most recent call last):
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/python_selector.py", line 79, in execute
maskArray = calculator.compute(inputs, query, ns=elocals)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/calculator.py", line 143, in compute
maskArray = calculator.compute(inputs, query, ns=elocals)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/calculator.py", line 143, in compute
retVal = eval(expression, globals(), mylocals)
File "<string>", line 1, in <module>
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 361, in max
retVal = eval(expression, globals(), mylocals)
File "<string>", line 1, in <module>
Error: Failed to evaluate Expression 'U == max(U)'. The following exception stack should provide additional developer specific information. This typically implies[40/1921]
med expression. Verify that the expression is valid.
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 361, in max
return _global_func(MaxImpl(), array, axis, controller)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 188, in _global_func
return _global_func(MaxImpl(), array, axis, controller)
res = impl.op()(array, axis)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 188, in _global_func
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 373, in max
( 38.351s) [pvserver.2 ] vtkPythonSelector.cxx:76 WARN| vtkPythonSelector (0x41a04c0): Could not invoke 'python_selector.execute()'
res = impl.op()(array, axis)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 373, in max
ans = numpy.max(narray, axis)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/fromnumeric.py", line 2505, in amax
Traceback (most recent call last):
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/python_selector.py", line 79, in execute
ans = numpy.max(narray, axis)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/fromnumeric.py", line 2505, in amax
maskArray = calculator.compute(inputs, query, ns=elocals)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/calculator.py", line 143, in compute
retVal = eval(expression, globals(), mylocals)
File "<string>", line 1, in <module>
initial=initial)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/_methods.py", line 28, in _amax
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 361, in max
return umr_maximum(a, axis, None, out, keepdims, initial)
initial=initial)ValueError: zero-size array to reduction operation maximum which has no identity
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/_methods.py", line 28, in _amax
return umr_maximum(a, axis, None, out, keepdims, initial)
ValueError: zero-size array to reduction operation maximum which has no identity
return _global_func(MaxImpl(), array, axis, controller)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 188, in _global_func
res = impl.op()(array, axis)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 373, in max
ans = numpy.max(narray, axis)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/fromnumeric.py", line 2505, in amax
Error: Failed to evaluate Expression 'U == max(U)'. The following exception stack should provide additional developer specific information. This typically implies a malfor
med expression. Verify that the expression is valid.
( 38.353s) [pvserver.1 ] vtkPythonSelector.cxx:76 WARN| vtkPythonSelector (0x81c39d0): Could not invoke 'python_selector.execute()'
Traceback (most recent call last):
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/python_selector.py", line 79, in execute
maskArray = calculator.compute(inputs, query, ns=elocals)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/paraview/detail/calculator.py", line 143, in compute
initial=initial)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/numpy/core/_methods.py", line 28, in _amax
retVal = eval(expression, globals(), mylocals)
File "<string>", line 1, in <module>
return umr_maximum(a, axis, None, out, keepdims, initial)
ValueError: zero-size array to reduction operation maximum which has no identity
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 361, in max
return _global_func(MaxImpl(), array, axis, controller)
File "/home/shuhao/ParaView-5.7.0-RC4-osmesa-MPI-Linux-Python3.7-64bit/lib/python3.7/site-packages/vtkmodules/numpy_interface/algorithms.py", line 217, in _global_func
comm.Allreduce([res, mpi_type], [res_recv, mpi_type], impl.mpi_op())
File "mpi4py/MPI/Comm.pyx", line 714, in mpi4py.MPI.Comm.Allreduce
mpi4py.MPI.Exception: Message truncated, error stack:
PMPI_Allreduce(450)...............: MPI_Allreduce(sbuf=0x7fb35c8bd300, rbuf=0x4bf1c80, count=1, datatype=MPI_DOUBLE, op=MPI_MAX, comm=MPI_COMM_WORLD) failed
PMPI_Allreduce(436)...............:
MPIR_Allreduce_impl(293)..........:
MPIR_Allreduce_intra_auto(178)....:
MPIR_Allreduce_intra_auto(84).....:
MPIR_Bcast_impl(310)..............:
MPIR_Bcast_intra_auto(223)........:
MPIR_Bcast_intra_binomial(112)....:
MPIDI_CH3U_Receive_data_found(131): Message from rank 0 and ta
```
The only way to get out of the frozen UI on the client is to either force quit or shutdown the pvserver.
I can confirm this bug doesn't exist when the pvserver is not running under mpiexec and thus using a single core or when the same operation is performed on the builtin paraview instance, hinting at a parallelization bug.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19343Assert Crash: double click on the scalar bar2021-11-09T13:48:54-05:00Nicolas VuailleAssert Crash: double click on the scalar barThis is a regression (see https://gitlab.kitware.com/paraview/paraview/issues/18215).
This was experienced on 5.7-RC4 and on master (8decb43ef3193540ae829b714cccae009e999af4)
**Only in Debug build as only an assert fails.**
### Steps
...This is a regression (see https://gitlab.kitware.com/paraview/paraview/issues/18215).
This was experienced on 5.7-RC4 and on master (8decb43ef3193540ae829b714cccae009e999af4)
**Only in Debug build as only an assert fails.**
### Steps
* wavelet, apply
* color by RTData
* double click on scalar bar
-> crash
### Trace
```
paraview: /home/nicolas/ParaView/paraview/ParaViewCore/ServerManager/Rendering/vtkSMScalarBarWidgetRepresentationProxy.cxx:146: void vtkSMScalarBarWidgetRepresentationProxy::BeginTrackingPropertiesForTrace(): Assertion `this->TraceItem == NULL' failed.
Loguru caught a signal: SIGABRT
Stack trace:
34 0x55e84ff39c5e ./bin/paraview(+0x7c5e) [0x55e84ff39c5e]
33 0x7fdd404efee3 __libc_start_main + 243
32 0x55e84ff400f8 ./bin/paraview(+0xe0f8) [0x55e84ff400f8]
31 0x7fdd3f284326 QCoreApplication::exec() + 150
30 0x7fdd3f27c4ec QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 300
29 0x7fdd3f2d5a03 QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 99
28 0x7fdd33b77201 g_main_context_iteration + 49
27 0x7fdd33b771c1 /usr/lib/libglib-2.0.so.0(+0x6c1c1) [0x7fdd33b771c1]
26 0x7fdd33b753ae g_main_context_dispatch + 638
25 0x7fdd28bf412c /usr/lib/libQt5XcbQpa.so.5(+0x6c12c) [0x7fdd28bf412c]
24 0x7fdd3f5f5afc QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 188
23 0x7fdd3f61b49b QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) + 635
22 0x7fdd3f619b45 QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 1573
21 0x7fdd3f27d9c2 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 386
20 0x7fdd3fc45e11 QApplication::notify(QObject*, QEvent*) + 817
19 0x7fdd3fc3c4f5 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 133
18 0x7fdd3e6c8f30 QVTKOpenGLWindow::event(QEvent*) + 96
17 0x7fdd3e6c9f4b QVTKRenderWindowAdapter::handleEvent(QEvent*) + 123
16 0x7fdd3e6c1d30 QVTKInteractorAdapter::ProcessEvent(QEvent*, vtkRenderWindowInteractor*) + 928
15 0x7fdd368e4da3 vtkObject::InvokeEvent(unsigned long, void*) + 61
14 0x7fdd368e463b /home/nicolas/ParaView/paraview-build/bin/../lib64/libvtkCommonCore-pv5.7.so.1(+0x7bb63b) [0x7fdd368e463b]
13 0x7fdd366c5819 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 71
12 0x7fdd3c93046f vtkAbstractWidget::ProcessEventsHandler(vtkObject*, unsigned long, void*, void*) + 553
11 0x7fdd3caeba71 vtkWidgetCallbackMapper::InvokeCallback(unsigned long) + 157
10 0x7fdd3c9629b5 vtkBorderWidget::SelectAction(vtkAbstractWidget*) + 903
9 0x7fdd368e4da3 vtkObject::InvokeEvent(unsigned long, void*) + 61
8 0x7fdd368e4887 /home/nicolas/ParaView/paraview-build/bin/../lib64/libvtkCommonCore-pv5.7.so.1(+0x7bb887) [0x7fdd368e4887]
7 0x7fdd3e49e4e0 /home/nicolas/ParaView/paraview-build/bin/../lib64/libvtkPVServerManagerRendering-pv5.7.so.1(+0xd04e0) [0x7fdd3e49e4e0]
6 0x7fdd3e4c3feb vtkSMScalarBarWidgetRepresentationProxy::ExecuteEvent(unsigned long) + 51
5 0x7fdd3e4c4239 vtkSMScalarBarWidgetRepresentationProxy::BeginTrackingPropertiesForTrace() + 77
4 0x7fdd404fc026 /usr/lib/libc.so.6(+0x33026) [0x7fdd404fc026]
3 0x7fdd404ee727 /usr/lib/libc.so.6(+0x25727) [0x7fdd404ee727]
2 0x7fdd404ee851 abort + 293
1 0x7fdd40503755 gsignal + 325
0 0x7fdd405037e0 /usr/lib/libc.so.6(+0x3a7e0) [0x7fdd405037e0]
( 10.396s) [paraview ] :0 FATL| Signal: SIGABRT
[1] 546436 abort (core dumped) ./bin/paraview
```
### System info
gcc 9.1;
cmake 3.15.3;
qt 5.13.15.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19332Modify ghost cells generator filter to also work with topologically regular g...2021-09-08T13:48:06-04:00Andrew BauerModify ghost cells generator filter to also work with topologically regular gridsThis is useful for loading silo files through the VisIt bridge where they come in as a composite dataset of rectilinear grids. I can convert them to a single rectilinear grid using a programmable filter but in parallel I don't have ghost...This is useful for loading silo files through the VisIt bridge where they come in as a composite dataset of rectilinear grids. I can convert them to a single rectilinear grid using a programmable filter but in parallel I don't have ghost information available for filters that need them.
This could also be useful for Catalyst for simulation codes that produce topologically regular grids.
I'm marking this as a 5.8 milestone as this is a semi-urgent need for some users. Please let me know if this doesn't seem reasonable for the 5.8 release since I'm not sure how soon our funding will be in place.5.10 (Fall 2021)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19271Please make the Find Data dialog to be dockable.2021-04-28T20:42:41-04:00W. Alan ScottPlease make the Find Data dialog to be dockable.Please make the Find Data dialog be dockable. Also, default it to the left side.Please make the Find Data dialog be dockable. Also, default it to the left side.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19267Add color map resource web page2021-11-09T15:20:38-05:00W. Alan ScottAdd color map resource web pagePlease add a web page on the paraview.org site that references different color map resources. These should include:
* Francesca Samsel's sciviscolor.org
* Ken Moreland's kenmoreland.com, specifically links on color maps
* Color Brewer -...Please add a web page on the paraview.org site that references different color map resources. These should include:
* Francesca Samsel's sciviscolor.org
* Ken Moreland's kenmoreland.com, specifically links on color maps
* Color Brewer - colorbrewer2.org
* Event Horizon Telescope color maps https://github.com/liamedeiros/ehtplot/blob/docs/docs/COLORMAPS.ipynb
Please contact Francesca, and also Ken, and ask for additional pages and references.
Please add one line to the Help menu, linking to this page.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19238Web: Pushing proxy property change doesn't trigger render in Python32021-11-04T11:21:35-04:00Scott WittenburgWeb: Pushing proxy property change doesn't trigger render in Python3With the latest 5.7 release candidate binaries, and only under Python3, ParaViewWeb visualizer can get into a state where changing proxy properties and applying them is not reflected in the 3D view until you interact with it in some way....With the latest 5.7 release candidate binaries, and only under Python3, ParaViewWeb visualizer can get into a state where changing proxy properties and applying them is not reflected in the 3D view until you interact with it in some way. To reproduce:
1. Create a cone
2. Change resolution and apply (you should see change reflected w/out needing to interact)
3. Delete the cone
4. Create a sphere
5. Change resolution phi or theta resolution and apply (change is not reflected until you interact)
After this point, it seems no more property changes applied to any pipeline elements are reflected in the view until you interact, or else kill the server and start fresh.5.10 (Fall 2021)Scott WittenburgScott Wittenburghttps://gitlab.kitware.com/paraview/paraview/-/issues/19149ParaView 5.7.0-RC1 Windows: NVIDIA IndeX representation causes ParaView to crash2021-09-16T17:34:30-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 Windows: NVIDIA IndeX representation causes ParaView to crash* ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet**
* Switch representation to "NVIDIA IndeX"
* ParaView crashes* ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet**
* Switch representation to "NVIDIA IndeX"
* ParaView crashes5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19148ParaView 5.7.0-RC1 windows: IndeX gives warning message when loading Wavelet2021-04-22T21:11:37-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC1 windows: IndeX gives warning message when loading Wavelet* Run ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet** source.
Immediately, IndeX produces a warning:
```
nvindex: 0.0 INDEX main warn : Index_debug_configuration: Unknown key 'async_s...* Run ParaView, builtin server
* Tools -> Manage Plugins...
* Load `pvNVIDIAIndeX`
* Add **Wavelet** source.
Immediately, IndeX produces a warning:
```
nvindex: 0.0 INDEX main warn : Index_debug_configuration: Unknown key 'async_subset_load' used with value '0'
```
It is not required to switch to the NVIDIA IndeX representation to see this warning.
/cc @eolivares5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/19128cgns reader block ids messed up2021-06-22T15:19:59-04:00W. Alan Scottcgns reader block ids messed upThe CGNS reader, and the hover cells on presents different block ids. As with Exodus, they should be consistent, repeatable, linear and contiguous. In other words, for a single block, I expect to find the same number throughout, and ha...The CGNS reader, and the hover cells on presents different block ids. As with Exodus, they should be consistent, repeatable, linear and contiguous. In other words, for a single block, I expect to find the same number throughout, and have it either increment 0,1,2,3,4 or use the numbering scheme from the file (blk-2, blk-1, etc.)
* Linux, master, remote server (16 processes).
* Open the Witney cgns dataset. Turn all blocks off, except have blk-2, Grid on. I turned on all variables, but it won't matter. Apply. You now have one block visible.
* Split View Vertically. Spreadsheet. Turn visibility on if needed. Sort on Block Number. Move back and forth, and you will find block numbers 8 and 9. Sort on block number. Now, you will see block numbers from 11 to 15!
These are bugs.
I'm fairly certain this will be a Watney bug.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachit