ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-05-16T15:28:09-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/17271python calculator - volume is wrong2017-05-16T15:28:09-04:00W. Alan Scottpython calculator - volume is wrongThe python calculator version of volume is wrong. This misrepresents data, and needs to be fixed.
Note - please test on at least image data (wavelet), exodus (disk_out_ref) and cth data (dave's small dataset).
Here is how to replicate...The python calculator version of volume is wrong. This misrepresents data, and needs to be fixed.
Note - please test on at least image data (wavelet), exodus (disk_out_ref) and cth data (dave's small dataset).
Here is how to replicate the issue on wavelet.
* Linux, 5.3.0 RC3, local server.
* Wavelet. Run from -5 to 5 for X, Y and Z. Apply.
--we now have a thousand cells, one unit in size each, so a total volume of 1000.
* Python Calculator. expression: volume(inputs[0]) Array Association: Cell Leave Array Output as result.
* Result is now junk. PV will show this as ranging from -0.999 to -1, which is another ParaView bug - numbers are actually -1 throughout.
* Show it in a spreadsheet, numbers will be -1.
This is a bug.
Now, lets start over, but leave the default Array Association, which is Point.
* Wavelet. Run from -5 to 5 for X, Y and Z. Apply.
--we now have a thousand cells, one unit in size each, so a total volume of 1000.
* Python Calculator. expression: volume(inputs[0]) Array Association: Point Leave Array Output as result.
* Result is now worse than junk - it is misleading. Further, the range now runs from 31.62 to 31.63, thus looking like there is very slight variation in the result! This needs to be fixed ASAP.
By the way, the range seen here is probably an artifact of bug #16978.
Basically, volume should work for cells, don't let users try to calculate volume on points. Alternatively, at least give a reasonable result (0 to 0).5.4 (ISC 2017)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/17263Documentation for filters in plugins does not work2017-04-04T22:13:45-04:00Utkarsh AyachitDocumentation for filters in plugins does not workSteps to reproduce (**v5.3.0-RC3**):
1. Open `can.ex2`, load all variables, Apply.
2. Load **Moments** plugin.
3. Create the **Moments Vectors** filter.
4. On the **Properties** panel, hit the [![image](/uploads/9e3d25a4d2c9835306f5...Steps to reproduce (**v5.3.0-RC3**):
1. Open `can.ex2`, load all variables, Apply.
2. Load **Moments** plugin.
3. Create the **Moments Vectors** filter.
4. On the **Properties** panel, hit the [![image](/uploads/9e3d25a4d2c9835306f5ef3d6355aa45/image.png)](*) button to get docs for the **Moments Vectors** filter. Nothing shows up. The same works fine if you did for the reader itself, for example.5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17256Flash in Linux2020-12-21T05:26:37-05:00W. Alan ScottFlash in LinuxThere is an obnoxious flash that is occurring in ParaView 5.3.0 RC3. Not sure if it is environment dependent.
* PV 5.3.0 RC3, Linux, local server. Using RGS to get to a Linux blade.
* Open can.exo. Apply.
* Right click the bloc...There is an obnoxious flash that is occurring in ParaView 5.3.0 RC3. Not sure if it is environment dependent.
* PV 5.3.0 RC3, Linux, local server. Using RGS to get to a Linux blade.
* Open can.exo. Apply.
* Right click the block. Hide Block.
* Right click the can. There is a flash, like we are flipping buffers.5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17253Format options in Annotate Global Data filter2017-12-06T16:24:35-05:00Boonthanome NouanesengsyFormat options in Annotate Global Data filterWhen using the Annotate Global Data filter, there is currently no way to format the output of the data, such as choosing whether to show in scientific notation or not, or choosing how many decimal places to show. It would be nice for tha...When using the Annotate Global Data filter, there is currently no way to format the output of the data, such as choosing whether to show in scientific notation or not, or choosing how many decimal places to show. It would be nice for that filter to have a "Format" text box, similar to how the Annotate Time filter handles it. I would imagine it would be user's responsibility to use the correct specifier, such as %i, %f, %s, etc.
@patchett2002
![screenshot](/uploads/0a67d0e7596ffa3080eb35decb6f40af/screenshot.png)5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17249Python shell can become unresponsive under certain conditions2017-04-12T17:10:01-04:00Utkarsh AyachitPython shell can become unresponsive under certain conditionsSteps to reproduce (v5.3.0-RC3):
* **Sphere**, Apply
* **Extract Selection**, Apply (do not select any cells before extracting the selection)
* **Tools | Python Shell** and type the following:
```python
a = GetActiveSource()
a....Steps to reproduce (v5.3.0-RC3):
* **Sphere**, Apply
* **Extract Selection**, Apply (do not select any cells before extracting the selection)
* **Tools | Python Shell** and type the following:
```python
a = GetActiveSource()
a.S<tab>
```
A popup menu with available options will show up. Now, continue typing
```python
a.S<tab>election<enter>
```
At this point, the shell has got into some weird state.
Try typing text like:
```python
print "hello"
```
Nothing shows up in the shell.
On quitting ParaVIew, I get the following stack trace:
```
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 491, in __getattr__
return getattr(self.SMProxy, name)
AttributeError: 'vtkPVServerManagerRenderingPython.vtkSMPVRepresent' object has no attribute 'ScalarOpacityFunction'
Traceback (most recent call last):
File "/usr/lib/python2.7/code.py", line 265, in push
more = self.runsource(source, self.filename)
File "/usr/lib/python2.7/code.py", line 76, in runsource
code = self.compile(source, filename, symbol)
File "/usr/lib/python2.7/codeop.py", line 168, in __call__
return _maybe_compile(self.compiler, source, filename, symbol)
File "/usr/lib/python2.7/codeop.py", line 82, in _maybe_compile
code = compiler(source, filename, symbol)
File "/usr/lib/python2.7/codeop.py", line 133, in __call__
codeob = compile(source, filename, symbol, self.flags, 1)
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 491, in __getattr__
return getattr(self.SMProxy, name)
AttributeError: 'vtkPVServerManagerCorePython.vtkSMSourceProxy' object has no attribute 'ShowBounds'
Traceback (most recent call last):
File "/usr/lib/python2.7/code.py", line 265, in push
more = self.runsource(source, self.filename)
File "/usr/lib/python2.7/code.py", line 76, in runsource
code = self.compile(source, filename, symbol)
File "/usr/lib/python2.7/codeop.py", line 168, in __call__
return _maybe_compile(self.compiler, source, filename, symbol)
File "/usr/lib/python2.7/codeop.py", line 82, in _maybe_compile
code = compiler(source, filename, symbol)
File "/usr/lib/python2.7/codeop.py", line 133, in __call__
codeob = compile(source, filename, symbol, self.flags, 1)
File "/home/utkarsh/Kitware/ParaView3/ParaViewBin-Qt5/lib/site-packages/paraview/servermanager.py", line 491, in __getattr__
return getattr(self.SMProxy, name)
```5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17240PV 5.3.0-rc2 - Large images created when using in-situ script2017-12-12T15:50:26-05:00Boonthanome NouanesengsyPV 5.3.0-rc2 - Large images created when using in-situ scriptUsing ParaView 5.3.0-rc2 and Catalyst for in-situ dumping of images. When using a script automatically generated from ParaView, the resulting images have a large size on disk. The pngs seem to not be compressed at all. For example, a 185...Using ParaView 5.3.0-rc2 and Catalyst for in-situ dumping of images. When using a script automatically generated from ParaView, the resulting images have a large size on disk. The pngs seem to not be compressed at all. For example, a 1855 x 1361 image is 7.6 MB. After opening it in an image editor and compressing it, the resulting size is 67 kb.5.4 (ISC 2017)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/17227VTKm Contour filter doesn't accept multiple values2017-04-25T10:47:32-04:00Chuck AtkinsVTKm Contour filter doesn't accept multiple valuesUsing the built-in Contour filter, you can specify multiple values to generate IsoContours for. However, when setting multiple values on the VTKmContour filter, only the first one is used. It should ideally be able to accept multiple v...Using the built-in Contour filter, you can specify multiple values to generate IsoContours for. However, when setting multiple values on the VTKmContour filter, only the first one is used. It should ideally be able to accept multiple values in the same way the regular Contour filter does or at the very least remove the UI option to set multiple values.5.4 (ISC 2017)Robert MaynardRobert Maynardhttps://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/17221Don't use avg for labels in 2d plots for single selections2017-04-12T15:47:00-04:00W. Alan ScottDon't use avg for labels in 2d plots for single selectionsPlease add a bit of logic to the 2d plots names. When a user selects only one point or cell, don't prepend the name with avg, and don't say Point Statistics.Please add a bit of logic to the 2d plots names. When a user selects only one point or cell, don't prepend the name with avg, and don't say Point Statistics.5.4 (ISC 2017)https://gitlab.kitware.com/paraview/paraview/-/issues/17220Turn off Median default on 2d charts.2017-04-12T15:47:16-04:00W. Alan ScottTurn off Median default on 2d charts.Please default Median off for 2d charts. This is both obnoxious for 90% of plots, and the vast majority of time users only plot one point or cell! Then, the average is all we want.Please default Median off for 2d charts. This is both obnoxious for 90% of plots, and the vast majority of time users only plot one point or cell! Then, the average is all we want.5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/172192d charts, Right Axis use custom range does not preload min and max.2017-04-12T10:08:20-04:00W. Alan Scott2d charts, Right Axis use custom range does not preload min and max.* Windows, 5.3.0-RC2, local server.
* disk_out_ref.exo. All vars on. Apply.
* Plot over line. Apply.
* Turn off all vars except Temp and Pres.
* Highlight Temp. Chart Axes, Bottom-Right.
* Properties tab/ Advanced.
* Left Axis Use Cu...* Windows, 5.3.0-RC2, local server.
* disk_out_ref.exo. All vars on. Apply.
* Plot over line. Apply.
* Turn off all vars except Temp and Pres.
* Highlight Temp. Chart Axes, Bottom-Right.
* Properties tab/ Advanced.
* Left Axis Use Custom Range. Looks good, the Min and Max are preloaded.
* Right Axis Use Custom Range. Way, way wrong. Rescaled from 0 to 1, should have been the min and max of the temperature. This is a bug.5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/17218OSPRay has bad background on Windows2017-05-11T13:51:32-04:00W. Alan ScottOSPRay has bad background on WindowsOSPRay has a really weird, bad background on Windows. Linux does not show the issue.
* Binaries from Kitware, 5.3.0-RC2, Windows, local server.
* Open can.exo. Apply.
* Enable OSPRay.
* I happen to have Mouse Trails set to ON. ...OSPRay has a really weird, bad background on Windows. Linux does not show the issue.
* Binaries from Kitware, 5.3.0-RC2, Windows, local server.
* Open can.exo. Apply.
* Enable OSPRay.
* I happen to have Mouse Trails set to ON. Ask me if you want details. As the mouse is moving across Outlook mail behind ParaView, the 2d subjects are actually bleeding into the ParaView window! In the attached image, you can see my background and a 2d e-mail thread Cory and I had going, underneath the can and color legend.
![junk1Screenshot](/uploads/09427a93de9450ce93beaa4581faf70b/junk1Screenshot.jpg)5.4 (ISC 2017)https://gitlab.kitware.com/paraview/paraview/-/issues/17208Add IceT performance information to the Timer Log2017-05-16T19:20:25-04:00W. Alan ScottAdd IceT performance information to the Timer LogIceT calculates internal performance information for all runs. Please pass this information to the Timer Log. Please at least include time spent compositing images, time passing sub images back and forth, compression time, and final ga...IceT calculates internal performance information for all runs. Please pass this information to the Timer Log. Please at least include time spent compositing images, time passing sub images back and forth, compression time, and final gather time.5.4 (ISC 2017)Andrew BauerAndrew Bauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/17205SaveScreenshot() hangs in parallel when magnification is passed as an argument2017-07-31T12:48:58-04:00Andrew BauerSaveScreenshot() hangs in parallel when magnification is passed as an argumentAttached script -- run with mpirun -np 2 bin/pvbatch testmagnification.py
[testmagnification.py](/uploads/deffd9e5fb786e8200689243506aafb2/testmagnification.py)Attached script -- run with mpirun -np 2 bin/pvbatch testmagnification.py
[testmagnification.py](/uploads/deffd9e5fb786e8200689243506aafb2/testmagnification.py)5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17200Scalar bar missing range labels when min and max are very close2017-05-05T17:14:36-04:00Cory Quammencory.quammen@kitware.comScalar bar missing range labels when min and max are very closeSteps to reproduce:
1. Sphere
2. Color by Normals
![image](/uploads/cb7f0240786a263afd5bf90164be6ef7/image.png)Steps to reproduce:
1. Sphere
2. Color by Normals
![image](/uploads/cb7f0240786a263afd5bf90164be6ef7/image.png)5.4 (ISC 2017)https://gitlab.kitware.com/paraview/paraview/-/issues/17194Cannot set scalar bar label text size2017-11-21T16:31:56-05:00Andrew BauerCannot set scalar bar label text sizeSteps to reproduce:
Wavelet
Change to Surface representation
Pseudo-color by RTData
Click on Edit Color Map button (horizontal scalar bar with circle on top)
Click on Edit color legend properties button (vertical scalar bar with e next t...Steps to reproduce:
Wavelet
Change to Surface representation
Pseudo-color by RTData
Click on Edit Color Map button (horizontal scalar bar with circle on top)
Click on Edit color legend properties button (vertical scalar bar with e next to it)
Change Text/Annotation Font Properties from 7 to 20 and hit Apply (shrinks the text)
Change Text/Annotation Font Properties from 20 to 25 and hit Apply (doesn't change the text)
Also, hover for "Edit color legend properties" should be consistent with pop-up dialogue box header which currently is "Edit Color Legend Parameters"5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17191VTK-m Contour Filter crashes when no contours are selected2017-05-01T14:35:02-04:00Kenneth MorelandVTK-m Contour Filter crashes when no contours are selectedIf you create a VTK-m Contour Filter and then try to run it with no isosurface selected, ParaView will crash. To replicate, do the following.
1. Load the VTKmFilters Plugin.
2. Create Wavelet source. Apply.
3. Add VTKm Contour Filter. A...If you create a VTK-m Contour Filter and then try to run it with no isosurface selected, ParaView will crash. To replicate, do the following.
1. Load the VTKmFilters Plugin.
2. Create Wavelet source. Apply.
3. Add VTKm Contour Filter. Apply. (Everything is fine so far.)
4. Delete the isosurface value so that there are non. Apply. Crash.5.4 (ISC 2017)Robert MaynardRobert Maynardhttps://gitlab.kitware.com/paraview/paraview/-/issues/171905.3.0-RC1: misc. regressions on macOS2017-05-09T12:22:38-04:00Elias Pipping5.3.0-RC1: misc. regressions on macOSThere are multiple issues here. I don't know what's going on or what's causing them so I'll just attach a few renderings, briefly explain how I obtained them, and hope the (unintentional?) differences between 5.2.0 and 5.3.0-RC1 speak fo...There are multiple issues here. I don't know what's going on or what's causing them so I'll just attach a few renderings, briefly explain how I obtained them, and hope the (unintentional?) differences between 5.2.0 and 5.3.0-RC1 speak for themselves.
In a script(\*), I render a scene to a PNG file. I get a render view and set its size like this
```python
renderView1 = GetActiveViewOrCreate('RenderView')
renderView1.ViewSize = [1000, 400]
```
I also attach a color bar to the plot
```python
velocityLUTColorBar = GetScalarBar(velocityLUT, renderView1)
velocityLUTColorBar.Title = 'Velocity'
velocityLUTColorBar.ComponentTitle = 'Magnitude [mm/s]'
velocityLUTColorBar.AutomaticLabelFormat = 0
velocityLUTColorBar.LabelFormat = '%.1f'
velocityLUTColorBar.RangeLabelFormat = '%.1f'
velocityLUTColorBar.NumberOfLabels = 6
velocityLUTColorBar.TitleFontSize = 7
velocityLUTColorBar.LabelFontSize = 6
velocityLUTColorBar.TitleJustification = 'Centered'
velocityLUTColorBar.AutoOrient = 0
velocityLUTColorBar.Orientation = 'Horizontal'
velocityLUTColorBar.AspectRatio = 40.0
# I do not understand these numbers
velocityLUTColorBar.Position = [0.36, 0.75]
velocityLUTColorBar.Position2 = [0.3, 0.0]
```
and put an annotation in place (this rendering is really one frame from a video(\*\*)):
```python
pythonAnnotation2 = PythonAnnotation(Input=timeInfo)
pythonAnnotation2.ArrayAssociation = 'Row Data'
pythonAnnotation2.Expression = """
'simulation time: {:.3f}s'.format((relativeTime[0]) * 1000)
"""
pythonAnnotation2Display = Show(pythonAnnotation2, renderView1)
pythonAnnotation2Display.WindowLocation = 'AnyLocation'
pythonAnnotation2Display.Position = [0.07, 0.05]
```
Now I observe four differences in the output between 5.3.0-RC1 and 5.2.0, all of which I find undesirable:
1. With 5.3.0-RC1, I get a 500x200 PNG instead of the 1000x400 I would expect (and which I get with 5.2.0!)
2. (After requesting 2000x800 with 5.3.0-RC1, resulting in a 1000x400 PNG) It seems font sizes are slightly different now (smaller)
3. (with the aforementioned change still) There are no periods on the colorbar tick labels
4. (with the aforementioned change still) If you look at the annotation at the bottom, you can see a nonsmooth transition from the upper half to the lower half, most noticeable in the numbers 7 and 9.
To illustrated, I'm attaching three PNGs: (1) The 1000x400 with 5.2.0, (2) the 500x200 with 5.3.0-RC1 arising from the same script and (3) the 1000x400 with 5.3.0-RC1 resulting from a hack to the script.
![test13_snapshot.0000-5.2](/uploads/0c22845f77b3819439e145d1c3fa3ca8/test13_snapshot.0000-5.2.png)
![test13_snapshot.0000-5.3.0-RC1](/uploads/ff2fd40ad9672878af12c296890e544f/test13_snapshot.0000-5.3.0-RC1.png)
![test13_snapshot.0000-5.3.0-RC1_new](/uploads/58608f4b2be120b21d5d05a8e2568c38/test13_snapshot.0000-5.3.0-RC1_new.png)
(\*) I don't mind sharing the script but it needs to load some data and so I expect it would be of limited use. I have not worked on a minimal working example, yet, hoping that one will not be necessary.
(\*\*) The complete video is supposed to look like [this one](http://page.mi.fu-berlin.de/pipping/files/publications/2016-RosenauCorbiDominguez-A-NumEQ.mp4) obtained with 5.1.2.
PS: I've manually disabled FXAA through `renderView1.UseFXAA = 0`.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17184Volume representation with varying opacity is lost when reloading Python script2017-05-08T23:15:28-04:00Jean M. FavreVolume representation with varying opacity is lost when reloading Python script[Volume.py](/uploads/bd477f5121af82ca7d6edb44f58b3f58/Volume.py)
Get a Wavelet, set Representation type to Volume, change the opacity, save as python script.
Reload. The GUI of the Colormap Editor is active, but the representation ...[Volume.py](/uploads/bd477f5121af82ca7d6edb44f58b3f58/Volume.py)
Get a Wavelet, set Representation type to Volume, change the opacity, save as python script.
Reload. The GUI of the Colormap Editor is active, but the representation does not use the opacity settings.
Tried with 5.3RC15.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17183handful of cinema problems2017-04-14T11:45:55-04:00David E. DeMarlehandful of cinema problemscinema import warnings are too terse
https://gitlab.kitware.com/cinema/cinema_python/merge_requests/100
problems with cinema value rendering export using and later computing the wrong ranges
https://gitlab.kitware.com/vtk/vtk/merge_requ...cinema import warnings are too terse
https://gitlab.kitware.com/cinema/cinema_python/merge_requests/100
problems with cinema value rendering export using and later computing the wrong ranges
https://gitlab.kitware.com/vtk/vtk/merge_requests/24735.4 (ISC 2017)