ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T21:43:06-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18057Wavelet/ Information Type wrong2021-03-23T21:43:06-04:00W. Alan ScottWavelet/ Information Type wrong* 5.5.0-rc3/ Linux.
* Sources/ Wavelet. Apply.
* Open the Information tab.
* Slide the Information tab as narrow as can be, grabbing the slider between the 3d window and the Information tab.
Notice that the Type will say: "ge (Uniform ...* 5.5.0-rc3/ Linux.
* Sources/ Wavelet. Apply.
* Open the Information tab.
* Slide the Information tab as narrow as can be, grabbing the slider between the 3d window and the Information tab.
Notice that the Type will say: "ge (Uniform Rectilinear Grid). We are truncating the left side, not the right side of the string. This is a bug.https://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/17639Color legend always shows up in bottom left corner when exporting to EPS or PDF2021-03-23T19:24:44-04:00Cory Quammencory.quammen@kitware.comColor legend always shows up in bottom left corner when exporting to EPS or PDFFrom a comment posted to https://blog.kitware.com/color-legend-improvements-coming-to-paraview-5-4/:
> With v5.4, whenever I export a scene in for example, eps or pdf format, the color legend is automatically placed in the left bottom c...From a comment posted to https://blog.kitware.com/color-legend-improvements-coming-to-paraview-5-4/:
> With v5.4, whenever I export a scene in for example, eps or pdf format, the color legend is automatically placed in the left bottom corner, even though I had placed somewhere else. It is fine for png or jpg though.5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18781Selection SubProxy redefinition in chart representation does not work correctly.2021-03-23T19:12:15-04:00Mathieu Westphal (Kitware)Selection SubProxy redefinition in chart representation does not work correctly.Trying to redefine a selection subproxy in a chart representation does not work as expected :
```
<ParaViewPlugin>
<ServerManagerConfiguration>
<ProxyGroup name="views">
<ContextViewProxy base_proxygroup="internal_views"
...Trying to redefine a selection subproxy in a chart representation does not work as expected :
```
<ParaViewPlugin>
<ServerManagerConfiguration>
<ProxyGroup name="views">
<ContextViewProxy base_proxygroup="internal_views"
base_proxyname="XYChartViewBase4Axes"
class="vtkPVXYChartView"
name="XYChartView2"
label="Line Chart View 2"
processes="client|renderserver|dataserver"
representation_name="XYChartRepresentation2"
post_creation="SetChartTypeToLine" >
<Documentation>This is the proxy for the XY line chart
view that support column selection.</Documentation>
</ContextViewProxy>
</ProxyGroup>
<ProxyGroup name="representations">
<ChartRepresentationProxy base_proxygroup="representations"
base_proxyname="XYChartRepresentation"
class="vtkXYChartRepresentation"
name="XYChartRepresentation2"
processes="client|dataserver|renderserver">
<Documentation>API for representations used by XYChartView and XYBarChartView.
</Documentation>
<SubProxy command="SetSelectionRepresentation">
<RepresentationProxy name="SelectionRepresentation"
class="vtkChartSelectionRepresentation"
override="1"
processes="client|dataserver|renderserver">
<InputProperty command="SetInputConnection"
name="OriginalSelectionInput"/>
</RepresentationProxy>
</SubProxy>
</ChartRepresentationProxy>
</ProxyGroup>
</ServerManagerConfiguration>
</ParaViewPlugin>
```
How to reproduce :
* Open ParaView
* Tools -> LoadPlugin -> Load -> [XYChartRepresentation2.xml](/uploads/98774ebf09cc9a7de4c1dbf435d102e5/XYChartRepresentation2.xml)
* Open vehicules_data.csv, Apply
* Create a new view, Line Chart View 2
* Show vehicules in new view
* Split the view in two, create a spreadsheet
* Select using the rectangle selection tools
* the selection is created correctly but nothing is visible in the chart view
note : unrelated to the override mechanism
@utkarsh.ayachitMathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/18609Writer Plugin with an already existing extension prevent default writer to be...2021-03-23T19:06:43-04:00Mathieu Westphal (Kitware)Writer Plugin with an already existing extension prevent default writer to be usedLoading a Plugin that defines a writer with an elready existing extension will prevent this writer to ever be used when saving data.
How to reproduce :
* Build ParaView
* Build this [plugin](/uploads/d1ce3703424d35844d73e45f0c24e7af/W...Loading a Plugin that defines a writer with an elready existing extension will prevent this writer to ever be used when saving data.
How to reproduce :
* Build ParaView
* Build this [plugin](/uploads/d1ce3703424d35844d73e45f0c24e7af/Writer.tgz), that create a .tiff writer with suplemental options
* Run paraview
* Load the built plugin
* Create a wavelet, apply
* Save Data, "test", select "Tiff File" (not the plugin)
* The plugin writer is used and supplemental options are shown
This make total sense regarding the way the writer is chosen, we would need the same kind of design as for the readers.https://gitlab.kitware.com/paraview/paraview/-/issues/18272ParaView does not allow to extend a proxy definition nor to change a property...2021-03-23T18:48:11-04:00Mathieu Westphal (Kitware)ParaView does not allow to extend a proxy definition nor to change a property default value in an xml pluginParaView does not allow to extend a proxy definition nor to change a property default value in an xml plugin.
It is actually possible to do that by copying the full proxy and changing adding from here.
However this is not a really good ...ParaView does not allow to extend a proxy definition nor to change a property default value in an xml plugin.
It is actually possible to do that by copying the full proxy and changing adding from here.
However this is not a really good way of doing it, as all the copied property may break at some point
if keeping paraview up to date, and new property added to paraview will not be automatically added.
I personally this feature would be a great one, and would allow lots of other to personalize paraview to their
usage, even with the release, without any C++ knowledge needed.https://gitlab.kitware.com/paraview/paraview/-/issues/18214I no longer use apche as a front end and Python the launcher as a front end2021-03-23T18:40:41-04:00luanliangI no longer use apche as a front end and Python the launcher as a front endI no longer use apche as the front, I want to realize the multi-user, how should I get assigned port Numbers, should how to configure and use Python the launcher as a front end, I have use this url directly, get in return is that,,![imag...I no longer use apche as the front, I want to realize the multi-user, how should I get assigned port Numbers, should how to configure and use Python the launcher as a front end, I have use this url directly, get in return is that,,![image](/uploads/bd99e5e9ed6d24069f72c579f575ac29/image.png)https://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/17957Multiple identical "sources" proxies in a saved XML state file (GlyphType)2021-03-23T18:09:21-04:00Artem BodrinMultiple identical "sources" proxies in a saved XML state file (GlyphType)Hello, dear developers.
I'm not sure if this is a bug, but I have noticed, that saved xml state file contains many identical proxies, that belongs to group "sources". These proxies are actual source proxies, and participating in propert...Hello, dear developers.
I'm not sure if this is a bug, but I have noticed, that saved xml state file contains many identical proxies, that belongs to group "sources". These proxies are actual source proxies, and participating in property <GlyphType> of every saved "GeometryRepresentation" proxy.
So every "GeometryRepresentation" have it's own bunch of GlyphType source proxy instances (listed in proxy_list Domain), and all of them are saved to a state file.
I can understand, that saving all of them can be explained by "unified approach" to saving proxy to state file, but I have trouble with resulting state file - we tracking it's change with VCS (git, if it matters), and so many unnecessary (cause they are identical, except GlobalId) proxies saved gives us additional pain.
As an additional side effect we have increased state loading time. This issue might be related to appearance of saved GlyphType proxies in a state file: #17768
Please, correct me if I'm wrong, but one can not change the Domain type at runtime, so this proxy_list will be constant until changed in a views_and_representations.xml. If so, than maybe there is a way to save GlyphType proxies to state file only once (or not at all) and reference their GlobalIds from any other GeometryRepresentation?
Thanks in advance, Artem.https://gitlab.kitware.com/paraview/paraview/-/issues/17887Dashboard, latest-packages: build failure on bigmac2021-03-23T18:02:52-04:00Cory Quammencory.quammen@kitware.comDashboard, latest-packages: build failure on bigmachttps://open.cdash.org/viewNotes.php?buildid=5178744https://open.cdash.org/viewNotes.php?buildid=5178744https://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/16205Clip 3D widget updates too often in auto update mode2021-03-23T12:37:30-04:00Kitware RobotClip 3D widget updates too often in auto update mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16205). Further discussion may take place here.**
---
When you are dragging the 3D plane widget for the clip filter and you have...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16205). Further discussion may take place here.**
---
When you are dragging the 3D plane widget for the clip filter and you have autoupdate on, it will update the pipeline regularly while the mouse is being dragged. For very small data this is not a big deal. However, if we change ParaView to autoupdate all the time, then this is very problematic for large data sets.
Before autoupdate is turned on all the time (or by default), this behavior should change to update only after the user lets go of the mouse.https://gitlab.kitware.com/paraview/paraview/-/issues/16120Warning with Auto Apply on and changing threshold scalars2021-03-23T12:35:04-04:00Kitware RobotWarning with Auto Apply on and changing threshold scalars**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16120). Further discussion may take place here.**
---
I have noticed that if you have Auto Apply on and then change the Scalars ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16120). Further discussion may take place here.**
---
I have noticed that if you have Auto Apply on and then change the Scalars property in the Threshold filter, you get an annoying and useless warning when the min/max go out of range. To replicate, do the following:
1. Turn on Auto Apply.
2. Open disk_out_ref. All variables on.
3. Add Threshold filter. By default, it will threshold on the AsH3 field.
4. Change the Scalars to Temp
When you change the scalars to Temp, you get the following warning:
Warning: In /Users/kitware/buildbot-slave/paraview-bigmac-osx-shared-release_opengl2_osx10_7_qt4_superbuild/build/paraview/src/paraview/ParaViewCore/ServerManager/Rendering/vtkSMTransferFunctionProxy.cxx, line 420
vtkSMTransferFunctionProxy (0x7fe39ae4d2c0): No prominent values for consumerhttps://gitlab.kitware.com/paraview/paraview/-/issues/14621Add support for cell locators to the probe filter2021-03-23T12:34:09-04:00Kitware RobotAdd support for cell locators to the probe filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14621). Further discussion may take place here.**
---
There are situations where FindCell can fail due to its use of point locat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14621). Further discussion may take place here.**
---
There are situations where FindCell can fail due to its use of point locators. This is specially an issue in grids that are not topologically well connected such as mesh refinement grids (unstructured) that have hanging nodes. Given the option to use a cell locator should address such cases. In fact, it may be a good idea to investigate using cell locators as the only option if the performance overhead is not large.https://gitlab.kitware.com/paraview/paraview/-/issues/15939Incorrect shading results in ParaViewWeb Local(VGL) mode2021-03-23T12:25:19-04:00Kitware RobotIncorrect shading results in ParaViewWeb Local(VGL) mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15939). Further discussion may take place here.**
---
It seems the Local(VGL) rendering mode in ParaViewWeb has issues with some...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15939). Further discussion may take place here.**
---
It seems the Local(VGL) rendering mode in ParaViewWeb has issues with some model files.
How to reproduce the issue:
open the visualiser, selecte the data file: 'can.ext2'.
Under 'Remote mode': all is ok, no issue
Under 'Local(VGL) mode': if the model is zoomed out to a certain distance, some faces on the model is shaded black.
Under 'Local(VGL) mode': the black area now display as transparency, looks like holes on the model.
Figures and data files are attached.you will need to modify the 'far' value in the frustum parameters to '100000.0' display the model.
I guees this is caused by the rendering mechanism differences between Paraview and ParaViewWeb . This issue exists in both paraview4.3 & 4.4, anyone knows how to solve it? or any other solutions the get correct rendering results in Local(VGL) mode? Thanks in advance!https://gitlab.kitware.com/paraview/paraview/-/issues/20483Annotate Global Data filter incorrect for integers2021-03-23T12:14:57-04:00Boonthanome NouanesengsyAnnotate Global Data filter incorrect for integersIn the Annotate Global Data filter, the default Format string is "%7.5g". If a field data has the value 1, then in Paraview 5.8.1, the annotation would show 1. In Paraview 5.9.0, the annotation now shows 0. In python, the output of `"%7....In the Annotate Global Data filter, the default Format string is "%7.5g". If a field data has the value 1, then in Paraview 5.8.1, the annotation would show 1. In Paraview 5.9.0, the annotation now shows 0. In python, the output of `"%7.5g" % 1` is 1, so this looks like a bug.
Here is a test dataset: [wavelet.vti](/uploads/dc4eb224042e5c24881336af76b3d817/wavelet.vti)
To reproduce:
- Open the file in Paraview 5.9.0, and create an Annotate Global Data Filter
- Hit Apply, and the annotation will show 0, but the actual value of the field data is 1
Edit: I just tried this on the latest master, and with master the annotation says 6.9531e-310.
@patchett2002 @cory.quammen @utkarsh.ayachit
![screenshot](/uploads/1ee2c6a21c6ce8de0daf510efcd675fd/screenshot.png)5.9.1 (Spring 2021)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15515Volume Renderring not working with multipiece dataset2021-03-23T11:59:17-04:00Kitware RobotVolume Renderring not working with multipiece dataset**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15515). Further discussion may take place here.**
---
Volume rendering is performed only on the first piece of a multipiece data...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15515). Further discussion may take place here.**
---
Volume rendering is performed only on the first piece of a multipiece dataset.
How to reproduce :
- Open a 3D multipiece dataset (see attached file)
- Switch to volume representation
What is seen:
- Only one of the two pieces is visible
What is expected:
- Both pieces should be renderedhttps://gitlab.kitware.com/paraview/paraview/-/issues/15008MPI tags need to be <= MPI_TAG_UB2021-03-23T11:57:26-04:00Kitware RobotMPI tags need to be <= MPI_TAG_UB**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15008). Further discussion may take place here.**
---
Currently in VTK/ParaView we don't ensure that the MPI tag are within vali...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15008). Further discussion may take place here.**
---
Currently in VTK/ParaView we don't ensure that the MPI tag are within valid ranges for the MPI implementation. This is causing issues with certain MPI implementations. Standard only guarantees a value >= 32767 for MPI_TAG_UB.https://gitlab.kitware.com/paraview/paraview/-/issues/15163Volume render crash in AMD graphic card(Win64)2021-03-23T11:53:19-04:00Kitware RobotVolume render crash in AMD graphic card(Win64)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15163). Further discussion may take place here.**
---
I'm using paraview 4.2 to pro-process the openfoam data. while using volum...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15163). Further discussion may take place here.**
---
I'm using paraview 4.2 to pro-process the openfoam data. while using volume render, the crash like:
ERROR: In C:\DBD\pvs-x64\paraview\src\paraview\VTK\Rendering\VolumeOpenGL\vtkOpenGLProjectedTetrahedraMapper.cxx, line 185
vtkOpenGLProjectedTetrahedraMapper (000000001BD57440): The required extensions are not supported.
The graphic card is R9 290X(with newest AMD official driver). Volume render works fine with my another computer with NVIDA GTX760.https://gitlab.kitware.com/paraview/paraview/-/issues/12319Show landmark labels in all 3D views2021-03-23T10:39:16-04:00Kitware RobotShow landmark labels in all 3D views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12319). Further discussion may take place here.**
---
Show landmark labels in all 3D views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12319). Further discussion may take place here.**
---
Show landmark labels in all 3D views