ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-06-15T09:06:52-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17292vtkZLibDataCompressor.cxx, line 77 vtkZLibDataCompressor (0xfce49c0): Zlib er...2023-06-15T09:06:52-04:00Aly AbdelazizvtkZLibDataCompressor.cxx, line 77 vtkZLibDataCompressor (0xfce49c0): Zlib error while uncompressing data.Hi,
When i parse throught the time_steps using pvpython. It always returns this error if the value is > 99. This error occurs with paraview-5.0.1+dfsg1 but works on the previous versions.
ERROR: In /build/paraview-arsa8T/paraview-5.0...Hi,
When i parse throught the time_steps using pvpython. It always returns this error if the value is > 99. This error occurs with paraview-5.0.1+dfsg1 but works on the previous versions.
ERROR: In /build/paraview-arsa8T/paraview-5.0.1+dfsg1/VTK/IO/Core/vtkZLibDataCompressor.cxx, line 77
vtkZLibDataCompressor (0xfce49c0): Zlib error while uncompressing data.
ERROR: In /build/paraview-arsa8T/paraview-5.0.1+dfsg1/VTK/IO/XML/vtkXMLUnstructuredDataReader.cxx, line 517
vtkXMLUnstructuredGridReader (0x5321e50): Cannot read points array from Points in piece 0. The data array in the element may be too short.
Regards,
Aly Abdelazizhttps://gitlab.kitware.com/paraview/paraview/-/issues/17130Problem with 2D Rotation about a point using Python Programmable Filter2021-03-23T18:32:47-04:00TProblem with 2D Rotation about a point using Python Programmable FilterHi,
I am trying to transform a STL file using the "Python Programmable Filter" and follwing python code. Not sure what I'm doing wrong here!
Any help is highly appreciated.
Thanks,
Tash
```python
import math
pdi = self.GetInput()
pd...Hi,
I am trying to transform a STL file using the "Python Programmable Filter" and follwing python code. Not sure what I'm doing wrong here!
Any help is highly appreciated.
Thanks,
Tash
```python
import math
pdi = self.GetInput()
pdo = self.GetOutput()
newPoints = vtk.vtkPoints()
numPoints = pdi.GetNumberOfPoints()
for i in range(0, numPoints):
coord = pdi.GetPoint(i)
angle = math.radians(90)
ox, oy, oz = (0,0,0)
x, y, z = coord[:3]
x = ox + math.cos(angle) * (x - ox) - math.sin(angle) * (y - oy)
y = oy + math.sin(angle) * (x - ox) + math.cos(angle) * (y - oy)
z = z*1
newPoints.InsertPoint(i, x, y, z)
pdo.SetPoints(newPoints)https://gitlab.kitware.com/paraview/paraview/-/issues/17243Center Axes Visibility and Orientation Axes Visibility checkboxes not linked ...2020-10-16T17:01:59-04:00Andrew BauerCenter Axes Visibility and Orientation Axes Visibility checkboxes not linked to GUI widgetsClicking on either the Center Axes Visibility or Orientation Axes Visibility in the Properties panel fails to update enabled/disabled property of the appropriate widgets in the upper right hand side of the GUI.
Clicking on these widgets...Clicking on either the Center Axes Visibility or Orientation Axes Visibility in the Properties panel fails to update enabled/disabled property of the appropriate widgets in the upper right hand side of the GUI.
Clicking on these widgets in the GUI does properly update the checkboxes in the Properties panel though.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17124line, plane, etc inserted from "Sources" always is below the previous figure...2023-06-15T09:05:51-04:00Bin Liline, plane, etc inserted from "Sources" always is below the previous figure in paraview 5.2, but by default is above the figure in previous version.e.g paraview 5.0.1a plane inserted from "Sources" display below the previous figure by default.
![5.20](/uploads/0b9db1ed3de218ef306c775a70edaeef/5.20.png)
a plane inserted from "Sources" display above the previous figure by default, which is more conve...a plane inserted from "Sources" display below the previous figure by default.
![5.20](/uploads/0b9db1ed3de218ef306c775a70edaeef/5.20.png)
a plane inserted from "Sources" display above the previous figure by default, which is more convenient.
![5.10](/uploads/7c778373cc98bde94a0c7c805b49beea/5.10.png)https://gitlab.kitware.com/paraview/paraview/-/issues/17122ParaView 5.2.0 AMR Source Fails when AMR Cut is Applied with Obsolete 3DWidge...2018-10-04T20:36:52-04:00John PatchettParaView 5.2.0 AMR Source Fails when AMR Cut is Applied with Obsolete 3DWidget request encountered in the proxy hints. ...In ParaView 5.2.0
load AMRGaussianPulseSource click OK
Filters -> AMR -> AMR CutPlane
Message pops up: Obsolete 3DWidget request encountered in the proxy hints. Please refer to the 'Major API Changes' guide in ParaView developer docume...In ParaView 5.2.0
load AMRGaussianPulseSource click OK
Filters -> AMR -> AMR CutPlane
Message pops up: Obsolete 3DWidget request encountered in the proxy hints. Please refer to the 'Major API Changes' guide in ParaView developer documentation.https://gitlab.kitware.com/paraview/paraview/-/issues/17233Calculator does not recognize variable2020-05-06T11:15:36-04:00Dan LipsaCalculator does not recognize variableLoad wrfout.nc in paraview using 'Netcdf file and generic CF conventions' (see attached) and add a calculator filter for which select T2 as the expression.
ParaView will crash.
Note that Python Calculator works fine.
The file is at
ht...Load wrfout.nc in paraview using 'Netcdf file and generic CF conventions' (see attached) and add a calculator filter for which select T2 as the expression.
ParaView will crash.
Note that Python Calculator works fine.
The file is at
https://drive.google.com/a/kitware.com/file/d/0Bw4g1toxn8kRc0lxQkRkc1QtOXc/view?usp=sharinghttps://gitlab.kitware.com/paraview/paraview/-/issues/17117Trace failing to trace values for `SelectArrays` property on `ContingencyStat...2021-03-23T12:53:46-04:00Utkarsh AyachitTrace failing to trace values for `SelectArrays` property on `ContingencyStatistics` filter+ Start ParaView (builtin mode)
+ Open can.ex2, load all variables, Apply.
+ Start Trace (**Tools | Start Trace**)
+ Create **Contigency Statistics** filter. You'll get errors as follows:
```python
Traceback (most recent call last):
F...+ Start ParaView (builtin mode)
+ Open can.ex2, load all variables, Apply.
+ Start Trace (**Tools | Start Trace**)
+ Create **Contigency Statistics** filter. You'll get errors as follows:
```python
Traceback (most recent call last):
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 782, in finalize
trace.append(accessor.trace_ctor(ctor, filter_type))
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 471, in trace_ctor
txt = self.trace_properties(other_props, in_ctor=False)
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 443, in trace_properties
return joiner.join([x.get_property_trace(in_ctor) for x in props])
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 555, in get_property_trace
else: return "%s = %s" % (varname, self.get_value())
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/smtrace.py", line 592, in get_value
return str(myobject)
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 662, in __repr__
if self.GetData() is not None:
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 786, in GetData
return self[0:len(self)]
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 961, in __getitem__
retVal.append(self.GetAssociation())
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 940, in GetAssociation
return GetAssociationAsString(int(val))
ValueError: invalid literal for int() with base 10: 'PedigreeNodeId'
```
The **SelectArrays** is getting a PyProperty of type `ArrayListProperty` which doesn't handle properties that don't have attribute type indicate in a separate property. Need to look into this.https://gitlab.kitware.com/paraview/paraview/-/issues/17116Support mipmaps for texture applied to a surfaces.2021-04-28T20:12:34-04:00Dan LipsaSupport mipmaps for texture applied to a surfaces.Mipmaps can improve the look of surfaces with texture on them by eliminating the artifacts visible when viewing the surface at an angle.
See the two attached images.
![paraview-no-mipmap](/uploads/8ca98460a426f140a07acf1ea67053fd/paravi...Mipmaps can improve the look of surfaces with texture on them by eliminating the artifacts visible when viewing the surface at an angle.
See the two attached images.
![paraview-no-mipmap](/uploads/8ca98460a426f140a07acf1ea67053fd/paraview-no-mipmap.png)
![paraview-mipmap](/uploads/73f3adb5c639d36204784db4393ebb9c/paraview-mipmap.png)
I have done preliminary work to add mipmaps to VTK/Paraview. See the attached patch.
[mipmap.patch](/uploads/a4fc062b5e61f182f2cfcc4e4bd04b8a/mipmap.patch)https://gitlab.kitware.com/paraview/paraview/-/issues/17111`Render Text as Paths` should be unchecked by default for both 3D and chart v...2021-03-23T18:11:18-04:00Utkarsh Ayachit`Render Text as Paths` should be unchecked by default for both 3D and chart view exportingWhen `Render Text as Paths` is checked, svg and pdf exports don't have any text. Two issues:
1. Fix the broken behavior when `Render T as P` is checked.
2. ~~Should the default be unchecked? Since the text gets exported okay when unche...When `Render Text as Paths` is checked, svg and pdf exports don't have any text. Two issues:
1. Fix the broken behavior when `Render T as P` is checked.
2. ~~Should the default be unchecked? Since the text gets exported okay when unchecked.~~
3. When "Render T as P" is unchecked, and a Line Chart View is exported, the labels for axes are not anchored at the right position.
Relates to https://paraview.uservoice.com/forums/11350-general/suggestions/17702473-add-real-vector-graphics
cc: @berkgeveci https://gitlab.kitware.com/paraview/paraview/-/issues/17217Cursor does not change on resize color legend2021-03-23T13:03:40-04:00W. Alan ScottCursor does not change on resize color legendThe cursor does not change shape when we rescale the color legend. Replicate as follows:
Windows or Linux Kitware binaries of 5.3.0-RC2, local server.
Sources/ Wavelet. Apply.
Surface and color by RTData.
Now, with the mouse, try to...The cursor does not change shape when we rescale the color legend. Replicate as follows:
Windows or Linux Kitware binaries of 5.3.0-RC2, local server.
Sources/ Wavelet. Apply.
Surface and color by RTData.
Now, with the mouse, try to grab the top of the color legend and drag it smaller or larger. If you do so in exactly the correct place it works, but the cursor doesn't change shape (as it did in 5.1.2) to give you a hint when you are at the right spot.https://gitlab.kitware.com/paraview/paraview/-/issues/17290Buildbot Warning : Python 2.7 Strict Aliasing2020-05-05T21:48:12-04:00Mathieu Westphal (Kitware)Buildbot Warning : Python 2.7 Strict Aliasing```
/usr/include/python2.7/object.h:769:22: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
((PyObject*)(op))->ob_refcnt++)
^
/usr/include/python2.7/boolobjec...```
/usr/include/python2.7/object.h:769:22: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
((PyObject*)(op))->ob_refcnt++)
^
/usr/include/python2.7/boolobject.h:27:31: note: in expansion of macro 'Py_INCREF'
#define Py_RETURN_TRUE return Py_INCREF(Py_True), Py_True
```
https://open.cdash.org/viewBuildError.php?type=1&buildid=4803988
Looks like we should silence this one. Shows up only with Catalyst.https://gitlab.kitware.com/paraview/paraview/-/issues/17109X thread initialization required when Connect()ing to pvserver; pthread_mutex...2021-03-23T12:55:45-04:00tfogalX thread initialization required when Connect()ing to pvserver; pthread_mutex_lock crash inside XrmQGetSearchListUsing 7db25af8b51995d2364254f21886cfa8a5e6f666, I get a crash in `pthread_mutex_lock` inside `XrmQGetSearchList`. The underlying problem appears to be that X never initialized internal threading resources.
The crash reproduces with the...Using 7db25af8b51995d2364254f21886cfa8a5e6f666, I get a crash in `pthread_mutex_lock` inside `XrmQGetSearchList`. The underlying problem appears to be that X never initialized internal threading resources.
The crash reproduces with the attached 'crash.py':`
/path/to/pvserver &
sleep 3
env -i DISPLAY="${DISPLAY}" HOME=${HOME} /path/to/pvpython crash.py`
and the attached patch (that just calls `XInitThreads`) fixes things for me.
The crash does *not* occur if I remove the `paraview.simple.Connect()`.
The machine is Ubuntu:`
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial`
[crash.py](/uploads/74d5007bfd0509a912b7e0a2b889ab2a/crash.py)
[x-init-threads-pv-fix.diff](/uploads/b39cd4917486c5c0e7dc62ce2b09f4f3/x-init-threads-pv-fix.diff)https://gitlab.kitware.com/paraview/paraview/-/issues/17289Buildbot warning : vtkTetra.cxx Array Bounds2020-05-05T21:48:12-04:00Mathieu Westphal (Kitware)Buildbot warning : vtkTetra.cxx Array Bounds```
vtkTetra.cxx:921:26: warning: array subscript is above array bounds
```
https://open.cdash.org/viewBuildError.php?type=1&buildid=4803988
Shows up only with Catalyst for some reasons.```
vtkTetra.cxx:921:26: warning: array subscript is above array bounds
```
https://open.cdash.org/viewBuildError.php?type=1&buildid=4803988
Shows up only with Catalyst for some reasons.https://gitlab.kitware.com/paraview/paraview/-/issues/17216Sources Text - Lower Left Corner doesn't work2020-06-10T12:55:03-04:00W. Alan ScottSources Text - Lower Left Corner doesn't workThere is a checkbox for Lower Left Corner in the Sources/ Text Properties tab. This checkbox does not work.
5.3.0 RC2, Windows
Sources/ Text.
Place text in the upper left corner.
With either the Use Window Location button checked or ...There is a checkbox for Lower Left Corner in the Sources/ Text Properties tab. This checkbox does not work.
5.3.0 RC2, Windows
Sources/ Text.
Place text in the upper left corner.
With either the Use Window Location button checked or unchecked, try selecting the Lower Left Corner check box. Nothing happens.
I would argue to just remove this functionality at this point. It is confusing what it should do, and is redundant with Use Window Location.5.9 (Fall 2020)Vicente Boleavicente.bolea@kitware.comVicente Boleavicente.bolea@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17286Buildbot Warning : Doxygen errors and warnings2020-05-05T21:48:11-04:00Mathieu Westphal (Kitware)Buildbot Warning : Doxygen errors and warningshttps://open.cdash.org/viewBuildError.php?type=1&buildid=5146173
```
warning: Tag `DETAILS_AT_TOP' at line 127 of file `/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilitie...https://open.cdash.org/viewBuildError.php?type=1&buildid=5146173
```
warning: Tag `DETAILS_AT_TOP' at line 127 of file `/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/doxyfile' has become obsolete.
To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"
warning: Tag `HTML_ALIGN_MEMBERS' at line 134 of file `/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/doxyfile' has become obsolete.
To avoid this warning please remove this line from your configuration file or upgrade it using "doxygen -u"
error: When enabling GENERATE_HTMLHELP the search engine (SEARCHENGINE) should be disabled. I'll do it for you.
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/ApplicationComponents/pqParaViewBehaviors.h:42: warning: Refusing to add group Behaviors to itself
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/ParaViewCore/ClientServerCore/Rendering/vtkPVContextInteractorStyle.h:16: warning: the name `-' supplied as the argument of the \class, \struct, \union, or \include command is not an input file
<unknown>:1: warning: no matching file member found for
static void vtkChartSelectionHelper::MakeSelection(vtkAnnotationLink *link, vtkIdTypeArray *selectionIds, vtkPlot *plot)
Possible candidates:
'static void MakeSelection(vtkAnnotationLink *link, vtkIdTypeArray *selectionIds, vtkPlot *plot)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void MakeSelection(vtkAnnotationLink *link, vtkIdTypeArray *selectionIds, vtkPlot *plot)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void MakeSelection(vtkAnnotationLink *link, vtkIdTypeArray *selectionIds, vtkPlot *plot)' at line 1 of file
<unknown>:1: warning: no matching file member found for
static void vtkChartSelectionHelper::MinusSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)
Possible candidates:
'static void MinusSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void MinusSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void MinusSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)' at line 1 of file
<unknown>:1: warning: no matching file member found for
static void vtkChartSelectionHelper::AddSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)
Possible candidates:
'static void AddSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void AddSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void AddSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)' at line 1 of file
<unknown>:1: warning: no matching class member found for
static void vtkChartSelectionHelper::ToggleSelection(vtkIdTypeArray *selection, vtkIdTypeArray *oldSelection)
<unknown>:1: warning: no matching file member found for
static void vtkChartSelectionHelper::BuildSelection(vtkAnnotationLink *link, int selectionMode, vtkIdTypeArray *plotSelection, vtkIdTypeArray *oldSelection, vtkPlot *plot)
Possible candidates:
'static void BuildSelection(vtkAnnotationLink *link, int selectionMode, vtkIdTypeArray *plotSelection, vtkIdTypeArray *oldSelection, vtkPlot *plot)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void BuildSelection(vtkAnnotationLink *link, int selectionMode, vtkIdTypeArray *plotSelection, vtkIdTypeArray *oldSelection, vtkPlot *plot)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static void BuildSelection(vtkAnnotationLink *link, int selectionMode, vtkIdTypeArray *plotSelection, vtkIdTypeArray *oldSelection, vtkPlot *plot)' at line 1 of file
<unknown>:1: warning: no matching file member found for
static int vtkChartSelectionHelper::GetMouseSelectionMode(const vtkContextMouseEvent &mouse, int selectionMode)
Possible candidates:
'static int GetMouseSelectionMode(const vtkContextMouseEvent &mouse, int selectionMode)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static int GetMouseSelectionMode(const vtkContextMouseEvent &mouse, int selectionMode)' at line 1 of file/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/build/Utilities/Doxygen/vtkNightlyDoc.tag:/home/kitware/Dashboards/MyTests/VTK-coverage/Utilities/Doxygen/dox/Charts/Core/vtkChartSelectionHelper.h
'static int GetMouseSelectionMode(const vtkContextMouseEvent &mouse, int selectionMode)' at line 1 of file
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/ParaViewCore/ServerManager/Rendering/vtkSMViewProxy.h:192: warning: Unsupported xml/html tag <ShowOneRepresentationAtATime> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqHighlightItemDelegate.h:58: warning: Found unknown command `\default'
warning: Included by graph for 'pqReaction.h' not generated, too many nodes. Consider increasing DOT_GRAPH_MAX_NODES.
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/MajorAPIChanges.md:124: warning: Unsupported xml/html tag <SourceProxy> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/MajorAPIChanges.md:125: warning: Unsupported xml/html tag <InputProperty> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/MajorAPIChanges.md:127: warning: Unsupported xml/html tag </InputProperty> found
/home/kitware/dashboards/buildbot/paraview-vall-l
...
CDash truncated output because it exceeded 16000 characters.
...
3/source/Utilities/Doxygen/pages/MajorAPIChanges.md:128: warning: Unsupported xml/html tag <InputProperty> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/MajorAPIChanges.md:130: warning: Unsupported xml/html tag </InputProperty> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/MajorAPIChanges.md:131: warning: Unsupported xml/html tag </SourceProxy> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/PropertyHints.md:140: warning: Unsupported xml/html tag <UseDirectoryName> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/PropertyHints.md:140: warning: Unsupported xml/html tag <Hints> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/PropertyHints.md:141: warning: Unsupported xml/html tag <AcceptAnyFile> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/ProxyHints.md:44: warning: Unsupported xml/html tag <Documentation> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/ProxyHints.md:46: warning: Unsupported xml/html tag </Documentation> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/ProxyHints.md:48: warning: Unsupported xml/html tag <Hints> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/ProxyHints.md:49: warning: Unsupported xml/html tag <ShowProxyDocumentationInPanel> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/ProxyHints.md:50: warning: Unsupported xml/html tag </Hints> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Utilities/Doxygen/pages/ProxyHints.md:51: warning: Unsupported xml/html tag </SourceProxy> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/ApplicationComponents/pqCatalystRemoveBreakpointReaction.h:43: warning: Found unknown command `\LiveInsitu'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Widgets/pqCheckableHeaderView.h:71: warning: The following parameters of pqCheckableHeaderView::pqCheckableHeaderView(Qt::Orientation orientation, QWidget *parent=0) are not documented:
parameter 'orientation'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqHighlightItemDelegate.h:58: warning: Found unknown command `\default'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqHighlightItemDelegate.h:58: warning: Found unknown command `\default'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Core/pqObjectBuilder.h:215: warning: Unsupported xml/html tag <DefaultFileNameProperty> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Core/pqPipelineFilter.h:128: warning: Unsupported xml/html tag <Visibility> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqPipelineModel.h:309: warning: argument 'annotation' of command @param is not found in the argument list of pqPipelineModel::enableFilterAnnotationKey(const QString &expectedAnnotation)
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqPipelineModel.h:315: warning: The following parameters of pqPipelineModel::enableFilterAnnotationKey(const QString &expectedAnnotation) are not documented:
parameter 'expectedAnnotation'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqPropertyWidgetDecorator.h:54: warning: Unsupported xml/html tag <Hints> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:62: warning: argument 'parent' of command @param is not found in the argument list of pqProxySILModel::rowCount(const QModelIndex &theParent=QModelIndex()) const
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:68: warning: The following parameters of pqProxySILModel::rowCount(const QModelIndex &theParent=QModelIndex()) const are not documented:
parameter 'theParent'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:74: warning: argument 'parent' of command @param is not found in the argument list of pqProxySILModel::columnCount(const QModelIndex &theParent=QModelIndex()) const
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:80: warning: The following parameters of pqProxySILModel::columnCount(const QModelIndex &theParent=QModelIndex()) const are not documented:
parameter 'theParent'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:86: warning: argument 'parent' of command @param is not found in the argument list of pqProxySILModel::hasChildren(const QModelIndex &theParent=QModelIndex()) const
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:92: warning: The following parameters of pqProxySILModel::hasChildren(const QModelIndex &theParent=QModelIndex()) const are not documented:
parameter 'theParent'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:98: warning: argument 'parent' of command @param is not found in the argument list of pqProxySILModel::index(int row, int column, const QModelIndex &theParent=QModelIndex()) const
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:106: warning: The following parameters of pqProxySILModel::index(int row, int column, const QModelIndex &theParent=QModelIndex()) const are not documented:
parameter 'theParent'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:113: warning: argument 'index' of command @param is not found in the argument list of pqProxySILModel::parent(const QModelIndex &theIndex) const
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxySILModel.h:119: warning: The following parameters of pqProxySILModel::parent(const QModelIndex &theIndex) const are not documented:
parameter 'theIndex'
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxyWidget.h:82: warning: Unsupported xml/html tag <UseDocumentationForLabels> found
/home/kitware/dashboards/buildbot/paraview-vall-linux-shared-debug_doc_extdeps_gui_mpi_python_python3/source/Qt/Components/pqProxyWidget.h:125: warning: Unsupported xml/html tag
```https://gitlab.kitware.com/paraview/paraview/-/issues/17215Too many advanced icons in color editor2021-11-09T15:30:42-05:00W. Alan ScottToo many advanced icons in color editorWe have two advanced icons in the color editor, and superficially, no logical reason for two. Can we combine them into one?We have two advanced icons in the color editor, and superficially, no logical reason for two. Can we combine them into one?Chet NieterChet Nieterhttps://gitlab.kitware.com/paraview/paraview/-/issues/17277Recorded Python scripts do not handle certain proxy parameters correctly2021-03-23T13:11:48-04:00Liang WangRecorded Python scripts do not handle certain proxy parameters correctlyWhen recording macros, parameters setting are often (or always?) recorded like, for example
```python
proxy.Foo = VALUE
```
However, this fails for certain derived proxies with error like
```sh
File "$PARAVIEWPATH/lib/python2.7/site...When recording macros, parameters setting are often (or always?) recorded like, for example
```python
proxy.Foo = VALUE
```
However, this fails for certain derived proxies with error like
```sh
File "$PARAVIEWPATH/lib/python2.7/site-packages/paraview/servermanager.py", line 308, in __setattr__
"to add this attribute.")
AttributeError: Attribute Foo does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.
```
I did a naive research on this. From the online documentation of [Proxy](http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/_modules/paraview/servermanager.html#Proxy),
```
Instead of::
proxy.GetProperty("Foo").SetElement(0, 1)
proxy.GetProperty("Foo").SetElement(0, 2)
you can do::
proxy.Foo = (1,2)
or
proxy.Foo.SetData((1,2))
or
proxy.Foo[0:2] = (1,2)
```
This feature is really implemented by updating the class dictionary. It appears to me that this can be manually done by c the `_createSetProperty` function. For certain derived proxies , their dictionary might not be updated with the extra parameters, thus calls like `proxy.Foo = value` fails.
My solution:
The extra parameters have to be accessed like `proxy.SetPropertyWithName('parameter_name', value)`. Or, a better choice might be to populate the dictionary with the extra parameters.
Please note that my understanding of pypython is very preliminary (a few days), thus I might not be understanding the features/solutions correctly. However, this is still a bug, in my opinion.https://gitlab.kitware.com/paraview/paraview/-/issues/17210Paraview 5.2 Crash when Choosing Center of Rotation in Volumetric View2021-03-23T13:04:00-04:00TimParaview 5.2 Crash when Choosing Center of Rotation in Volumetric ViewI have a raw binary dataset, a few hundred MBs. When I load it and view as volume, Paraview crashes when I press the "Mouse press to pick center of rotation" button, and then I click on the dataset.
Windows 10, Intel i7 6700HQ, nVidia 1...I have a raw binary dataset, a few hundred MBs. When I load it and view as volume, Paraview crashes when I press the "Mouse press to pick center of rotation" button, and then I click on the dataset.
Windows 10, Intel i7 6700HQ, nVidia 1060, 32GB RAM, most recent drivers.https://gitlab.kitware.com/paraview/paraview/-/issues/17207Memory allocation in Paraview2020-05-07T04:15:52-04:00Arthur P.Memory allocation in ParaviewHello,
I'm trying to make an animation (3D isocontour) using XDMF reader of HDF5 data (1Go per file). I have about a thousand files to process. When I'm creating the animation, Paraview always open and allocate the new timestep in memory...Hello,
I'm trying to make an animation (3D isocontour) using XDMF reader of HDF5 data (1Go per file). I have about a thousand files to process. When I'm creating the animation, Paraview always open and allocate the new timestep in memory meaning that after 10 time step the memory allocated by Paraview is already about 10Go, not enough for my system (8Go). Then, Paraview crashes...
I've tried a different approach by using python scripts to open each file independently but I got the same memory leaking problem. Even if I delete everything in my pipeline, Paraview always hold some data in memory. So when I move to the next time step, there is some memory (1Go) remaining from the last time step... The same issue happens, Paraview grows in memory and crashes...
Why is memory leaking in Paraview?
Why am I not able to free the memory of the application using python script? Delete(*) or del * does not seem to clear everything..
Any solution for me?
The only solution I see is to create a bash script to open and close the paraview application for each of my time step...
Thank you.https://gitlab.kitware.com/paraview/paraview/-/issues/17199Warning: Polyhedra Mesh warning2021-03-23T13:04:17-04:00W. Alan ScottWarning: Polyhedra Mesh warningWhen reading in the datasets from bug #16062, there is a warning output in the release builds. Please fix it.
had to make up a value for selection
(:0, )When reading in the datasets from bug #16062, there is a warning output in the release builds. Please fix it.
had to make up a value for selection
(:0, )https://gitlab.kitware.com/paraview/paraview/-/issues/17270error paraview.smtrace.Untraceable2023-06-15T11:20:45-04:00Ufuk Turuncogluerror paraview.smtrace.UntraceableTo create issue, please download simple dataset from [here](https://www.dropbox.com/s/eqe7jj1nsct04kc/dataset.tar.gz?dl=0) and follow these steps,
* Load sample dataset atm_input3d_100 using atm_input3d_100.vtm file. It is multi block d...To create issue, please download simple dataset from [here](https://www.dropbox.com/s/eqe7jj1nsct04kc/dataset.tar.gz?dl=0) and follow these steps,
* Load sample dataset atm_input3d_100 using atm_input3d_100.vtm file. It is multi block dataset.
* Add Transform filter and set Scale in z axis as 0.0005
* Add Calculator filter and calculate **wspd** variable using formula **sqrt(ulev*ulev+vlev*vlev)**
* Add Threshold filter and set range for **wspd** as 15-50 and change representation as Points
* Use **Select Points Through (g)** button and select circular shape in the middle of the domain
* Add Extract Selection filter from menu and push apply
* Try to create Python script with CoProcessing menu
It will generates following error,
`Traceback (most recent call last):
File "<string>", line 10, in <module>
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpexport.py", line 97, in DumpCoProcessingScript
export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 351, in DumpPipeline
state = smstate.get_state(filter=filter, raw=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smstate.py", line 170, in get_state
traceitem.finalize()
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 766, in finalize
trace.append(accessor.trace_ctor(ctor, filter_type))
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 177, in trace_ctor
self, ctor, filter, ctor_args, skip_assignment)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 444, in trace_ctor
ctor_props_trace = self.trace_properties(ctor_props, in_ctor=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 437, in trace_properties
return joiner.join([x.get_property_trace(in_ctor) for x in props])
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 547, in get_property_trace
if in_ctor: return "%s=%s" % (varname, self.get_value())
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 567, in get_value
data = [str(Trace.get_accessor(x)) for x in self.get_object()[:]]
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smtrace.py", line 167, in get_accessor
"it. Skipping this action." % repr(obj))
paraview.smtrace.Untraceable: "<paraview.servermanager.FrustumSelectionSource object at 0x1376d54d0> is not 'known' at this point. Hence, we cannot trace it. Skipping this action."`
and if you try to generate Python script again with CoProcessing menu, now it gives different one
`Traceback (most recent call last):
File "<string>", line 10, in <module>
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpexport.py", line 97, in DumpCoProcessingScript
export_rendering, simulation_input_map, screenshot_info, cinema_tracks, array_selection)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/cpstate.py", line 351, in DumpPipeline
state = smstate.get_state(filter=filter, raw=True)
File "/Applications/ParaView-5.2.0.app/Contents/Python/paraview/smstate.py", line 105, in get_state
raise RuntimeError ("Cannot generate Python state when tracing is active.")
RuntimeError: Cannot generate Python state when tracing is active.`
I think that the second one is related with first one because in the first case the tracing (to create Python script for co-processing) is not fully completed and somehow it triggers the second error. So, the main error can be tracked down from the first error message. The error is probably related with the Extract Selection filter but i am not sure. BTW, I am getting same error under Linux and MacOS using PV version 5.3.0RC2.https://gitlab.kitware.com/paraview/paraview/-/issues/17102openfoam: use dictionary 'arch' information for selecting 64/32 bit2020-05-05T04:05:24-04:00olesenopenfoam: use dictionary 'arch' information for selecting 64/32 bitNow available starting with the 1612 version - can now use that.
Patch on its way
@dlonieNow available starting with the 1612 version - can now use that.
Patch on its way
@dloniehttps://gitlab.kitware.com/paraview/paraview/-/issues/17178Rendering error when mixing volume and surface rendering2023-06-15T09:01:33-04:00Sujin PhilipRendering error when mixing volume and surface renderingTo reproduce:
0. Connect to pvserver with 2 processes
1. Source > Wavelet > Apply
2. Representation = Volume, Coloring = RTData
3. Source > Sphere > Radius = 13 > Apply
4. Representation = Surface With Edges, Coloring = vtkProcessId
Som...To reproduce:
0. Connect to pvserver with 2 processes
1. Source > Wavelet > Apply
2. Representation = Volume, Coloring = RTData
3. Source > Sphere > Radius = 13 > Apply
4. Representation = Surface With Edges, Coloring = vtkProcessId
Some polygons are missing on the sphere (see attached image, you can set the alpha value in the transfer function of the volume rendering to zero for clearer picture)
![rerror-client](/uploads/70f53a85852066ad04cc93a7d0b8a222/rerror-client.png)[render-error.pvsm](/uploads/d740e053b6b4866915d48c3da6a6d2a9/render-error.pvsm)https://gitlab.kitware.com/paraview/paraview/-/issues/17267Auto Apply with readers2023-06-15T15:53:48-04:00W. Alan ScottAuto Apply with readersMake the readers work properly with Auto Apply on. One idea is to have Readers ignore Auto Apply, thus you always manually select variables then hit the Apply button. Another idea (from Ken) is to have a floating panel pop up, that you...Make the readers work properly with Auto Apply on. One idea is to have Readers ignore Auto Apply, thus you always manually select variables then hit the Apply button. Another idea (from Ken) is to have a floating panel pop up, that you then set up, and click OK.
This is needed for PV 6.0https://gitlab.kitware.com/paraview/paraview/-/issues/17101openfoam: problem reading lagrangian2020-05-05T04:08:32-04:00olesenopenfoam: problem reading lagrangian- templated code using hard-coded double will fail if openfoam is compiled with single-precision.
- the "OpenFOAM 1.3" positions format (points + cellI) is also current again > 2.4.x
Patch on the way.
@dlonie- templated code using hard-coded double will fail if openfoam is compiled with single-precision.
- the "OpenFOAM 1.3" positions format (points + cellI) is also current again > 2.4.x
Patch on the way.
@dloniehttps://gitlab.kitware.com/paraview/paraview/-/issues/17177Open big *.VTK files with ParaView2020-05-05T03:46:52-04:00ChristopherOpen big *.VTK files with ParaViewHello together,
I’m having poblems to open big vtk files ( about <4GB) with ParaView. With smaller files I have no Problems.
For the big files ParaView says that “ **a reader for D:\... could not be found. Please choose one”**.. When I...Hello together,
I’m having poblems to open big vtk files ( about <4GB) with ParaView. With smaller files I have no Problems.
For the big files ParaView says that “ **a reader for D:\... could not be found. Please choose one”**.. When I choose the vtk type the files gets loaded but nothing is visible.
I first posted the topic in the VTK User mailing list. There I got the following answer from Cory (She said I should repost it here):
"As I recall, Microsoft's runtime requires the use of special file-handling functions for reading files larger than 4 GB, even when running on a 64-bit version of Windows. I do not believe the VTK legacy library does not use these functions, which is likely why you are seeing this behavior in ParaView. I'm not aware of a simple fix, unfortunately."
Does somebody know a solution?
My System:
ParaView 5.2.0
Win 7 Ultimate 64 bit
i7-6700 @ 3.4 Ghz with 32 GB Ram
Thanks for your help.
Greetings from Germany
Chrishttps://gitlab.kitware.com/paraview/paraview/-/issues/17100openfoam: false error message when reading ascii2021-04-28T20:36:37-04:00olesenopenfoam: false error message when reading asciiReading points file in ASCII is successful, but emits the warning that 64-bit (DP) was selected etc. Patched.
@dlonieReading points file in ASCII is successful, but emits the warning that 64-bit (DP) was selected etc. Patched.
@dloniehttps://gitlab.kitware.com/paraview/paraview/-/issues/17099openfoam reader: read failure with facezones2021-03-23T12:47:29-04:00olesenopenfoam reader: read failure with facezonesReading a `List<bool>` as `List<label>` causes the failure. Patch on its' way.
@dlonieReading a `List<bool>` as `List<label>` causes the failure. Patch on its' way.
@dloniehttps://gitlab.kitware.com/paraview/paraview/-/issues/17094Bug in bug python recording for glyphs2020-06-09T13:10:31-04:00Karl MeredithBug in bug python recording for glyphsThere appears to be a bug in the python code that gets recorded for glyphs:
The setting of the 2D glyph subtype appears before the change to the overall glyph type to select "2D Glyph" happens.
I.e. recording with the bug:
...
``...There appears to be a bug in the python code that gets recorded for glyphs:
The setting of the 2D glyph subtype appears before the change to the overall glyph type to select "2D Glyph" happens.
I.e. recording with the bug:
...
```
# Properties modified on glyph1.GlyphType
glyph1.GlyphType.GlyphType = 'Vertex'
# Properties modified on glyph1
glyph1.GlyphType = '2D Glyph'
# Properties modified on glyph1.GlyphType
glyph1.GlyphType.GlyphType = 'Vertex'
```
...
And a hand fixed version:
...
```
# Properties modified on glyph1.GlyphType
#glyph1.GlyphType.GlyphType = 'Vertex'
# Properties modified on glyph1
glyph1.GlyphType = '2D Glyph'
# Properties modified on glyph1.GlyphType
glyph1.GlyphType.GlyphType = 'Vertex'
```
Thanks to David DeMarle for figuring out that this was a bug.
KarlDavid E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/17166XDMF3 reader does not seem to populate DataItems referenced by an XPath2023-06-15T08:45:21-04:00mccoysXDMF3 reader does not seem to populate DataItems referenced by an XPathThe [Xdmf format](http://xdmf.org/index.php/XDMF_Model_and_Format) says that an Xdmf `DataItem` should be able to reference another one using an XPath within the same file.
However, the Xdmf3 reader does not seem to correctly populate t...The [Xdmf format](http://xdmf.org/index.php/XDMF_Model_and_Format) says that an Xdmf `DataItem` should be able to reference another one using an XPath within the same file.
However, the Xdmf3 reader does not seem to correctly populate those DataItems. For instance, the following attribute references to a DataItem that has previously been defined with `Name="X"`.
```xml
<Attribute Name="A" Center="Node" AttributeType="Scalar">
<DataItem ItemType="Uniform" NumberType="Float" Dimensions="441" Format="XML" Reference="XML">
/Xdmf/Domain/DataItem[@Name="X"]
</DataItem>
</Attribute>
```
When loading into ParaView with the Xdmf3 reader, the grid displays only zeroes for this attribute. However, if I change the content of the DataItem to an actual list of numbers instead of a reference, it works.
Complete example file [here](/uploads/9eb6675d98cc85c08f3498039c35da44/Fields0.xmf). I use ParaView 5.2.0 on MacOs 10.11.6.Julien FaustyJulien Faustyhttps://gitlab.kitware.com/paraview/paraview/-/issues/17093disable_sub_trace does not disable completelly the trace2021-03-23T12:56:51-04:00Mathieu Westphal (Kitware)disable_sub_trace does not disable completelly the traceThere is a feature in ParaView which allows to disable the sub trace of a proxy property when tracing with python.
However it does not disable it completelly, there is still a line in the trace that come from
smtrace.py:826
How to repro...There is a feature in ParaView which allows to disable the sub trace of a proxy property when tracing with python.
However it does not disable it completelly, there is still a line in the trace that come from
smtrace.py:826
How to reproduce :
- Open ParaView, load LPT Plugin
- Create a box, apply
- Start trace
- Add a Lagrangian Seed Helper
- Apply -> the following appears in the trace when it should not :
```# Properties modified on lagrangianSeedHelper1.IntegrationModel
lagrangianSeedHelper1.IntegrationModel.SurfaceType = ['FIELD', '']```https://gitlab.kitware.com/paraview/paraview/-/issues/17164Qt 5: test playback fails on OsX for several tests2020-05-21T20:40:28-04:00Utkarsh AyachitQt 5: test playback fails on OsX for several tests- [ ] CoProcessingFullWorkflow
- [ ] CoProcessingFullWorkflowWithOnlyPlots
- [ ] CoProcessingFullWorkflowWithPlots
- [ ] pv.CatalystCinemaGUI
- [ ] pv.CatalystGUI
- [ ] pv.CatalystLivePause
- [ ] pv.CatalystLiveSetBreakpoint
- [ ] pv.Lag...- [ ] CoProcessingFullWorkflow
- [ ] CoProcessingFullWorkflowWithOnlyPlots
- [ ] CoProcessingFullWorkflowWithPlots
- [ ] pv.CatalystCinemaGUI
- [ ] pv.CatalystGUI
- [ ] pv.CatalystLivePause
- [ ] pv.CatalystLiveSetBreakpoint
- [ ] pv.LagrangianSeedHelperCustom
- [ ] pv.LagrangianSurfaceHelperComposite
- [ ] pv.TemporalParallelism
- [ ] pvcs.CatalystLivePause
- [ ] pvcs.CatalystLiveSetBreakpoint
These have been currently excluded on **ista**.Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17087Changing the format specifier on the Annotate Time source from %f to either %...2020-10-27T20:27:01-04:00Charles BellChanging the format specifier on the Annotate Time source from %f to either %d or %i crashes ParaViewThe default format specifier for the Annotate Time source is
Time: %f
That results in a default format with 6 decimals after the decimal point e.g. 7.000000
As an animation runs, the default values increment as integers. So one might...The default format specifier for the Annotate Time source is
Time: %f
That results in a default format with 6 decimals after the decimal point e.g. 7.000000
As an animation runs, the default values increment as integers. So one might expect a format specifier of %d or %i to just show in the value converted to an int
Doing that freezes, crashes or locks up program execution with no run time exception, error message.
As a workaround, I found I could simply use Time: %.0f to get displayed values e.g. 0, 1, 2 , 3, ...
I'm happy using this, but others will surely bump into this issue eventually when using Annotate Time source.
Hovering over the text field entry does not give any applicable hints or tips such as typical format specifiers for printf in fortran, c, java, etc. such as in c programming language :
* %d (print as a decimal integer)
* %6d (print as a decimal integer with a width of at least 6 wide)
* %f (print as a floating point)
* %4f (print as a floating point with a width of at least 4 wide)
* %.4f (print as a floating point with a precision of four characters after the decimal point)
* %3.2f (print as a floating point at least 3 wide and a precision of 2)
* %i or %d int
* %c char
* %f float (see also the note below)
* %s string
Thanks for wonderful program.https://gitlab.kitware.com/paraview/paraview/-/issues/17831Add support for freeze python to vtkPythonInterpreter itself2017-12-14T16:57:51-05:00Utkarsh AyachitAdd support for freeze python to vtkPythonInterpreter itselfThis will be caused by paraview/paraview!2023. Since logic to setup Python path migrated to VTK, now we need to migrate logic to not bother setting up Python path also to VTK when using frozen Python.This will be caused by paraview/paraview!2023. Since logic to setup Python path migrated to VTK, now we need to migrate logic to not bother setting up Python path also to VTK when using frozen Python.https://gitlab.kitware.com/paraview/paraview/-/issues/17832Cleanup where plugins are located in ParaView2017-11-22T21:19:10-05:00Utkarsh AyachitCleanup where plugins are located in ParaViewFix plugins and `.plugins` file to looked up as follows:
* On Linux, under `lib/paraview-5.2/plugins/`
* On Windows, under `bin/plugins/`
* On OsX , under `<app>/Contents/Plugins`Fix plugins and `.plugins` file to looked up as follows:
* On Linux, under `lib/paraview-5.2/plugins/`
* On Windows, under `bin/plugins/`
* On OsX , under `<app>/Contents/Plugins`5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17833Ability to set defaults for properties need a revamp2021-03-23T13:57:18-04:00Utkarsh AyachitAbility to set defaults for properties need a revampThere are several issues with the functionality to [let users change defaults](https://blog.kitware.com/new-in-paraview-easy-saving-of-custom-defaults-in-paraview/) that should be addressed for it to be more useful.
- [ ] **All-or-nothi...There are several issues with the functionality to [let users change defaults](https://blog.kitware.com/new-in-paraview-easy-saving-of-custom-defaults-in-paraview/) that should be addressed for it to be more useful.
- [ ] **All-or-nothing**: current approach is a all or nothing approach. Either all changes properties get saved to defaults or none. We need to be able to pick the property to save.
- [ ] **data-dependent properties are not saved**: while this is understandable for properties that depend on data arrays for example, we are not able to save/override defaults for properties like "Gaussian Radius" on the GeometryRepresentation. That's a major bummer!https://gitlab.kitware.com/paraview/paraview/-/issues/17834`./bin/pvpython -m paraview.web.test_server` should work2020-05-05T02:20:24-04:00Utkarsh Ayachit`./bin/pvpython -m paraview.web.test_server` should workpvpython/pvbatch doesn't support Python's command line arguments. That's a bummer. If that was supported, the following would be a nice way of launching paraview web server.
```bash
./bin/pvpython -m paraview.web.test_server
```pvpython/pvbatch doesn't support Python's command line arguments. That's a bummer. If that was supported, the following would be a nice way of launching paraview web server.
```bash
./bin/pvpython -m paraview.web.test_server
```https://gitlab.kitware.com/paraview/paraview/-/issues/17835non-superbuild `make install` on OsX does not work correct for compiled Pytho...2017-11-22T21:55:10-05:00Utkarsh Ayachitnon-superbuild `make install` on OsX does not work correct for compiled Python modulesThe issue is this:
We build `vtk<module>Python.so` Python module libraries during the build process and put them under `lib/python${pyver}/site-packages/vtk`. They are subsequently copied over to `lib/python${pyver}/site-packages/paravi...The issue is this:
We build `vtk<module>Python.so` Python module libraries during the build process and put them under `lib/python${pyver}/site-packages/vtk`. They are subsequently copied over to `lib/python${pyver}/site-packages/paraview/vtk`. Now, the installation rules for these, simply copy the `site-packages` directory over to the installed location under the app. Which means that the libs don't get fixed to update according to the `CMAKE_INSTALL_NAME_DIR` specified. That results in all of these `*.so` libraries referring to the libraries under the build directory rather than using `@executable_path/../Libraries` prefix.
Need to fix that. We should not be installing libraries by copying them.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/178362D annotation arrow2021-03-23T20:19:58-04:00Shuhao Wu2D annotation arrowAs far as I can tell, there seems to be no annotation arrows that can be drawn similar to a 2D text, directly on the view. This is important to produce plots that contains some text label with an arrow pointing to a specific region of th...As far as I can tell, there seems to be no annotation arrows that can be drawn similar to a 2D text, directly on the view. This is important to produce plots that contains some text label with an arrow pointing to a specific region of the plot.
Is this a feature that could be implemented for Paraview? I can try implementing it myself if someone can point me towards the right direction?https://gitlab.kitware.com/paraview/paraview/-/issues/16800Color palettes and undo/redo causes crash2021-06-22T21:53:17-04:00Kitware RobotColor palettes and undo/redo causes crash**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16800). Further discussion may take place here.**
---
Color palettes are not behaving correctly with the undo/redo feature. It i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16800). Further discussion may take place here.**
---
Color palettes are not behaving correctly with the undo/redo feature. It is causing lots of bizarre behavior including crashes. To replicate, do the following:
1. Create a Cylinder source. Apply.
2. Hit undo until you reach the end of the stack.
3. Hit redo until you reach the end of the stack.
4. Change the color palette to Black Background
When you change the color palette to Black Background, ParaView crashes. (I can replicate this on Windows and Mac.)
There is other weird behavior that is probably related. For example, if you follow steps 1-3 and then go to settings, the Color Palette tab is missing.5.10 (Fall 2021)https://gitlab.kitware.com/paraview/paraview/-/issues/15443Volume rendering non first block fails2020-06-11T20:59:57-04:00Kitware RobotVolume rendering non first block fails**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15443). Further discussion may take place here.**
---
You can only volume render the first block of a multi-block dataset. This...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15443). Further discussion may take place here.**
---
You can only volume render the first block of a multi-block dataset. This is a bug, and desperately needs to be fixed.
* Linux, master, local server.
* Open can.exo. All variables on. Turn off the first block (leaving the second block, the plate, turned on). Apply.
* Volume render.
<<Bug>> You will see lots of warnings, and nothing gets volume rendered. Without tricks, this makes volume rendering non first blocks impossible.
This is version 4.4.0-junk of ParaView.
PV_INSTALL_DIR is /projects/viz/paraview/ParaView/4.4.0-junk/Linux-eng-sci-rhel6-x86_64
[1] 28584
ERROR: In /projects/viz/paraview/src/ParaView/4.4.0-junk/ParaView4/VTK/Common/DataModel/vtkDataObjectTree.cxx, line 318
vtkMultiBlockDataSet (0x6305920): Invalid iterator location.
ERROR: In /projects/viz/paraview/src/ParaView/4.4.0-junk/ParaView4/ParaViewCore/VTKExtensions/Rendering/vtkVolumeRepresentationPreprocessor.cxx, line 75
vtkVolumeRepresentationPreprocessor (0x6271a00): Could not extract a dataset from multiblock input.
ERROR: In /projects/viz/paraview/src/ParaView/4.4.0-junk/ParaView4/VTK/Common/ExecutionModel/vtkExecutive.cxx, line 784
vtkCompositeDataPipeline (0x62805c0): Algorithm vtkVolumeRepresentationPreprocessor(0x6271a00) returned failure for request: vtkInformation (0x5937030)
Debug: Off
Modified Time: 386168
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FORWARD_DIRECTION: 0
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
5.9 (Fall 2020)https://gitlab.kitware.com/paraview/paraview/-/issues/16115Axes Grid labels, tick marks and grid disappear when zoomed in2018-09-11T20:59:06-04:00Kitware RobotAxes Grid labels, tick marks and grid disappear when zoomed in**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16115). Further discussion may take place here.**
---
When zooming in a long way, the Axes Grid labels, tick marks and grid disa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16115). Further discussion may take place here.**
---
When zooming in a long way, the Axes Grid labels, tick marks and grid disappear.
I can reproduce this by opening ParaView (no need to load dataset) and enabling Axes Grid, changing the interaction mode to 2D, then zooming in on the y axis. The tick marks and labels disappear at high zoom.
At some positions, the labels and ticks will display on only part of the axis. For instance, when no dataset is loaded, zooming in on the y axis at y=0 produces this effect.5.6 (Fall 2018)Shreeraj JadhavShreeraj Jadhavhttps://gitlab.kitware.com/paraview/paraview/-/issues/17837Problem of evenly spaced streamline 2D2018-12-19T13:27:29-05:00Gwang-Jin LeeProblem of evenly spaced streamline 2DDear ParaView developers,
I'm using Paraview-5.4.1-822 version. And I thank for adding evenly spaced streamline 2D.
I succeeded in getting evenly spaced streamline from some data.
But when I tried to apply evenly spaced streamline 2D to...Dear ParaView developers,
I'm using Paraview-5.4.1-822 version. And I thank for adding evenly spaced streamline 2D.
I succeeded in getting evenly spaced streamline from some data.
But when I tried to apply evenly spaced streamline 2D to my data which has zero values at obstacles, paraview ended abnormally.
![velocity](/uploads/673e8d74979b0c819cb632478bba32b8/velocity.png)
I attached my data. Thank you.[Gangnam_Wind_section_xy_above20.0m_2016-01-24_08_10_0.vtp](/uploads/b09cfe3c062e4592a0cfefcaaeb5f6c7/Gangnam_Wind_section_xy_above20.0m_2016-01-24_08_10_0.vtp)
P.S. When using "Save data" to csv file, tab(\t) appears instead of comma(,).
Best regards,
Gwang-Jin Leehttps://gitlab.kitware.com/paraview/paraview/-/issues/17838Glyph Filter cannot scale and orient by different arrays.2018-09-20T15:41:49-04:00Ken MartinGlyph Filter cannot scale and orient by different arrays.As it says, if you want to orient by one vector and scale by a different one the PV GUI cannot handle it. The glyph mapper can do this.As it says, if you want to orient by one vector and scale by a different one the PV GUI cannot handle it. The glyph mapper can do this.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17839Exporting Data as STL limits Precision2021-04-28T20:02:12-04:00Allen S. Harvey Jr.Exporting Data as STL limits PrecisionParaview's STL writer in ASCII mode limits numbers to 6 digits from the looks of things. Please increase this and/or switch to scientific notation. If needing to use these ASCII files, the loss of precision can result in non-watertight...Paraview's STL writer in ASCII mode limits numbers to 6 digits from the looks of things. Please increase this and/or switch to scientific notation. If needing to use these ASCII files, the loss of precision can result in non-watertight and non-manifold geometry.https://gitlab.kitware.com/paraview/paraview/-/issues/17840Plot3D reader in 5.1 and newer does not read Big Endian files2019-01-11T02:09:18-05:00Allen S. Harvey Jr.Plot3D reader in 5.1 and newer does not read Big Endian filesStarting with Paraview versions greater than 5.0.1 is not reading big endian written Plot3D files. By default the reader attempts to determine the endianness, but always defaults to little Endian. Even if the user selects big Endian in...Starting with Paraview versions greater than 5.0.1 is not reading big endian written Plot3D files. By default the reader attempts to determine the endianness, but always defaults to little Endian. Even if the user selects big Endian in the paraview properties window of the Plot3D file, it still attempts to read as little Endian.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17841Crash plot global data over time2017-11-22T21:53:52-05:00W. Alan ScottCrash plot global data over timeWe have a bad crash, plot global data over time.
* Linux, 5.4.1, local server.
* Load can.exo, all variables on, Apply.
* Plot global data over time. Apply.
* In the pipeline browser, choose the can.exo.
* Turn off one of the global var...We have a bad crash, plot global data over time.
* Linux, 5.4.1, local server.
* Load can.exo, all variables on, Apply.
* Plot global data over time. Apply.
* In the pipeline browser, choose the can.exo.
* Turn off one of the global variables. (These are at the bottom of the list of variables). Apply.
Blamo. Crash.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17842Volume Representation Clips when thin axis is scaled2020-05-21T20:27:44-04:00Glendon HolstVolume Representation Clips when thin axis is scaledWhen the thin axis of a volume is scaled, the volume rendering will clip off parts of the volume at some angles (possibly when the scaled axis is close to parallel with the camera?).
To reproduce:
* Open a 3D image dataset (Uniform Rect...When the thin axis of a volume is scaled, the volume rendering will clip off parts of the volume at some angles (possibly when the scaled axis is close to parallel with the camera?).
To reproduce:
* Open a 3D image dataset (Uniform Rectilinear Grid) of points
* The dataset should have one thin dimension (e.g., 600x600x30, for NetCDF weather data)
* Or, clip a cubic volume to get a 10% slice (produces a different kind of visual artifact)
* Assuming that Z is the thin axis for remaining repro case.
* Choose the appropriate scalar variable
* Choose Representation: Volume
* Set the Z component of Transforming / Scale to 10 (other dimension's scale stay at 1)
* Click the Z-align view (either +Z or -Z)
* Rotate the volume slightly off the Z axis.
The results:
* For the thin image data, the results should be the edges of the volume are clipped.
* For the clipped cubic volume, the visual result are a 'dirtier' version, with clipped edges, but also filled with black dots and lines obscuring the image.
Tested with:
* Found in multiple builds in the v5.x series (v5.1.2, v5.3.0, v5.4.1)
* Last tested with Kitware build of ParaView-SC17-5.5.preview-Qt5-MPI-Linus-64bit
Example images attached.[ClippingExampleImages.zip](/uploads/e5706094786c454939a0961ce7ec6893/ClippingExampleImages.zip)https://gitlab.kitware.com/paraview/paraview/-/issues/17167New properties on "Render VIew" should be hidden.2017-11-19T19:27:19-05:00Utkarsh AyachitNew properties on "Render VIew" should be hidden.See this:
![image](/uploads/7b3677f168d6589d0903faf3788324fa/image.png)
Both are set using **Settings | Camera**, hence should not be visible on the **Properties Panel**.See this:
![image](/uploads/7b3677f168d6589d0903faf3788324fa/image.png)
Both are set using **Settings | Camera**, hence should not be visible on the **Properties Panel**.5.3Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/17165Qt 5: Polygon selection lasso does not show in the Render View2017-11-19T19:27:19-05:00Utkarsh AyachitQt 5: Polygon selection lasso does not show in the Render View* Start ParaView
* Click on [![image](/uploads/d58175d8154ee332912fa4ac995afc63/image.png)](#), and the click-and-drag in the **Render View**. nothing renders. You should have seen a lasso being drawn.* Start ParaView
* Click on [![image](/uploads/d58175d8154ee332912fa4ac995afc63/image.png)](#), and the click-and-drag in the **Render View**. nothing renders. You should have seen a lasso being drawn.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17159Qt5 + Mesa: Render Windows appears translucent2022-08-03T12:28:09-04:00Utkarsh AyachitQt5 + Mesa: Render Windows appears translucent![image](/uploads/c6903c88eb36f20faa357506e745ce1d/image.png)
The text from the terminal below the ParaView window bleeds through.![image](/uploads/c6903c88eb36f20faa357506e745ce1d/image.png)
The text from the terminal below the ParaView window bleeds through.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17157Static Qt 5 builds fail.2017-11-19T19:27:19-05:00Utkarsh AyachitStatic Qt 5 builds fail.ParaView version: **v5.2.0-350-gf4b1fec**
Static builds with Qt5 fail with following link errors:
```sh
lib/libCatalystScriptGeneratorPlugin.a(CatalystScriptGeneratorPlugin_Plugin.cxx.o): In function `CatalystScriptGeneratorPlugin_...ParaView version: **v5.2.0-350-gf4b1fec**
Static builds with Qt5 fail with following link errors:
```sh
lib/libCatalystScriptGeneratorPlugin.a(CatalystScriptGeneratorPlugin_Plugin.cxx.o): In function `CatalystScriptGeneratorPlugin_Plugin::CatalystScriptGeneratorPlugin_Plugin()::StaticCatalystScriptGeneratorPluginPluginInstance::StaticCatalystScriptGeneratorPluginPluginInstance()':
/home/utkarsh/Kitware/ParaView3/ParaViewBin-static/Plugins/CatalystScriptGenerator/CatalystScriptGeneratorPlugin_Plugin.cxx:187: undefined reference to `qt_static_plugin_CatalystScriptGeneratorPlugin()'
lib/libLagrangianParticleTracker.a(LagrangianParticleTracker_Plugin.cxx.o): In function `LagrangianParticleTracker_Plugin::LagrangianParticleTracker_Plugin()::StaticLagrangianParticleTrackerPluginInstance::StaticLagrangianParticleTrackerPluginInstance()':
/home/utkarsh/Kitware/ParaView3/ParaViewBin-static/Plugins/LagrangianParticleTracker/LagrangianParticleTracker_Plugin.cxx:190: undefined reference to `qt_static_plugin_LagrangianParticleTracker()'
lib/libNonOrthogonalSource.a(NonOrthogonalSource_Plugin.cxx.o): In function `NonOrthogonalSource_Plugin::NonOrthogonalSource_Plugin()::StaticNonOrthogonalSourcePluginInstance::StaticNonOrthogonalSourcePluginInstance()':
/home/utkarsh/Kitware/ParaView3/ParaViewBin-static/Plugins/NonOrthogonalSource/NonOrthogonalSource_Plugin.cxx:188: undefined reference to `qt_static_plugin_NonOrthogonalSource()'
lib/libSLACTools.a(SLACTools_Plugin.cxx.o): In function `SLACTools_Plugin::SLACTools_Plugin()::StaticSLACToolsPluginInstance::StaticSLACToolsPluginInstance()':
/home/utkarsh/Kitware/ParaView3/ParaViewBin-static/Plugins/SLACTools/SLACTools_Plugin.cxx:189: undefined reference to `qt_static_plugin_SLACTools()'
lib/libSierraPlotTools.a(SierraPlotTools_Plugin.cxx.o): In function `SierraPlotTools_Plugin::SierraPlotTools_Plugin()::StaticSierraPlotToolsPluginInstance::StaticSierraPlotToolsPluginInstance()':
/home/utkarsh/Kitware/ParaView3/ParaViewBin-static/Plugins/SierraPlotTools/SierraPlotTools_Plugin.cxx:186: undefined reference to `qt_static_plugin_SierraPlotTools()'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
```5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17156Text in 3D View not rendered correctly2017-11-19T19:27:19-05:00Utkarsh AyachitText in 3D View not rendered correctlySteps to reproduce:
1. Text source, set **Text** to 0.467, Apply
2. Change **Font Properties** to change to size to 7. (you may have to incrementally lower this to get to buggy state if 7 doesn't show the issue).
![image](/uploads/6...Steps to reproduce:
1. Text source, set **Text** to 0.467, Apply
2. Change **Font Properties** to change to size to 7. (you may have to incrementally lower this to get to buggy state if 7 doesn't show the issue).
![image](/uploads/625a1028567a82c4bf94736d6a2788d2/image.png)
That's bad. The same bug affects labels in Scalar Bar too.5.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17144Clamp and update every timestep is broken2017-11-19T19:27:19-05:00W. Alan ScottClamp and update every timestep is brokenClamp and update every timestep is broken. This is needed by a customer. Thus, marking must have.
* Master, Linux, local server.
* Edit/ Settings/ Transfer Function Reset Mode/ change to "Clamp and update every timestep".
* Open...Clamp and update every timestep is broken. This is needed by a customer. Thus, marking must have.
* Master, Linux, local server.
* Edit/ Settings/ Transfer Function Reset Mode/ change to "Clamp and update every timestep".
* Open Can.exo. All vars on. Apply.
* Color by ACCL. Step through numerous steps. The Color legend should update every timestep.
This is critical functionality for some users. Functionality lost after the 5.2.0 release. Marking as required for the 5.3 release.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17142Make Qt5 require OpenGL2 in ParaView2017-11-19T19:27:20-05:00Utkarsh AyachitMake Qt5 require OpenGL2 in ParaViewadd a check for it or force it or complain when things don't match. we don't support Qt5 and OpenGL1add a check for it or force it or complain when things don't match. we don't support Qt5 and OpenGL15.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17135Maximum time limit of 4095 for annotated .vtu file2017-11-19T19:27:20-05:00David BennMaximum time limit of 4095 for annotated .vtu fileUpon loading an annotated .vtu file with TimeStep annotations such as this into Paraview 5.2.0 (under 64 bit SUSE Linux):
`<DataArray type="Float64" Name="V" TimeStep="10560" format="appended" RangeMin="-87.934331219" RangeMax="-87.44...Upon loading an annotated .vtu file with TimeStep annotations such as this into Paraview 5.2.0 (under 64 bit SUSE Linux):
`<DataArray type="Float64" Name="V" TimeStep="10560" format="appended" RangeMin="-87.934331219" RangeMax="-87.443353026" offset="7801035604" />`
I see the following in Paraview:
![timemax4095](/uploads/7da3e44c98f680a4198757dbf81281b4/timemax4095.png)
such that a maximum of 4095 time steps are available, as opposed to the expected 10,560 time steps.
The number of time steps can be found in the TimeValues attribute of the UnstructuredGrid element:
`<UnstructuredGrid TimeValues="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 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 ...`
When the *non-annotated* .vtu file is loaded, the expected number of *frames* are visible.
There is an inherent limitation within Paraview that prevents more than 4095 time steps from being loaded/visualised.
A colleague found the place in the code where the 4095 limit occurs:
```
int vtkXMLReader::ReadPrimaryElement(vtkXMLDataElement* ePrimary)
{
const int tsMax = 4096;
double timevalues[tsMax];
int numTimeSteps =
ePrimary->GetVectorAttribute("TimeValues", tsMax, timevalues);
assert( numTimeSteps <= tsMax);
this->SetNumberOfTimeSteps( numTimeSteps );
...
```
Changing 4096 to a larger value (e.g. 65536) allows more time steps to be used within Paraview, but I wondered about a solution without an upper bound on the number of time steps. I spent time looking at the code being called and what was required.
vtkXMLReader::ReadPrimaryElement calls vtkXMLDataElement::GetVectorAttribute() which calls vtkXMLDataElement::vtkXMLDataElementVectorAttributeParse().
In ReadPrimaryElement(), only the number of time steps is required. This corresponds to the number of space-delimited tokens (time step numbers) in the TimeValues attribute. The timevalues double array passed to GetVectorAttribute() is not used for anything within ReadPrimaryElement().
Accordingly, I've modified the code locally to this:
```
int vtkXMLReader::ReadPrimaryElement(vtkXMLDataElement* ePrimary)
{
const char* timeValuesAttr = ePrimary->GetAttribute("TimeValues");
int numTimeSteps =
ePrimary->SpaceDelimitedTokenCount(timeValuesAttr);
this->SetNumberOfTimeSteps( numTimeSteps );
...
```
and added vtkXMLDataElement::SpaceDelimitedTokenCount():
```
int vtkXMLDataElement::SpaceDelimitedTokenCount(const char* str)
{
const int find_token = 1;
const int skip_token = 2;
const int end = 3;
int state = find_token;
int count = 0;
while(str && state != end)
{
switch(state)
{
case find_token:
// Iterate until non-space (token or EOLN: 0)
while(*str == ' ') ++str;
state = *str != 0 ? skip_token : end;
break;
case skip_token:
++count;
// Iterate past token until space or EOLN
while(*str && *str != ' ') ++str;
state = *str != 0 ? find_token : end;
break;
default:
state = end;
}
}
return count;
}
```
This may not be the best class for it. In any case, it works well.
Initially I wrote this in terms of a variant of vtkXMLDataElement::vtkXMLDataElementVectorAttributeParse():
```
int vtkXMLDataElement::SpaceDelimitedTokenCount(const char* str)
{
if(!str) { return 0; }
std::stringstream vstr;
vstr.imbue(std::locale::classic());
vstr << str;
char ch;
int count = 0;
while(vstr)
{
vstr >> ch;
count++;
}
return count-1;
}
```
I used the following simple test cases (with spaceDelimitedTokenCount2() referring to the second implementation above passed as a non-member function to testTokenCounter()):
```
void testTokenCounter(int (*f)(const char*))
{
const char* str1 = "1 2 3 4 5";
std::cout << f(str1) << std::endl;
const char* str2 = "1 2 3 4 5";
std::cout << f(str2) << std::endl;
const char* str3 = " 1 2 3 4 5 ";
std::cout << f(str3) << std::endl;
// Fails with spaceDelimitedTokenCount2()
const char* str4 = " 1 2 3 4 52 ";
std::cout << f(str4) << std::endl;
const char* str5 = " ";
std::cout << f(str5) << std::endl;
const char* str6 = " ";
std::cout << f(str6) << std::endl;
const char* str7 = "";
std::cout << f(str7) << std::endl;
const char* str8 = 0;
std::cout << f(str8) << std::endl;
std::cout << std::endl;
}
```
and found that the second approach yielded a count of 6 tokens instead of 5. I think the first implementation is less opaque in any case, at the cost of being a little more verbose.
I submit this problem and potential solution for your consideration.
From a git clone of VTK, I see:
> $ git rev-parse HEAD
> c0a653bf5fd488f7ae7bcd24e8321b542f4b5f6b5.3Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17095Add scipy to the ParaView python2017-11-19T19:27:20-05:00W. Alan ScottAdd scipy to the ParaView pythonNumerous users have asked for the combination of the following to be be added to ParaView bundles.
* numpy (already supported),
* scipy
* matplotlib (already supported)
* pandas (reported as paraview/paraview#17187)
Please a...Numerous users have asked for the combination of the following to be be added to ParaView bundles.
* numpy (already supported),
* scipy
* matplotlib (already supported)
* pandas (reported as paraview/paraview#17187)
Please add these packages.5.3Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/17091Fatal Nan coloring issue2017-11-19T19:27:20-05:00W. Alan ScottFatal Nan coloring issueWe have a variable coloring issue with the 5.2.0 release. This issue is probably a showstopper for the 5.2.0 release.
Follow directions below exactly.
* Linux, Kitware 5.2.0 release, local server. Bug does not show with either ...We have a variable coloring issue with the 5.2.0 release. This issue is probably a showstopper for the 5.2.0 release.
Follow directions below exactly.
* Linux, Kitware 5.2.0 release, local server. Bug does not show with either Windows or OS X. Close the startup window.
* Open can.exo. All vars on. Apply.
* Edit Color Map. (Not necessary, but instructive)
* Change coloring to DISPL. Can and color legend will go blue.
\<\<Notice that the color legend has no ticks.>>
\<\<Notice that the text "Data range too small to render" appears in the Color Map Editor>>
* Go forward one timestep.
* Rescale to data range.
\<\<Notice that can and the color legend go yellow - i.e., the Nan color. Nothing a user ever does can come out of this state.>>
* Change coloring to ACCL. Normal coloring. (Note that we are on timestep 1, where there is actually data in the can.)
We have not figured out how to get DISPL to work again without shutting down ParaView.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17079Clear Opengl framebuffers on open2017-11-19T19:27:20-05:00W. Alan ScottClear Opengl framebuffers on openPlease clear the Opengl frame buffers upon ParaView open. Actively overwrite the front and back frame buffers. Currently, on Linux, when you run Paraview , visualize something and close ParaView, (or any other 3d program), and then reo...Please clear the Opengl frame buffers upon ParaView open. Actively overwrite the front and back frame buffers. Currently, on Linux, when you run Paraview , visualize something and close ParaView, (or any other 3d program), and then reopen ParaView, the old frame buffer pictures show. This is potentially a big issue if someone is showing a coworker something, and said co-worker sees something he/she should not see.
Talk to me if you want a more specific example.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17077*.pvsm files not being shown in `Load State` dialog2017-11-19T19:27:20-05:00Utkarsh Ayachit*.pvsm files not being shown in `Load State` dialogSee the images below. The `state.pvsm` file doesn't show up until I choose `All files(*)`.
![image](/uploads/34f19e7a011f1f4aa558e69074de53c4/image.png)
![image](/uploads/f0a9e8a2b6e173cef2c1651072013c30/image.png)See the images below. The `state.pvsm` file doesn't show up until I choose `All files(*)`.
![image](/uploads/34f19e7a011f1f4aa558e69074de53c4/image.png)
![image](/uploads/f0a9e8a2b6e173cef2c1651072013c30/image.png)5.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17040Reload Files would be better under the File menu2017-11-19T19:27:20-05:00Berk GeveciReload Files would be better under the File menuReload Files is currently under the Edit menu. IMHO, it would be better under the File menu.Reload Files is currently under the Edit menu. IMHO, it would be better under the File menu.5.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17025Incomplete Python installation in Linux Binary of ParaView 5.2.02017-11-19T19:27:20-05:00bgschaidIncomplete Python installation in Linux Binary of ParaView 5.2.0Downloaded the binary http://www.paraview.org/files/v5.2/ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz and installed it. This broke one of my pvpython-scripts because the module SimpleXMLRPCServer could not be imported. Checking lib/...Downloaded the binary http://www.paraview.org/files/v5.2/ParaView-5.2.0-Qt4-OpenGL2-MPI-Linux-64bit.tar.gz and installed it. This broke one of my pvpython-scripts because the module SimpleXMLRPCServer could not be imported. Checking lib/python2.7 directory in the installation showed that this module and some others are missing (compared to previous binaries for the same system where the python-libraries are in a slightly different place)5.3Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/17009Slow animation with selections2017-11-19T19:27:20-05:00W. Alan ScottSlow animation with selectionsWe have a bug with the selection code. It creates huge slowdowns playing animations. Here is how to replicate:
* 5.2.0-RC3. Mac. Local server.
* can.exo. All vars on. Apply.
* Play. This is how fast can.exo should play.
* Le...We have a bug with the selection code. It creates huge slowdowns playing animations. Here is how to replicate:
* 5.2.0-RC3. Mac. Local server.
* can.exo. All vars on. Apply.
* Play. This is how fast can.exo should play.
* Leave at last timestep.
* Find Data. Cells from can.ex2. EQPS >= 1.5. Run Selection Query.
* Play. Notice how slow can.exo plays.
* Reset Session.
* can.exo. All vars on. Apply.
* Play. Notice how can has slowed down! This slowdown is universal to all animation - it also now shows up when animating a sphere Start Theta!
* I also believe that every time you add another seleciton query , ParaView slows down even more. For instance, Find Data. Global ID is max. Run Selection Query. Play
* Again, Find Data. Global ID is min. Run Selection Query. Play.
It slows down more and more for each Selection Query.
The only cure is to close and restart ParaView.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16987Add ability for Houdini writer to output all time steps2017-11-19T19:27:20-05:00W. Alan ScottAdd ability for Houdini writer to output all time stepsAdd the ability for Houdini to write all time steps of a data set.Add the ability for Houdini to write all time steps of a data set.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16967Crash with trace recorder2017-11-19T19:27:20-05:00W. Alan ScottCrash with trace recorderWe have a crash with the trace recorder. Replicate as follows:
Linux, master, local server.
Tools/ Start Trace. OK.
Crash
This needs to be fixed asap.We have a crash with the trace recorder. Replicate as follows:
Linux, master, local server.
Tools/ Start Trace. OK.
Crash
This needs to be fixed asap.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16965Document the --mesa-llvm and --mesa-swr command line arguments2017-11-19T19:27:20-05:00W. Alan ScottDocument the --mesa-llvm and --mesa-swr command line argumentsSomehow, document the --mesa-llvm and --mesa-swr command line arguments when they exist. Preferably, this would be the command line --help. As a fallback (that I don't like), do so on the wiki.Somehow, document the --mesa-llvm and --mesa-swr command line arguments when they exist. Preferably, this would be the command line --help. As a fallback (that I don't like), do so on the wiki.5.3Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/16963Start Trace outputs unnecessary message2017-11-19T19:27:20-05:00Kenneth MorelandStart Trace outputs unnecessary messageWhen you start the Python trace recorder, you get a confusing and ultimately meaningless message that looks like an error. To replicate, simply select `Tools` -> `Start Trace` and then accept the default options by clicking `OK`. When yo...When you start the Python trace recorder, you get a confusing and ultimately meaningless message that looks like an error. To replicate, simply select `Tools` -> `Start Trace` and then accept the default options by clicking `OK`. When you do, the Output Messages window pops up with the following content.
![PythonTraceOutput](/uploads/5e1f8c0ca29f09aaee3e0b390d1edad1/PythonTraceOutput.png)
This amounts to something producing
```
updating active connection Connection (builtin:) [3]
```
which is captured by the VTK output window.5.2 (SC-16)Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/16959Trace recorder on Mac has error print2017-11-19T19:27:20-05:00W. Alan ScottTrace recorder on Mac has error printOS X, 5.2.0-RC1, local server. Trace recorder has an error print.
Run the Kitware 5.2.0-RC1.
Tools/ Start Trace.
You get the following:
updating active connection Connection (builtin:) [1]OS X, 5.2.0-RC1, local server. Trace recorder has an error print.
Run the Kitware 5.2.0-RC1.
Tools/ Start Trace.
You get the following:
updating active connection Connection (builtin:) [1]5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16952update ParaView superbuild to use latest versions of the guide2017-11-19T19:27:20-05:00Utkarsh Ayachitupdate ParaView superbuild to use latest versions of the guideUpdate ParaView superbuild to use latest version of the guide and other pregenerated PDFs.
You may need to regenerate the new PDFs after updating the "updated for version..." txts in them, if applicable.Update ParaView superbuild to use latest version of the guide and other pregenerated PDFs.
You may need to regenerate the new PDFs after updating the "updated for version..." txts in them, if applicable.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/16946Change hidden line option to be base Properties tab2017-11-19T19:27:20-05:00W. Alan ScottChange hidden line option to be base Properties tabPlease expose the Hidden Line Removal checkbox for default Properties tab. Currently, it is only available on the advanced tab.Please expose the Hidden Line Removal checkbox for default Properties tab. Currently, it is only available on the advanced tab.5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/16941Master bug for various rendering issues2017-11-19T19:27:20-05:00Utkarsh AyachitMaster bug for various rendering issues1. ~~Selection not working: paraview/paraview#16940~~ -- MR !1093
2. ~~Changing color arrays not working: paraview/paraview#16942~~
3. ~~Resizing in remote rendering causes rendering to disappear: paraview/paraview#16943~~ (fix in VTK...1. ~~Selection not working: paraview/paraview#16940~~ -- MR !1093
2. ~~Changing color arrays not working: paraview/paraview#16942~~
3. ~~Resizing in remote rendering causes rendering to disappear: paraview/paraview#16943~~ (fix in VTK, will land in ParaView at next update of VTK)
4. ~~Multiblock selection + surface with edges: missing selection info paraview/paraview#16944~~5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16924Issues with `vtmMPIIMageReader`2017-11-19T19:27:20-05:00Utkarsh AyachitIssues with `vtmMPIIMageReader`Created from paraview/paraview#16876:
Message from @wascott:
@utkarsh.ayachit @dlonie @wascott This one now appears to hang before even getting the chance to set up the extents. Mind trying it, see if you can replicate the cras...Created from paraview/paraview#16876:
Message from @wascott:
@utkarsh.ayachit @dlonie @wascott This one now appears to hang before even getting the chance to set up the extents. Mind trying it, see if you can replicate the crash? I had 16 ranks on Chama, master from a few days ago, Linux.
I got lots and lots of:
Generic Warning: In /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/VTK/Parallel/MPI/vtkMPICommunicator.cxx, line 72
MPI had an error
------------------------------------------------
MPI_ERR_ARG: invalid argument of some other kind
------------------------------------------------
Generic Warning: In /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/VTK/Parallel/MPI/vtkMPICommunicator.cxx, line 72
MPI had an error
------------------------------------------------
MPI_ERR_ARG: invalid argument of some other kind
------------------------------------------------
Generic Warning: In /projects/viz/paraview/src/ParaView/5.2.0-junk/ParaView5/VTK/Parallel/MPI/vtkMPICommunicator.cxx, line 72
MPI had an error
------------------------------------------------
MPI_ERR_ARG: invalid argument of some other kind5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/16913Annotate color for blocks is failing pvbatch.2017-11-19T19:27:20-05:00W. Alan ScottAnnotate color for blocks is failing pvbatch.I have a user that is trying to batch process numerous datasets. He is doing the following:
* Paraview, Linux, local server.
* Trace recorder on.
* Open bake.e. All vars on (probably not needed). Apply.
* Save Screenshot.
* Trace...I have a user that is trying to batch process numerous datasets. He is doing the following:
* Paraview, Linux, local server.
* Trace recorder on.
* Open bake.e. All vars on (probably not needed). Apply.
* Save Screenshot.
* Trace recorder off. Save the trace (not as Macro).
* Reset Session
* Open, then delete Screenshot created earlier.
* Tools/ Python Shell. Run the saved trace.
* >>>> This works.
* Open, then delete Screenshot created earlier.
* pvbatch trace from earlier.
* >>>> This does not work. Annotated colors have been replaced with the default color map.
This is impacting a user.5.2 (SC-16)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16912ospray volume rendering2017-11-19T19:27:20-05:00David E. DeMarleospray volume rendering5.2 (SC-16)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/16884Expose more SPH kernes in ParaView2017-11-19T19:27:20-05:00Utkarsh AyachitExpose more SPH kernes in ParaViewCurrently:
* SPHQuinticKernel
Need to add:
* SPHCubicKernel
* SPHQuarticKernel
* WendlandQuinticKernel
SPHQuinticKernel should remain the default initial valueCurrently:
* SPHQuinticKernel
Need to add:
* SPHCubicKernel
* SPHQuarticKernel
* WendlandQuinticKernel
SPHQuinticKernel should remain the default initial value5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15228Additional ruler work - functionality2017-11-19T19:27:20-05:00Kitware RobotAdditional ruler work - functionality**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15228). Further discussion may take place here.**
---
We need the ruler modified as follows:
* Allow the user to select t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15228). Further discussion may take place here.**
---
We need the ruler modified as follows:
* Allow the user to select the end points by some unique variable, such as global node id. Be sure to error check for multiple server, to make sure the user didn't do anything stupid.
* ~~Allow the user to free hand select points on a surface (current functionality), OR center of cell on a surface closest to pick OR nearest point on a surface to pick. Don't make users type in locations or rubber band select points. Keep the ability to manually type in end points.~~
* ~~Have the end point that will be placed with the 'P' key highlighted in some way. Currently, you don't know which point gets selected, and it is confusing.~~
* ~~Redo the tick marks on the ruler. We only show quartiles. Offer the user - either show subdivisions (1/2, 1/4, 1/8 etc) or standard units (if the line is 27 units long, place a mark at 5, 10, 15, 25 and maybe 25 units. This is what a real ruler does.~~5.2 (SC-16)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/14886Descriptive statistics max appears wrong2017-11-19T19:27:21-05:00Kitware RobotDescriptive statistics max appears wrong**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14886). Further discussion may take place here.**
---
The descriptive statistics filter seems to be providing the wrong valu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14886). Further discussion may take place here.**
---
The descriptive statistics filter seems to be providing the wrong value for maximum, at least when it is used in conjunction with plot selection over time. To replicate, do the following:
1. Load can.ex2. Turn on EQPS. Apply.
2. Merge blocks. Apply.
3. Add Descriptive Statistics filter. Change attribute mode to Cell Data. Select EQPS variable (only). Apply.
4. In the spreadsheet of the statistical model, select the row associated with EQPS. (If you only selected the EQPS previously, it should be the only row.)
5. Add the Plot Selection Over Time Filter. Apply.
6. Delete the spreadsheet views (to see the plot more easily). Select only the Maximum series. Notice the weird sawtooth nature of the plot. That is not right. It should be mostly (if not totally) monotonically increasing.
7. Select the Merge Blocks filter in the pipeline browser.
8. Open Find Data. Query for the max EQPS. Plot selection over time. Apply.
9. In this plot, select only the maximum EQPS value. This curve shape is expected.
I've attached an image of the results.
The two versions of maximum should give the same value. Considering how weird the curve from descriptive statistics looks, I believe that is the one that is incorrect.
5.2 (SC-16)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17335Texture map cylinder filter needs origin inputs2017-11-19T19:27:21-05:00W. Alan ScottTexture map cylinder filter needs origin inputsWe need to add origin to the Texture Map Cylinder filter. For instance, if I have a oil pipe burst simulation, and I simulated only 1/4 of the diameter of the pipe, I want to be able to properly place the origin.We need to add origin to the Texture Map Cylinder filter. For instance, if I have a oil pipe burst simulation, and I simulated only 1/4 of the diameter of the pipe, I want to be able to properly place the origin.5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17313File Dialog is grouping unrelated files as a sequence2017-11-19T19:27:21-05:00Robert M. O'BaraFile Dialog is grouping unrelated files as a sequenceI need to support 2 mesh formats:
* .2dm is a 2D mesh
* .3dm is a 3D mesh
If I have foo.2dm and foo.3dm in the same directory, ParaView's File Dialog's filtering mechanism will not show foo.2dm when filtering on .2dm or foo.3dm ...I need to support 2 mesh formats:
* .2dm is a 2D mesh
* .3dm is a 3D mesh
If I have foo.2dm and foo.3dm in the same directory, ParaView's File Dialog's filtering mechanism will not show foo.2dm when filtering on .2dm or foo.3dm when filtering on .3dm. To see the files you need to show all files and then the dialog shows them grouped together.![Screen_Shot_2017-03-22_at_11.02.54_AMEDT](/uploads/ac15b5fa721a605693b891686efb59d0/Screen_Shot_2017-03-22_at_11.02.54_AMEDT.png)![Screen_Shot_2017-03-22_at_11.02.21_AMEDT](/uploads/2dafef779f481bde1d71463fd6fb6fef/Screen_Shot_2017-03-22_at_11.02.21_AMEDT.png)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17235Find Data dialog is very slow to show up2017-11-19T19:27:21-05:00Utkarsh AyachitFind Data dialog is very slow to show upSteps:
1. Start ParaView
2. Open **can.ex2**, Apply
3. Using [![image](/uploads/576976e42f0a9f1046d96c8cab20f4e2/image.png)](*), create a selection on the block.
4. Now hit **v** to show the Find Data dialog -- it takes a long time t...Steps:
1. Start ParaView
2. Open **can.ex2**, Apply
3. Using [![image](/uploads/576976e42f0a9f1046d96c8cab20f4e2/image.png)](*), create a selection on the block.
4. Now hit **v** to show the Find Data dialog -- it takes a long time to show up.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17224Change ParaView ? (help) to be the Help menu2017-11-19T19:27:21-05:00W. Alan ScottChange ParaView ? (help) to be the Help menuPlease change the blue ? to open the Help menu. This is right below the "Tools" menu. I also wouldn't mind if it was just deleted. We already have a Help menu!
aka remove this button: [![image](/uploads/3711bfba9fa0d0a9ae699fc2aedb...Please change the blue ? to open the Help menu. This is right below the "Tools" menu. I also wouldn't mind if it was just deleted. We already have a Help menu!
aka remove this button: [![image](/uploads/3711bfba9fa0d0a9ae699fc2aedb8038/image.png)](*)
5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17161CMake warnings with Qt 5 & cmake 3.5.22018-06-09T18:11:24-04:00Utkarsh AyachitCMake warnings with Qt 5 & cmake 3.5.2I get the following warnings.
```sh
CMake Warning (dev) at /Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5ModuleLocation.cmake:4 (set):
Policy CMP0053 is not set: Simplify variable reference and escape sequence
ev...I get the following warnings.
```sh
CMake Warning (dev) at /Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5ModuleLocation.cmake:4 (set):
Policy CMP0053 is not set: Simplify variable reference and escape sequence
evaluation. Run "cmake --help-policy CMP0053" for policy details. Use the
cmake_policy command to set the policy and suppress this warning.
For input:
'${_qt5_install_prefix}/Qt5@module@/Qt5@module@Config.cmake'
the old evaluation rules produce:
'/Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5Config.cmake'
but the new evaluation rules produce:
'/Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5@module@/Qt5@module@Config.cmake'
Using the old result for compatibility since the policy is not set.
Call Stack (most recent call first):
/Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5Config.cmake:25 (include)
ThirdParty/QtTesting/vtkqttesting/CMakeLists.txt:17 (FIND_PACKAGE)
This warning is for project developers. Use -Wno-dev to suppress it.
CMake Warning (dev) at /Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5ModuleLocation.cmake:4 (set):
Policy CMP0053 is not set: Simplify variable reference and escape sequence
evaluation. Run "cmake --help-policy CMP0053" for policy details. Use the
cmake_policy command to set the policy and suppress this warning.
For input:
'${_qt5_install_prefix}/Qt5@module@/Qt5@module@Config.cmake'
the old evaluation rules produce:
'/Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5Config.cmake'
but the new evaluation rules produce:
'/Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5@module@/Qt5@module@Config.cmake'
Using the old result for compatibility since the policy is not set.
Call Stack (most recent call first):
/Users/utkarsh/Kitware/Tools/qt/5.8.0/install/lib/cmake/Qt5/Qt5Config.cmake:25 (include)
ThirdParty/QtTesting/vtkqttesting/Testing/Cpp/CMakeLists.txt:4 (FIND_PACKAGE)
This warning is for project developers. Use -Wno-dev to suppress it.
```5.3Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/17155If server dies during filter execution, the "Save State" prompt is not useable.2017-11-19T19:27:21-05:00Utkarsh AyachitIf server dies during filter execution, the "Save State" prompt is not useable.Try this:
1. Connect ParaView to pvserver (single rank is fine)
2. Create `Programmable Source` with the following script:
```python
import sys
sys.exit(1)
```
3. Apply
We're simulating a server crash here. On **Apply**, the se...Try this:
1. Connect ParaView to pvserver (single rank is fine)
2. Create `Programmable Source` with the following script:
```python
import sys
sys.exit(1)
```
3. Apply
We're simulating a server crash here. On **Apply**, the server will exit and you should get the following prompt
![image](/uploads/c3fcda5f38ae81603665b9bb2be5fc43/image.png)
However the dialog is not usable! One cannot click on any of the buttons!
Now try this:
1. Connect to pvserver (1 rank).
2. Just `Ctrl-C` to kill the pvserver processes.
This time the same dialog pops up, but is usable. I can click on it to save state etc.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17145Variables disappear on extract selection.2017-11-19T19:27:21-05:00W. Alan ScottVariables disappear on extract selection.A bug from a user. I will give the dataset to Utkarsh. (Note to self - workstation, mst..., cylinder_a_v3.0a.5.e.) (Note to Utkarsh, same dataset as #17081. Same restrictions apply.)
* ParaView master, local server, Linux.
* This d...A bug from a user. I will give the dataset to Utkarsh. (Note to self - workstation, mst..., cylinder_a_v3.0a.5.e.) (Note to Utkarsh, same dataset as #17081. Same restrictions apply.)
* ParaView master, local server, Linux.
* This dataset has three vectors of interest - Q_XX, Q_YY and Q_ZZ, which are orthogonal to each other.
* Read data, all vars on, apply.
* Select one cell. Extract Selection. Apply. Now, I have one cell to play with.
Notice that cell variable Q_XX has disappeared. It doesn't show up as a color to paint with, or in the Information tab. This is a bug.5.3Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17133Add CGNS as a third party library to ParaView source.2017-11-19T19:27:21-05:00W. Alan ScottAdd CGNS as a third party library to ParaView source.We now have a billion and five votes for this. Make it so.
From e-mail from Utkarsh,
> Given that there is an increasing interest in using CGNS with ParaView
> and that it's quite tedious to build with an external CGNS, I am
> w...We now have a billion and five votes for this. Make it so.
From e-mail from Utkarsh,
> Given that there is an increasing interest in using CGNS with ParaView
> and that it's quite tedious to build with an external CGNS, I am
> wondering if we should consider adding CGNS as a third-party library
> to ParaView source itself.
Note - make sure this works local server and remote server (i.e., clusters), and on Windows, Mac and Linux. Have me test the cluster side.5.4 (ISC 2017)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/17128quadratic tetrahedra failing with ghost cell generation2017-11-19T19:27:21-05:00W. Alan Scottquadratic tetrahedra failing with ghost cell generationI have a dataset that is failing with ghost cell generation. This is true for D3, Ghost Cell Generation, and Extract Surface. Ken and my speculation is that this case is either not being caught, or needs to be added.
Test as follows...I have a dataset that is failing with ghost cell generation. This is true for D3, Ghost Cell Generation, and Extract Surface. Ken and my speculation is that this case is either not being caught, or needs to be added.
Test as follows:
* Linux, 5.1.2, remote server. I am using 8 ranks.
* Open the spread file hollowSphere_fieldVars.e.48. Apply. (This dataset looks like the ice layer of Europa or a pressure vessel.).
* D3 or Ghost Cell Generator. Apply.
* Change Opacity to 0.2. Notice the processor boundaries.
Now, to show it work correctly, do the following:
* Linux, 5.1.2, remote server. I am using 8 ranks.
* Open the spread file hollowSphere.g.48. Apply. (This dataset looks like the ice layer of Europa).
* Tesselate. Apply.
* D3 or Ghost Cell Generator. Apply.
* Change Opacity to 0.2. Notice the processor boundaries are gone.
I will give the dataset to Utkarsh. It is UUR.
I need either this bug fixed (this one preferrably) or #17137 and #17136 5.3Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17231vtkTable block of multiblock dataset cannot be saved2017-11-20T09:48:24-05:00Mathieu Westphal (Kitware)vtkTable block of multiblock dataset cannot be savedWhen saving a multiblock dataset, vtkTable block are not saved at all.
How to reproduce:
- Open ParaView
- Open vehicles.csv
- GroupDataSet
- SaveData
- The table is not saved on the diskWhen saving a multiblock dataset, vtkTable block are not saved at all.
How to reproduce:
- Open ParaView
- Open vehicles.csv
- GroupDataSet
- SaveData
- The table is not saved on the disk5.5 (Spring 2018)Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/13096Fix Cancel action on Fix Path in State Files dialog2017-11-20T09:48:25-05:00Kitware RobotFix Cancel action on Fix Path in State Files dialog**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13096). Further discussion may take place here.**
---
PROBLEM:
Cancel of data path dialog continues to load possibly incorrect ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13096). Further discussion may take place here.**
---
PROBLEM:
Cancel of data path dialog continues to load possibly incorrect data paths.
SOLUTION:
Add canceling of entire loading of state file after clicking on 'X' or 'Cancel' button in "Fix Paths in State Files" dialog.
patched files: pqApplicationCore.[h, cxx], pqFixPathsInStateFilesBehavior.cxx
action: copy pqApplicationCore.* to ParaView-3.14.0/Qt/Core
copy pqFixPathsInStateFilesBehavior.cxx to ParaView-3.14.0/Qt/ApplicationComponents
DESCRIPTION: When user loads state file with filenames specified in it, dialog pops up to allow user to update filenames
paths. In case user clicks on Cancel or 'X' button, patch allows stopping entire process of loading of state files, instead of
stopping only fixing pathnames in state file being loaded as it was previously done. Perhaps previous behavior was intended
feature, but canceling of entire loading process when user clicks on 'X' or 'Cancel' looks much more natural than continuing with
loading of state file.
CHANGES: To make this patch, following changes were made (ParaView source patch):
- Added QuitLoadingStateFile property and its mutator to pqApplicationCore class,
- Added logic of quiting loading of state file in case flag is set in pqApplicationCore::loadStateFile() routine,
- Added setting of pqApplicationCore::QuitLoadingStateFile flag in pqFixPathsInStateFilesBehavior class.
5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17843Mismatch in generated image size with Save Screenshot2017-12-14T15:16:55-05:00Utkarsh AyachitMismatch in generated image size with Save ScreenshotOn occasion, ParaView fails to generate an output image matching the requested size. Simply run the [script](/uploads/9b023b5c9f1822631cc5c91da0f70e4e/foo.py) as follows:
```bash
# Using ParaView 5.4.1 on Linux
> pvpython -dr foo.py
```...On occasion, ParaView fails to generate an output image matching the requested size. Simply run the [script](/uploads/9b023b5c9f1822631cc5c91da0f70e4e/foo.py) as follows:
```bash
# Using ParaView 5.4.1 on Linux
> pvpython -dr foo.py
```
Instead of generating a 300x300 image, it generates a 300x299 image.
The issue arises because the vertical layout size in the file is odd and then when it splits that into two parts, the math in `vtkSMViewLayoutProxy::SetSize` has rounding issues and looses 1 pixel from the requested size.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17844New crash reading exodus dataset2017-12-14T16:56:58-05:00W. Alan ScottNew crash reading exodus datasetWe have a new crash when reading an exodus dataset. This is one file of a 128 file dataset, but it still should load OK. All headers in Exodus are the same, by spec. This file opens fine with ParaView 5.4.1. OK, here is how to replic...We have a new crash when reading an exodus dataset. This is one file of a 128 file dataset, but it still should load OK. All headers in Exodus are the same, by spec. This file opens fine with ParaView 5.4.1. OK, here is how to replicate.
* ParaView nightly, from Kitware, 11/20/2017. Tarball came up with the following: ParaView-5.4.1-868-g63ddf4d-Qt5-MPI-Linux-64bit. Local server, Linux.
* File/ Open. File is edcWildFiareParticle-DoNotRelease.e. Select variables active, Coords_, P_V_F, and Temp_p.
* Apply
Immediate seg fault.
Dying in vtkExodusIIReaderPrivate14GetCacheOrReadE19vtkExodusIICacheKey
I will send the dataset and full printout to Utkarsh and Cory.5.5 (Spring 2018)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/17845Superbuild is Broken - fontconfig, when gperf is missing2017-11-22T21:14:20-05:00W. Alan ScottSuperbuild is Broken - fontconfig, when gperf is missingThe Superbuild is broken for systems that don't include gperf. Ask me if you need a CMakeCache.txt. Here is the output.
ParaView:
> git describe
v5.4.1-870-gf326787
SuperBuild:
> git describe
v5.4.1-119-ga0ca86c
Local build, Qt en...The Superbuild is broken for systems that don't include gperf. Ask me if you need a CMakeCache.txt. Here is the output.
ParaView:
> git describe
v5.4.1-870-gf326787
SuperBuild:
> git describe
v5.4.1-119-ga0ca86c
Local build, Qt enabled, MPI off, no Mesa build.
Local-Lan:Build$ make
[ 6%] Built target cxx11
[ 13%] Built target bzip2
[ 19%] Built target zlib
[ 24%] Built target png
[ 31%] Built target python
[ 36%] Built target numpy
[ 42%] Built target szip
[ 49%] Built target hdf5
[ 50%] Built target cxx11_check
[ 55%] Built target boost
[ 62%] Built target visitbridge
[ 67%] Built target freetype
[ 73%] Built target libxml2
[ 75%] Performing build step for 'fontconfig'
Making all in fontconfig
Making all in fc-blanks
Making all in fc-case
Making all in fc-lang
Making all in fc-glyphname
Making all in src
GEN fcobjshash.h
/.../Build/superbuild/fontconfig/src/missing: line 81: gperf: command not found
WARNING: 'gperf' is missing on your system.
You might have modified some files without having the proper
tools for further handling them. Check the 'README' file, it
often tells you about the needed prerequisites for installing
this package. You may also peek at any GNU archive site, in
case some other package contains this missing 'gperf' program.
gmake[5]: *** [fcobjshash.h] Error 1
gmake[4]: *** [all-recursive] Error 1
gmake[3]: *** [all] Error 2
CMake Error at /.../Build/superbuild/sb-fontconfig-build.cmake:43 (message):
Failed with exit code 2
make[2]: *** [superbuild/fontconfig/stamp/fontconfig-build] Error 1
make[1]: *** [superbuild/CMakeFiles/fontconfig.dir/all] Error 2
make: *** [all] Error 2
@utkarsh.ayachit @ben.boeckel5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17846Low resolution vector graphics output2022-12-01T09:43:55-05:00Nicolas CelliLow resolution vector graphics outputHi,
I am using paraview for publication purposes. Whenever I try to export my figures in vector graphics format (.svg, .ps, .eps ...), I get some sort of issue that make it unusable and I have to use the "screenshot" option. The only pro...Hi,
I am using paraview for publication purposes. Whenever I try to export my figures in vector graphics format (.svg, .ps, .eps ...), I get some sort of issue that make it unusable and I have to use the "screenshot" option. The only problem is, I definitely need vector graphics, not raster images for some papers (and/or further editing).
Basically, the resolution if the vector graphics is the one of the render view, which is very low and I cannot find how to set. I can get high-res only if I zoom in to 200% in the render view, but then of course, the output file will only have the zoom view, which is only a fraction of the figure. How can I get a high-resolution vector graphics figure?
In addition to this, only .svg files look render properly: .ps, .pdf etc all have shifts in colourbar and axes with messed up labels.
I am using paraview 5.4.1 on a 2017 MacBook Pro with 16Gb RAM.
Thanks in advance,
Nicolas5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17847Preview mode fails to recognize when layout is big enough to use full-scale p...2017-12-14T17:22:09-05:00Shawn WaldonPreview mode fails to recognize when layout is big enough to use full-scale previewIf you pop the view out into its own window and maximize it (on a 1920 x 1080 monitor), then you still get the "view is not big enough using a scaled down preview mode" behavior even for the smallest preview mode (1280 x 800) which shoul...If you pop the view out into its own window and maximize it (on a 1920 x 1080 monitor), then you still get the "view is not big enough using a scaled down preview mode" behavior even for the smallest preview mode (1280 x 800) which should fit with room to spare. (I clicked the Ok and don't show again on the dialog if that matters). See image below:
![unneccesarily_scaled_down_preview](/uploads/e7d075eb47e82d6e5e7f80599db46541/unneccesarily_scaled_down_preview.png)
This was found testing !1889, so the screenshot is from that branch. `master` has other issues using preview mode in a popped-out layout window that that branch resolves.5.5 (Spring 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16984Add warning dialog when using OpenGl1 backend2017-11-21T16:31:54-05:00Utkarsh AyachitAdd warning dialog when using OpenGl1 backendAdd warning dialog when using OpenGl1 backendAdd warning dialog when using OpenGl1 backend5.3https://gitlab.kitware.com/paraview/paraview/-/issues/16964ColorBy function does not manage color legend2017-11-21T16:31:54-05:00Kenneth MorelandColorBy function does not manage color legendWhen you are changing the field variable you are coloring a mesh by in the GUI, the scalar bar annotation is updated to give you a color legend with the displayed field. However, when you use the Python `ColorBy` function, which is suppo...When you are changing the field variable you are coloring a mesh by in the GUI, the scalar bar annotation is updated to give you a color legend with the displayed field. However, when you use the Python `ColorBy` function, which is supposed to set up the coloring in the same way as the GUI, the color legend is not updated. To replicate, do the following:
1. Load disk_out_ref.ex2. Turn on all variables. Apply.
2. Open the Python Shell.
3. Type the command
```
ColorBy(GetRepresentation(), ('POINTS', 'Pres'))
```
The points get colored correctly, but the color bar is not changed to the new coloring. If the view had a color bar in the view before calling `ColorBy`, it sticks around after the colors change, which makes it hard to get rid of. The correct behavior is to get rid of color bars that are not used anymore and add the one that is.5.3https://gitlab.kitware.com/paraview/paraview/-/issues/16961Select with polygon no longer showing polygon2017-11-21T16:31:54-05:00Kenneth MorelandSelect with polygon no longer showing polygonWhen you use the `Select Cells With Polygon` or `Select Points With Polygon`, you can no longer see the polygon being drawn. To replicate:
1. Load or create some 3D data (sphere, superquadratic, disk_out_ref, whatever). Apply.
2. Click ...When you use the `Select Cells With Polygon` or `Select Points With Polygon`, you can no longer see the polygon being drawn. To replicate:
1. Load or create some 3D data (sphere, superquadratic, disk_out_ref, whatever). Apply.
2. Click either `Select Cells With Polygon` or `Select Points With Polygon`.
3. Draw a funny shape. You no longer see the polygon being drawn, but it appears that cells are being selected.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/16892Broken connectivity of plot data2017-11-21T16:31:54-05:00Utkarsh AyachitBroken connectivity of plot data(from @DennisConklin)
>
I have made up an example of this and in the process have gained some insight as to why it happens, and possible ways to avoid it in the future. Attached is a powerpoint to show it, a data file and a state f...(from @DennisConklin)
>
I have made up an example of this and in the process have gained some insight as to why it happens, and possible ways to avoid it in the future. Attached is a powerpoint to show it, a data file and a state file to play with.
[Broken_Connectivity_of_Plot_Data.pptx](/uploads/06733f5aa39bb1b73e0d2b3d72ca4d07/Broken_Connectivity_of_Plot_Data.pptx)
[ring.e](/uploads/866e16b7149c8a6f177687e0f20e8a62/ring.e)
[PlotData.pvsm](/uploads/98acd122fb9aea1b8e5f242e27c468e1/PlotData.pvsm)5.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16841Move Glyph3D Representation to Plugin2017-11-21T16:31:54-05:00Mathieu Westphal (Kitware)Move Glyph3D Representation to PluginGlyph3D is an unfinished feature that has
languished for several releases now. It can be much faster than the
standard cpu level vtk glyphs, because it is implemented in the GPU
space and uses instancing instead of replicated geometry...Glyph3D is an unfinished feature that has
languished for several releases now. It can be much faster than the
standard cpu level vtk glyphs, because it is implemented in the GPU
space and uses instancing instead of replicated geometry memory, but
without the GUI hooks in paraview to control what is glyphed and how,
it is less than useful. Moving it to a Plugin would clarify the UI for average users.Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/15887Resample with dataset doesn't work with time2017-11-21T16:31:54-05:00Kitware RobotResample with dataset doesn't work with time**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15887). Further discussion may take place here.**
---
The Resample with dataset filter doesn't work correctly over time. He...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15887). Further discussion may take place here.**
---
The Resample with dataset filter doesn't work correctly over time. Here is how to replicate. I will send dataset to Utkarsh.
* Dataset is Resample-Cone-DoNotRelease. This has two files, donor.g and recipient.g.
* Linux, 5.0.0-RC2, local server.
* Timestep 0.
* (If desired, but not necessary, Edit/ Settings/ Clamp and update every timestep).
* Open donor.g. All vars on. Apply.
* Open recipient.g. All vars on. Apply.
* Filter/ Alphabetical/ ResampleWithDataset.
** Input == donor.g
** Source == recipient.g
** OK
** Turn on Pass Cell Array
** Turn on Pass Point Arrays
** Turn off Compute Tolerance. 1e-3.
** Apply.
* Paint by TEMPK.
Lets look at our data.
* Turn visibility off for ResampleWithDataset.
* Turn visibility on for donor.g.
* (Rescale to datarange, there is a weirdness here.)
* Move forward a few timesteps, one at a time. Timestep 0 - Min is about 293.9, max is 293.9. Timestep 1 - min is 294.0, max is 294.4
Now, we can see the bug.
* Turn visibility off for donor.g.
* Turn visibility on for ResampleWithDataset.
* Back to time 0. Min is 0, max is 293.9. Not sure if this is correct.
* Forward to time 1. Min is 0, max is 293.9. This is wrong.
Basically, Rescale with Dataset isn't updating as time is changing.
(Note to me - Trevor, blade.)
5.3Sujin PhilipSujin Philiphttps://gitlab.kitware.com/paraview/paraview/-/issues/15864Annotated color legend isn't hidden correctly for trace2017-11-21T16:31:54-05:00Kitware RobotAnnotated color legend isn't hidden correctly for trace**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15864). Further discussion may take place here.**
---
We are having strange behavior for the annotated color legend, where i...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15864). Further discussion may take place here.**
---
We are having strange behavior for the annotated color legend, where it appears when it shouldn't. I have found a trivial way to replicate it using the trace recorder. This may be a symptom of other issues, I cannot tell.
* Windows, local server, 4.4.0.
* Start trace.
* Open can.exo. All vars on. Apply.
* Clip. Apply.
* Color by EQPS.
* Stop trace. Save trace as macro.
* Reset session.
* Run macro.
>> The Annotated color legend shows up, even though can is hidden. This is a bug.
5.2 (SC-16)Shawn WaldonShawn Waldon