ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2019-09-06T15:36:10-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/19307Release ParaView 5.7.0-RC32019-09-06T15:36:10-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7.0-RC3# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0`.
- [ ] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.7.0-RC3
echo 5.7.0-RC3 > version.txt
git commit -m 'Update version number to 5.7.0-RC3' version.txt
git tag -a -m 'ParaView 5.7.0-RC3' v5.7.0-RC3 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC3:release v5.7.0-RC3`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0-RC3`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update
git checkout -b update-to-v5.7.0-RC3
```
- Update `CMakeLists.txt`
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.7.0-RC3" CACHE STRING "Force version to 5.7.0-RC3" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0-RC3
- [x] ARG SUPERBUILD_TAG=v5.7.0-RC3
- [x] `git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile`
- [x] `git commit -m "Update the default version to 5.7.0-RC3"`
- [x] `git gitlab-push`
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, and force push
```
git add CMakeLists.txt
git commit --amend
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.7.0-RC3' v5.7.0-RC3 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC3:release v5.7.0-RC3`
# Validating binaries
- For each binary, check
- [x] Getting started guide opens
- [x] Examples load and match thumbnails in dialog
- [x] Python
- [x] `import numpy`
- [x] Plugins are present and load properly
- [x] Text source LaTeX `$A^2$`
- [x] OSPRay
- [x] IndeX runs
- [x] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.7/`)
- [x] Ask @chuck.atkins to sign macOS binary
- [x] Regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.7
```
- [x] Test download links on https://www.paraview.org/download
# Post-release
- [ ] Write and publish blog post with release notes.
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19308Split render view in tiles of same size2021-03-24T05:45:47-04:00Riccardo RossiSplit render view in tiles of same sizeIt would be very useful to have a command/option to split the render view in tiles of same width and/or height or control the size by input number or percentage of the main window.It would be very useful to have a command/option to split the render view in tiles of same width and/or height or control the size by input number or percentage of the main window.https://gitlab.kitware.com/paraview/paraview/-/issues/19309Plugins need more configuration in 5.7-RC3 vs. 5.7-RC22020-05-06T23:45:31-04:00Jean M. FavrePlugins need more configuration in 5.7-RC3 vs. 5.7-RC2I have four different plugins which compile fine under 5.7-RC2
When moving to RC3, I need to explicitly set three variables to make cmake happy. There are the same variables needed to compile ParaView to begin with. So it looks like RC3...I have four different plugins which compile fine under 5.7-RC2
When moving to RC3, I need to explicitly set three variables to make cmake happy. There are the same variables needed to compile ParaView to begin with. So it looks like RC3 does not propagate them anymore.
export ospray_DIR=/path-to-ospray<br>
export OpenImageDenoise_DIR=/path-to-oidn<br>
export VisRTX_DIR=/path-to-visrtx
or do I need to update my CMakeList.txt?https://gitlab.kitware.com/paraview/paraview/-/issues/19310SurfaceLIC: inconsistent results on low-resolution image data2019-09-17T03:01:39-04:00Lutz HofmannSurfaceLIC: inconsistent results on low-resolution image dataSurfaceLIC on very low resolution image data (e.g., 3x3x1) yields different results than after applying Resample To Image to a higher resolution (e.g., 99x99x1).
Stream Tracer, on the other hand, yields the same results on both resolutio...SurfaceLIC on very low resolution image data (e.g., 3x3x1) yields different results than after applying Resample To Image to a higher resolution (e.g., 99x99x1).
Stream Tracer, on the other hand, yields the same results on both resolutions, which is the behaviour, that I would expect from SurfaceLIC as well.
An example is shown below, with streamlines in black computed by Stream Tracer (they coincide on both resolutions) and critical points for context.
This issue is present in all ParaView versions, that I have tested (5.3.0, 5.6.0, 5.7.0-RC2).
# LIC on 3x3 image
![lowres](/uploads/04d94229d57f68191e80e4b99e034e19/lowres.png)
# LIC after resampling to 99x99
![highres](/uploads/9f8754cfa2a3526accc8490ce6b0af73/highres.png)
# Statefile and data
[surfacelic_bug.tar.gz](/uploads/72dce73038ef0d9ad00fdebb5792f6aa/surfacelic_bug.tar.gz)https://gitlab.kitware.com/paraview/paraview/-/issues/19311Segfault on right click picking in RenderView2019-10-29T21:27:02-04:00Mathieu Westphal (Kitware)Segfault on right click picking in RenderViewWith master **and with all ReleaseCandidates**, the following segfaults :
* Open ParaView
* Sphere Apply
* Right click on sphere in render view
```
paraview: /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager...With master **and with all ReleaseCandidates**, the following segfaults :
* Open ParaView
* Sphere Apply
* Right click on sphere in render view
```
paraview: /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager/Core/vtkSMVectorPropertyTemplate.h:125: T& vtkSMVectorPropertyTemplate<T>::GetElement(unsigned int) [with T = long long int]: Assertion `idx < this->Values.size()' failed.
Thread 1 "paraview" received signal SIGABRT, Aborted.
0x00007ffff7c0a755 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff7c0a755 in raise () from /usr/lib/libc.so.6
#1 0x00007ffff7bf5851 in abort () from /usr/lib/libc.so.6
#2 0x00007ffff7bf5727 in __assert_fail_base.cold () from /usr/lib/libc.so.6
#3 0x00007ffff7c03026 in __assert_fail () from /usr/lib/libc.so.6
#4 0x00007ffff5408053 in vtkSMVectorPropertyTemplate<long long>::GetElement (this=0x55555a77b5d0, idx=0) at /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager/Core/vtkSMVectorPropertyTemplate.h:125
#5 0x00007ffff5406bdc in vtkSMIdTypeVectorProperty::GetElement (this=0x55555a77b400, idx=0) at /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager/Core/vtkSMIdTypeVectorProperty.cxx:109
#6 0x00007ffff544dd4e in vtkSMPropertyHelper::GetProperty<int> (this=0x7fffffffda90, index=0) at /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx:91
#7 0x00007ffff5449770 in vtkSMPropertyHelper::GetAsInt (this=0x7fffffffda90, index=0) at /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyHelper.cxx:659
#8 0x00007ffff5bd1885 in vtkSMRenderViewProxy::PickBlock (this=0x555557c5f4d0, x=126, y=305, flatIndex=@0x7fffffffdb78: 0) at /home/glow/work/paraview/paraviewFirst/paraview/ParaViewCore/ServerManager/Rendering/vtkSMRenderViewProxy.cxx:719
#9 0x00007ffff60ffd23 in pqRenderView::pickBlock (this=0x5555561a3b60, pos=0x7fffffffdbc0, flatIndex=@0x7fffffffdb78: 0) at /home/glow/work/paraview/paraviewFirst/paraview/Qt/Core/pqRenderView.cxx:567
#10 0x00007ffff7a1ee5a in pqPipelineContextMenuBehavior::eventFilter (this=0x555555d1d770, caller=0x555557e72420, e=0x7fffffffe430) at /home/glow/work/paraview/paraviewFirst/paraview/Qt/ApplicationComponents/pqPipelineContextMenuBehavior.cxx:167
#11 0x00007ffff69946d3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#12 0x00007ffff73514c4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007ffff735ac6c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#14 0x00007ffff69949c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#15 0x00007ffff5de17da in QVTKOpenGLWidget::<lambda(QEvent*)>::operator()(QEvent *) const (__closure=0x555557e79470, evt=0x7fffffffe430) at /home/glow/work/paraview/paraviewFirst/paraview/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:66
#16 0x00007ffff5de20a4 in QtPrivate::FunctorCall<QtPrivate::IndexesList<0>, QtPrivate::List<QEvent*>, void, QVTKOpenGLWidget::QVTKOpenGLWidget(vtkGenericOpenGLRenderWindow*, QOpenGLContext*, QWidget*, Qt::WindowFlags)::<lambda(QEvent*)> >::call(QVTKOpenGLWidget::<lambda(QEvent*)> &, void **) (f=...,
arg=0x7fffffffe080) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146
#17 0x00007ffff5de2065 in QtPrivate::Functor<QVTKOpenGLWidget::QVTKOpenGLWidget(vtkGenericOpenGLRenderWindow*, QOpenGLContext*, QWidget*, Qt::WindowFlags)::<lambda(QEvent*)>, 1>::call<QtPrivate::List<QEvent*>, void>(QVTKOpenGLWidget::<lambda(QEvent*)> &, void *, void **) (f=..., arg=0x7fffffffe080)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#18 0x00007ffff5de2033 in QtPrivate::QFunctorSlotObject<QVTKOpenGLWidget::QVTKOpenGLWidget(vtkGenericOpenGLRenderWindow*, QOpenGLContext*, QWidget*, Qt::WindowFlags)::<lambda(QEvent*)>, 1, QtPrivate::List<QEvent*>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x555557e79460, r=0x5555561898c0, a=0x7fffffffe080, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:439
#19 0x00007ffff69c0b70 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#20 0x00007ffff5dcff2a in QVTKOpenGLWindow::windowEvent (this=0x5555561898c0, _t1=0x7fffffffe430) at VTK/GUISupport/Qt/GUISupportQt_autogen/EWIEGA46WW/moc_QVTKOpenGLWindow.cpp:146
#21 0x00007ffff5de3ef3 in QVTKOpenGLWindow::event (this=0x5555561898c0, evt=0x7fffffffe430) at /home/glow/work/paraview/paraviewFirst/paraview/VTK/GUISupport/Qt/QVTKOpenGLWindow.cxx:274
#22 0x00007ffff73514d5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#23 0x00007ffff735aa21 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#24 0x00007ffff69949c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#25 0x00007ffff6d32789 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5
#26 0x00007ffff6d3405b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5
#27 0x00007ffff6d0c37c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#28 0x00007fffe04cdfec in ?? () from /usr/lib/libQt5XcbQpa.so.5
#29 0x00007fffeb284cf4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0x00007fffeb286b11 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x00007fffeb286b51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0x00007ffff69ec9a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#33 0x00007ffff69935ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#34 0x00007ffff699b326 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#35 0x00005555555620ec in main (argc=1, argv=0x7fffffffe988) at Applications/ParaView/paraview_main.cxx:107
```
Should this be fixed for release @cory.quammen @utkarsh.ayachit ?5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19312Add button to save contents of Output Messages window to a file2019-10-29T21:53:32-04:00Cory Quammencory.quammen@kitware.comAdd button to save contents of Output Messages window to a fileCurrently, you can copy and paste. Make it easy to save to a file with a button in the UI.Currently, you can copy and paste. Make it easy to save to a file with a button in the UI.5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19313Plugin auto-load option: "no entry in PV plugin manager"2021-03-24T05:45:02-04:00Cornelis BockemühlPlugin auto-load option: "no entry in PV plugin manager"Own plugins can be written and directly integrated into a custom application. Loading them can be automatic with the REQUIRED_PLUGINS list of the paraview_client_add cmake function or inside the program using the vtkPVPluginTracker class...Own plugins can be written and directly integrated into a custom application. Loading them can be automatic with the REQUIRED_PLUGINS list of the paraview_client_add cmake function or inside the program using the vtkPVPluginTracker class.
In all these cases, the plugins will appear in the list of the plugin manager - as "loaded".
But this does not make too much sense because loading them is not any more required, and unloading makes not much sense (and I would even doubt whether it can be reliable to "unload" a shared library from a running program!?)
Having an an option during plugin auto-load to not show a plugin in the PV plugin manager makes sense thus and avoids filling the list with useless entries.https://gitlab.kitware.com/paraview/paraview/-/issues/19314Small code adaptations to allow deriving classes from the spreadsheet view2021-11-09T13:02:32-05:00Cornelis BockemühlSmall code adaptations to allow deriving classes from the spreadsheet viewIn order to derive own variants of the spreadsheet view, two small adaptations would required in existing PV code:
1) in **pqStandardServerManagerModelInterface.cxx**, the following is required:
```
QObject* parent = NULL;
QStrin...In order to derive own variants of the spreadsheet view, two small adaptations would required in existing PV code:
1) in **pqStandardServerManagerModelInterface.cxx**, the following is required:
```
QObject* parent = NULL;
QString xmlname = proxy->GetXMLName();
- if (xmlname == pqSpreadSheetView::spreadsheetViewType())
+ if (vtkSMSpreadSheetViewProxy::SafeDownCast(proxy))
{
return new pqSpreadSheetView(group, name, proxy, server, parent);
}
```
this implies also an #include <vtkSMSpreadSheetViewProxy.h>
2) in the **vtkSpreadSheetView** class, the following functions must be virtual in order to call them also from base class interfaces:
```
virtual vtkIdType GetNumberOfColumns();
virtual vtkIdType GetNumberOfRows();
virtual const char* GetColumnName(vtkIdType index);
virtual bool IsColumnInternal(vtkIdType index);
virtual bool IsColumnInternal(const char* columnName);
virtual const char* GetColumnLabel(vtkIdType index);
virtual const char* GetColumnLabel(const char* columnName);
virtual bool GetColumnVisibility(vtkIdType index);
virtual vtkVariant GetValue(vtkIdType row, vtkIdType col);
virtual vtkVariant GetValueByName(vtkIdType row, const char* columnName);
virtual bool IsRowSelected(vtkIdType row);
virtual bool IsAvailable(vtkIdType row);
virtual bool Export(vtkCSVExporter* exporter);
virtual vtkTable* FetchBlock(vtkIdType blockindex, bool skipCache = false);
```https://gitlab.kitware.com/paraview/paraview/-/issues/19315Getting Started fails with Linux2019-09-09T22:45:54-04:00W. Alan ScottGetting Started fails with LinuxWeird. Getting Started fails with Linux.
* Download 5.7.0-RC3, Kitware download, Linux.
* Help/ Getting started.
* The Getting Started guide opens, but does not work with mouse controls. Here are the error messages output:
This to...Weird. Getting Started fails with Linux.
* Download 5.7.0-RC3, Kitware download, Linux.
* Help/ Getting started.
* The Getting Started guide opens, but does not work with mouse controls. Here are the error messages output:
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.
@utkarsh.ayachit @cory.quammen @wascott
How critical is this? I would say very. Can you replicate it?5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19317OptiX crashes paraview2024-03-07T20:47:09-05:00Mikkel SteenbergOptiX crashes paraviewI just downloaded the newest version to see whether I could get the Optix path tracer to work on my new laptop with RTX, but Paraview keeps crashing when I turn Optix on.
Build: Paraview-5.7.0-RC3-Windows-Python3.7-msvc2015-64bit
Graphic...I just downloaded the newest version to see whether I could get the Optix path tracer to work on my new laptop with RTX, but Paraview keeps crashing when I turn Optix on.
Build: Paraview-5.7.0-RC3-Windows-Python3.7-msvc2015-64bit
Graphic card: NVIDIA Quadro RTX 3000 (vers. 431.86)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19318Point Gaussian seems to ignore depth test2020-08-04T11:24:21-04:00Michael MigliorePoint Gaussian seems to ignore depth testTested on master commit 5b33972e34.
Point Gaussian ignores the depth test leading to a confusing perception of the depth
Steps:
- Create a point source with 1000 points in a radius of 1
- Create an elevation filter
- Select elevation p...Tested on master commit 5b33972e34.
Point Gaussian ignores the depth test leading to a confusing perception of the depth
Steps:
- Create a point source with 1000 points in a radius of 1
- Create an elevation filter
- Select elevation point data
- Select point gaussian representation
- Increase point gaussian radius
![Peek_2019-09-11_09-21](/uploads/a7eb2135c00af286cf61c5e2684625ac/Peek_2019-09-11_09-21.gif)https://gitlab.kitware.com/paraview/paraview/-/issues/19319Normal Gyphs filter: deprecation warning2019-10-29T21:54:52-04:00Cory Quammencory.quammen@kitware.comNormal Gyphs filter: deprecation warningWhen you add a **Normal Glyphs** filter, you get the following warning message:
```
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMProxy.cxx, line 886
vtk...When you add a **Normal Glyphs** filter, you get the following warning message:
```
Warning: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/ParaViewCore/ServerManager/Core/vtkSMProxy.cxx, line 886
vtkSMSourceProxy (0x7ff411447220): Proxy (filters, GlyphLegacy) has been deprecated in ParaView 5.6 and will be removed by ParaView 5.7.
It has been replaced by 'GlyphWithCustomSource'. Please consider using that instead.
```
Update the `CompoundSourceProxy` to use the new Glyph filter instead.5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19320Expose VTK modules cmake option in ParaView cmake advanced option2019-10-16T21:41:53-04:00Cornelis BockemühlExpose VTK modules cmake option in ParaView cmake advanced optionWhen building ParaView, it not possible to trigger the build of VTK modules that are not needed by ParaView.
It would be very practical to expose the `VTK_MODULE_ENABLE_VTK_*` VTK cmake option in ParaView cmake options.
Anyone would ha...When building ParaView, it not possible to trigger the build of VTK modules that are not needed by ParaView.
It would be very practical to expose the `VTK_MODULE_ENABLE_VTK_*` VTK cmake option in ParaView cmake options.
Anyone would have the liberty to enable any VTK modules and Provide them in their own ParaView based application without needing to patch ParaView in any way.Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19321some new variables in vtkSpreadSheetView class should be protected, not private2019-09-17T03:55:17-04:00Cornelis Bockemühlsome new variables in vtkSpreadSheetView class should be protected, not privateIn order to derive a view from the vtkSpreadSheetView, some internal variables need to be protected and not private:
CRMICallbackTag
PRMICallbackTag
Identifier
If they are private, too much of the class needs to be completely duplicated!In order to derive a view from the vtkSpreadSheetView, some internal variables need to be protected and not private:
CRMICallbackTag
PRMICallbackTag
Identifier
If they are private, too much of the class needs to be completely duplicated!https://gitlab.kitware.com/paraview/paraview/-/issues/19322Temporal cache crash in 5.7.0-RC32020-06-09T20:24:54-04:00Tim BiedertTemporal cache crash in 5.7.0-RC3Reproducer: ParaView-5.7.0-RC3-Windows-Python3.7-msvc2015-64bit from website
**Sphere source -> Apply -> Temporal cache -> Apply -> Crash**
Stack trace (for this release build) seems like a nullptr access in vtkFiltersHybrid-pv5.7.dll.Reproducer: ParaView-5.7.0-RC3-Windows-Python3.7-msvc2015-64bit from website
**Sphere source -> Apply -> Temporal cache -> Apply -> Crash**
Stack trace (for this release build) seems like a nullptr access in vtkFiltersHybrid-pv5.7.dll.https://gitlab.kitware.com/paraview/paraview/-/issues/19323Have edit boxes select all text when they grab focus2020-03-23T21:56:12-04:00W. Alan ScottHave edit boxes select all text when they grab focusPlease have edit boxes select all text when they grab focus. This is in response to a user complaint.
Here are some details on how to replicate:
* If you bring up a FastUniformGrid, then clip it, then rotate the clip around, you get e...Please have edit boxes select all text when they grab focus. This is in response to a user complaint.
Here are some details on how to replicate:
* If you bring up a FastUniformGrid, then clip it, then rotate the clip around, you get edit boxes for the normal. These are filled in with half a dozen numbers, but if you click on them, they expand to around two dozen numbers. Further, your cursor is now in the middle of the number, which is useless.
* Next, if you click in the Normal X, to change it to 1.0, you get as I describe above. Note that you now have to arrow the cursor to the right, and then delete everything – or, <ctrl>a, then delete everything.5.9 (Fall 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19324CMake Configuration Step of PV 5.7.0-RC3 fails2019-09-17T00:09:14-04:00Max ZeyenCMake Configuration Step of PV 5.7.0-RC3 failsThe VTK associated with PV 5.7.0-RC3 gives CMake errors during the configuration step. (Unknown CMake command check_symbol_exists in VTK/Common/Core/CMakeLists.txt:442).
Compared to VTK master, there is an `include(CheckSymbolExists)` mi...The VTK associated with PV 5.7.0-RC3 gives CMake errors during the configuration step. (Unknown CMake command check_symbol_exists in VTK/Common/Core/CMakeLists.txt:442).
Compared to VTK master, there is an `include(CheckSymbolExists)` missing before the first `check_symbol_exists` call.https://gitlab.kitware.com/paraview/paraview/-/issues/19325SaveScreenshot scalar bar too big even for high resolution2020-02-19T14:06:09-05:00Dan LipsaSaveScreenshot scalar bar too big even for high resolutionI see this on the master branch.
In Python scripting I use
SaveScreenshot(imageName) to get a 300 x 300 image. The scalar bar is big because probably there is a lower limit on how many pixels fonts use.
![low_warpx](/uploads/eda4005ae9...I see this on the master branch.
In Python scripting I use
SaveScreenshot(imageName) to get a 300 x 300 image. The scalar bar is big because probably there is a lower limit on how many pixels fonts use.
![low_warpx](/uploads/eda4005ae9c1bd81f73b772949cdaaf3/low_warpx.png)
If I use
SaveScreenshot(imageName, ImageResolution=(1024, 1024))
I get the following image. The fonts have a lot more pixels to work with, but the scalar bar has the same proportional size as before. I do use a reset camera in my script.
![high_warpx](/uploads/1c0d29e687cd6a4f0f68cad05b066b20/high_warpx.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19326Release ParaView 5.7.0-RC42019-09-16T13:24:31-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7.0-RC4# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0`.
- [ ] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.7.0-RC4
echo 5.7.0-RC4 > version.txt
git commit -m 'Update version number to 5.7.0-RC4' version.txt
git tag -a -m 'ParaView 5.7.0-RC4' v5.7.0-RC4 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC4:release v5.7.0-RC4`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0-RC4`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update
git checkout -b update-to-v5.7.0-RC4
```
- Update `CMakeLists.txt`
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.7.0-RC4" CACHE STRING "Force version to 5.7.0-RC4" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0-RC4
- [x] ARG SUPERBUILD_TAG=v5.7.0-RC4
- [x] `git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile`
- [x] `git commit -m "Update the default version to 5.7.0-RC4"`
- [x] `git gitlab-push`
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, and force push
```
git add CMakeLists.txt
git commit --amend
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.7.0-RC4' v5.7.0-RC4 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0-RC4:release v5.7.0-RC4`
# Validating binaries
- For each binary, check
- [ ] Getting started guide opens
- [ ] Examples load and match thumbnails in dialog
- [ ] Python
- [ ] `import numpy`
- [ ] Plugins are present and load properly
- [ ] Text source LaTeX `$A^2$`
- [ ] OSPRay
- [ ] IndeX runs
- [ ] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.7/`)
- [x] Ask @chuck.atkins to sign macOS binary
- [ ] Regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt`
```
buildListing.sh
updateMD5sum.sh v5.7
```
- [x] Test download links on https://www.paraview.org/download
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19327FXAA has no effect on Eye dome lighting2021-12-23T13:05:10-05:00Jonathan BorduasFXAA has no effect on Eye dome lightingDear users/devs of the Eye Dome Lighting plugin: @patchett2002 @ethan.stam @demarle @utkarsh.ayachit,
The FXAA seems to have no effects on the hard edge anti-aliasing of an Eye Dome Lighting View port.
When zooming out, the aliasing e...Dear users/devs of the Eye Dome Lighting plugin: @patchett2002 @ethan.stam @demarle @utkarsh.ayachit,
The FXAA seems to have no effects on the hard edge anti-aliasing of an Eye Dome Lighting View port.
When zooming out, the aliasing effects can be quite important (opaque purple surface on transparent grey surface).
![image](/uploads/1748e72854fca17869da94d9f3f57aa9/image.png)
The same setup using a screenshot export in 4K resolution creates a good result:
![image](/uploads/137047f49c0b9094cb46c954c4540c82/image.png)
If both surface are opaque, the anti-aliasing is acceptable:
![image](/uploads/8de47147b485f0aaca8e798c5a6c9f95/image.png)
Is it normal that a opaque/transparent combination increase drastically the aliasing effects ?
Is there a setting to reduce the aliasing ?
I am testing on ParaView-latest-MPI-Windows-Python3.7-msvc2015-64bit.exeSankhesh JhaveriSankhesh Jhaverihttps://gitlab.kitware.com/paraview/paraview/-/issues/19328incorrect cache when playing animation2020-10-27T18:32:50-04:00Utkarsh Ayachitincorrect cache when playing animationWhile rare, this highlights a peculiar case when animation cache my not be cleared when needed.
* Ensure animation caching is enabled in the **Settings** dialog
* Sphere, Apply
* Hit ![image](/uploads/63c8c43fc7c49b5559ef01ac8f8998c8/im...While rare, this highlights a peculiar case when animation cache my not be cleared when needed.
* Ensure animation caching is enabled in the **Settings** dialog
* Sphere, Apply
* Hit ![image](/uploads/63c8c43fc7c49b5559ef01ac8f8998c8/image.png) -- time 0 is cached
* Hit ![image](/uploads/0446fe4002198f0a5835a3465584b7d9/image.png) -- time 0.11111 is cached
* Animation View, add track for Sphere, Start Theta -- default values
* Hit ![image](/uploads/63c8c43fc7c49b5559ef01ac8f8998c8/image.png) -- time 0, start theta is 0
* Hit ![image](/uploads/0446fe4002198f0a5835a3465584b7d9/image.png) -- time 0.11111, start theta is not 0, but the rendering shows full sphere i.e. obsolete values from cache are being used!
* Hit ![image](/uploads/0446fe4002198f0a5835a3465584b7d9/image.png) on more time and correct frame is rendered for time 0.22222, however going back to frame 1, you'll get bad sphere.https://gitlab.kitware.com/paraview/paraview/-/issues/19329Color under opacity curve in not updated properly2019-11-07T05:28:57-05:00Michael MiglioreColor under opacity curve in not updated properlyTested on current master (commit 3ac4bc1ddd)
- Create a Wavelet
- Open Color Map Editor
- Change Diverging to HSV
- Color is not updated
- Moving the mouse cursor to the curve trigger the update
![2019-09-17-095627_402x592](/uploads/6b...Tested on current master (commit 3ac4bc1ddd)
- Create a Wavelet
- Open Color Map Editor
- Change Diverging to HSV
- Color is not updated
- Moving the mouse cursor to the curve trigger the update
![2019-09-17-095627_402x592](/uploads/6b4c07810a715417538c46582958d955/2019-09-17-095627_402x592.png)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19330HTG serial write as vtm not working2020-06-05T11:38:58-04:00Ethan StamHTG serial write as vtm not workingTested on MacOS with 5.7.0-RC4
I can't write out Hyper Tree Grid's as a vtm with the current RC.
To reproduce:
* Open ParaView
* Sources -> Hyper Tree Grid (Random) -> Apply
* File -> Save
* Choose vtm as the format and save with t...Tested on MacOS with 5.7.0-RC4
I can't write out Hyper Tree Grid's as a vtm with the current RC.
To reproduce:
* Open ParaView
* Sources -> Hyper Tree Grid (Random) -> Apply
* File -> Save
* Choose vtm as the format and save with the default settings
I get the following error, and nothing is written:
```
ERROR: In /Users/kitware/dashboards/buildbot-slave/a64f5607/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 813
vtkPVCompositeDataPipeline (0x6080009a2f40): Input for connection index 0 on input port index 0 for algorithm vtkXMLPMultiBlockDataWriter(0x7f971f9164e0) is of type vtkHyperTreeGrid, but a vtkMultiBlockDataSet is required.
```
@sebastien.jourdain @patchett20025.8 (Winter 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19331Write htg as phtg not working on master branch2020-01-14T11:06:26-05:00Ethan StamWrite htg as phtg not working on master branchTested with master build, MacOS
@sebastien.jourdain @yohann.bearzi I am unable to write .phtg's with the current paraview master branch.
To reproduce:
* Open paraview
* Sources -> Hyper Tree Grid (random) -> Apply
* File -> Save as ...Tested with master build, MacOS
@sebastien.jourdain @yohann.bearzi I am unable to write .phtg's with the current paraview master branch.
To reproduce:
* Open paraview
* Sources -> Hyper Tree Grid (random) -> Apply
* File -> Save as phtg with default settings
I get the error:
```
( 20.623s) [paraview ]vtkDemandDrivenPipeline:813 ERR| vtkPVCompositeDataPipeline (0x7f84e25c7db0): Input for connection index 0 on input port index 0 for algorithm vtkPassSelectedArrays(0x7f84e208be60) is of type vtkHyperTreeGrid, but a vtkDataSet is required.
```
I added this to vtkPassArrays. It seemed to work, but I'm not sure if it's the right fix...
```c++
info->Append(vtkAlgorithm::INPUT_REQUIRED_DATA_TYPE(), "vtkHyperTreeGrid");
```5.8 (Winter 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)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/19333ParaView hangs when reading big CGNS SIL2020-09-30T02:59:13-04:00Mickael PHILITParaView hangs when reading big CGNS SILWhen opening a CGNS file with around 400 CGNS zones, calls to ClearSelections or SetSelections of the SIL class are very slow to process and ends up with the interface hanging.
Initialization of the SIL status is not fast enough.When opening a CGNS file with around 400 CGNS zones, calls to ClearSelections or SetSelections of the SIL class are very slow to process and ends up with the interface hanging.
Initialization of the SIL status is not fast enough.https://gitlab.kitware.com/paraview/paraview/-/issues/19334Make ParaView buildable with WSL on windows and document the prodecure2019-09-30T21:48:31-04:00William YoungMake ParaView buildable with WSL on windows and document the prodecureParaView does not seem to build on WSL because of xmlpatterns not working.
Please make ParaView buildable on WSL and if it is already, document the procedure.
Initial bug report was as follows :
> Paraview cmake error with the ...ParaView does not seem to build on WSL because of xmlpatterns not working.
Please make ParaView buildable on WSL and if it is already, document the procedure.
Initial bug report was as follows :
> Paraview cmake error with the "AcceleratedAlgorithms_doc" dependency
>
> Hi, I am trying to make a build of open source Paraview using the ubuntu bash terminal, my machine runs on Windows 10. I thought I had downloaded all of the required dependencies, as per this documentation: https://www.paraview.org/Wiki/ParaView:Build_And_Install#Download_And_Install_CMake
> but at the "Build Paraview" part of the documentation, I run into this error once I get to the part of the cmake where the AcceleratedAlgorithms_doc is scanned:
>
> `CMake Error at /mnt/c/Users/mmmto/OneDrive/Documents/GitHub/ParaView/CMake/ParaViewClient.cmake:577 (message):
> Failed to convert servermanager XML: xmlpatterns: could not exec
> '/usr/lib/qt5/bin/xmlpatterns': No such file or directory`
>
> I know that xmlpatterns exists on my machine, but it exists in `/usr/lib`, and not `/usr/lib/qt5/bin/`.
>
> Any help would be appreciated.https://gitlab.kitware.com/paraview/paraview/-/issues/19335Setting of background image in render view is not traced with Python tracing2020-05-22T14:10:02-04:00Cory Quammencory.quammen@kitware.comSetting of background image in render view is not traced with Python tracingOriginal discussion here:
https://discourse.paraview.org/t/programmatically-set-background-image/2574Original discussion here:
https://discourse.paraview.org/t/programmatically-set-background-image/2574Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/19336Bad QT UI rescaling on Win10, Intel graphics, PV 5.7RC2 or RC42019-11-13T13:56:42-05:00Aron HelserBad QT UI rescaling on Win10, Intel graphics, PV 5.7RC2 or RC4Just had a driver update on my Win10 laptop, with:
- Intel(R) UHD Graphics 630
- OpenGL version: 3.2.0 - Build 26.20.100.6999 (this is the Intel driver version)
and when I choose a field for 'Coloring', the gui scales to double-size
![i...Just had a driver update on my Win10 laptop, with:
- Intel(R) UHD Graphics 630
- OpenGL version: 3.2.0 - Build 26.20.100.6999 (this is the Intel driver version)
and when I choose a field for 'Coloring', the gui scales to double-size
![image](/uploads/cdb7c42b397c679f5daf549f419199bf/image.png)
i.e. Choose a Sphere source, Apply, under Display.. Coloring, choose Normals - and the screenshot results.
I have a high-dpi primary display, and an a normal external monitor attached. I'm pretty sure this started with the update to the Intel graphics drivers.
This may be a FYI more than anything - if I force PV to use my Nvidia card instead, the issue is gone.https://gitlab.kitware.com/paraview/paraview/-/issues/19337Opening case and pvsm from command line2019-09-19T07:52:59-04:00Maarten MOSTERTOpening case and pvsm from command lineHello everyone,
I am a bit new and try to open ParaView with the following command line
paraFoam -case /home/myhomedir/OpenFOAM/myhomedir-7/run/propeller -state=/home/myhomedir/OpenFOAM/myhomedir-7/run/basicMesh.pvsm
I tried various va...Hello everyone,
I am a bit new and try to open ParaView with the following command line
paraFoam -case /home/myhomedir/OpenFOAM/myhomedir-7/run/propeller -state=/home/myhomedir/OpenFOAM/myhomedir-7/run/basicMesh.pvsm
I tried various variants and understood that the -state part could be omitted but nothing really works.
Thank you for your help
Maarten,https://gitlab.kitware.com/paraview/paraview/-/issues/19338ParaView crashing when specifying wrong extents for RAW ImageData2021-03-24T05:58:44-04:00Matthieu DorierParaView crashing when specifying wrong extents for RAW ImageDataI'm using ParaView 5.6.2 on MacOSX.
I'm opening a RAW file containing a 3D array of integers (30x30x30 elements). If I specify extents such that the product would be larger than the data size (e.g. if I set [0,30]x[0,30]x[0,30] instead o...I'm using ParaView 5.6.2 on MacOSX.
I'm opening a RAW file containing a 3D array of integers (30x30x30 elements). If I specify extents such that the product would be larger than the data size (e.g. if I set [0,30]x[0,30]x[0,30] instead of [0,29]x[0,29]x[0,29]), ParaView hangs when I click "apply" and I have to kill it.https://gitlab.kitware.com/paraview/paraview/-/issues/19339Assert fail when the legend takes too much space in a line chart view2021-03-24T05:53:01-04:00Mathieu Westphal (Kitware)Assert fail when the legend takes too much space in a line chart viewIf the legend takes too much spaces, the chart fails to draws on an assert and ParaView segfaults.
Steps to reproduce :
* Open ParaView
* Open SinceWaves.csv, Apply
* Show in a LineChartView
* Show all arrays
* place legend at the...If the legend takes too much spaces, the chart fails to draws on an assert and ParaView segfaults.
Steps to reproduce :
* Open ParaView
* Open SinceWaves.csv, Apply
* Show in a LineChartView
* Show all arrays
* place legend at the bottom
* Hide last three arrays
* Increase legend font size to 14
* Show one more array
```
paraview: /home/glow/work/paraview/paraviewFirst/paraview/VTK/Rendering/Context2D/vtkContextClip.cxx:71: virtual void vtkContextClip::SetClip(float, float, float, float): Assertion `width >= 0 && height >= 0' failed.
Thread 1 "paraview" received signal SIGABRT, Aborted.
0x00007ffff7c08755 in raise () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff7c08755 in raise () from /usr/lib/libc.so.6
#1 0x00007ffff7bf3851 in abort () from /usr/lib/libc.so.6
#2 0x00007ffff7bf3727 in __assert_fail_base.cold () from /usr/lib/libc.so.6
#3 0x00007ffff7c01026 in __assert_fail () from /usr/lib/libc.so.6
#4 0x00007ffff16c8b05 in vtkContextClip::SetClip (this=0x555559abcda0, x=20, y=574, width=242, height=-2) at /home/glow/work/paraview/paraviewFirst/paraview/VTK/Rendering/Context2D/vtkContextClip.cxx:71
```https://gitlab.kitware.com/paraview/paraview/-/issues/19340Custom filters spread like viruses2019-11-19T20:09:51-05:00W. Alan ScottCustom filters spread like virusesParaView seems to append all custom filters to any statefile that is saved (even custom filters that are used), and further stores any custom filter, that is read from a statefile, in the local config.
Full writeup, with .pvsm, is here:...ParaView seems to append all custom filters to any statefile that is saved (even custom filters that are used), and further stores any custom filter, that is read from a statefile, in the local config.
Full writeup, with .pvsm, is here: https://discourse.paraview.org/t/custom-filters-spread-like-viruses/2597
OK to slip to 5.9.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19341glTF exported streamlines ends up in wrong position2021-03-24T05:52:49-04:00Lars OlssonglTF exported streamlines ends up in wrong positionWhen exporting streamlines (streamtracer + tubes and glyphs) to glTF in 5.7 RC4, the exported geometries ends up in the wrong position. The export worked correctly in RC3. Note: we're also exporting stl and they end up in the correct pos...When exporting streamlines (streamtracer + tubes and glyphs) to glTF in 5.7 RC4, the exported geometries ends up in the wrong position. The export worked correctly in RC3. Note: we're also exporting stl and they end up in the correct position....so it seems to be streamline specific.https://gitlab.kitware.com/paraview/paraview/-/issues/19342Tetrahedralizer produces invalid/degenerate cells for certain types of input ...2022-07-26T09:19:20-04:00Eduardo OlivaresTetrahedralizer produces invalid/degenerate cells for certain types of input datacc @utkarsh.ayachit
It seems the tetrahedralizer filter, which is applied internally by ParaView for some volume representations, produces invalid cells depending on the cell type of input dataset. While debugging, we saw duplicated ce...cc @utkarsh.ayachit
It seems the tetrahedralizer filter, which is applied internally by ParaView for some volume representations, produces invalid cells depending on the cell type of input dataset. While debugging, we saw duplicated cells and overlapping cells sharing edges.
I have attached 3 repro cases:
[repro.tar](/uploads/f4a87e402a898104c012ed4d5c7b935a/repro.tar)
When the volume is built using wedges and tets everything seems fine: "dummyGrid_tetra_and_wedge.vtu"...
but when building the same volume with polyhedrons instead, it results on an ill mesh: "dummyGrid_polyhedron.vtu".
IndeX volume representation was failing to render the resulting mesh and ParaView shows some artifacts for "volume" representation and heavy artifacts when using "Bunyk ray caster" that even becomes unstable and shows this error in the log (ParaView 5.7 RC3).
`"\bbd\ecd3383f\build\superbuild\paraview\src\VTK\Rendering\Volume\vtkUnstructuredGridBunykRayCastFunction.cxx, line 957 vtkUnstructuredGridBunykRayCastFunction (0000029D36277020): Degenerate topology - cell face used more than twice."`
There is a second case where this happens (multiblock_structure.vtm), when using structured data and applying the "MergeBlock" filter with "MergePoints" option enabled. If "MergePoints" is disabled then it renders, but with artifacts at the boundaries between blocks.https://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/19344Release ParaView 5.7.02019-11-01T20:42:34-04:00Cory Quammencory.quammen@kitware.comRelease ParaView 5.7.0# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
...# Preparatory steps
- Update ParaView guides
- User manual
- [x] Rename to ParaViewGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Catalyst Guide
- [x] Rename to ParaViewCatalystGuide-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Getting Started Guide
- [x] Rename to ParaViewGettingStarted-5.7.0.pdf
- [x] Upload to www.paraview.org/files/v5.7
- Assemble release notes into `Documentation/release/ParaView-5.7.0`.
- [x] Get positive review and merge.
# Update ParaView
- [x] Update `release` branch for **paraview**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
```
- [x] Update `version.txt` and tag the commit
```
git checkout -b update-to-v5.7.0
echo 5.7.0 > version.txt
git commit -m 'Update version number to 5.7.0' version.txt
git tag -a -m 'ParaView 5.7.0' v5.7.0 HEAD
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master` (do *not* add `Backport: release`)
- [x] Get positive review
- [x] `Do: merge`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0:release v5.7.0`
- Update documentation page
- [x] See `https://github.com/Kitware/paraview-docs/blob/gh-pages/versions.json`
- Create tarballs
- [x] ParaView (`Utilities/Maintenance/create_tarballs.bash --txz --tgz --zip -v v5.7.0`)
- Upload tarballs to `paraview.org`
- [x] `rsync -rptv $tarballs paraview.release:ParaView_Release/v5.7/`
# Update ParaView-Superbuild
- [x] Update `release` branch for **paraview/paraview-superbuild**
```
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update
git checkout -b update-to-v5.7.0
```
- Update `CMakeLists.txt`
- [x] Set ParaView source selections in `CMakeLists.txt` and force explicit
version in `CMakeLists.txt`:
```
# Force source selection setting here.
set(paraview_SOURCE_SELECTION "5.7.0" CACHE STRING "Force version to 5.7.0" FORCE)
set(paraview_FROM_SOURCE_DIR OFF CACHE BOOL "Force source dir off" FORCE)
```
- Update versions
- [x] Guide selections in `versions.cmake`
- [x] Docker: update default tag strings (in `Scripts/docker/ubuntu/Dockerfile`)
- [x] ARG PARAVIEW_TAG=v5.7.0
- [x] ARG SUPERBUILD_TAG=v5.7.0
- [x] Commit changes and push to GitLab
```
git add versions.cmake CMakeLists.txt Scripts/docker/ubuntu/Dockerfile
git commit -m "Update the default version to 5.7.0"
git gitlab-push
```
- Integrate changes to `master` branch
- [x] Create a merge request targeting `master`, title beginning with WIP (do *not* add `Backport: release` to description)
- [x] Build binaries (`Do: test`)
- [x] Download the binaries that have been generated in the dashboard results. They will be deleted within 24 hours.
- [x] Remove explicit version forcing added in CMakeLists.txt, amend the commit, and force push
```
git add CMakeLists.txt
git commit --amend
git gitlab-push -f
```
- Finalize merge request
- [x] Remove WIP from merge request title
- [x] Get positive review
- [x] `Do: merge`
- [x] `git tag -a -m 'ParaView superbuild 5.7.0' v5.7.0 HEAD`
- Integrate changes to `release` branch
- [x] `git push origin update-to-v5.7.0:release v5.7.0`
# Sign macOS binaries
- [x] Upload to signing server, run script, download resulting .pkg and .dmg files
- [x] Install from .pkg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.7.0.app/`
- [x] Install from .dmg and verify that it is signed with `codesign -dvvv /Applications/ParaView-5.7.0.app/`
# Validating binaries
- For each binary, check
- [x] Getting started guide opens
- [x] Examples load and match thumbnails in dialog
- [x] Python
- [x] `import numpy`
- [x] Plugins are present and load properly
- [x] Text source LaTeX `$A^2$`
- [x] OSPRay raycasting and pathtracing runs
- [x] OptiX pathtracing runs
- [x] IndeX runs
- [x] AutoMPI
- Binary checklist
- [x] macOS
- [x] Linux
- [x] Linux osmesa
- [x] Windows MPI (.exe)
- [x] Windows MPI (.zip)
- [x] Windows no-MPI (.exe)
- [x] Windows no-MPI (.zip)
# Upload binaries
- [x] Upload binaries to `paraview.org` (`rsync -rptv $binaries paraview.release:ParaView_Release/v5.7/`)
- [x] Ask @utkarsh.ayachit to regenerate `https://www.paraview.org/files/listing.txt` and `md5sum.txt` on the website
```
buildListing.sh
updateMD5sum.sh v5.7
```
- [x] Test download links on https://www.paraview.org/download
# Update documentation
- [x] Upload versioned documentation to `https://github.com/kitware/paraview-docs`
- [x] Write and publish blog post with release notes.
- [x] Update release notes
(https://www.paraview.org/Wiki/ParaView_Release_Notes)
# Post-release
- [x] Post an announcement in the Announcements category on
[discourse.paraview.org](https://discourse.paraview.org/).
- [x] Update link to ParaView Guide PDF at https://www.paraview.org/paraview-guide/
- [x] Move unclosed issues to next release milestone in GitLab
/cc @ben.boeckel
/cc @cory.quammen
/cc @utkarsh.ayachit5.7 (Summer 2019)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19345Automatic selection of objects in pipeline browser when mouse-picked in rende...2021-03-24T05:52:02-04:00Riccardo RossiAutomatic selection of objects in pipeline browser when mouse-picked in render viewBack in the 4.3.1 release, the objects in the pipeline browser where automatically selected when picked in the render view with the mouse.
For example, if you have two tiles in the render view and two objects active separately in each t...Back in the 4.3.1 release, the objects in the pipeline browser where automatically selected when picked in the render view with the mouse.
For example, if you have two tiles in the render view and two objects active separately in each tile, by clicking one or the other they would be also selected in the pipeline.
In my understanding this feature is gone and now an extra click is required to perform the same operation, one to change the active tile and another one to select the object in the same tile.
If that's the case, would be nice to have it back or at least be able to activate such behavior.https://gitlab.kitware.com/paraview/paraview/-/issues/19346fontconfig 2.13.91 cause ParaView binaries to crash on startup.2019-12-18T10:40:08-05:00Nicolas Vuaillefontconfig 2.13.91 cause ParaView binaries to crash on startup.On a fontconfig updated archlinux (2.13.91+23+g65087ac), **all ParaView binaries** crash.
tested with following versions:
* ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit
* ParaView-5.5.2-Qt5-MPI-Linux-64bit
* ParaView-5.7.0-RC4-MPI-Linu...On a fontconfig updated archlinux (2.13.91+23+g65087ac), **all ParaView binaries** crash.
tested with following versions:
* ParaView-5.4.1-Qt5-OpenGL2-MPI-Linux-64bit
* ParaView-5.5.2-Qt5-MPI-Linux-64bit
* ParaView-5.7.0-RC4-MPI-Linux-Python3.7-64bit
It was not reproduced on ubuntu 18.04 where binaries work fine.
Also, no problem on arch with a built ParaView, neither with a superbuild (with qt 5.9)
Output is as follows :
```
... lots of font config errors, but already present before update
Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 5: invalid attribute 'translate'
Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 5: invalid attribute 'selector'
Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 6: invalid attribute 'xmlns:its'
Fontconfig error: "/etc/fonts/conf.d/90-synthetic.conf", line 6: invalid attribute 'version'
Fontconfig error: Cannot load config file from /etc/fonts/fonts.conf
... the rest is new
Fontconfig warning: FcPattern object weight does not accept value [40 210)
Loguru caught a signal: SIGSEGV
Stack trace:
15 0x40771d ./ParaView-5.7.0-MPI-Linux-Python3.7-64bit/bin/paraview() [0x40771d]
14 0x7f995f64dee3 __libc_start_main + 243
13 0x407530 ./ParaView-5.7.0-MPI-Linux-Python3.7-64bit/bin/paraview() [0x407530]
12 0x40c10b ./ParaView-5.7.0-MPI-Linux-Python3.7-64bit/bin/paraview() [0x40c10b]
11 0x407f85 ./ParaView-5.7.0-MPI-Linux-Python3.7-64bit/bin/paraview() [0x407f85]
10 0x409ce2 ./ParaView-5.7.0-MPI-Linux-Python3.7-64bit/bin/paraview() [0x409ce2]
9 0x7f995f32ac36 pqStatusBar::pqStatusBar(QWidget*) + 22
8 0x7f995ee5bf9e QStatusBar::setSizeGripEnabled(bool) + 78
7 0x7f995ee5bd26 QStatusBar::reformat() + 262
6 0x7f995e554703 QFontMetrics::height() const + 19
5 0x7f995e53812a QFontPrivate::engineForScript(int) const + 154
4 0x7f995e5600c2 QFontDatabase::load(QFontPrivate const*, int) + 1138
3 0x7f995e55f6a5 QFontDatabase::findFont(QFontDef const&, int) + 245
2 0x7f995e55ba31 /home/glow/work/paraview/others/ParaView-5.7.0-MPI-Linux-Python3.7-64bit/bin/../lib/libQt5Gui.so.5(+0x1c4a31) [0x7f995e55ba31]
1 0x7f99354e48be /home/glow/work/paraview/others/ParaView-5.7.0-MPI-Linux-Python3.7-64bit/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0xbc8be) [0x7f99354e48be]
0 0x7f995f6617e0 /usr/lib/libc.so.6(+0x3a7e0) [0x7f995f6617e0]
( 0.072s) [paraview ] :0 FATL| Signal: SIGSEGV
Segmentation fault (core dumped)
```
Trace:
```
Loguru caught a signal: SIGSEGV
Stack trace:
15 0x40771d ./bin/paraview() [0x40771d]
14 0x7fd2d3538ee3 __libc_start_main + 243
13 0x407530 ./bin/paraview() [0x407530]
12 0x40c10b ./bin/paraview() [0x40c10b]
11 0x407f85 ./bin/paraview() [0x407f85]
10 0x409ce2 ./bin/paraview() [0x409ce2]
9 0x7fd2d3215c36 pqStatusBar::pqStatusBar(QWidget*) + 22
8 0x7fd2d2d46f9e QStatusBar::setSizeGripEnabled(bool) + 78
7 0x7fd2d2d46d26 QStatusBar::reformat() + 262
6 0x7fd2d2441703 QFontMetrics::height() const + 19
5 0x7fd2d242512a QFontPrivate::engineForScript(int) const + 154
4 0x7fd2d244d0c2 QFontDatabase::load(QFontPrivate const*, int) + 1138
3 0x7fd2d244c6a5 QFontDatabase::findFont(QFontDef const&, int) + 245
2 0x7fd2d2448a31 /home/nicolas/ParaView/releases/ParaView-5.7.0-RC4-MPI-Linux-Python3.7-64bit/bin/../lib/libQt5Gui.so.5(+0x1c4a31) [0x7fd2d2448a31]
1 0x7fd2a90ea8be /home/nicolas/ParaView/releases/ParaView-5.7.0-RC4-MPI-Linux-Python3.7-64bit/plugins/platforms/../../lib/libQt5XcbQpa.so.5(+0xbc8be) [0x7fd2a90ea8be]
0 0x7fd2d354c7e0 /usr/lib/libc.so.6(+0x3a7e0) [0x7fd2d354c7e0]
( 1.274s) [paraview ] :0 FATL| Signal: SIGSEGV
[1] 1742859 segmentation fault (core dumped) ./bin/paraview
```
A work around is to downgrade fontconfig to version `2:2.13.1+12+g5f5ec56-1`, deleting the contents of `/var/cache/fontconfig` and rebuilding the cache by running `sudo /usr/bin/fc-cache -rs`. (thanks @lhofmann1)5.8 (Winter 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19347vtkPVGridAxes3DRepresentation: avoid calling MarkModified in SetPosition/SetS...2021-03-24T05:51:10-04:00Utkarsh AyachitvtkPVGridAxes3DRepresentation: avoid calling MarkModified in SetPosition/SetScaleMarkModified should not be called unless absolutely necessary since it causes pipeline updates. vtkPVGridAxes3DRepresentation can be easily re-worked to avoid that.MarkModified should not be called unless absolutely necessary since it causes pipeline updates. vtkPVGridAxes3DRepresentation can be easily re-worked to avoid that.https://gitlab.kitware.com/paraview/paraview/-/issues/19348Add key control to toggle 3D widget visibility in filters that use them2024-03-07T20:47:09-05:00Cory Quammencory.quammen@kitware.comAdd key control to toggle 3D widget visibility in filters that use them> when you create a slice [...] and then try to move the object around, sometimes you end up selecting the widget and modifying the slice.
>
> It would be useful, in my opinion, to have a key (shift or alt) to temporarily and on the fly ...> when you create a slice [...] and then try to move the object around, sometimes you end up selecting the widget and modifying the slice.
>
> It would be useful, in my opinion, to have a key (shift or alt) to temporarily and on the fly disable the widget without having to go back to the property panel and switch the widget off, and that could also help with the scenario you described.
> Maybe add another check box, right below "Show Plane"? Maybe "Interactive Plane"? Then, add a hot key toggle?
From discussion in #19345.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19349Error in finding a continuous curve for stress distribution along an arbitrar...2019-09-30T02:06:22-04:00Hamidreza MahdaviError in finding a continuous curve for stress distribution along an arbitrary direction for Tri-Quadratic-Hexahedron gridsDear all,
I would like to calculate the values of stress along any arbitrary directions inside my model. However, for some angles, I cannot get a continuous curve, and I don’t know why. I’m uploading the two vtu. files as well as the rel...Dear all,
I would like to calculate the values of stress along any arbitrary directions inside my model. However, for some angles, I cannot get a continuous curve, and I don’t know why. I’m uploading the two vtu. files as well as the related state file. As can be seen in the state file and also the two png. files, I can get a continuous stress curve on a 45-degree plane with respect to the x axis when I’m interested in calculating the stress values along a line oriented at 0-degree with respect to this plane (The blue curve). However, for the same plane, I cannot get a continuous curve along a line oriented at 45 degrees on this plane (The red curve). Does anyone know how to solve this problem?
[Cauchy_Problem.pvsm](/uploads/fa3696397510e53f9c286725d69ebe14/Cauchy_Problem.pvsm)![The_blue_curve](/uploads/3d5078de2656498e6cd4cf4a361553d7/The_blue_curve.png)
![The_red_curve](/uploads/16ad0ead4c77a04a6bc1fb49d60c5d1b/The_red_curve.png)[UC_with_inclusion_incl_319.vtu](/uploads/c0622db8398cca5c4c3c74c165cc2948/UC_with_inclusion_incl_319.vtu)
[UC_with_inclusion_319.vtu](/uploads/a2f04ab807be9c429c06ecd10deb7d6a/UC_with_inclusion_319.vtu)https://gitlab.kitware.com/paraview/paraview/-/issues/19350Enhancement Request: Downselect Open File Formats Displayed2022-09-27T16:30:33-04:00Joel A. KuleszaEnhancement Request: Downselect Open File Formats DisplayedThere are many supported file types in the Open File... dialog (a good thing), but the many I don’t use get in the way of the few that I do. If I could hide those I don’t use, it would make the drop-down menu much more functional.
It wo...There are many supported file types in the Open File... dialog (a good thing), but the many I don’t use get in the way of the few that I do. If I could hide those I don’t use, it would make the drop-down menu much more functional.
It would be helpful if an advanced preference can be created to hide/show file types (with the default setting as show all).
Discourse discussion: https://discourse.paraview.org/t/option-to-hide-file-formats-in-open-dialog/2646
cc: @patchett2002 @ethan.stamAron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/19351HTG writer breaks with vector arrays2020-01-14T11:06:26-05:00David E. DeMarleHTG writer breaks with vector arraysreported at LANL, worked previously, appended mode support seems to have broken itreported at LANL, worked previously, appended mode support seems to have broken it5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19352Font size of annotation vs colorbar2019-10-02T03:23:14-04:00Riccardo RossiFont size of annotation vs colorbarWhy is there a discrepancy between the font size in points of text annotations compared to colorbar title and annotations (see attached, text annotation font size 18, colorbar title and annotations font size 16)?
Any reason or a potenti...Why is there a discrepancy between the font size in points of text annotations compared to colorbar title and annotations (see attached, text annotation font size 18, colorbar title and annotations font size 16)?
Any reason or a potential bug?
![dummy](/uploads/56a9ef3ef0b749a4d73d3a39b4d92ee0/dummy.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19353Allow vtkGhostType to be displayed in the GUI as a selectable array for filters2019-12-09T21:25:32-05:00Andrew BauerAllow vtkGhostType to be displayed in the GUI as a selectable array for filtersFor at least the `Image Data to Uniform Grid` filter we need to be able to select `vtkGhostType` array in the GUI. See the discussion at https://discourse.paraview.org/t/xml-specification-questions-for-a-filter/2641. It's currently not b...For at least the `Image Data to Uniform Grid` filter we need to be able to select `vtkGhostType` array in the GUI. See the discussion at https://discourse.paraview.org/t/xml-specification-questions-for-a-filter/2641. It's currently not being shown due to `vtkPVDataSetAttributesInformation.cxx` ignoring it in `vtkSkipArray`.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19354Annotation filters font size behavior2021-04-26T20:17:44-04:00Riccardo RossiAnnotation filters font size behaviorFont size in annotation filters currently scales with the size of the render view, making the text not consistent with the font size of other objects like the colorbar, where title and annotations do not scale with the view.
It would be...Font size in annotation filters currently scales with the size of the render view, making the text not consistent with the font size of other objects like the colorbar, where title and annotations do not scale with the view.
It would be nice to have an option along with the annotation filter to prevent the text from scaling and have all the text in the window consistent in terms of font size.https://gitlab.kitware.com/paraview/paraview/-/issues/19355Volume Rendering with multiple dataset does not handle depth correctly2021-03-24T05:50:43-04:00Mathieu Westphal (Kitware)Volume Rendering with multiple dataset does not handle depth correctlyWhen using Volume Rendering in ParaView with multiple datasets, depths is not managed correctly, even with the "Depth Peeling For Volumes" setting enabled.
Steps to reproduce :
* Open ParaView
* Wavelet, Apply
* Volume
* Wavelet, 0 20,...When using Volume Rendering in ParaView with multiple datasets, depths is not managed correctly, even with the "Depth Peeling For Volumes" setting enabled.
Steps to reproduce :
* Open ParaView
* Wavelet, Apply
* Volume
* Wavelet, 0 20, 0, 20, Apply
* Volume
* Move the camera around
![Peek_2019-10-02_10-57](/uploads/9fee4055dce90d79f5472b8350d56883/Peek_2019-10-02_10-57.gif)
@ken-martin @michael.migliorehttps://gitlab.kitware.com/paraview/paraview/-/issues/19356typo in ParaViewPlugin.cmake module file2020-01-14T11:06:26-05:00Cornelis Bockemühltypo in ParaViewPlugin.cmake module fileIn ParaViewPlugin.cmake(860 - referring to master of today), there is an S too much in the following construct:
```cmake
if (_paraview_add_plugin_MODULE_ARGS)
if (NOT _paraview_add_plugin_MODULES_FILES OR
NOT _paraview_add...In ParaViewPlugin.cmake(860 - referring to master of today), there is an S too much in the following construct:
```cmake
if (_paraview_add_plugin_MODULE_ARGS)
if (NOT _paraview_add_plugin_MODULES_FILES OR
NOT _paraview_add_plugin_MODULES)
message(FATAL_ERROR
"The `MODULE_ARGS` argument requires `MODULE_FILES` and `MODULES` to be provided.")
endif ()
endif ()
```
It must be ...MODULE_FILES instead of ...MODULES_FILES!5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19357The ImageDataToUniformGrid filter for composite datasets should only be avail...2020-08-13T11:37:42-04:00Andrew BauerThe ImageDataToUniformGrid filter for composite datasets should only be available in the GUI if there is a vtkImageData in the composite datasetThis is nitpicking but the `ImageDataToUniformGrid` filter should not be available in the GUI (i.e. grayed out) if the composite dataset doesn't have any vtkImageDatas in it. See the discussion at https://discourse.paraview.org/t/xml-spe...This is nitpicking but the `ImageDataToUniformGrid` filter should not be available in the GUI (i.e. grayed out) if the composite dataset doesn't have any vtkImageDatas in it. See the discussion at https://discourse.paraview.org/t/xml-specification-questions-for-a-filter/2641. Steps to reproduce:
1. Create an `UnstructuredCellTypes` source
2. Create a `GroupDatasets` filter
The `ImageDataToUniformGrid` filter is now available in the GUI but shouldn't be since the composite dataset only has an unstructured grid in it. In reality nothing bad happens but nothing good happens either so we can make the GUI a bit cleaner by removing this option in this instance.
Note that if others are ok with the above behavior, I'm fine with it as well. I don't think of this as a serious flaw in the GUI.5.9 (Fall 2020)Feimi YuFeimi Yuhttps://gitlab.kitware.com/paraview/paraview/-/issues/19358v5.7.0 plugin system: invalid location2019-11-19T03:28:08-05:00Julien Schuellerv5.7.0 plugin system: invalid locationI'm trying to compile a plugin with the newest version 5.7, it failed so I tried the example:
https://kitware.github.io/paraview-docs/latest/cxx/PluginHowto.html
```
[ 71%] Building CXX object Plugin/CMakeFiles/CellDerivatives.dir/CellD...I'm trying to compile a plugin with the newest version 5.7, it failed so I tried the example:
https://kitware.github.io/paraview-docs/latest/cxx/PluginHowto.html
```
[ 71%] Building CXX object Plugin/CMakeFiles/CellDerivatives.dir/CellDerivativesPlugin.cxx.o
[ 85%] Linking CXX shared module //CellDerivatives/CellDerivatives.so
/opt/rh/devtoolset-2/root/usr/libexec/gcc/x86_64-redhat-linux/4.8.2/ld: cannot open output file //CellDerivatives/CellDerivatives.so: No such file or directory
```
The location of the plugin is wrong: `//CellDerivatives/CellDerivatives.so`
I pushed the whole example here for you to reproduce:
https://github.com/jschueller/paraview-plugin-example
cc @ben.boeckel5.8 (Winter 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19359v5.7.0 plugin system: undefined PV_PLUGIN_IMPORT_INIT2019-11-19T19:00:33-05:00Julien Schuellerv5.7.0 plugin system: undefined PV_PLUGIN_IMPORT_INITthe PV_PLUGIN_IMPORT_INIT macro is undefined with newest 5.7 version, with:
```
#include "vtkPVPlugin.h"
PV_PLUGIN_IMPORT_INIT(CellDerivatives)
int main()
{
PV_PLUGIN_IMPORT(CellDerivatives);
}
```
I get the following error:
```
ma...the PV_PLUGIN_IMPORT_INIT macro is undefined with newest 5.7 version, with:
```
#include "vtkPVPlugin.h"
PV_PLUGIN_IMPORT_INIT(CellDerivatives)
int main()
{
PV_PLUGIN_IMPORT(CellDerivatives);
}
```
I get the following error:
```
main.cxx:3:22: error: expected constructor, destructor, or type conversion before ‘(’ token
PV_PLUGIN_IMPORT_INIT(CellDerivatives)
```
according to https://kitware.github.io/paraview-docs/latest/cxx/PluginHowto.html it should still be there,
is there something I missed ?
I updated https://github.com/jschueller/paraview-plugin-example with this (from the previous plugin issue)
https://gitlab.kitware.com/paraview/paraview/-/issues/19360new flag VTK_PYTHON_OPTIONAL_LINK must be off to compile ParaView + python + ...2019-12-11T07:11:18-05:00Aron Helsernew flag VTK_PYTHON_OPTIONAL_LINK must be off to compile ParaView + python + testsFiling this on VTK, as @cory.quammen suggested, but it might be ParaView instead.
When compiling ParaView master as of today (10/1/2019),
- linux Ubuntu 16.04,
- gcc 5.4.0,
- ninja,
- debug build
I am unable to complete a build wit...Filing this on VTK, as @cory.quammen suggested, but it might be ParaView instead.
When compiling ParaView master as of today (10/1/2019),
- linux Ubuntu 16.04,
- gcc 5.4.0,
- ninja,
- debug build
I am unable to complete a build with
```
set(PARAVIEW_ENABLE_PYTHON ON CACHE BOOL "")
set(PARAVIEW_ENABLE_WEB ON CACHE BOOL "")
set(PARAVIEW_BUILD_TESTING ON CACHE BOOL "")
```
All the C++ test applications, like `vtkPVAnimationCxxTests`, fail to link, complaining of missing symbols from the Python C API, like
```
lib/libvtkPythonInterpreter-pv5.7.so.5.7: undefined reference to `PyImport_AddModule'
libvtkWrappingPythonCore-pv5.7.so.1: undefined reference to `PyByteArray_Type'
```
The flag `VTK_PYTHON_OPTIONAL_LINK` is on by default. If I turn it off, the entire build succeeds. Alternatively, if I don't enable testing, the entire build succeeds.
Should the default value of `VTK_PYTHON_OPTIONAL_LINK` be off?Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19361v5.7.0 plugin system: compile-time import2019-10-03T11:35:21-04:00Julien Schuellerv5.7.0 plugin system: compile-time importwith v5.7.0 we cannot link a plugin anymore because it use the MODULE_LIBRARY type:
```
paraview_plugin_build(PLUGINS ${plugins})
add_executable(plugin_load main.cxx)
target_link_libraries (plugin_load PRIVATE ParaView::pqApplicationCo...with v5.7.0 we cannot link a plugin anymore because it use the MODULE_LIBRARY type:
```
paraview_plugin_build(PLUGINS ${plugins})
add_executable(plugin_load main.cxx)
target_link_libraries (plugin_load PRIVATE ParaView::pqApplicationComponents)
target_link_libraries (plugin_load PRIVATE CellDerivatives)
```
So I tried to use the TARGET property, but without luck:
```
paraview_plugin_build(
PLUGINS ${plugins}
TARGET CellDerivatives_interface)
add_executable(plugin_load main.cxx)
target_link_libraries (plugin_load PRIVATE ParaView::pqApplicationComponents)
target_link_libraries (plugin_load PRIVATE CellDerivatives_interface)
```
It configures but it seems to have no effect:
```
main.cxx:(.text+0x5): undefined reference to `pv_plugin_instance_CellDerivatives'
```
Is it a bug ?
The example is still taken from the doc, and available at https://github.com/jschueller/paraview-plugin-examplehttps://gitlab.kitware.com/paraview/paraview/-/issues/19362Add an Export Inspector option for something like "Execute pipeline"2020-12-08T10:29:57-05:00Ethan StamAdd an Export Inspector option for something like "Execute pipeline"@dhr @patchett2002 @demarle
It would be useful to have an option somewhere in the Export Inspector -> Data Extracts -> Writers drop down that only executes the pipeline up to your selected filter and doesn't register any writers.
An e...@dhr @patchett2002 @demarle
It would be useful to have an option somewhere in the Export Inspector -> Data Extracts -> Writers drop down that only executes the pipeline up to your selected filter and doesn't register any writers.
An example is when you make a programmable filter that saves a matplotlib plot on apply, and you want to run that with a catalyst script in situ. To get that catalyst script, you still have to select a writer, either from the data extracts or image extracts, and comment it out later yourself. If you don't select an extract, you get the error:
```Nothing to export, use Export Inspector to configure what you want to write.```5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19363Loading a state with source from a file containing numbers in the name replac...2019-11-19T20:14:47-05:00Mathieu Westphal (Kitware)Loading a state with source from a file containing numbers in the name replace numbers by dots.When loading a state with the "Search File under specified directory", the number in the filenames are replaced by dots.
Steps to reproduce :
* Open ParaView
* Open [bot2.wrl](/uploads/5ed72d158994af1f71a85dc11d392b9c/bot2.wrl) (any fi...When loading a state with the "Search File under specified directory", the number in the filenames are replaced by dots.
Steps to reproduce :
* Open ParaView
* Open [bot2.wrl](/uploads/5ed72d158994af1f71a85dc11d392b9c/bot2.wrl) (any file with a number in the name will do). Apply.
* Save State anywhere
* Reset Session
* Load State
* Select "Search File under specified directory", point to the folder containing bot2.wrl
* In the pipeline browser, the source is incorrectly named "bot..wrl"5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19364Intel GPU driver update 26.20.100.6708 on windows breaks Qt GUI --> FIXED by ...2020-06-29T09:54:10-04:00JaberIntel GPU driver update 26.20.100.6708 on windows breaks Qt GUI --> FIXED by UPGRADING intel driversUsing ParaView on windows with the **26.20.100.6708 <= intel driver < 26.20.100.7528** can lead to a broken GUI.
Steps to reproduce :
* Run windows with the intel driver and chipset (driver version may matter, tbd)
* Run ParaView wit...Using ParaView on windows with the **26.20.100.6708 <= intel driver < 26.20.100.7528** can lead to a broken GUI.
Steps to reproduce :
* Run windows with the intel driver and chipset (driver version may matter, tbd)
* Run ParaView with the intel driver
* Show the color editor dock widget (which contains a QVTKOpenGLNativeWidget)
* Open a datafile
* GUI looks like this or is all black :
![image](/uploads/249ad9518749206f293d5fdb8779a3b1/image.png)
**A workaround is to use the actual GPU of the laptop instead of the intel chipset, or to upgrade your driver after 26.20.100.7528 or to not upgrade the GPU driver**
Reports :
| Chipset | Driver | Status |
| ------ | ------ | ------ |
| 6700hq | 26.20.100.7158 | Bug |
| P630 | 26.20.100.6911 | Bug |
| 630 | 22.20.16.4708 | No Bug |
| 620 | 26.20.100.6999 | Bug |
| 620 | 26.20.100.7584 | fixed, unconfirmed |
Report of the bug :
* https://discourse.paraview.org/t/paraview-automatically-zooms-in/3211
* https://discourse.paraview.org/t/strange-effects-with-volume-representation/2951/3
* https://discourse.vtk.org/t/intel-uhd-620-vtk-qt-bug-with-new-drivers-on-windows/1694/11
* https://discourse.paraview.org/t/weird-display-resolution/3035/3
* https://discourse.paraview.org/t/paraview-visualization-distorted-after-apply/3248https://gitlab.kitware.com/paraview/paraview/-/issues/19365Quick launch dialog fails to select some filters/sources2019-10-29T21:56:36-04:00Joachim PouderouxQuick launch dialog fails to select some filters/sourcesThere is an issue with the Quick Launch dialog (CTRL-SPACE).
Some entries are not correctly managed, certainly because of the & char in the action name.
Tested on Linux with PV master > 5.7.
Example:
- CTRL+SPACE
- type 'A' => one ...There is an issue with the Quick Launch dialog (CTRL-SPACE).
Some entries are not correctly managed, certainly because of the & char in the action name.
Tested on Linux with PV master > 5.7.
Example:
- CTRL+SPACE
- type 'A' => one can see the Axes source in the list
- type 'X' => the Axes source disappears
![Screenshot_20191007_145620](/uploads/d99629c349142dd192d2ec024b00aa8b/Screenshot_20191007_145620.png)
![Screenshot_20191007_145639](/uploads/774f574c52ce473d2ac56b2e0467f4d0/Screenshot_20191007_145639.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19366RayTracing produce image in image when saving animation in higher resolution2021-08-16T15:39:41-04:00Mathieu Westphal (Kitware)RayTracing produce image in image when saving animation in higher resolutionSaving an animation with higher resolution and ray tracing can result in the following image
![actualTest.0018](/uploads/573f8868e0a8a82270eeb934abb9831f/actualTest.0018.png)
Steps to reproduce :
* Open can.ex2
* Enable Ray Tracing
* E...Saving an animation with higher resolution and ray tracing can result in the following image
![actualTest.0018](/uploads/573f8868e0a8a82270eeb934abb9831f/actualTest.0018.png)
Steps to reproduce :
* Open can.ex2
* Enable Ray Tracing
* Enable shadows
* Change to OSPRay pathtracer
* 20 samples per pixel
* Save animation, as .png
* Change resolution to 1920 x 1080
* one or two image may look like this. Resave animation if not.David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19367ParaView GUI needs is not clear about HTG array alignment.2020-03-24T16:54:54-04:00David E. DeMarleParaView GUI needs is not clear about HTG array alignment.The information panel shows the arrays as being point aligned, when they are closer to cell aligned.
The colormap array choice, shows both point and cell aligned versions of each array, but the point one is not-functional.
The spreadshee...The information panel shows the arrays as being point aligned, when they are closer to cell aligned.
The colormap array choice, shows both point and cell aligned versions of each array, but the point one is not-functional.
The spreadsheet view does not let you see any of the arrays.
Meanwhile the .htg file format labels the arrays as being point aligned and the htg reader does not give you an option to choose from the available arrays to load.5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19368disallow filter changes when playing animations2021-03-24T05:50:09-04:00Utkarsh Ayachitdisallow filter changes when playing animations* Load `can.ex2`.
* Add a **Clip** filter, defaults are fine.
* Run animation. Loop it so it repeats indefinitely.
* Now modify the clip filter with the widget in the Render View while the animation is running. Apply.
* Notice that the c...* Load `can.ex2`.
* Add a **Clip** filter, defaults are fine.
* Run animation. Loop it so it repeats indefinitely.
* Now modify the clip filter with the widget in the Render View while the animation is running. Apply.
* Notice that the clip has not been modified and the animation is running from the cached timesteps.
* Now stop the animation. Change the plane again and click Apply. The geometry is updated.
* Run the animation again. The geometry is updated correctly the first time through.
To support this case, it may be best to disallow changes while animations are playing except camera changes, play, pause and such.https://gitlab.kitware.com/paraview/paraview/-/issues/19369Add crinkle slice filter for hyper tree grid2019-10-10T11:17:25-04:00Yohann Bearzi (Kitware)Add crinkle slice filter for hyper tree gridThe crinkle option does not exist for the slice filter of hyper tree grids because no such filter is implemented. Such a filter should be written and added to the features of the slice widget in ParaView.The crinkle option does not exist for the slice filter of hyper tree grids because no such filter is implemented. Such a filter should be written and added to the features of the slice widget in ParaView.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19370Non-axis aligned plane clip filter for hyper tree grids2019-10-14T13:40:28-04:00Yohann Bearzi (Kitware)Non-axis aligned plane clip filter for hyper tree gridsThe clip filter for hyper tree grid only supports axis aligned planes. One could add any planes by using the quadric version of the filter and adding it to the interface of the clip filter for hyper tree grids.The clip filter for hyper tree grid only supports axis aligned planes. One could add any planes by using the quadric version of the filter and adding it to the interface of the clip filter for hyper tree grids.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19371ParaView ignores Blocks on this dataset2020-09-29T20:37:51-04:00W. Alan ScottParaView ignores Blocks on this datasetMy user gave me a dataset that ignores block selections. This dataset came from a single .g file, then was spread into numerous .g files. The block selection does not work. Here is how to replicate:
* Windows (or Linux), 5.6.0 (or 5.7...My user gave me a dataset that ignores block selections. This dataset came from a single .g file, then was spread into numerous .g files. The block selection does not work. Here is how to replicate:
* Windows (or Linux), 5.6.0 (or 5.7.0), built in server.
* Open the spread dataset, ztest.g.8.[0-7].
* Select only the second and third block (i.e., leave block 98 unselected).
* Apply.
* Compare with selecting all blocks. They are the same. This is a bug.
Dataset is paraview_block_issue.tar.bz2 on Windows. User is Mike W. I can pass this to Cory and/or Utkarsh.
@utkarsh.ayachit @cory.quammen I would appreciate this being looked at as soon as possible (and the contract allows). This may represent a bug on Sandia's code's part, and I would like to give feedback if true.5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19372Erroneous Material on X3D and VRML output of Lines2023-06-23T06:09:30-04:00Nicholas PolysErroneous Material on X3D and VRML output of LinesWe LOVE the X3D and VRML export!! :-)
but we found a bug... stil in 5.6.x :
the ISO specs say that lines are not lit/shaded, so diffuseColor is not used.
The RGB Material should be output as emissiveColor
for LineSets and PointSet...We LOVE the X3D and VRML export!! :-)
but we found a bug... stil in 5.6.x :
the ISO specs say that lines are not lit/shaded, so diffuseColor is not used.
The RGB Material should be output as emissiveColor
for LineSets and PointSets
https://www.web3d.org/standards
https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/rendering.html#LineSet
https://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/shape.html#Materialhttps://gitlab.kitware.com/paraview/paraview/-/issues/19373Paraview 5.6 Crashes on MPAS Data2020-01-07T19:59:54-05:00Nathan WoodsParaview 5.6 Crashes on MPAS DataI have some MPAS data that will not open in 5.6.0 or 5.6.1. It opens correctly in 5.5.2. Unfortunately, the file is 2GB, and too big to upload here.
In 5.5.2, when opening this file, I get the "Open Data With..." dialogue box, with the ...I have some MPAS data that will not open in 5.6.0 or 5.6.1. It opens correctly in 5.5.2. Unfortunately, the file is 2GB, and too big to upload here.
In 5.5.2, when opening this file, I get the "Open Data With..." dialogue box, with the option to choose MPAS NetCDF (Unstructured). This opens correctly.
In 5.6.1, I do not get the dialogue box, and I find the following error in my Output Messages:
```
Utilities\VisItBridge\databases\vtkVisItMFIXCDFReader.cxx, line 110
vtkVisItMFIXCDFReader (000002278D6FB090): There was an error opening C:\Users\303487\Desktop\Antarctica Data\ais2km_100yr_spinup.nc. It may be an invalid file.
ERROR: In C:\bbd\ecd3383f\build\superbuild\paraview\src\VTK\Common\ExecutionModel\vtkExecutive.cxx, line 782
vtkPVCompositeDataPipeline (000002278D413FD0): Algorithm vtkVisItMFIXCDFReader(000002278D6FB090) returned failure for request: vtkInformation (00000227981B67A0)
Debug: Off
Modified Time: 278047
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FORWARD_DIRECTION: 0
ALGORITHM_AFTER_FORWARD: 1
```5.8 (Winter 2020)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19374remove deprecated Catalyst Script Generator GUI and other dead code paths2020-11-27T13:09:34-05:00David E. DeMarleremove deprecated Catalyst Script Generator GUI and other dead code pathsThe Export Inspector isn't new anymore, time to remove its predecessor and clean up some code.
- [x] remove Temporal Script Plugin
- [x] remove Catalyst Script Generator Wizard and Catalyst Writers
- [x] transition tests that use the ol...The Export Inspector isn't new anymore, time to remove its predecessor and clean up some code.
- [x] remove Temporal Script Plugin
- [x] remove Catalyst Script Generator Wizard and Catalyst Writers
- [x] transition tests that use the old GUI
https://gitlab.kitware.com/paraview/paraview/merge_requests/3627
- [x] update the documentation to describe the new GUI instead of the old plugin
https://gitlab.kitware.com/paraview/paraview-guide-ce/commit/d01f71c0d4c477bcfc358e1c46587dcfa48a49a4
https://gitlab.kitware.com/paraview/paraview-guide-ce/merge_requests/94
https://gitlab.kitware.com/paraview/paraview-tutorial/merge_requests/10
- [ ] remove Catalyst Writers XML definitions, while keeping backward compatibility
- [ ] remove original INVERTIBLE_LUT value rendering approach
https://gitlab.kitware.com/vtk/vtk/merge_requests/6062
https://gitlab.kitware.com/paraview/paraview/merge_requests/3640
- [ ] remove old python code paths in cpstate.py, cinema and others, streamline what remains. For example outward facing pose camera.
https://gitlab.kitware.com/paraview/paraview/merge_requests/36355.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19375visible hidden edges in v5.7.02019-11-27T22:03:08-05:00Mario Binkowskivisible hidden edges in v5.7.0Hidden edges are (partly) visible with ParaView 5.7.0
```python
#from paraview.simple import *
box1 = Box()
renderView1 = GetActiveViewOrCreate('RenderView')
renderView1.ResetCamera()
box2 = Box()
box2.Center = [100.0, 100.0, 100.0]
#b...Hidden edges are (partly) visible with ParaView 5.7.0
```python
#from paraview.simple import *
box1 = Box()
renderView1 = GetActiveViewOrCreate('RenderView')
renderView1.ResetCamera()
box2 = Box()
box2.Center = [100.0, 100.0, 100.0]
#box2.Center = [150.0, 150.0, 150.0]
#box2.Center = [200.0, 200.0, 200.0]
appendGeometry1 = AppendGeometry(Input=[box1, box2])
appendGeometry1Display = Show(appendGeometry1, renderView1)
appendGeometry1Display.SetRepresentationType('Surface With Edges')
```
The extent of visible hidden edges depends on the relation of cell size and model size. To make this more clear you can fiddle with box2.Center in the example above. Did I miss any settings to avoid this behavior?https://gitlab.kitware.com/paraview/paraview/-/issues/19376more time support for vtm files2022-06-28T13:48:23-04:00Boonthanome Nouanesengsymore time support for vtm filesRight now the Paraview in-situ adaptors at LANL are writing out vtk multiblock files (vtm). Both the simulation time and cycle time are written out as field data, which can then be shown on a Renderview using the Annotate Global Data Fil...Right now the Paraview in-situ adaptors at LANL are writing out vtk multiblock files (vtm). Both the simulation time and cycle time are written out as field data, which can then be shown on a Renderview using the Annotate Global Data Filter. Unfortunately, this does not extend to the pipeline and GUI, and this frustrates users that want to see and plot with the actual time of the data.
There seems to be time support in VTK and Paraview. The PVD format appears to have time support. But this time support is not in vtm files. We are already writing some time information to vtm files, so it would be great to add support for vtm files to properly insert time information into the pipeline and for the GUI to recognize it.
Things I'd like to be able to do with vtm files:
- have the 'Time:' box at the top reflect the simulation time or cycle number. that box updates correctly as you step through the timesteps.
- be able to query the time of a vtm file easily in scripts and code. something like data.GetTime(), so people can easily do quantitative calculations with time, or make their own graphs and charts.
- create a plot over time, and the simulation time or cycle number is used for the x-axis
- the annotate time filter works correctly
Proposed ways to do this:
A. extend the xml file formats to allow for a time tag that the pipeline and gui will recognize. this would be nice in that all vtk xml file formats can now specify time, not just vtm files.
B. add an option to the readers to choose which field data to treat as time. this is nice as the user can choose to either use cycle number or simulation time as their official 'time' when loading their data.
C. designate some field data names as keywords, and if a dataset has certain keywords, use that field data as time. for example, check if 'simulation_time' exists in the field data, and if so use that as time.
D. create a filter that applies a certain field data as time
Sample Dataset: [mg_diff.tar.gz](/uploads/a04bbc3885c813809198e0bb250b079c/mg_diff.tar.gz)
Below is a screenshot of what I'm talking about. @patchett2002 @demarle @cmbiwer
![time](/uploads/333257cb17a3426caf7358dbd1f51a10/time.png)5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19377legend font size settings not respected when saving animation for split-view ...2021-04-07T11:04:23-04:00Paul Navrátillegend font size settings not respected when saving animation for split-view layoutHello,
I stumbled on a corner case in the Save Animation feature that I at least wanted to put on the radar. If you change the font size for a legend in a split-view layout and then use Save Animation and click "Save All Views", the leg...Hello,
I stumbled on a corner case in the Save Animation feature that I at least wanted to put on the radar. If you change the font size for a legend in a split-view layout and then use Save Animation and click "Save All Views", the legend font size resets to default (16 point). If you only save one view, the legend font size settings are kept. It appears to be related to the window adjustments that ParaView makes in order to combine the views for the final render.
I've attached a screen-capture showing the legends (set to Arial 12 for title and Arial 8 for text/annotation) and an output frame from the animation showing the larger font results.
Thanks!
![Screen_Shot_2019-10-09_at_3.23.26_PM](/uploads/7b238b6786bbe23de5845c4b88733794/Screen_Shot_2019-10-09_at_3.23.26_PM.png)
![3d_diptych.0047](/uploads/f92ef95846c6edb5ed0db9b1e5642c1d/3d_diptych.0047.png)https://gitlab.kitware.com/paraview/paraview/-/issues/19378[Plugin] UI_FILES must be in the main directory so autouic can find them2020-05-21T20:01:34-04:00Mathieu Westphal (Kitware)[Plugin] UI_FILES must be in the main directory so autouic can find themIn the current implementation, UI_FILES must be in the directory where the paraview_add_plugin takes place.
Hence the following **does not work** :
```
set(ui_files
Ressource/myFile.ui)
paraview_add_plugin(Plugin
...
UI_FILES ...In the current implementation, UI_FILES must be in the directory where the paraview_add_plugin takes place.
Hence the following **does not work** :
```
set(ui_files
Ressource/myFile.ui)
paraview_add_plugin(Plugin
...
UI_FILES ${ui_files})
```
while this works perfectly
```
set(ui_files
myFile.ui)
paraview_add_plugin(Plugin
...
UI_FILES ${ui_files})
```
Here is a slightly modified version of the SierraPlotToolsPlugin that shows this behavior.
[SierraPlotToolsStandAlone.tgz](/uploads/f8023e2248b599c438ae93af26e15b3b/SierraPlotToolsStandAlone.tgz)
```
-- Build files have been written to: /home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/build
[ 5%] Automatic MOC and UIC for target SierraPlotTools
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqPlotVariablesDialog.cxx"
The file includes the uic file "ui_pqVariablePlot.h",
but the user interface file "pqVariablePlot.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqVariablePlot.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqPlotter.cxx"
The file includes the uic file "ui_pqSierraToolsRichTextDocs.h",
but the user interface file "pqSierraToolsRichTextDocs.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraToolsRichTextDocs.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsDataLoadManager.cxx"
The file includes the uic file "ui_pqSierraPlotToolsDataLoadManager.h",
but the user interface file "pqSierraPlotToolsDataLoadManager.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsDataLoadManager.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsManager.cxx"
The file includes the uic file "ui_pqSierraPlotToolsActionHolder.h",
but the user interface file "pqSierraPlotToolsActionHolder.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsActionHolder.ui"
AutoUic error
-------------
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqSierraPlotToolsManager.cxx"
The file includes the uic file "ui_pqVariablePlot.h",
but the user interface file "pqVariablePlot.ui"
could not be found in the following locations
"/home/glow/work/paraview/paraviewFirst/paraview/Plugins/SierraPlotToolsStandAlone/Plugin/pqVariablePlot.ui"
make[2]: *** [Plugin/CMakeFiles/SierraPlotTools_autogen.dir/build.make:58: Plugin/CMakeFiles/SierraPlotTools_autogen] Error 1
make[1]: *** [CMakeFiles/Makefile2:122: Plugin/CMakeFiles/SierraPlotTools_autogen.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
```5.9 (Fall 2020)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/19379CMake can't enable VTK::IOOggTheora2019-10-11T08:34:40-04:00Charles GueunetCMake can't enable VTK::IOOggTheoraThe VTK target `VTK::IOOggTheora` is shown as an *OPTIONAL_DEPENDS* on the *ParaViewCore/Animation/vtk.module* but there is no option on the ParaView CMake to enable this target.The VTK target `VTK::IOOggTheora` is shown as an *OPTIONAL_DEPENDS* on the *ParaViewCore/Animation/vtk.module* but there is no option on the ParaView CMake to enable this target.https://gitlab.kitware.com/paraview/paraview/-/issues/19380VTK::FiltersParallelVerdict is missing2020-01-14T11:06:26-05:00Lutz HofmannVTK::FiltersParallelVerdict is missingUsing the `Cell Size` filter causes ParaView to crash with error
```
vtkSIProxy.cxx:408 ERR| vtkSISourceProxy (0x563cc6884000): Failed to create 'vtkPCellSizeFilter'. ...
```
This is caused by a missing VTK::FiltersParallelVerdict mod...Using the `Cell Size` filter causes ParaView to crash with error
```
vtkSIProxy.cxx:408 ERR| vtkSISourceProxy (0x563cc6884000): Failed to create 'vtkPCellSizeFilter'. ...
```
This is caused by a missing VTK::FiltersParallelVerdict module.
Steps to reproduce: 1. Create Line source 2. Apply Cell Size filter
Tested with ParaView v5.7.0 (binaries from paraview.org, and built from source). The issue is not present in ParaView v5.6.2.
#### Workaround
VTK built from master is also not building VTK::FiltersParallelVerdict by default, but it can be enabled by setting `VTK_MODULE_ENABLE_VTK_FiltersParallelVerdict=YES`.
The same can be done to fix the issue with ParaView, even though the VTK_MODULE_ENABLE... variables do not appear in CMake cache.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19381ParaView crashes on data load and visibility toggle with Dell Windows update2019-10-31T13:16:12-04:00Laura OelsnerParaView crashes on data load and visibility toggle with Dell Windows updateI've tried with different releases (5.6 and 5.7: ParaView-5.7.0-MPI-Windows-Python3.7-msvc2015-64bit, ParaView-5.7.0-Windows-Python3.7-msvc2015-64bit, and ParaView-5.6.2-MPI-Windows-msvc2015-64bit). When I load my data or example visuali...I've tried with different releases (5.6 and 5.7: ParaView-5.7.0-MPI-Windows-Python3.7-msvc2015-64bit, ParaView-5.7.0-Windows-Python3.7-msvc2015-64bit, and ParaView-5.6.2-MPI-Windows-msvc2015-64bit). When I load my data or example visualization data, the GUI either goes fuzzy or entirely black. I can't say the timing for sure, but this started happening after a Dell Windows update.
One way to reproduce fuzzy GUI:
* open ParaView-5.7.0-MPI-Windows-Python3.7-msvc2015-64bit
* open example visualization can.ex2 (Exodus II file with timesteps, Clip filter)
* turn on visibility of can.ex2 --> fuzzy and rendering artifacts (see attached screenshot)
One way to reproduce all-black window:
* open ParaView-5.7.0-MPI-Windows-Python3.7-msvc2015-64bit
* open example visualization can.ex2 (Exodus II file with timesteps, Clip filter)
* toggle visibility of Clip2 on and off --> entirely black window (see attached screenshot)
Screenshots of my graphics driver, all black GUI, and fuzzy GUI:
![Driver](/uploads/65bb2a8efd8403860476925e37beacc4/Driver.PNG)
![blackScreen](/uploads/afd6fb535f11d5052eb34a223eff8782/blackScreen.PNG)
![fuzzyCanSample](/uploads/105ba876e338911aeb695017c531b825/fuzzyCanSample.PNG)
EDIT: In both cases, when the window goes fuzzy or black, I am still able to click on buttons, although there might be some distance between the button and where my cursor is. Pop-up windows from clicking buttons in the Display tab under properties, for example, are full resolution. Likewise, if I pull the Animation View panel out of the main window and into its own window, it becomes full resolution.https://gitlab.kitware.com/paraview/paraview/-/issues/19382Eye Dome Lighting is different with Axes Grid on2024-03-07T20:47:10-05:00Boonthanome NouanesengsyEye Dome Lighting is different with Axes Grid onThe Eye Dome Lighting view is shading differently depending on if the Axes Grid is on or off, and behavior is also different if using Paraview locally or with client-server. With Axes Grid on, the shading is lighter than when Axes Grid i...The Eye Dome Lighting view is shading differently depending on if the Axes Grid is on or off, and behavior is also different if using Paraview locally or with client-server. With Axes Grid on, the shading is lighter than when Axes Grid is off.
When using Paraview locally, the shading is identical with Axes Grid on or off. But if Polar Axes is toggled, then the shading looks different.
When using Paraview in client-server mode, the shading is different when toggling Axes Grid and Polar Axes.
Images of toggling Axes Grid in client-server mode. It would be ideal of the lighting was always like the lighter version, looking like with the Axes Grid turned on.
![client-server-no-axes-small](/uploads/91a2601a1e7794c96c38242149b1da24/client-server-no-axes-small.png)![client-server-axes-small](/uploads/4b72b2893ae57d529b06914e8663f3b5/client-server-axes-small.png)
I have tested the client-server behavior with Paraview 5.5.2, as that's the most current version we support for client-server connections. I've tested the local behavior with the head of the git master from about a week ago.
Unfortunately the data is too large to post, but if anyone would like it I can send it. It's about 150 MB compressed.
How to reproduce:
- load the Eye Dome Lighting plugin
- create a new view of type Eye Dome Lighting
- load the dataset
- in the Properties Tab, change the Point Size to 3
- toggle the Data Axes Grid or Polar Axes checkbox on and off5.13 (Summer 2024)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/19383remove openssl libs from windows binaries2020-01-14T11:06:27-05:00Utkarsh Ayachitremove openssl libs from windows binariesremove openssl libs from windows binaries
cc: @ben.boeckel @cory.quammenremove openssl libs from windows binaries
cc: @ben.boeckel @cory.quammen5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19384Add cylinder widget for hyper tree grid clip2019-10-17T10:42:54-04:00Yohann Bearzi (Kitware)Add cylinder widget for hyper tree grid clipThere is no cylinder widget yet for clipping hyper tree grids. This feature should be added to resemble more the gui of regular data sets.There is no cylinder widget yet for clipping hyper tree grids. This feature should be added to resemble more the gui of regular data sets.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19385StreamTracerWithCustomSource of ParaView 5.7 with SurfaceStreamlines = 1 goes...2022-08-22T11:07:19-04:00Emanuele LeggioStreamTracerWithCustomSource of ParaView 5.7 with SurfaceStreamlines = 1 goes up to 20 times slower than previous versions of ParaViewI conducted many tests with ParaView 5.7 and I noticed that by activating the SurfaceStreamlines in StreamTracerWithCustomSource filter the processing times have increased a lot.
To prove this claim I considered 3 cases with increasing...I conducted many tests with ParaView 5.7 and I noticed that by activating the SurfaceStreamlines in StreamTracerWithCustomSource filter the processing times have increased a lot.
To prove this claim I considered 3 cases with increasing numbers of cells, all surfaces are with triangular mesh, seed point come from the surfaces.
| case | seed point | cell |
| :-----: | :-----: | :-----: |
| A | 1260 | 688294 |
| B | 11044 | 5531204 |
| C | 92947 | 40727434 |
I have tested 4 pre-builded versions of ParaView and two SuperBuild:
Pre-build:
* 5.3.0
* 5.4.1
* 5.5.2
* 5.7.0
SuperBuild:
* 5.6.0 (PV5.6SB)
* 5.7.0 (PV5.7SB)
I tested both the case with SurfaceStreamlines = 1 and SurfaceStreamlines = 0.
Each test was repeated 3 times in order to average the times; only with PV5.7SB I did only one run for each test. A little less than 100 runs in total.
To complete the analysis I report the number of points and cells of the final result in addition to the processing times.
Obviously all the tests were conducted on the same machine with the same operating system and in a serial manner without other processes.
RESULTS:
![results1](/uploads/6c1f2899eadfa1ddd2994f55b2a0167d/results1.png)
in the attachment you can find the two simple scripts I used to do this analysis and all the intermediate results logs.
[execute_streamTraceWCS.py](/uploads/b6ea9703fcb78bd4cd8ff13a631fba39/execute_streamTraceWCS.py)
[main_launch.py](/uploads/0a0d86374565e7b8aeb300f9f78b2425/main_launch.py)
[results.tar.gz](/uploads/f3a762a2546bfad325cb50a01d2c3d98/results.tar.gz)https://gitlab.kitware.com/paraview/paraview/-/issues/19386Resample to Hyper Tree Grid: cell version2020-02-24T17:14:30-05:00Yohann Bearzi (Kitware)Resample to Hyper Tree Grid: cell version`vtkResampleToHyperTreeGrid` currently only supports point data input. The way the filter is implemented really fits this kind of data. One can dump each new input in a `vtkAbstractAccumulator` either by summing a function of the input (...`vtkResampleToHyperTreeGrid` currently only supports point data input. The way the filter is implemented really fits this kind of data. One can dump each new input in a `vtkAbstractAccumulator` either by summing a function of the input (using a `vtkArithmeticAccumulator`), by sorting each point in an array to extract a quantile (using a `vtkQuantileAccumulator`), or by incrementing by one bins, for the entropy for example (using a `vtkBinsAccumulator`).
Then classes based on `vtkAbstractArrayMeasurement` can take the output of those `vtkAbstractAccumulator` and produce the desired measure.
I refactored the code a bit in https://gitlab.kitware.com/paraview/paraview/merge_requests/3625, which should be merged soon. The naming in the previous paragraph matches this new implementation.
However, obviously, cell data cannot directly fit in this framework. Let's see how we can modify the paradigm to make it happen. Let's only consider `vtkCell3D` for the moment. The challenge is to make the resampling filter a unified framework for points and volumetric cells. If one has that, generalizing to 2D cells or 1D cells should be a piece of cake.
The most straightforward way to make this filter perform the same action as with the point-wise version is to consider points as volumetric objects, which is possible using 3D Dirac distributions $`\delta_{p_i}`$, centered at point $`p_i`$, such that
```math
\left\{
\begin{array}{l}
\delta_{p_i}((x,y,z) = \not \ p_i) = 0\\
\int\int\int \delta_{p_i}(x,y,z)dxdydz = 1
\end{array}
\right.
```
If one can translate the point-wise computation to a computation dealing with volumes, it is very straightforward to feed any volumetric cell as inputs instead. Let us note $`\delta_i`$ such that if the input is formed of points, $`\delta_i=\delta_{p_i}`$, and if the input is a volumetric cell $`c_i`$, $`\delta_i(p) = 1`$ if $`p\in c_i`$, and $`\delta_i(p)=0`$ elsewhere.
Let us note $`\omega_i(C)`$ the intersection volume between a hyper tree cell $`C`$ and the point / cell $`i`$. By definition:
```math
\omega_i(C) =\int\int\int_{(x,y,z)\in C} \delta_i(x,y,z)dxdydz
```
Thus, for example, what is actually calculated for `vtkArithmeticAccumulator`, is the integral over the cells of a function $`f`$ of Dirac distributions scaled by their associated value $`\alpha_i`$, weighted by $`\omega_i(C)`$. In other words, this accumulated value $`\mathcal A(c)`$ has the expression:
```math
\mathcal A(C) = \sum_i \omega_i(C) f(\alpha_i)
```
What is incremented in the bin for $`v_i`$ of `vtkBinsAccumulator` is the intersection volume between those Diracs and the current hyper tree cell. Thus, given a regular discretization $`(b_j)_{j\in\mathbb Z}`$ of the space of values, the bin $`\mathcal B_{[b_j, b_{j+1}[}(C)`$ follows:
```math
\mathcal B_{[b_j, b_{j+1}[}(C) = \sum_{\alpha_i\in[b_j,b_{j+1}[} \omega_i(C)
```
Similarly this intersection volume is what is used in to compute the quantile as a width of each element. The quantile $`\mathcal Q_x(C)`$ is then defined as:
```math
\begin{array}{ll}
\mathcal Q_x(C) =& \text{argmin}_{\alpha_i} \left(x - \frac{\sum_{\alpha_j \le \alpha_i}\omega_j(C)}{\sum_j \omega_j(C)} \ge 0\right)
\end{array}
```
In addition to this, it should be possible to resample `vtkPolyData` with cells of different inner dimension. This can be dealt with by picturing the co-dimensions of those cells to be Diracs. One would also need to add a parameter to scale the influence of points / lines / polygons / polyhedron that could be hidden in the advanced parameters in the GUI. If one plays with such scale factors while dealing with cells of the same inner dimension, the result of the resampling would not be altered.
So basically the goal in this update is to compute the intersected volume between 3D cells / hyper tree grid cells, which would be set as the weight $`\omega_i(c)`$. The version for 2D or 1D cells will respectively be the intersected area / length of the cell and the hyper tree grid cell.
@patchett2002 @ethan.stam Are we in the same page?
@demarle FYI5.9 (Fall 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19387Calculator input is broken2020-03-23T22:08:33-04:00W. Alan ScottCalculator input is brokenCalculator input is broken. This is probably due to #19323.
The problem is that we want to handle edit boxes that seperate the interaction of only numbers input boxes (click on it, and it highlights, type it then replaces) from formu...Calculator input is broken. This is probably due to #19323.
The problem is that we want to handle edit boxes that seperate the interaction of only numbers input boxes (click on it, and it highlights, type it then replaces) from formula input boxes (select something, it highlights, select something else, the original gets wiped out). Here is how to replicate:
* Master (v5.7.0-537-g96ce074), local server, Linux.
* Sources/ Fast Uniform Grid. Apply.
* Calculator. Important!!!! - Click in the formula box. Scalars/ coordsX, then *. Note that the coordsX was highlighted, and is now replaced by the *.
This is a bug.
5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19388CGNS, and ExtractSubsetWithSeed, is wireframe2019-10-29T16:11:44-04:00W. Alan ScottCGNS, and ExtractSubsetWithSeed, is wireframeCGNS is loading as a wireframe. Since we want to apply filters to CGNS that require an outside surface, these filters fail. Further, it can be confusing why these filters fail.
Please have all CGNS datasets load as solid.
Here is h...CGNS is loading as a wireframe. Since we want to apply filters to CGNS that require an outside surface, these filters fail. Further, it can be confusing why these filters fail.
Please have all CGNS datasets load as solid.
Here is how to replicate the issue Watney had:
* Linux, remote server (64 ranks, but builtin server will show the problem - slowly...), master.
* Load Watney CGNS dataset. Should be 144 files. Turn on velocity_1, velocity_2 and velocity_3. Apply.
* Calculator. (Note - do NOT click in the formula box. #19387.). Formula will be velocity_1*iHat+velocity_2*jHat+velocity_3*kHat. Apply.
* ExtractSubsetWithSeed filter. Use 'p' key to make a cell selection.
Doesn't work, we need a surface. This is a bug.5.8 (Winter 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19389HTG scalar clip filter has no output on invert2019-10-28T17:33:31-04:00Ethan StamHTG scalar clip filter has no output on invert@demarle @yohann.bearzi @patchett2002
Found on MacOS with 5.7.0-561-g50d981fa96
The Hyper Tree Grid scalar clip filter has no output when "Invert" is checked. It is expected to invert the scalar clip like the unstructured grid clip doe...@demarle @yohann.bearzi @patchett2002
Found on MacOS with 5.7.0-561-g50d981fa96
The Hyper Tree Grid scalar clip filter has no output when "Invert" is checked. It is expected to invert the scalar clip like the unstructured grid clip does.
To recreate:
1. Sources -> Hyper Tree Grid (random) -> Apply
2. Clip filter -> Choose scalar in the "Hyper Tree Grid Clipper" drop down -> Set the value to 2
3. Check the "Invert" box -> Apply
There is no output in RenderView1. Comparing to the same clip on an unstructured grid in RenderView2:
![Screen_Shot_2019-10-14_at_1.10.19_PM](/uploads/363d0e1d0dec65e3f67ef6d4f7e159be/Screen_Shot_2019-10-14_at_1.10.19_PM.png)5.8 (Winter 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19390Volume rendering of vectors is wrong2020-08-25T17:34:11-04:00W. Alan ScottVolume rendering of vectors is wrongVolume rendering of vector data is wrong. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* disk_out_ref.exo. All vars on. Apply.
* Paint by V. Volume render.
Bug. Notice that you only see one half of the disk_out_ref.ex...Volume rendering of vector data is wrong. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* disk_out_ref.exo. All vars on. Apply.
* Paint by V. Volume render.
Bug. Notice that you only see one half of the disk_out_ref.exo. What you see should be symmetric.
Interesting - Change the color legend to be -22 to 22. Now, you see there are actually negative components!
To see what I would expect, do as follows:
* calculator. Formula is mag(V). Apply.
* Paint by Result. Volume Render.
![Capture](/uploads/037f280e890e67be8a0a3c8443cda407/Capture.PNG)
My guess is we have two options. Either not allow volume rendering of vectors, or calculate the magnitude of these vectors.5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/19391ExtractSubsetWithSeed crashes on CGNS dataset2019-11-04T21:38:38-05:00W. Alan ScottExtractSubsetWithSeed crashes on CGNS datasetWe have a crash using ExtractSubsetWithSeed, on the HiFiRE-1_run34_3L, sparc-volume CGNS dataset. Here is how to replicate.
* Master (ParaView is v5.7.0-537-g96ce074, Superbuild is v5.7.0-91-gf77a7db), Linux, remote server (64 ranks).
...We have a crash using ExtractSubsetWithSeed, on the HiFiRE-1_run34_3L, sparc-volume CGNS dataset. Here is how to replicate.
* Master (ParaView is v5.7.0-537-g96ce074, Superbuild is v5.7.0-91-gf77a7db), Linux, remote server (64 ranks).
* Turn on ONLY blk-3. Turn on all variables, EXCEPT nonlinear*. Apply.
* Surface.
* +Z.
* ExtractSubsetWithSeed. ij(plane). <ctrl>-p right in the middle of the concave center. Make sure something was found. Apply.
Crash, server side. Here is what I think is important:
```
32 0x401609 /snip/pvserver() [0x401609]
31 0x2aaaaacf1545 __libc_start_main + 245
30 0x401acc /snip/pvserver() [0x401acc]
29 0x401a22 /snip/pvserver() [0x401a22]
28 0x2aaab106a784 vtkMultiProcessController::ProcessRMIs() + 34
27 0x2aaab106a7d1 vtkMultiProcessController::ProcessRMIs(int, int) + 75
26 0x2aaab106a3b6 vtkMultiProcessController::BroadcastProcessRMIs(int, int) + 258
25 0x2aaab106b184 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 786
24 0x2aaaace0ffde /snip/bin/../lib/libvtkPVServerImplementationCore-pv5.7.so.1(+0x88fde) [0x2aaaace0ffde]
23 0x2aaaace12212 vtkPVSessionCore::ExecuteStreamSatelliteCallback() + 212
22 0x2aaaace12332 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 222
21 0x2aaaad954dfd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 67
20 0x2aaaad954f4f vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 309
19 0x2aaaad95591f vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 453
18 0x2aaaad957199 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 679
17 0x2aaaab46ce2c /snip/bin/../lib/libvtkPVServerManagerApplication-pv5.7.so.1(+0x3cfe2c) [0x2aaaab46ce2c]
16 0x2aaaace5d3b4 vtkSISourceProxy::UpdatePipeline(int, double, bool) + 560
15 0x2aaab1b2bfb0 vtkStreamingDemandDrivenPipeline::Update(int) + 48
14 0x2aaab1b2c124 vtkStreamingDemandDrivenPipeline::Update(int, vtkInformationVector*) + 370
13 0x2aaab1acd3a7 vtkDemandDrivenPipeline::UpdateData(int) + 679
12 0x2aaab1b2bd85 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
11 0x2aaab1accb98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1208
10 0x2aaab1ac5964 vtkCompositeDataPipeline::ForwardUpstream(vtkInformation*) + 766
9 0x2aaab1b2bd85 vtkStreamingDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2991
8 0x2aaab1accc98 vtkDemandDrivenPipeline::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1464
7 0x2aaab1ac322a vtkCompositeDataPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 1022
6 0x2aaab1acd54d vtkDemandDrivenPipeline::ExecuteData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 103
5 0x2aaab1ad4cae vtkExecutive::CallAlgorithm(vtkInformation*, int, vtkInformationVector**, vtkInformationVector*) + 118
4 0x2aaab1acb092 vtkDataObjectAlgorithm::ProcessRequest(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 90
3 0x2aaac2eb05c6 vtkExtractSubsetWithSeed::RequestData(vtkInformation*, vtkInformationVector**, vtkInformationVector*) + 2046
2 0x2aaac2e4a5c7 /snip/bin/../lib/libvtkFiltersParallelDIY2-pv5.7.so.1(+0x8b5c7) [0x2aaac2e4a5c7]
1 0x2aaac2e46fc4 /snip/bin/../lib/libvtkFiltersParallelDIY2-pv5.7.so.1(+0x87fc4) [0x2aaac2e46fc4]
0 0x2aaaaad053f0 /lib64/libc.so.6(+0x363f0) [0x2aaaaad053f0]
```5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19392Change default volume fraction value for ExtractCTHParts2020-10-27T21:35:17-04:00W. Alan ScottChange default volume fraction value for ExtractCTHPartsIn the ExtractCTHParts filter, please change the Volume Fraction Value default to be 0.45. This looks better, and was recommended by our resident experts.
Marking as 5.8 since I believe it is trivial, OK to slip to 5.9.In the ExtractCTHParts filter, please change the Volume Fraction Value default to be 0.45. This looks better, and was recommended by our resident experts.
Marking as 5.8 since I believe it is trivial, OK to slip to 5.9.5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19393HTG Clip filter cannot invert on 'Plane', 'Sphere', 'Cylinder', 'Quadric', 'Box'2024-03-07T20:47:10-05:00Yohann Bearzi (Kitware)HTG Clip filter cannot invert on 'Plane', 'Sphere', 'Cylinder', 'Quadric', 'Box'The invert flag in `vtkHyperTreeGridAxisClip` filter is only taken into account in the axis aligned plane version. The algorithm needs to be changed to add this functionality for all methods.The invert flag in `vtkHyperTreeGridAxisClip` filter is only taken into account in the axis aligned plane version. The algorithm needs to be changed to add this functionality for all methods.5.13 (Summer 2024)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19394Add stereo options to 'Save Screenshot'2019-10-21T12:33:08-04:00Ethan StamAdd stereo options to 'Save Screenshot'@demarle @patchett2002
Add the option to 'Save Screenshot' with stereo capabilities like those seen in 'Save Animation'
![Screen_Shot_2019-10-15_at_9.46.00_AM](/uploads/cb98d9adce173ec6533905801792b72a/Screen_Shot_2019-10-15_at_9.46.0...@demarle @patchett2002
Add the option to 'Save Screenshot' with stereo capabilities like those seen in 'Save Animation'
![Screen_Shot_2019-10-15_at_9.46.00_AM](/uploads/cb98d9adce173ec6533905801792b72a/Screen_Shot_2019-10-15_at_9.46.00_AM.png)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/19396No scalar values when saving a matplotlib plot of 2D image data2020-12-09T21:29:31-05:00Ethan StamNo scalar values when saving a matplotlib plot of 2D image data@terryturton @dhr
Found with ParaView 5.7.0
We are using the following programmable filter to save a matplotlib plot within a catalyst script:
```python
import matplotlib.pyplot as plt
import numpy as np
import vtk
from vtk.util.numpy...@terryturton @dhr
Found with ParaView 5.7.0
We are using the following programmable filter to save a matplotlib plot within a catalyst script:
```python
import matplotlib.pyplot as plt
import numpy as np
import vtk
from vtk.util.numpy_support import vtk_to_numpy
PNGOutputFilename = "plot.png"
indata = self.GetInput()
array = indata.GetPointData().GetArray("RTData")
if (array):
np_array = vtk_to_numpy(array)
plt.close()
plt.plot(np_array)
plt.savefig(PNGOutputFilename)
```
With 2D image data, we get the error:
```No scalar values found for texture input!```
The image of the plot does still get saved, but this error causes the in situ use case to hang.
To recreate (In the GUI):
* Sources -> Wavelet -> Apply
* Filters -> Slice -> Apply
* Filters -> Resample to Image -> set the dimensions to 1,100,100 -> Apply
* Filters -> Programmable Filter -> copy and paste the script above -> Apply5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19397Ffmpeg support - libavresample is deprecated2019-10-16T09:16:40-04:00Henrique GropelliFfmpeg support - libavresample is deprecatedHello! Ffmpeg when compiled from latest version from git, doesn't build anymore libavresample which were switched to libswresample. While cmake is searching for libavresample.Hello! Ffmpeg when compiled from latest version from git, doesn't build anymore libavresample which were switched to libswresample. While cmake is searching for libavresample.Ken MartinKen Martinhttps://gitlab.kitware.com/paraview/paraview/-/issues/19398Lines are bleading through thin objects, Sufrace with Edges, Parallel2024-03-07T20:47:10-05:00W. Alan ScottLines are bleading through thin objects, Sufrace with Edges, ParallelWe are having lines bleeding through thin objects, such as the seat of a chair, parallel projection, with Surface with Edges. This was first reported here: https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769. ...We are having lines bleeding through thin objects, such as the seat of a chair, parallel projection, with Surface with Edges. This was first reported here: https://discourse.paraview.org/t/surface-with-edges-representation-in-5-7/2769. Dataset in this bug works well (chair.obj), but here is another way to replicate:
* Linux, 5.7.0, builtin server.
* Load disk_out_ref.exo. Apply.
* Slice filter. Apply.
* Linear Extrusion filter. Vector == 1, 0, 0. Scale Factor == 0.2. Apply.
* Projects/ Camera Parallel Projection.
* Surface with Edges.
Now, by varying Scale Factor, you can see the lines on the back of the object come and go. 0.3 is worse, 0.4 is much better, but we have bleeding along the edges.
Somehow or another, in parallel projection, our coincident line code is WAY too extreme.
I checked, and Linux, 5.6.0, builtin server did NOT have this issue.
OK to slip to 5.9.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/19399Paraview crashes reading 7th order vtkLagrangeTriangle2020-01-31T21:20:38-05:00Jørgen Schartum DokkenParaview crashes reading 7th order vtkLagrangeTriangleThe following example causes paraview to segfault when opening. It is a seventh order LagrangeTriangle.
```
<?xml version="1.0"?>
<VTKFile type="UnstructuredGrid" version="0.1" >
<UnstructuredGrid>
<Piece NumberOfPoints="36" NumberOfCe...The following example causes paraview to segfault when opening. It is a seventh order LagrangeTriangle.
```
<?xml version="1.0"?>
<VTKFile type="UnstructuredGrid" version="0.1" >
<UnstructuredGrid>
<Piece NumberOfPoints="36" NumberOfCells="1">
<Points>
<DataArray type="Float64" NumberOfComponents="3" format="ascii">0 0 0 1 0 0 0 1 0 0.14286 0 0 0.28571 0 0 0.42857 0 0 0.57143 0 0 0.71429 0 0 0.85714 0 0 0.85714 0.14286 -0.02041 0.71429 0.28571 0.02041 0.57143 0.42857 -0.02041 0.42857 0.57143 0.02041 0.28571 0.71429 -0.02041 0.14286 0.85714 0.02041 0 0.85714 0.02041 0 0.71429 -0.02041 0 0.57143 0.02041 0 0.42857 -0.02041 0 0.28571 0.02041 0 0.14286 -0.02041 0.14286 0.14286 -0.02041 0.71429 0.14286 -0.02041 0.14286 0.71429 -0.02041 0.28571 0.14286 -0.02041 0.42857 0.14286 -0.02041 0.57143 0.14286 -0.02041 0.57143 0.28571 0.02041 0.42857 0.42857 -0.02041 0.28571 0.57143 0.02041 0.14286 0.57143 0.02041 0.14286 0.42857 -0.02041 0.14286 0.28571 0.02041 0.28571 0.28571 0.02041 0.42857 0.28571 0.02041 0.28571 0.42857 -0.02041 </DataArray>
</Points>
<Cells>
<DataArray type="UInt32" Name="connectivity" format="ascii">0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 </DataArray>
<DataArray type="UInt32" Name="offsets" format="ascii">36 </DataArray>
<DataArray type="UInt8" Name="types" format="ascii">69 </DataArray>
</Cells>
</Piece>
</UnstructuredGrid>
</VTKFile>
```
Could anyone give me any pointers on why it doesnt work?https://gitlab.kitware.com/paraview/paraview/-/issues/19400Selections, and Extract Selection, don't trace correctly.2019-10-30T20:38:40-04:00W. Alan ScottSelections, and Extract Selection, don't trace correctly.Selections, with extract selection, are not tracing correctly. Here is how to replicate:
* Linux, master (v5.7.0-537-g96ce074), builtin server.
* Start Trace.
* Open can.exo. All vars on. Apply.
* Select cells on. Select something on...Selections, with extract selection, are not tracing correctly. Here is how to replicate:
* Linux, master (v5.7.0-537-g96ce074), builtin server.
* Start Trace.
* Open can.exo. All vars on. Apply.
* Select cells on. Select something on the can.
* Extract Selection. Apply.
* Stop Trace. Save it as a macro.
* Reset session
* Run the macro.
We get the following error:
Traceback (most recent call last):
File "<string>", line 95, in <module>
NameError: name 'extractSelection1' is not defined
I don't see the selection anywhere.
The offending line is here:
# show data in view
extractSelection1Display = Show(extractSelection1, renderView1)
Watney bug.5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19401ospray amr bug2024-03-07T20:47:11-05:00Carson Brownleeospray amr bugswitching on and off ospray rendering with an amr volume appears to crash in some cases. Reproducible with amr guassian source. @demarleswitching on and off ospray rendering with an amr volume appears to crash in some cases. Reproducible with amr guassian source. @demarle5.13 (Summer 2024)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19402Hyper Tree Grid does not have Ghosts cell structure2020-01-16T18:43:27-05:00Yohann Bearzi (Kitware)Hyper Tree Grid does not have Ghosts cell structureI don't think there was an issue on that. `vtkHyperTreeGrid` does not have ghost cell structure for multi-processing. One would need ghost hyper trees so filters using super cursors can reach hyper tree interfaces with other processes.
...I don't think there was an issue on that. `vtkHyperTreeGrid` does not have ghost cell structure for multi-processing. One would need ghost hyper trees so filters using super cursors can reach hyper tree interfaces with other processes.
A filter that needs this feature is `vtkHyperTreeGridContour` filter. Right now, when applying this filter using MPI, cells at the interfaces are discarded.5.8 (Winter 2020)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19403Trace recorder is missing views2020-09-16T17:58:28-04:00W. Alan ScottTrace recorder is missing viewsThe trace recorder is missing creating a view or layout. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* Tools/ Start Trace.
* Sources/ Wavelet. Apply.
* Plot over line filter. Apply.
* File/ Save Screenshot. Save All Vie...The trace recorder is missing creating a view or layout. Here is how to replicate:
* Linux, 5.7.0, builtin server.
* Tools/ Start Trace.
* Sources/ Wavelet. Apply.
* Plot over line filter. Apply.
* File/ Save Screenshot. Save All Views - checked. OK.
* Tools/ Stop Trace. Save this python script.
Now, run this python script using pvbatch. It will fail, as follows:
( 3.216s) [main thread ]vtkSMSaveScreenshotProx:408 ERR| vtkSMSaveScreenshotProxy (0x5612fb0): Cannot WriteImage without a view or layout.
Watney bug.
Marking as required, but ok to move to Inportant if there is a manual way to edit the scripts correctly.5.8 (Winter 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19404Sidesets are rendering incorrectly2020-08-31T13:19:29-04:00W. Alan ScottSidesets are rendering incorrectlytri6 sidesets are rendering incorrectly. This works correctly with EnSight. Here is how to replicate:
* 5.7.0, Windows, builtin server.
* Open tri6sWFace2.exo. Advanced. Turn the Set on, turn the Block off. Apply.
Looks like a Pica...tri6 sidesets are rendering incorrectly. This works correctly with EnSight. Here is how to replicate:
* 5.7.0, Windows, builtin server.
* Open tri6sWFace2.exo. Advanced. Turn the Set on, turn the Block off. Apply.
Looks like a Picasso painting.
Ask me for the data. I can give it to Utkarsh or Cory.
![Capture](/uploads/e01ef857f910c4c96d4dc0826dcc1c13/Capture.PNG)5.9 (Fall 2020)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19405Hyper Tree Grid documentation2021-11-11T14:19:58-05:00Yohann Bearzi (Kitware)Hyper Tree Grid documentationThe Hyper Tree Grid documentation is extremely poor, and sometimes in French... At some point a large sweep needs to be done to make it easier for users.The Hyper Tree Grid documentation is extremely poor, and sometimes in French... At some point a large sweep needs to be done to make it easier for users.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/19406Sources/ Ellipse misses one segment2020-06-16T12:21:04-04:00W. Alan ScottSources/ Ellipse misses one segmentSources/ Ellipse misses one segment. Here is how to replicate:
* Linux, master, builtin server.
* Sources/ Ellipse. Resolution 4. Start Angle 0. Sector Angle 90. Apply. I will call this ellipse-0.
* Sources/ Ellipse. Resolution 4...Sources/ Ellipse misses one segment. Here is how to replicate:
* Linux, master, builtin server.
* Sources/ Ellipse. Resolution 4. Start Angle 0. Sector Angle 90. Apply. I will call this ellipse-0.
* Sources/ Ellipse. Resolution 4. Start Angle 90. Sector Angle 90. Apply. I will call this ellipse-90.
These two partial ellipses should touch, but don't.
* Change ellipse-0 and ellipse-90 to be non-Closed.
This is what I would expect. Now, they touch correctly. Close and non-Close should look exactly the same, only one has a closing line.
This is a Watney bug.5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19407probe isn't working with ctrl p2021-03-24T06:06:57-04:00W. Alan Scottprobe isn't working with ctrl pThe <ctrl>p option for probe isnt' working. Here is how to replicate:
* Sources/ FastUniformGrid. Apply. Surface with edges.
* Turn Auto Apply On. (I don't think this step is needed.)
* Probe. Now, <ctrl>-p. Nothing happens.The <ctrl>p option for probe isnt' working. Here is how to replicate:
* Sources/ FastUniformGrid. Apply. Surface with edges.
* Turn Auto Apply On. (I don't think this step is needed.)
* Probe. Now, <ctrl>-p. Nothing happens.