ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:57-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22367ParaView 5.12.0-RC1: Warning about missing property OSPRayMaterial2024-03-07T20:23:57-05:00Cory Quammencory.quammen@kitware.comParaView 5.12.0-RC1: Warning about missing property OSPRayMaterial* Start ParaView, built-in server
* Add Sphere source
* Color by Normals - X
* Check **Enable Ray Tracing** view property
* Switch **Back End** to "OSPRay pathtracer"
* You will get the warning:
```
Generic Warning: In vtkSMPropertyHelp...* Start ParaView, built-in server
* Add Sphere source
* Color by Normals - X
* Check **Enable Ray Tracing** view property
* Switch **Back End** to "OSPRay pathtracer"
* You will get the warning:
```
Generic Warning: In vtkSMPropertyHelper.cxx, line 570
Failed to locate property: OSPRayMaterial
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22366Ensight Reader fails due to quotation marks around file names2023-11-08T10:05:52-05:00njwallaEnsight Reader fails due to quotation marks around file namesThe Ensight case reader fails to identify file names of referenced files (e.g. the *.geo and scalar files) when those filenames are within quotes in the *.case file. This can occur for files exported from ANSYS Fluent at least since 202...The Ensight case reader fails to identify file names of referenced files (e.g. the *.geo and scalar files) when those filenames are within quotes in the *.case file. This can occur for files exported from ANSYS Fluent at least since 2022, when ANSYS decided to put the internally-referenced filenames in quotes. Manually editing the .case file to remove the quotes (e.g. `"simulation-case.geo"` becomes `simulation-case.geo`) allows the file to be loaded without issue. A suggested fix would be to simply remove outer quotes when reading in a filename.https://gitlab.kitware.com/paraview/paraview/-/issues/22365Default Compression Level Should be 5 not 62024-02-03T00:11:19-05:00John PatchettDefault Compression Level Should be 5 not 6When saving data in vtk xml file formats with compression in the ParaView GUI, the default compression level defaults to 6. Compression level 5 is labeled as the best cost/performance. Make Compression level 5 the default.When saving data in vtk xml file formats with compression in the ParaView GUI, the default compression level defaults to 6. Compression level 5 is labeled as the best cost/performance. Make Compression level 5 the default.Yohann Bearzi (Kitware)Yohann Bearzi (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/22364Save State and Screenshot Plugin - Allow embedded PVSM in PNG2023-11-07T13:25:12-05:00John PatchettSave State and Screenshot Plugin - Allow embedded PVSM in PNGSave State and Screenshot Plugin should have a persistently configurable option to save state and screenshot in a single PNG file using the state embedded in png capability. https://www.kitware.com/paraview-state-embedded-in-png-screensh...Save State and Screenshot Plugin should have a persistently configurable option to save state and screenshot in a single PNG file using the state embedded in png capability. https://www.kitware.com/paraview-state-embedded-in-png-screenshots/https://gitlab.kitware.com/paraview/paraview/-/issues/22363Save State and Screenshot Plugin - Make a Default Save Location and prefix name2023-11-07T13:21:13-05:00John PatchettSave State and Screenshot Plugin - Make a Default Save Location and prefix nameThe Save State and Screenshot Plugin should have a default location to save ParaView screenshots and states. I would prefer the $HOME/Pictures directory (on mac) and whatever might be appropriate for Windows and Linux Desktops. Possibly ...The Save State and Screenshot Plugin should have a default location to save ParaView screenshots and states. I would prefer the $HOME/Pictures directory (on mac) and whatever might be appropriate for Windows and Linux Desktops. Possibly $HOME/ParaView or $HOME/ParaView/PVSM . Has to be easy to get to, so one can view their ParaView states and drag and drop pvsm files back into ParaView. If the directory isn't there, it should be made. Default directory should be configurable, perhaps in settings/preferences general tab, advanced settings?https://gitlab.kitware.com/paraview/paraview/-/issues/22362Save State and Screenshot Plugin requires reconfigure for every RenderView ch...2023-11-07T13:11:39-05:00John PatchettSave State and Screenshot Plugin requires reconfigure for every RenderView changeThe save state and screenshot plugin currently requires a reconfigure everytime the resolution changes or a view is opened or closed. The plugin should automatically save the resolutions of the views that are currently visible. The idea ...The save state and screenshot plugin currently requires a reconfigure everytime the resolution changes or a view is opened or closed. The plugin should automatically save the resolutions of the views that are currently visible. The idea of the plugin is to make it easy, a single click, to save the current state and the screenshot that that state represents. The collage of views should be saved at the resolutions they are being previewed at/or are. Do not require a reconfiguration based on resolution or other RenderView changes.https://gitlab.kitware.com/paraview/paraview/-/issues/22361PVD files with punctuation in the name fail to reload2023-11-08T08:31:53-05:00Aron HelserPVD files with punctuation in the name fail to reloadFollow on to https://gitlab.kitware.com/paraview/paraview/-/issues/22297 with issues found during the fix, and the creation of a test in https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6564
* the XML record/play test frame...Follow on to https://gitlab.kitware.com/paraview/paraview/-/issues/22297 with issues found during the fix, and the creation of a test in https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6564
* the XML record/play test framework can't handle a filename with ";" in it - the xml is reported as invalid.
* The pvcs and pvcrs version of `RecentFilesHardFilename` fail on windows and linux (but not mac), because the PVD writer can't create the sub-directory to store the .vtp file
```plaintext
vtkXMLPVDWriter.cxx:348 ERR| vtkXMLPVDWriter (000001A38ACFEDA0): Sorry unable to create directory: C:\glr\builds\paraview\paraview-ci\build\Testing\Temporary\nametest `~!@ #$%^ (){}[] _-=+ ,. stuff.vtp
```
* Create a sphere source, `Save Data As...` a pvd file with the name "filetest \`<span dir="">\~</span>!@ #$%^ (){}\[\] \_-=+ ;,. stuff.pvd" and re-load of the file fails:
```plaintext
( 157.305s) [paraview ] vtkXMLParser.cxx:364 ERR| vtkXMLDataParser (0x5596bc5f9740): Error parsing XML in stream at line 3, column 42, byte index 146: not well-formed (invalid token)
( 157.317s) [paraview ] vtkXMLReader.cxx:576 ERR| vtkPVDReader (0x5596bba41ad0): Error parsing input file. ReadXMLInformation aborting.
( 157.318s) [paraview ] vtkPVDReader.cxx:121 ERR| vtkPVDReader (0x5596bba41ad0): Could not read file information
```
I can't investigate further at this time, so I'm filing this issue.https://gitlab.kitware.com/paraview/paraview/-/issues/22360Loading a single time step data does not change number of frames to 12024-03-04T04:33:56-05:00Nicolas VuailleLoading a single time step data does not change number of frames to 1 When loading a single timestep data, ParaView still displays multiple times available in the toolbar and in the time manager.
[SingleTs.zip](/uploads/0a119a91dbb30b2850da9faf5dcabefb/SingleTs.zip) is a sphere and a single timestep with... When loading a single timestep data, ParaView still displays multiple times available in the toolbar and in the time manager.
[SingleTs.zip](/uploads/0a119a91dbb30b2850da9faf5dcabefb/SingleTs.zip) is a sphere and a single timestep with time value 42.
This seems to be an old behavior.
| | master (near 5.12) | 5.11 | 5.8 |
| ------ | ------ | ------ | ----- |
| _defaults_ | | | |
| animation view | [0, 1], **10 values** | same | same |
| toolbar | combobox with 10 values | line edit, display 0 | line edit, display 0 |
| _load single ts_ | | | |
| info panel | ok : one ts, value 42 | same | same |
| toolbar | 42, **10 timesteps** in [42, **43**] | line edit on 42 | line edit on **0** |
| anim view | [42, **43**], **10 ts** | [42, **43**], **10 ts** | **[0, 1], 10 ts** |
So:
- ParaView has 10 timesteps by default in the animation scene. Not sure it is the right choice here.
- Loading a single time step data does not override the number of frames. This is more likely a bug.
Some related issues:
https://gitlab.kitware.com/paraview/paraview/-/issues/19777
https://gitlab.kitware.com/paraview/paraview/-/issues/21477
https://gitlab.kitware.com/paraview/paraview/-/issues/22369https://gitlab.kitware.com/paraview/paraview/-/issues/22358Catalyst: Need support for optionally creating meshes and/or variables in Con...2023-12-11T12:09:45-05:00Berk GeveciCatalyst: Need support for optionally creating meshes and/or variables in ConduitCurrently, every time Catalyst is called, it is expected that the simulation populates the Conduit data structures for ParaView to consume. This means that even if there are extractors with frequencies > 1 per time step, data is being co...Currently, every time Catalyst is called, it is expected that the simulation populates the Conduit data structures for ParaView to consume. This means that even if there are extractors with frequencies > 1 per time step, data is being converted every time, which may be costly. Even though it is possible to manage the frequency on the simulation side, this reduces the usefulness of having a frequency parameter for the extractors. Furthermore, different pipelines/extractors may need different meshes and/or variables and the current implementation is all or nothing because ParaView has no means to communicate what it needs to the simulation adaptor populating the Conduit tree.
@acbauerhttps://gitlab.kitware.com/paraview/paraview/-/issues/22357Test syntax2023-11-04T01:19:02-04:00W. Alan ScottTest syntax//as
\\ blar//as
\\ blarhttps://gitlab.kitware.com/paraview/paraview/-/issues/22353CI: macOS arm64 test failure - FeatureEdgesFilterHTG and FeatureEdgesRepresen...2023-11-06T04:03:54-05:00Thomas GallandCI: macOS arm64 test failure - FeatureEdgesFilterHTG and FeatureEdgesRepresentationHTGIssue seems related to the `Render Lines As Tube` display property, used in the test.
Similar test done without it passes (see `FeatureEdgesHTG` XML test).
Test image / Valid image / Diff image:
![image](/uploads/779ff87a1a23552c7f...Issue seems related to the `Render Lines As Tube` display property, used in the test.
Similar test done without it passes (see `FeatureEdgesHTG` XML test).
Test image / Valid image / Diff image:
![image](/uploads/779ff87a1a23552c7f0365841df182e2/image.png)
![FeatureEdgesRepresentationHTG](/uploads/9bf523bf1566139a7f8e13e4f97502eb/FeatureEdgesRepresentationHTG.png)
![image](/uploads/92ea30d95f6583afa8f53ec5978e1f19/image.png)
Related MR : https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6538
Related Issue: https://gitlab.kitware.com/paraview/paraview/-/issues/22352https://gitlab.kitware.com/paraview/paraview/-/issues/22352CI: fedora test failure - FeatureEdgesFilterHTG and FeatureEdgesRepresentatio...2023-11-06T05:27:14-05:00Thomas GallandCI: fedora test failure - FeatureEdgesFilterHTG and FeatureEdgesRepresentationHTGIssue seems related to the `Render Lines As Tube` display property, used in the test.
Similar test done without it passes (see `FeatureEdgesHTG` XML test).
This test seems to always fail on `fedora35_shared_mpi_python_qt_vtkmoverrid...Issue seems related to the `Render Lines As Tube` display property, used in the test.
Similar test done without it passes (see `FeatureEdgesHTG` XML test).
This test seems to always fail on `fedora35_shared_mpi_python_qt_vtkmoverride`.
This test seems to be flaky on `fedora35_shared_mpi_python_qt`.
Test image / Valid image / Diff image:
![image](/uploads/d5009f09414e1b1c873bf278dfa21375/image.png)
![FeatureEdgesRepresentationHTG](/uploads/9bf523bf1566139a7f8e13e4f97502eb/FeatureEdgesRepresentationHTG.png)
![image](/uploads/8d04b61682426d9080a6478e32f597bd/image.png)
Related MRs : https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6538 https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6566
Related Issue : https://gitlab.kitware.com/paraview/paraview/-/issues/22353https://gitlab.kitware.com/paraview/paraview/-/issues/22351SPDX: vtkSMTransferFunctionPresetsBuiltin.h does not have SPDX information2023-10-31T11:05:58-04:00Cory Quammencory.quammen@kitware.comSPDX: vtkSMTransferFunctionPresetsBuiltin.h does not have SPDX information`vtkSMTransferFunctionPresetsBuiltin.h` is generated from `ColorMaps.json`. The `ParaView::ProcessXML` process should pull license information from the JSON file and add it to the generated file, but the JSON file currently has no copyri...`vtkSMTransferFunctionPresetsBuiltin.h` is generated from `ColorMaps.json`. The `ParaView::ProcessXML` process should pull license information from the JSON file and add it to the generated file, but the JSON file currently has no copyright information.https://gitlab.kitware.com/paraview/paraview/-/issues/22349CI: SplitViewTrace is flaky2023-10-27T07:54:38-04:00Mathieu Westphal (Kitware)CI: SplitViewTrace is flakySplitViewTrace test seems flaky on all os, it was excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6554
![a](/uploads/c7cf9b555cd49d964379646214102227/a.png)SplitViewTrace test seems flaky on all os, it was excluded here: https://gitlab.kitware.com/paraview/paraview/-/merge_requests/6554
![a](/uploads/c7cf9b555cd49d964379646214102227/a.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22347Name exceeds 32 characters limit2023-10-25T16:21:45-04:00Xujiang LiuName exceeds 32 characters limitOS: Windows 10 Version 2022
ParaView Version: 5.11.2
Description
When using Paraview to export variables after time-averaging processing, the variable name exceeds the 32-character limit![微信截图_20231025215503](/uploads/f9b7a2d17ccebc8c3e...OS: Windows 10 Version 2022
ParaView Version: 5.11.2
Description
When using Paraview to export variables after time-averaging processing, the variable name exceeds the 32-character limit![微信截图_20231025215503](/uploads/f9b7a2d17ccebc8c3e37ebd5eddf965a/微信截图_20231025215503.png)https://gitlab.kitware.com/paraview/paraview/-/issues/22345Fluent CFF reader crash on Properties Restore application default setting values2023-10-26T16:28:41-04:00Louis GombertFluent CFF reader crash on Properties Restore application default setting valuesStep to reproduce :
- Open `room.cas.h5` from testing data using the FluentCFFReader.
- Apply
- In the properties panel, click on the circular arrows icon (Restore application default setting values) of the properties category
- (C...Step to reproduce :
- Open `room.cas.h5` from testing data using the FluentCFFReader.
- Apply
- In the properties panel, click on the circular arrows icon (Restore application default setting values) of the properties category
- (Crash)
Tested on ParaView master on Linux with my own build & nightly binaryhttps://gitlab.kitware.com/paraview/paraview/-/issues/22344ReloadFile cached state behavior should be controllable2023-10-25T03:38:09-04:00Mathieu Westphal (Kitware)ReloadFile cached state behavior should be controllableWhen using the ReloadFiles feature, the user is prompter for looking for new files or reloading existing files, but is prompted once by reader. This behavior should be controllable with a `Dont ask again` logic.
Steps to repro:
- run ...When using the ReloadFiles feature, the user is prompter for looking for new files or reloading existing files, but is prompted once by reader. This behavior should be controllable with a `Dont ask again` logic.
Steps to repro:
- run ParaView
- Open any file, apply
- RightClick, ReloadFiles, pick one of the two option in the prompt
- RightClick, ReloadFiles, no prompthttps://gitlab.kitware.com/paraview/paraview/-/issues/22343Ghost cells generator fails to produce ghosts on a wavelet2024-03-26T13:50:48-04:00Yohann Bearzi (Kitware)Ghost cells generator fails to produce ghosts on a waveletThe following state file works with 5.11.0, but not with master. There should be a non-empty output in `Extract Ghost Cells`
[ghost_image_data.pvsm](/uploads/f6b953701340abfe6d14413522fb9650/ghost_image_data.pvsm)The following state file works with 5.11.0, but not with master. There should be a non-empty output in `Extract Ghost Cells`
[ghost_image_data.pvsm](/uploads/f6b953701340abfe6d14413522fb9650/ghost_image_data.pvsm)Charly BollingerCharly Bollingerhttps://gitlab.kitware.com/paraview/paraview/-/issues/22342GhostCellGenerator fails to generate correct ghost cells with certain options2023-10-24T10:37:36-04:00Mathieu Westphal (Kitware)GhostCellGenerator fails to generate correct ghost cells with certain optionsSteps to reproduce:
- `mpirun -np 4 ./bin/pvserver`
- run ParaView
- connect to server
- Sphere, resolution 80, Apply
- RedistributeDataSet, AssignToOneRegion, Apply
- GhostCellGenerator, GenerateGlobalIds, Apply
![image](/upload...Steps to reproduce:
- `mpirun -np 4 ./bin/pvserver`
- run ParaView
- connect to server
- Sphere, resolution 80, Apply
- RedistributeDataSet, AssignToOneRegion, Apply
- GhostCellGenerator, GenerateGlobalIds, Apply
![image](/uploads/c4ed9244964d781ef750b23158c79f9b/image.png)
Note: Not generating the global ids fixes the issuehttps://gitlab.kitware.com/paraview/paraview/-/issues/22341GhostCellGenerator flag cells as ghosts when it should not2023-10-24T10:37:35-04:00Mathieu Westphal (Kitware)GhostCellGenerator flag cells as ghosts when it should notGhostCellGenerator flag cells as ghosts when it should not
Steps to reproduce:
- `mpirun -np 4 ./bin/pvserver`
- run ParaView
- connect to server
- UnstructuredCellTypes, Apply
- RedistributeDataSet, AssignToAllRegions, Apply
- G...GhostCellGenerator flag cells as ghosts when it should not
Steps to reproduce:
- `mpirun -np 4 ./bin/pvserver`
- run ParaView
- connect to server
- UnstructuredCellTypes, Apply
- RedistributeDataSet, AssignToAllRegions, Apply
- GhostCellGenerator, Apply
![image](/uploads/3e8ebf23cc9c5b4626536a21f9729146/image.png)