ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-03-14T10:43:47-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/21268Make Ghost Cells Generator HTG compatible2022-03-14T10:43:47-04:00Yohann Bearzi (Kitware)Make Ghost Cells Generator HTG compatibleCurrently, the `Ghost Cells Generator` doesn't work for Hyper Tree Grids. There is a specific ghost cells generator for them called `Hyper Tree Grid Ghost Cells Generator`. `Ghost Cells Generator` should be HTG compatible and `Hyper Tree...Currently, the `Ghost Cells Generator` doesn't work for Hyper Tree Grids. There is a specific ghost cells generator for them called `Hyper Tree Grid Ghost Cells Generator`. `Ghost Cells Generator` should be HTG compatible and `Hyper Tree Grid Ghost Cells Generator` be removed with correct backward compatibility.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21261Elevation camera manipulation for Adjust Camera not working properly2024-03-07T20:23:49-05:00Andrew BauerElevation camera manipulation for Adjust Camera not working properlyThere's something wrong with the calculation for how to do the `Elevation` changes to the `Adjust Camera` manipulation in the 3D View. Steps to reproduce in PV 5.10:
1. Create a `Wavelet` source with Whole Extent [20, 40, -10, 10, -10, ...There's something wrong with the calculation for how to do the `Elevation` changes to the `Adjust Camera` manipulation in the 3D View. Steps to reproduce in PV 5.10:
1. Create a `Wavelet` source with Whole Extent [20, 40, -10, 10, -10, 10]. The key point here is to not have the center of the grid at the origin.
2. Click on `Set view direction to +X`
3. Bring up the `Adjust Camera` dialog
4. Change `Elevation` change to 8.00 degrees.
5. Click on the `Elevation` button several times.
The `Wavelet` output should be staying at the center of the view but it doesn't. If the `Wavelet` `Whole Extent` was kept at the default of [-10, 10, -10, 10, -10, 10] and the other steps were repeated the `Wavelet` output would stay at the center of the view.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21237Warp by vector and IOSS reader failing in 2d2023-01-30T21:32:38-05:00W. Alan ScottWarp by vector and IOSS reader failing in 2dThe Warp by vector filter is failing for data read from the IOSS reader. If I have a 2d dataset, with two scalars named mesh_displacement_X and mesh_displacement_Y, this is being combined into a vector mesh_displacement_ with two compon...The Warp by vector filter is failing for data read from the IOSS reader. If I have a 2d dataset, with two scalars named mesh_displacement_X and mesh_displacement_Y, this is being combined into a vector mesh_displacement_ with two components. Now, if I try to warp by vector, the filter is grayed out. The way you enable the warp by vector filter is with the calculator, forming a 3 component array (with 0 as the Z component).
I need to run datasets that show this through R&A. Will do so.5.11 (Spring 2022)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21167OSPRay is not rendering triangles2024-03-07T20:23:48-05:00W. Alan ScottOSPRay is not rendering trianglesOSPRay is not rendering triangles in some cases. Here is how to replicate.
* MacOS, 5.10.0, builtin server.
* Enable Ray Tracing.
* Sources/ Wavelet.
* Contour. Take defaults. Apply.
* Change to Solid Color (White). Holes show up b...OSPRay is not rendering triangles in some cases. Here is how to replicate.
* MacOS, 5.10.0, builtin server.
* Enable Ray Tracing.
* Sources/ Wavelet.
* Contour. Take defaults. Apply.
* Change to Solid Color (White). Holes show up better.
* +Z or -Z.
Lots of triangles are not rendered. This is a bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21153allow save screenshot for non integer scales2024-03-07T20:23:48-05:00W. Alan Scottallow save screenshot for non integer scalesThis feature request is an extention of #21109. #21109 has the details to test saving screenshots. As mentioned at the bottom of #21109, we wish to allow users to scale screenshots to scale to non integer values. For instance, we want...This feature request is an extention of #21109. #21109 has the details to test saving screenshots. As mentioned at the bottom of #21109, we wish to allow users to scale screenshots to scale to non integer values. For instance, we want to save screenshots with a scale of 0.75 or 1.5. Then, text used for the color legend and simultaniously sources/ text should scale to this value, and also scale the same.
Again, see #21109 for details how to replicate this issue.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21151Memory display color2024-03-07T20:23:48-05:00W. Alan ScottMemory display colorI think I would recommend changing the memory display bar background color and thresholds. This is the new memory display below the renderview.
With regards to the background, it is currently quite bright and distracting. Please cha...I think I would recommend changing the memory display bar background color and thresholds. This is the new memory display below the renderview.
With regards to the background, it is currently quite bright and distracting. Please change the background color to match the background of the progress bar - i.e., a gray rather than a white. The green is OK, leave as is.
After a bit of experimenting, what I believed was happening is happening with memory. ParaView is grabbing memory for calculations and output arrays, doing calculations, then releasing calculation memory. Thus, what the memory inspector is showing is correct after processing, but a huge undercount when any processing and/or rendering is occurring.
The way I tested was on RedHat Linux. Run ParaView. Sources/ Fast Uniform Grid. Only create the Distance Squared scalars. In a terminal, start running "free -h". Either have it run every second, or keep up-arrowing. What we care about is the last entry, "available". You may want to open the memory inspector, but this isn't necessary as we can see the memory footprint on the new memory display bar. Start increasing the size of the fast uniform grid. With 64 GBytes of memory, mine was OK at about -1000 to 1000, -1000 to 1000, -400 to 400. Memory showed about 65% full. Changing the Z to -400 to 450 crashed, but as I was only increasing about 8%, it shouldn't have. Note that free gave me a low of about 9 GBytes of free memory, but a final of about 20GBytes.
Please change the thresholds for the memory display bar to go yellow at 50% memory used, and red at 60% memory used.
@mwestphal5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21141Color legend label format and range label format are not similar2024-03-07T20:23:48-05:00W. Alan ScottColor legend label format and range label format are not similarThe color legend label formats and range label formats are not the same, but should be. The range has an extra number in the exponent. They need to be the same. Here is how to replicate:
* 5.10.0-RC2, MacOS
* Wavelet. Apply. Surfac...The color legend label formats and range label formats are not the same, but should be. The range has an extra number in the exponent. They need to be the same. Here is how to replicate:
* 5.10.0-RC2, MacOS
* Wavelet. Apply. Surface. Color by RTData.
* Color map editor. Color legend editor.
* Advanced.
* Turn off automatic label format.
* Change Label Format to: %-#6.3e
* Change Range Label Format to: %-#6.3e
The exponents have a different number of digits. This is a bug.
![Screen_Shot_2021-12-21_at_10.57.03_AM](/uploads/abdb57fded5873eceffc2474ad16e878/Screen_Shot_2021-12-21_at_10.57.03_AM.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21099Save Screenshot save current settings fails2024-03-07T20:23:46-05:00W. Alan ScottSave Screenshot save current settings failsSave Screenshot, save current settings is failing. Here is how to replicate:
* MacOS, 5.10.0-RC1.
* Sources/ Wavelet. Apply.
* File/ Save Screenshot.
* Change Image Resolution to 2048X1280
* Save Current setting values as defaults. ...Save Screenshot, save current settings is failing. Here is how to replicate:
* MacOS, 5.10.0-RC1.
* Sources/ Wavelet. Apply.
* File/ Save Screenshot.
* Change Image Resolution to 2048X1280
* Save Current setting values as defaults.
* Save the screenshot.
* File/ Save Screenshot.
The image resolution should still be 2048X1280. This is a bug.
It is reported that other state is also not saved, such as compression level.
Alan, test everything once this is fixed.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21060Treat writers similarly to filters (gray them out)2024-03-07T20:23:46-05:00W. Alan ScottTreat writers similarly to filters (gray them out)Please change the way we deal with save data/ export scene for cases where the input data is not appropriate for the writer. Currently, the writer is just not listed. What we should do is gray these writers out, and preferably offer so...Please change the way we deal with save data/ export scene for cases where the input data is not appropriate for the writer. Currently, the writer is just not listed. What we should do is gray these writers out, and preferably offer some type of tip why this writer is grayed out.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21043Allow filters to be copied from one source to another2022-08-22T17:52:06-04:00W. Alan ScottAllow filters to be copied from one source to anotherPlease allow filters to be moved from one source to another. An example would be opening can.ex2, and adding ... i don't know ... 4 clips to it, then 4 plot over lines under that. Open a new dataset, such as can.exo. Now, I want to mo...Please allow filters to be moved from one source to another. An example would be opening can.ex2, and adding ... i don't know ... 4 clips to it, then 4 plot over lines under that. Open a new dataset, such as can.exo. Now, I want to move all 4 filters to be under can.exo. This currently can be done by moving each and every filter, but we want t one click solution.
One idea is to duplicate the source/ filter tree, than redirect the original source. Another would be to allow users to copy and paste the filter tree. Yet another would be to "move" all of the filters as a group from one source/filter to another.Caitlin RossCaitlin Rosshttps://gitlab.kitware.com/paraview/paraview/-/issues/20966Multiblock inspector opacity needs initialization2023-10-30T17:41:47-04:00W. Alan ScottMultiblock inspector opacity needs initializationThe multiblock inspector needs to have opacity settings initialized. They work, they just are extremely misleading. Here is how to replicate:
* MacOS, nightly (5.9.1-1808-gdb1698b0d4), builtin server.
* can.exo. Apply.
* View/ Multib...The multiblock inspector needs to have opacity settings initialized. They work, they just are extremely misleading. Here is how to replicate:
* MacOS, nightly (5.9.1-1808-gdb1698b0d4), builtin server.
* can.exo. Apply.
* View/ Multiblock inspector. Click on block 1 opacity.
The opacity will show 0. This is incorrect, it should show 1. Note that the opacity actually works correctly, and once you touch it, it shows correctly.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20935On screen block information wrong when another block is selected.2021-09-03T19:00:56-04:00W. Alan ScottOn screen block information wrong when another block is selected.The on screen block information and controls are wrong when another block is selected. Here is how to replicate:
* Master, Linux, builtin server.
* bake.e. Apply. (Ask me for bake if needed.)
* +Z
* View/ Multiblock inspector.
* Sele...The on screen block information and controls are wrong when another block is selected. Here is how to replicate:
* Master, Linux, builtin server.
* bake.e. Apply. (Ask me for bake if needed.)
* +Z
* View/ Multiblock inspector.
* Select block_4. (The thin block on the right will be selected).
* Now, right click on one of the two big blocks facing you. They both (along with all blocks) will show as block_4. If you hide block, the selected block_4 will be hidden, rather than the one selected.
This is a bug.https://gitlab.kitware.com/paraview/paraview/-/issues/20876Allow assembles to be modified by right click menu2021-08-05T22:06:04-04:00W. Alan ScottAllow assembles to be modified by right click menuOn the renderview, please enable assembles to be modified by using the right click menu, same as blocks. Same functionality.On the renderview, please enable assembles to be modified by using the right click menu, same as blocks. Same functionality.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20812Find Data - Edit Label Properties - Restore Defaults fails2021-06-25T18:20:35-04:00W. Alan ScottFind Data - Edit Label Properties - Restore Defaults failsFind Data - Edit Label Properties, restore defaults fails. This is true for the everything in this dialog.
* Master, Linux, builtin server.
* Wavelet. Apply. Surface.
* Make a cell selection on.
* Find Data, Cell Labels, Id.
* Fi...Find Data - Edit Label Properties, restore defaults fails. This is true for the everything in this dialog.
* Master, Linux, builtin server.
* Wavelet. Apply. Surface.
* Make a cell selection on.
* Find Data, Cell Labels, Id.
* Find Data, Edit Label Properties. Try everything - changing colors, bold, font change, etc.
* Restore Default Settings (little icon lower left).
Nothing restores. This is a bug.5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20807Add MPEG4 to Linux2022-03-13T11:09:58-04:00W. Alan ScottAdd MPEG4 to LinuxWhen we find non copyright burdened codecs for MPEG4 for Linux, please implement it.When we find non copyright burdened codecs for MPEG4 for Linux, please implement it.https://gitlab.kitware.com/paraview/paraview/-/issues/20806Add MPEG4 to MacOS2021-06-25T13:18:46-04:00W. Alan ScottAdd MPEG4 to MacOSWhen we find non copyright burdened codecs for MPEG4 for MacOS, please implement it.When we find non copyright burdened codecs for MPEG4 for MacOS, please implement it.https://gitlab.kitware.com/paraview/paraview/-/issues/20788Add Redistribute View Horizontally and Vertically buttons2021-06-17T05:03:56-04:00W. Alan ScottAdd Redistribute View Horizontally and Vertically buttonsPlease add buttons to redistribute views horrizontally or vertically. Mathieu's proposal is here: https://discourse.paraview.org/t/add-feature-to-evenly-distribute-views/7417. Note that he redistrubuted the right side vertically, the ...Please add buttons to redistribute views horrizontally or vertically. Mathieu's proposal is here: https://discourse.paraview.org/t/add-feature-to-evenly-distribute-views/7417. Note that he redistrubuted the right side vertically, the main window horizontally and the three smaller views also horizontally. Good idea!5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20779Add Boolean operations filter for polydata2021-09-22T19:54:37-04:00Cory Quammencory.quammen@kitware.comAdd Boolean operations filter for polydataThis could be done by adding XML to expose the `vtkBooleanOperationPolyDataFilter` already in VTK, but there are numerous cases where that filter falls down.
Alternatively, we can pick up Bill Lorensen's work integrating Roland Reomer's...This could be done by adding XML to expose the `vtkBooleanOperationPolyDataFilter` already in VTK, but there are numerous cases where that filter falls down.
Alternatively, we can pick up Bill Lorensen's work integrating Roland Reomer's boolean operations filter into VTK, but merge them into VTK itself rather than building as a remote module. See discussion [here](https://discourse.vtk.org/t/adding-roemers-boolean-filter-as-a-remote-module/1635).5.11 (Spring 2022)https://gitlab.kitware.com/paraview/paraview/-/issues/20604Ruler enhancements2024-03-07T20:23:45-05:00W. Alan ScottRuler enhancementsPlease add a ruler enhancement. Please have the ruler go from one point to another. This can either be by GlobalNodeId or two selected points, your choice. Have the ruler optionally, default on, displace by the Displacement variable o...Please add a ruler enhancement. Please have the ruler go from one point to another. This can either be by GlobalNodeId or two selected points, your choice. Have the ruler optionally, default on, displace by the Displacement variable over time. Finally, this needs to be something that can be seen in the spreadsheet, and written to a file.
If short term the answer is a programmable filter, please write this up in the Discourse Tips and Tricks.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20551Desciptive Statistics should ignore NaNs by default2021-03-11T22:03:22-05:00W. Alan ScottDesciptive Statistics should ignore NaNs by defaultDescriptive Statistics should be able to ignore NaNs. This should be the default, with the option to turn off. Make the turn off option advanced.Descriptive Statistics should be able to ignore NaNs. This should be the default, with the option to turn off. Make the turn off option advanced.5.11 (Spring 2022)