ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2018-01-07T03:59:29-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/16107Trace record pallet changes2018-01-07T03:59:29-05:00Kitware RobotTrace record pallet changes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16107). Further discussion may take place here.**
---
Please add the ability to record pallet changes when saving a screenshot. **This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16107). Further discussion may take place here.**
---
Please add the ability to record pallet changes when saving a screenshot. https://gitlab.kitware.com/paraview/paraview/-/issues/16106Auto convert may cause failure to reset Threshold's range values2018-01-07T03:59:29-05:00Kitware RobotAuto convert may cause failure to reset Threshold's range values**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16106). Further discussion may take place here.**
---
For some variables, having the Auto Convert Properties enabled in the sett...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16106). Further discussion may take place here.**
---
For some variables, having the Auto Convert Properties enabled in the settings will cause the Threshold filter's "Reset using current data values" to not update correctly.https://gitlab.kitware.com/paraview/paraview/-/issues/16095Time line in 2d plot Global Data is bad2018-02-26T13:16:52-05:00Kitware RobotTime line in 2d plot Global Data is bad**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16095). Further discussion may take place here.**
---
There are cases where the green time line for the 2d plot Global Data is b...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16095). Further discussion may take place here.**
---
There are cases where the green time line for the 2d plot Global Data is bad. Please fix it. This is impacting a user.
* Linux, 5.0.1, local server.
* can.exo. All vars on. Apply.
* Plot global variables over time. Apply.
* Move forward to timestep 10.
* Turn off all variables. Turn on YMON. Notice where the green time line is.
* Without changing YMON, turn on display of ZMON. Notice that the green time line is crazy.
* Turn off YMON. Notice that the green time line has gone away.
This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/16081When loading only sidesets from an exodus file, the written version's sideset...2019-02-14T19:35:47-05:00Kitware RobotWhen loading only sidesets from an exodus file, the written version's sidesets are empty.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16081). Further discussion may take place here.**
---
Steps to reproduce.
Load bake.e
Select no blocks and select all side s...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16081). Further discussion may take place here.**
---
Steps to reproduce.
Load bake.e
Select no blocks and select all side sets.
Save as a new exodus file.
Load the file in and note that it contains all side sets, but that they contain no data (and don't display in the window).https://gitlab.kitware.com/paraview/paraview/-/issues/16079Possible negative magnitude when coloring by vectors with angular periodic fi...2018-01-07T03:59:29-05:00Kitware RobotPossible negative magnitude when coloring by vectors with angular periodic filter**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16079). Further discussion may take place here.**
---
The range on the color bar sometimes gives strange results when using the ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16079). Further discussion may take place here.**
---
The range on the color bar sometimes gives strange results when using the Angular Periodic Filter. In particular it is possible to get negative values for a vector magnitude. To replicate, do the following.
1. Create a plane source. Origin = [0,0,0], Point1 = [1,0,0], Point2 = [0,1,0]. Apply.
2. Add the calculator filter. Make the expression "coords" (just the point coordinates). Apply.
3. Add Angular Periodic Filter. Rotation Angle = 90. Axis = Z. Apply.
4. Color by "Result" and "Magnitude"
Note that the range of the magnitude starts at -1, which is clearly wrong.https://gitlab.kitware.com/paraview/paraview/-/issues/16077Axis grid state and error2018-01-07T03:59:29-05:00Kitware RobotAxis grid state and error**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16077). Further discussion may take place here.**
---
Two bugs here.
Please change the Axis Grid/ Cull backface/ cull frontfa...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16077). Further discussion may take place here.**
---
Two bugs here.
Please change the Axis Grid/ Cull backface/ cull frontface to be a standard setting - not advanced.
Also, bug:
* Master, Linux, local server.
* Load bake.e. Apply.
* Select Axis Grid. (Advanced, but that will change as per above.). Turn off Cull Front Face AND turn off Cull Back Face. No annotation appears! This needs to be fixed.https://gitlab.kitware.com/paraview/paraview/-/issues/16074Crash when loading XDMF file2023-06-19T10:33:41-04:00Kitware RobotCrash when loading XDMF file**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16074). Further discussion may take place here.**
---
Opening the attached XDMF2 file crashes paraview version 5.01, when using ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16074). Further discussion may take place here.**
---
Opening the attached XDMF2 file crashes paraview version 5.01, when using the XDMF reader.
The same file can be read and displayed without problems in version 4.3.
This was tried with the version 5.0.1 from the webpage and from the Ubuntu repositories.https://gitlab.kitware.com/paraview/paraview/-/issues/16046Hide cells and blocks shortcut2018-01-07T03:59:30-05:00Kitware RobotHide cells and blocks shortcut**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16046). Further discussion may take place here.**
---
Here is a request from a user. What I envision is an additional button li...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16046). Further discussion may take place here.**
---
Here is a request from a user. What I envision is an additional button like the "Interactive Select Cells On". Something like "Interactive Hide Cells On" and Interactive Hide Blocks On". OK, verbiage from my user:
This is a feature or enhancement request for helping to speed up post-processing of a typical system-level analysis that we do. It can take a long time to "drill down" to visualize the element (cell) block that we are interested in. For example, we may have a large system model with hundreds of blocks, but all we really care about is a spring or screw that's buried inside some wall and hidden from view by cement, epoxies, plywood or other parts. It would be nice to have a single 'hot-key' to hide a series of blocks by picking. Yes, there are other ways of doing this (load only the blocks of interest, cutting planes, etc.), but sometimes this isn't known a-priori and it'd be nice to be able to click-navigate through a model more easily.
Anyways, I envision something like:
*User presses "H" key to toggle 'block hiding mode', cursor turns into a 'target'
*User clicks on a block, that block is hidden.
*User clicks on another block, that block is hidden.
*User clicks on another block, that block is hidden.
*User presses "H" key to toggle 'block hiding mode' off, cursor returns to normal.
https://gitlab.kitware.com/paraview/paraview/-/issues/16044Catalyst rendering edition doesn't have scalar bar2023-11-08T21:22:23-05:00Kitware RobotCatalyst rendering edition doesn't have scalar bar**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16044). Further discussion may take place here.**
---
Catalyst rendering edition doesn't have scalar bar support. That makes the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16044). Further discussion may take place here.**
---
Catalyst rendering edition doesn't have scalar bar support. That makes the renderings quite useless.https://gitlab.kitware.com/paraview/paraview/-/issues/16043Multiple dataset, volume rendering, remote server weirdnesses2018-08-08T22:24:32-04:00Kitware RobotMultiple dataset, volume rendering, remote server weirdnesses**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16043). Further discussion may take place here.**
---
We have a strange set of attributes to ParaView when running multiple data...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16043). Further discussion may take place here.**
---
We have a strange set of attributes to ParaView when running multiple datasets, one volume rendered, remote server. Here is how to replicate:
* Master, Linux, 8 remote servers. (May not show with fewer - I don't know.) (Does not show up Local server.)
* Load disk_out_ref.exo. All vars on. Apply.
* Color by Temp. Volume render.
* Load can.exo. All vars on. Apply.
<<Bug>> Rotate the can around. You will find a big red stripe on the top of the can.exo's plate.
* Turn visibility off for disk_out_ref.exo.
<<Bug>> The can is now being clipped in a crazy way. Only the upper left quadrant shows, and as you move it around, these clip planes change.
Marking for 5.1, since this one could be super confusing. This is a good example of how to fix it.
https://gitlab.kitware.com/paraview/paraview/-/issues/16036Selection display inspector GUI can be hard to navigate2018-08-08T22:24:32-04:00Kitware RobotSelection display inspector GUI can be hard to navigate**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16036). Further discussion may take place here.**
---
From a user:
Unfortunately, I'm often outputting tensors/matrices as va...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16036). Further discussion may take place here.**
---
From a user:
Unfortunately, I'm often outputting tensors/matrices as variables and this means I get data at every gauss point, on every element in that matrix. Typically this is a 3x3 matrix, with 8 gauss points = 72 cell variable names for just a single Tensor variable (e.g., "Rotation" variable). Symmetric matrices are slightly less with 6x8 = 48 variable names (e.g., "Stress" or "Strain" variable).
Browsing these is a bit of a pain -- as you can see, if I click the selection display inspector button, then Cell Labels, my screen is 100% filled with variable names. I don't know what the right solution is (maybe a scrolling list instead?), and it isn't a huge issue that needs to be addressed immediately. Just bringing attention to it.
https://gitlab.kitware.com/paraview/paraview/-/issues/16028Option to have sidesets and edgesets be displayed on standard properties tab2018-08-08T22:24:33-04:00Kitware RobotOption to have sidesets and edgesets be displayed on standard properties tab**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16028). Further discussion may take place here.**
---
Please add the option, set off by default, to allow a user to display side...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16028). Further discussion may take place here.**
---
Please add the option, set off by default, to allow a user to display sidesets and edgesets on the standard properties tab. https://gitlab.kitware.com/paraview/paraview/-/issues/16022More powerful animation track2022-07-05T06:14:37-04:00Kitware RobotMore powerful animation track**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16022). Further discussion may take place here.**
---
We need a more powerful animation track in the animation view. What I wan...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16022). Further discussion may take place here.**
---
We need a more powerful animation track in the animation view. What I want to do is the following, in any order, and be able to transition seamlessly.
* Be able to move down a spline, and smoothly transition to another spline.
* Be able to smoothly pause motion for an amount of time (seconds).
An example of what I want is: https://www.youtube.com/watch?v=Tfi8BLca07M
Utkarsh's comments were:
In addition to just better camera, one of things they are doing is animating camera, while the time for the data is paused, they animate time, then animate camera again and so on.
One, in theory, can do that in ParaView, we surely should make it more useable.
https://gitlab.kitware.com/paraview/paraview/-/issues/16018ParaViewWeb: the VGL renderer does not render all .pvd files2020-05-05T05:03:10-04:00Kitware RobotParaViewWeb: the VGL renderer does not render all .pvd files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16018). Further discussion may take place here.**
---
When I open a *.pvd file, the visualization does not appear, and the follo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16018). Further discussion may take place here.**
---
When I open a *.pvd file, the visualization does not appear, and the following errors are produced:
'2016-03-01 13:54:04-0800 [HTTPChannel,6,127.0.0.1] Property CaptureZBuffer has no GetData() method, skipping'
'2016-03-01 13:54:04-0800 [HTTPChannel,6,127.0.0.1] Property StartCaptureLuminance has no GetData() method, skipping'
'2016-03-01 13:54:04-0800 [HTTPChannel,6,127.0.0.1] Property StartCaptureValues has no GetData() method, skipping'
'2016-03-01 13:54:04-0800 [HTTPChannel,6,127.0.0.1] Property StopCaptureLuminance has no GetData() method, skipping'
'2016-03-01 13:54:04-0800 [HTTPChannel,6,127.0.0.1] Property StopCaptureValues has no GetData() method, skipping'https://gitlab.kitware.com/paraview/paraview/-/issues/16017ParaViewWeb: selecting a color palette with VGL renderer crashes pvpython se...2020-05-05T05:04:10-04:00Kitware RobotParaViewWeb: selecting a color palette with VGL renderer crashes pvpython server**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16017). Further discussion may take place here.**
---
When I try to color a .vtu with a color palette using the VGL renderer in ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16017). Further discussion may take place here.**
---
When I try to color a .vtu with a color palette using the VGL renderer in ParaViewWeb, there is a segmentation fault:
"Segmentation fault: 11 /Applications/paraview.app/Contents/bin/pvpython /Applications/paraview.app/Contents/Python/paraview/web/pv_web_visualizer.py --port 9000 --content /Applications/paraview.app/Contents/www --data-dir ${TFDATA} --proxies ${TFPVFILTER}/pvweb-filter.json --color-palette-file ${TFPVCOLORPALETTE}/colormaps.xml"
https://gitlab.kitware.com/paraview/paraview/-/issues/16008Block number insanity saving/ reading exodus data.2018-08-08T22:24:34-04:00Kitware RobotBlock number insanity saving/ reading exodus data.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16008). Further discussion may take place here.**
---
Block numbers go insane saving and loading files. This needs to be fixed....**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=16008). Further discussion may take place here.**
---
Block numbers go insane saving and loading files. This needs to be fixed.
* 4.4.0, Linux, local server.
* open can.exo. All vars on (not needed), apply.
* Cell data to Point data filter. Apply.
* File/ Save Data as Exodus.
* Reset Session.
* Load the file. Notice that the block numbers will be 12 and 80! They should be 1 and 2.
https://gitlab.kitware.com/paraview/paraview/-/issues/15996VRML writer and/or reader is broken2018-08-08T22:24:34-04:00Kitware RobotVRML writer and/or reader is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15996). Further discussion may take place here.**
---
The VRML writer and/or reader is broken. Here is how to replicate:
* 4...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15996). Further discussion may take place here.**
---
The VRML writer and/or reader is broken. Here is how to replicate:
* 4.4.0, local server, Linux.
* Load z_pinch1.8.[0-7]. All vars on. Apply. (Ask Utkarsh for this file set.)
* Go to last timestep. Paint by J.
* Filters/ Extract Surface. Apply.
* File / Export Scene/ vrml. Write this file somewhere.
* Edit/ Reset Session.
* Load VRML file. It won't have correct colors. Be sure to try to color by a variable.
https://gitlab.kitware.com/paraview/paraview/-/issues/15989Angular periodic filter is slow2024-02-02T14:01:37-05:00Kitware RobotAngular periodic filter is slow**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15989). Further discussion may take place here.**
---
The Angular Periodic Filter is slow, especially if a user has multiple blo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15989). Further discussion may take place here.**
---
The Angular Periodic Filter is slow, especially if a user has multiple blocks and uses a thin slice. If possible, please fix this.
* 5.0.0, Linux, local server.
* Load DoNotRelease-cylinderUpset.e. This dataset has two blocks, and lots of variables, and about 150 timesteps. Load the blocks, load all of the variables, do NOT load the sets. Apply.
* Clear the timer log. (Tools/ Timer Log).
* Angular Periodic Filter. Turn both blocks on. Resolution angle 1, Axis Z. Apply.
* Open the timer log. Notice how long it has taken.
This is impacting a user. This toy dataset takes a few seconds to load. The actual dataset (which cannot be shared) takes 20 to 60 seconds per timestep. One way to see what the user sees is to change the Resolution angle to 0.2.
From timer log:
PropertiesPanel::Apply, 3.59576 seconds
Execute vtkAngularPeriodicFilter id: 51, 0.031081 seconds
AngularPeriodicFilter::GatherInformatio, 0.076252 seconds
AngularPeriodicFilter::GatherInformatio, 0.059751 seconds
AngularPeriodicFilter::GatherInformatio, 0.046584 seconds
RenderView::Update, 2.65698 seconds
vtkPVView::Update, 2.65694 seconds
Execute vtkGeometryRepresentationWithFa, 2.65619 seconds
vtkPVGeometryFilter::RequestData, 2.58984 seconds
vtkPVGeometryFilter::RequestCompositeDa, 2.58983 seconds
vtkPVGeometryFilter::ExecuteCompositeDa, 1.65151 seconds
vtkSMRepresentationProxy::GetRepresente, 0.069979 seconds
Still Render, 0.496506 seconds
OpenGL Dev Render, 0.102788 seconds
I am sending the dataset to Utkarsh directly.Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/15982Probe filter not working with dataset with voxels2022-07-29T11:46:45-04:00Kitware RobotProbe filter not working with dataset with voxels**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15982). Further discussion may take place here.**
---
The probe filter is not working with the attached dataset. I suspect it is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15982). Further discussion may take place here.**
---
The probe filter is not working with the attached dataset. I suspect it is related to the fact that this data set is an unstructured grid containing voxel cells (as opposed to hexahedral cells). To replicate, do the following.
1. Open the attached data set. Apply.
2. Add the probe filter. Apply.
Note that all the fields in the probe filter are listed as 0 even though that is not even in the range of many of the fields in the attached data set.https://gitlab.kitware.com/paraview/paraview/-/issues/15978tiff reader doesn't work in parallel2021-03-23T12:15:54-04:00Kitware Robottiff reader doesn't work in parallel**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15978). Further discussion may take place here.**
---
We've experienced a variety of bugs in the tiff reader in parallel. In ser...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15978). Further discussion may take place here.**
---
We've experienced a variety of bugs in the tiff reader in parallel. In serial the reader works fine. Image processing software validates the tiff images.
Our use case involves a stack of 556 tiffs. On the Cray with 64 procs the data is scrambled and there are VTK error reports in the log(attached).
I tried to reproduce on my workstation using the "autro mpi" feature with 2 and 8 procs, but I saw a different bug, namely that the data is always displayed as solid color even when we select the array. Oddly there is no error output.
Although the full stack is too large to upload, I'm attaching a few slices from the stack, to explore the issue.
Also I'll attach the error log from the 64 proc run.