ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2017-11-21T16:31:59-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/16891ruler hangs2017-11-21T16:31:59-05:00W. Alan Scottruler hangsThis one seems to be hard to replicate. Here is my best shot.
* Linux, master, remote server.
* Open can.exo. Apply.
* Auto apply.
* Sources/ Ruler.
Now, place the cursor over the can and start hitting the p key. First time sho...This one seems to be hard to replicate. Here is my best shot.
* Linux, master, remote server.
* Open can.exo. Apply.
* Auto apply.
* Sources/ Ruler.
Now, place the cursor over the can and start hitting the p key. First time should hang.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16100Additional line with plot global data over time, in parallel.2017-11-22T15:14:17-05:00Kitware RobotAdditional line with plot global data over time, in parallel.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16100). Further discussion may take place here.**
---
This bug only shows in parallel, numerous mpi ranks, with number of ra...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16100). Further discussion may take place here.**
---
This bug only shows in parallel, numerous mpi ranks, with number of ranks less than or equal to number of files. Basically, the end point is connected back to the first point in the plot global data over time.
* Linux, 8 pvservers, 5.0.1.
* Load z_pinch1.8.[0-7]. Load all variables. Apply.
* Plot global data over time. Apply.
* Turn off all variables. Turn on variable ZMON.
<<Bug>> Notice the straight line going back to the start. This is a bug.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/16099Plot global data over time in parallel is broken2017-11-22T15:14:17-05:00Kitware RobotPlot global data over time in parallel is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16099). Further discussion may take place here.**
---
If a user tries to plot global data over time, in parallel, with fewer...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16099). Further discussion may take place here.**
---
If a user tries to plot global data over time, in parallel, with fewer files than MPI ranks, ParaView displays nothing. Here is a trivial example.
* Linux, 8 servers (2 will show the bug), 5.0.1.
* Load can.ex2. All vars on. Apply.
* plot global data over time. Apply.
* No variables of interest are available to plot, an none are plotted. This is a bug.5.2 (SC-16)Utkarsh AyachitUtkarsh Ayachithttps://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 Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/12535D3 divde cells mode broken2018-08-28T09:39:49-04:00Kitware RobotD3 divde cells mode broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12535). Further discussion may take place here.**
---
The D3 filter has stopped working when in divide cells mode. To repli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12535). Further discussion may take place here.**
---
The D3 filter has stopped working when in divide cells mode. To replicate, do the following:
1. Run ParaView client/server or multicore with 8 process. (Less will probably also cause the failure, but I haven't tried.)
2. Open the attached CurvedCylinder.vtu. Apply.
3. Run D3, change to Divide cells boundary mode. Apply. (Note that there is a separate modification bug with D3 where if you change the boundary mode after the first apply, the filter will not re-execute.)
The result is wonky. (See the attached image.) This problem is not in ParaView 3.10, but it is in the latest master branch.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/9213Loop subdivision filter crashes paraview on some inputs2017-11-21T16:31:55-05:00Kitware RobotLoop subdivision filter crashes paraview on some inputs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9213). Further discussion may take place here.**
---
I'm sure there is just something about the input that the filter doesn'...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9213). Further discussion may take place here.**
---
I'm sure there is just something about the input that the filter doesn't expect - but it should generate an error message rather than simply crash. An example input is attached.5.2 (SC-16)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/15868ResetCamera creates bad python2017-11-22T15:14:21-05:00Kitware RobotResetCamera creates bad python**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15868). Further discussion may take place here.**
---
Having a ResetCamera between two filters makes the first filter non vi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15868). Further discussion may take place here.**
---
Having a ResetCamera between two filters makes the first filter non visible. I created a trace as follows, and will attach said trace. I will add a comment where the bad ResetCamera is.
* ParaView 4.4.0, local server, Windows.
* Start trace recorder.
* Wavelet. Apply.
* Contour. 100. Apply.
* Turn visibility of the contour off.
* Reset
* Contour. 200. Apply.
* Stop trace. Save this trace.
* Reset Session.
* Tools/ Python Shell/ run this trace.
Also relates to paraview/paraview#160055.3Shawn WaldonShawn Waldonhttps://gitlab.kitware.com/paraview/paraview/-/issues/16958Dragging slider bar in properties panel creates too many undo events2017-06-28T16:59:11-04:00Kenneth MorelandDragging slider bar in properties panel creates too many undo eventsWhen you drag a slider bar for one of the properties in the properties panel that is automatically updated, it creates an undo event for every incremental update provided by the GUI, which needlessly fills the undo stack. To replicate, d...When you drag a slider bar for one of the properties in the properties panel that is automatically updated, it creates an undo event for every incremental update provided by the GUI, which needlessly fills the undo stack. To replicate, do the following:
1. Create a Sphere source. Apply.
2. In the properties panel, slowly drag the slider for opacity.
3. Try undo. Note that each undo is a small and worthless amount.
One possible fix for this is to ignore incremental updates and only respond when the user releases the mouse from the slider. This is probably the easiest fix plus it would prevent problems when an update takes longer than a few milliseconds.5.4 (ISC 2017)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/17823Paraview is crashing on macOS 10.12 every time I use trackpad to scroll in pi...2018-02-23T08:29:41-05:00lorak41Paraview is crashing on macOS 10.12 every time I use trackpad to scroll in pipeline browser.Using Macbook's trackpad in pipeline browser results in an immediate crash. Problem does not occur with a mouse.
![Screen_Shot_2017-11-08_at_00.05.50](/uploads/8ef5cee8e282bb542dec95cd0f123f83/Screen_Shot_2017-11-08_at_00.05.50.png)Using Macbook's trackpad in pipeline browser results in an immediate crash. Problem does not occur with a mouse.
![Screen_Shot_2017-11-08_at_00.05.50](/uploads/8ef5cee8e282bb542dec95cd0f123f83/Screen_Shot_2017-11-08_at_00.05.50.png)5.5 (Spring 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17764Polyline Source widget broken2017-11-22T21:58:08-05:00Mathieu Westphal (Kitware)Polyline Source widget brokenTHe polyline source widget is broken and does not get updated when moving points .
- Open ParaView
- Create Polyline Source
- Move points
- Widget is not moving with the points
![Bug_PolyLineSource](/uploads/0aa8d998ed9e09d7365213c396f...THe polyline source widget is broken and does not get updated when moving points .
- Open ParaView
- Create Polyline Source
- Move points
- Widget is not moving with the points
![Bug_PolyLineSource](/uploads/0aa8d998ed9e09d7365213c396f3cd2e/Bug_PolyLineSource.png)5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/17689Crash when scrolling Pipeline browser (macOS 10.12, Qt 5.9.1)2018-01-15T19:28:41-05:00bobpepinCrash when scrolling Pipeline browser (macOS 10.12, Qt 5.9.1)Hi,
there seems to be some infinite looping going on when scrolling in the pipeline browser.
How to reproduce:
1. Make your Pipeline Browser window as small as possible
2. Create a couple Wavelet sources, enough so that the widget needs ...Hi,
there seems to be some infinite looping going on when scrolling in the pipeline browser.
How to reproduce:
1. Make your Pipeline Browser window as small as possible
2. Create a couple Wavelet sources, enough so that the widget needs to scroll
3. Highlight the first source and use Down Arrow until the widget starts to scroll and scrollbars appear
3. Play around for some time, scrolling both with the scrollbars and the middle mouse button
* OS: macOS Sierra 10.12.6
* Paraview: 5.4.1-509-gc685f84c (git)
* Qt: 5.9.1
Stack trace attached (top 38 frames from where the stack overflowed, repeats downwards).
[stack.txt](/uploads/f7fe0fe10324f3c1087cda66e4ee7ff7/stack.txt)5.5 (Spring 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18490ospray and embree won't build with cray programming environment in paraview 5.62018-09-27T18:14:14-04:00David E. DeMarleospray and embree won't build with cray programming environment in paraview 5.6Per discourse discussion:
https://discourse.paraview.org/t/building-5-6-0-rc1-on-cray/570
confirmed on theta@anlPer discourse discussion:
https://discourse.paraview.org/t/building-5-6-0-rc1-on-cray/570
confirmed on theta@anl5.6 (Fall 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18304Coloring by "Solid Color" is not recorded by python trace2018-09-10T21:26:43-04:00Jeremias GonzalezColoring by "Solid Color" is not recorded by python traceColoring by "Solid Color" is not recorded by python trace.
Steps to reproduce :
* Run ParaView
* Source->Wavelet, Apply
* Color By "RTData"
* Representation "Surface"
* Tools -> Start Trace, Show incremental, ok
* Color By "Solid ...Coloring by "Solid Color" is not recorded by python trace.
Steps to reproduce :
* Run ParaView
* Source->Wavelet, Apply
* Color By "RTData"
* Representation "Surface"
* Tools -> Start Trace, Show incremental, ok
* Color By "Solid Color"
* No python code related to color by is recorded on the trace.
This was originally reported in my thread here: https://discourse.paraview.org/t/solid-color-option-not-recorded-in-trace/3255.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18122Navigate button in File Dialog remains enabled after navigation2018-07-16T21:28:05-04:00Sachin KrishnanNavigate button in File Dialog remains enabled after navigationThis is a minor issue.
The state of the 'navigate' button in the file dialog is not updated (remains enabled) after it is clicked. User can navigate to non-existing directories by repeatedly clicking the navigate button.
To reproduce:
...This is a minor issue.
The state of the 'navigate' button in the file dialog is not updated (remains enabled) after it is clicked. User can navigate to non-existing directories by repeatedly clicking the navigate button.
To reproduce:
1. Invoke the open file dialog box
2. Select any directory.
3. Click the 'navigate' button. Now, you can click the 'navigate' button any number of times.5.6 (Fall 2018)https://gitlab.kitware.com/paraview/paraview/-/issues/18055plot by log axis scaling is broken2018-07-16T21:21:25-04:00W. Alan Scottplot by log axis scaling is brokenPlot by log on an axis, scaling, is broken. Here is how to replicate. Since there is a simple workaround (use custom range), I am targeting this at 5.6. Can't slip.
* 5.5.0-rc3, Linux, remote server (probably not necessary)
* Open di...Plot by log on an axis, scaling, is broken. Here is how to replicate. Since there is a simple workaround (use custom range), I am targeting this at 5.6. Can't slip.
* 5.5.0-rc3, Linux, remote server (probably not necessary)
* Open disk_out_ref.exo. All vars on. Apply.
* Plot over line. Apply.
* Turn all variables off. Turn on plot of temp.
* Slide down, click Left Axis Log Scale.
The min and max on the left axis, which should not have changed, have now jumped to about 2.5 to 3.0. Correct numbers should be about 280 to 920.5.6 (Fall 2018)Allison Vacantialliepiper16@gmail.comAllison Vacantialliepiper16@gmail.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/17640changing Number of Table Values misses a render2018-07-12T15:38:47-04:00W. Alan Scottchanging Number of Table Values misses a renderChanging the number of table values misses a render. Please fix this.
* ParaView 5.4.0, Linux, local server.
* Load disk_out_ref.exo. Load all vars. Apply.
* Clip. Apply. Paint by Temp. Show Plane off. X+.
* Color Map Editor. Ch...Changing the number of table values misses a render. Please fix this.
* ParaView 5.4.0, Linux, local server.
* Load disk_out_ref.exo. Load all vars. Apply.
* Clip. Apply. Paint by Temp. Show Plane off. X+.
* Color Map Editor. Change Color Discretization to 6. <CR>.
Notice that the rendering of the clipped disk_out_ref hasn't updated.5.6 (Fall 2018)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/19250ParaView 5.7.0-RC2: Texture Map filters (To Sphere or To Plane) are crashing ...2019-08-22T19:39:42-04:00Cory Quammencory.quammen@kitware.comParaView 5.7.0-RC2: Texture Map filters (To Sphere or To Plane) are crashing ParaView 5.7.0 RC2 on LinuxTexture Map filters (To Sphere or To Plane) are crashing ParaView 5.7.0 RC2 (Also RC1) on Linux:
( 22.417s) [paraview ] vtkSIProxy.cxx:415 ERR| vtkSISourceProxy (0x7f8a4c010630): Failed to create ‘vtkTextureMapToSphere’. This typically ...Texture Map filters (To Sphere or To Plane) are crashing ParaView 5.7.0 RC2 (Also RC1) on Linux:
( 22.417s) [paraview ] vtkSIProxy.cxx:415 ERR| vtkSISourceProxy (0x7f8a4c010630): Failed to create ‘vtkTextureMapToSphere’. This typically means that ParaView does not know about the request class to create an instance of if. Ensure that it has been correctly wrapped using the client-server wrappers and the wrapping has been initialized. Note class names are case-sensitive. Check for typos. Aborting for debugging purposes.
( 49.536s) [paraview ] vtkSIProxy.cxx:415 ERR| vtkSISourceProxy (0x70e1150): Failed to create ‘vtkTextureMapToPlane’. This typically means that ParaView does not know about the request class to create an instance of if. Ensure that it has been correctly wrapped using the client-server wrappers and the wrapping has been initialized. Note class names are case-sensitive. Check for typos. Aborting for debugging purposes.
Originally reported at https://discourse.paraview.org/t/paraview-5-7-0-release-candidate-2-available-for-download/23975.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/19217Cinema 'Export Now' exports incorrect float (recolorable) images2019-09-09T14:35:17-04:00DavidCinema 'Export Now' exports incorrect float (recolorable) imagesFloat images exported contain only ```Nan``` values.
Attached is a folder containing files to run the following test, which shows the bug:
[float_bug.zip](/uploads/6d8bf3eb690eda591e0d0b2a6083a4c0/float_bug.zip)
- open ParaView
- load...Float images exported contain only ```Nan``` values.
Attached is a folder containing files to run the following test, which shows the bug:
[float_bug.zip](/uploads/6d8bf3eb690eda591e0d0b2a6083a4c0/float_bug.zip)
- open ParaView
- load small.csv
- close the table view window that is created
- add TableToStructuredGrid filter, setting the following:
- Whole extents to 0,1 0,1 0,0
- 'X column' to x
- 'Y column' to y
- 'Z column' to z
- Coloring to 'scalar'
- Zoom so that the data fills the entire view (there is no background showing)
- run the ```test.xml``` script
- Change the 'Root Directory' field to export ```test.cdb``` to this test directory
- File->Export Now
- run ```uncompress``` script
- this will produce one ```raw``` files:
- ```uncompressed_scalar.raw```
- ```uncompressed_depth.raw```
- run ```od -f uncompressed_scalar.raw```
- this shows that the resulting uncompressed image contains only ```NaN``` values5.7 (Summer 2019)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/19216Composable+Recolorable specD export of mandelbrot crashes2019-08-13T09:22:25-04:00Ethan StamComposable+Recolorable specD export of mandelbrot crashesTested on MacOS 10.13.6 with the 5.7.0-RC1 nightly binary
Follow along with #19215, but use the Mandelbrot source
* Enable and pick iterations in export inspector->advanced->data extracts->cinema image options
* Export a static cinem...Tested on MacOS 10.13.6 with the 5.7.0-RC1 nightly binary
Follow along with #19215, but use the Mandelbrot source
* Enable and pick iterations in export inspector->advanced->data extracts->cinema image options
* Export a static cinema image database with composable+recolorable selected
* Check "Save the cinema D table" as well
* File -> Export Now crashes my client
This seems too specific to worry about getting a fix in 5.7.0, as it is the only case we've found to cause the crash.
cc: @demarle @dhr5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/19190Paraview crashing when clipping certain multiblock dataset2019-09-11T17:07:49-04:00Boonthanome NouanesengsyParaview crashing when clipping certain multiblock datasetWhen the below dataset is loaded into Paraview and a Clip filter is applied, Paraview will crash.
The dataset is a multiblock of five blocks, with each block being an unstructured grid.
The crash happened on both Paraview 5.6.0 and 5...When the below dataset is loaded into Paraview and a Clip filter is applied, Paraview will crash.
The dataset is a multiblock of five blocks, with each block being an unstructured grid.
The crash happened on both Paraview 5.6.0 and 5.7.0-RC1. I'm using the Linux client. If using the Mac client, you can prevent the crash by changing the variable being shown to something that isn't partial, for example zt. After that if you use Clip, there is no crash. If you use Extract Block to single out a block, then it does not crash.
Dataset: [data.tar.gz](/uploads/fb54d238fcafe09323ad6b175bd0213b/data.tar.gz)5.7 (Summer 2019)Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)