ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2020-12-21T05:26:37-05:00https://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/17175Spreadsheet's `Composite Data Set Index` widget not working correctly in all ...2020-02-13T01:37:42-05:00Utkarsh AyachitSpreadsheet's `Composite Data Set Index` widget not working correctly in all cases* Open `can.ex2`, Apply
* Close active view, and show data in spreadsheet view
* Now in python shell, do this and observer the changes to the **Composite Data Set Index** widget on the Display properties after each property change
`...* Open `can.ex2`, Apply
* Close active view, and show data in spreadsheet view
* Now in python shell, do this and observer the changes to the **Composite Data Set Index** widget on the Display properties after each property change
```python
a = GetDisplayProperties()
a.CompositeDataSetIndex = [ 0 ] # wrong widget state
a.CompositeDataSetIndex = [ 1 ] # wrong widget state
a.CompositeDataSetIndex = [ 2 ] # correct
a.CompositeDataSetIndex = [ 2, 3 ] # semi-correct. the state for **Element Blocks**
# is wrong (should be fully checked, not partially checked, see below)
```
![image](/uploads/8d660f3d7a4443fc1bd3a7f30db0b901/image.png)
`pqSignalAdaptorCompositeTreeWidget` needs to be refactored5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/14430time steps not right for reading a series of vtm files2018-08-08T22:26:12-04:00Kitware Robottime steps not right for reading a series of vtm files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14430). Further discussion may take place here.**
---
The time steps for reading a series of vtm files with each vtm file being ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14430). Further discussion may take place here.**
---
The time steps for reading a series of vtm files with each vtm file being time independent is wrong. The steps to reproduce are:
1) Create a multiblock data set (I created a wavelet and a line source and then combined them with the group datasets filter)
2) Write this multiblock to several files like (tmp1.vtk, tmp2.vtm, tmp3.vtm,...)
3) Load these files in as a file series
4) Select a point and then do a plot selection over time -- the time in the plot will show only time 0.
Note that the information tab shows the expected time steps. Note that steps 1 and 2 can be skipped by using the data sets that I attached. 5.4 (ISC 2017)https://gitlab.kitware.com/paraview/paraview/-/issues/14618Deleting file with animation running freezes paraview2018-08-08T22:26:03-04:00Kitware RobotDeleting file with animation running freezes paraview**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14618). Further discussion may take place here.**
---
Starting a multi-file series animation and then deleting the respective fi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14618). Further discussion may take place here.**
---
Starting a multi-file series animation and then deleting the respective file(..s) from the pipeline browser renders paraview non-responsive (OS X 10.9.2)5.4 (ISC 2017)https://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/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/17306Export Scene for 2d plots misses columns2017-12-06T16:24:20-05:00W. Alan ScottExport Scene for 2d plots misses columnsI believe we are missing columns of information when Export Scene is run for 2d plots. Here is how to replicate:
* 5.3.0, Linux, local server.
* can.exo, all vars on, apply.
* Select Points On. Select maybe 10 points somewhere on ...I believe we are missing columns of information when Export Scene is run for 2d plots. Here is how to replicate:
* 5.3.0, Linux, local server.
* can.exo, all vars on, apply.
* Select Points On. Select maybe 10 points somewhere on the can.
* Plot Selection Over Time. Apply. Turn on only ACCL Magnitude.
* Export Scene.
Now, open the file. You will find columns for time, average, median, min/max (I believe it is max), and q1/q3 (I believe it is the third quartile.
What I want is time, average, median, min, max, q1 and then q3.5.4 (ISC 2017)Chet NieterChet Nieterhttps://gitlab.kitware.com/paraview/paraview/-/issues/17358Shapo Cannot Build against ParaView/5.[2|3].0-osmesa installations' VTK libra...2017-12-06T16:23:53-05:00Jennifer GreenShapo Cannot Build against ParaView/5.[2|3].0-osmesa installations' VTK librariesAttempts to build Shapo against 5.2.0-osmesa VTK installations are failing. This is a show-stopper for production code releases to effectively utilize ParaView installations at our site. @patchett2002 @chuck.atkinsAttempts to build Shapo against 5.2.0-osmesa VTK installations are failing. This is a show-stopper for production code releases to effectively utilize ParaView installations at our site. @patchett2002 @chuck.atkins5.4 (ISC 2017)Chuck AtkinsChuck Atkinshttps://gitlab.kitware.com/paraview/paraview/-/issues/17398macOS: Orthographic Slice View renders incorrectly2017-12-05T15:36:30-05:00Utkarsh AyachitmacOS: Orthographic Slice View renders incorrectly![image](/uploads/171bc453800922e4993155db89b9e7ac/image.png)
This was with v5.3.0-460-gecc87b7c9c![image](/uploads/171bc453800922e4993155db89b9e7ac/image.png)
This was with v5.3.0-460-gecc87b7c9c5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/14980Scalar bar legend labels have not reliable behaviour for display2017-12-04T12:46:57-05:00Kitware RobotScalar bar legend labels have not reliable behaviour for display**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14980). Further discussion may take place here.**
---
In the "Color map editor", there is a dialog box "Edit color legend parame...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14980). Further discussion may take place here.**
---
In the "Color map editor", there is a dialog box "Edit color legend parameters".
It allows to choose the number of labels that you want to show along the scalar bar legend by filling the field "Number Of Labels".
But the number of the labels asked for the displaying doesn't correspond to the real number of the displayed labels.
The behaviour is similar to the following:
Number Of Labels = 1 --> 0 label is displayed
Number Of Labels = 2 --> 1 label is displayed
Number Of Labels = 3 to 5 --> 2 labels are displayed
Number Of Labels = 6 to 14 --> 5 labels are displayed
Number Of Labels = 15 to 23 --> 14 labels are displayed
Number Of Labels = 24 to 29 --> 23 labels are displayed
Number Of Labels = 30 to 59 --> 29 labels are displayed
Number Of Labels => 60 OR = 0 --> 59 labels are displayed
Could it be possible that the number of labels asked is exactly the number of labels displayed ?5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15049Logarithmic color legend tick marks in wrong position2017-12-04T12:46:56-05:00Kitware RobotLogarithmic color legend tick marks in wrong position**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15049). Further discussion may take place here.**
---
Suppose I set up a logarithmic color legend that spans, for example, from ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15049). Further discussion may take place here.**
---
Suppose I set up a logarithmic color legend that spans, for example, from 10 to 100.
One would expect to have default tick marks at 10, 20, 30 ... 100. The total amount of tick marks would thus be 10.
Please, check this: you have 11 tick marks. Thus, ticks are not intuitive to read, as one does not know which values they represent.
I also noticed that the manual annotations do not account for logarithmic scaling, so that if I want to add a manual annotation I have to calculate the non-logarithmic position of the annotation with the following formula:
xmin=minimum value of legend
xmax=maximum value of legend
x=desired annotation value
x' = xmin + (xmax-xmin)*(log10(x)-log10(xmin))/(log10(xmax)-log10(xmin))
For example, in the above example, if I add an annotation at x=30, it will appear at the position of x=30 of the nonlogarithmic color legend. When I apply the above formula, I get x'=52.9409. That is the position I have to assign the annotation of x=30 when using logarithmic scale, if I want it to be correctly located.
Thank you very much.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15319Scalar Bar label position is WRONG!2017-11-30T11:38:10-05:00Kitware RobotScalar Bar label position is WRONG!**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15319). Further discussion may take place here.**
---
+ Sphere, Apply,
+ Calculator, Expression= "1", Apply
+ Color by "Result...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15319). Further discussion may take place here.**
---
+ Sphere, Apply,
+ Calculator, Expression= "1", Apply
+ Color by "Result"
+ Edit Color Map,
+ Set color map range to custom range (0, 10). Edit the color legend properties and change the maximum number of labels to 25. Uncheck "Draw Sub Tick Marks", just to keep the legend easy to read.
+ Change number of table values to 10. You'll get a color legend similar to the one attached. This is wrong!
Verify by change the Calculator expression to 0, 1, 2,.... and see what color it produces and what it shows as in the color legend.
5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15862Removing title on color legend messes up ticks and labels2017-11-22T15:14:21-05:00Kitware RobotRemoving title on color legend messes up ticks and labels**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15862). Further discussion may take place here.**
---
I have discovered on ParaView 4.4 with Mac that if you remove the title on...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15862). Further discussion may take place here.**
---
I have discovered on ParaView 4.4 with Mac that if you remove the title on the color legend it messes up the placement of the ticks and other labels. To replicate, do the following.
1. Create a Mandelbrot source. Apply.
2. Move the color legend to the bottom of the view so that it lies horizontal.
3. Open the color map editor.
4. Click the edit color legend properties button to open that dialog.
5. In that dialog, delete the contents of the Title edit box.
6. Click OK.
At this point you will see that the tick marks rise above the bar. Even more strangely, if you move the bar with the mouse, the ticks will start to zoom up to the top of the view and beyond.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/16000Color legend: with few colors the size of the individual blocks are different2017-11-22T15:14:19-05:00Kitware RobotColor legend: with few colors the size of the individual blocks are different**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16000). Further discussion may take place here.**
---
Color legend: with few colors (from 5 to 30) the size of the individual bl...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16000). Further discussion may take place here.**
---
Color legend: with few colors (from 5 to 30) the size of the individual blocks are different and there is no correspondence with ticks.
This wrong behavior occurs with all versions of ParaView 4.x and 5.x, on Windows and Linux.
I tested ParaView 4.3.1, 4.4.0 and 5.0.0 on Windows 7 and 10, Fedora 21 and 22, Linux Mint 17 and I found same behavior.
Example: attached image Linux_pv5_20colors.png; block of the first color has a width of 52 pixel, block of the second color has a width of 40 pixel.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17153Default label format for Color Legend not very useful2017-11-21T16:31:56-05:00Utkarsh AyachitDefault label format for Color Legend not very usefulSee discussion on paraview/paraview#17149. It's not clear why we have the werid label format default, rather than just using `%g`.See discussion on paraview/paraview#17149. It's not clear why we have the werid label format default, rather than just using `%g`.5.4 (ISC 2017)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://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/15643View label making it hard to swap views2017-11-21T16:31:55-05:00Kitware RobotView label making it hard to swap views**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15643). Further discussion may take place here.**
---
When you have multiple views open, you can change the arrangement of v...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15643). Further discussion may take place here.**
---
When you have multiple views open, you can change the arrangement of views by pressing the mouse button down on the toolbar of one view and dragging it to the toolbar of another view. Unless the GUI window is very large, these view toolbars are completely covered by buttons and the label. It is most natural to grab where the label is and drag from there to prevent accidentally hitting one of the buttons. However, if you try to drag from the label, the drag does not work. The region of the toolbar with the label should behave the same as a blank part.
Note that I am observing this behavior on Mac. I have not checked if this behavior is the same on other platforms.5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16832ExtractSelection does not support to clean the selection input2017-11-21T16:31:55-05:00Mathieu Westphal (Kitware)ExtractSelection does not support to clean the selection inputWhen Extracting a Selection with extractSelection, the selection cannot be cleaned.
How to reproduce :
* Open Paraview
* Create Sphere
* Add extractSelection filter
* Select cells on surface of the sphere
* Copy active se...When Extracting a Selection with extractSelection, the selection cannot be cleaned.
How to reproduce :
* Open Paraview
* Create Sphere
* Add extractSelection filter
* Select cells on surface of the sphere
* Copy active selection in extract selection filter, Apply
* clean selection on sphere
* Copy active selection in extact selection filter, Apply
* Nothing happens when it should have cleaned it with no output.
Notes :
pqSelectionInputWidget.cxx:304 returns when selection is null.5.4 (ISC 2017)Shawn WaldonShawn Waldonhttps://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/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.com