ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:59-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/22389Paraview 5.12.0-RC1: Loading State File Error for vtkAppendSelection in Paral...2024-03-07T20:23:59-05:00Zongze YangParaview 5.12.0-RC1: Loading State File Error for vtkAppendSelection in Parallel Server when Using State File Created with `Find Data` and `Plot Over Time`The encountered error is as follows:
```
ERROR: In vtkDemandDrivenPipeline.cxx, line 677
vtkPVCompositeDataPipeline (0x600005419f00): Input port 0 of algorithm vtkAppendSelection (0x600005627c00) has 0 connections but is not optional.
`...The encountered error is as follows:
```
ERROR: In vtkDemandDrivenPipeline.cxx, line 677
vtkPVCompositeDataPipeline (0x600005419f00): Input port 0 of algorithm vtkAppendSelection (0x600005627c00) has 0 connections but is not optional.
```
However, it appears that this error does not impact the rendering results.
## Steps to Reproduce the Issue:
1. Initiate the server (optional):
```bash
mpiexec -n 2 pvserver
```
2. Load the file `can.ex2` (Examples -> can.ex2)
3. Navigate to View -> Find Data:
Locate the point (4, 4, 1) with a tolerance of 1, and then proceed to `Plot Over Time`.
4. Save the state. (The state files are attached.)
The error consistently manifests when using the state file in conjunction with the mpi-server, irrespective of whether the state file was created with or without the mpi-server.
[test-mpi2.pvsm](/uploads/90562b4c7d2a365bb3efa7d09be7a71b/test-mpi2.pvsm)
[test-nompi.pvsm](/uploads/3662d6a453176671d9a3b584ea3036f1/test-nompi.pvsm)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22385ParaView 5.12.0-RC1: non-responsive floating windows : ‘Output Messages’ and ...2024-03-07T20:23:59-05:00Lourenço Sassetti MendesParaView 5.12.0-RC1: non-responsive floating windows : ‘Output Messages’ and ‘Choose Preset’This occurs using WSL2, under Windows 11, using both Ubuntu 22.04 and OpenSuse 15.5. It’s very easy to replicate.
It has nothing to do with specific states or files. Also occurs with “paraview --dr”.
1) The ‘Output Messages’ window when...This occurs using WSL2, under Windows 11, using both Ubuntu 22.04 and OpenSuse 15.5. It’s very easy to replicate.
It has nothing to do with specific states or files. Also occurs with “paraview --dr”.
1) The ‘Output Messages’ window when undocked, can’t be docked any more or resized, but it's still possible to close or select the checkboxes. If it pops up automatically, while using ParaView, it becomes completely non-responsive. The only option is to close it in the ‘View’ menu. It’s annoying because you’re not able to choose where it will pop up. The only way I found to dock it again is resetting ParaView: ‘Edit’ > ‘Reset To Default Settings’ and restart ParaView. This issue occurs both in versions 5.11.2 and 5.12.0.
2) In v5.12.0, the ‘Color Map Editor’ > ‘Choose Preset’ window is always non-responsive to mouse events, and even with TAB you can’t move to all checkboxes. It gets stuck in the default color presets table displayed, and you can’t select the other groups of presets (linear, diverging, etc). This issue occurs only in version 5.12.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22384ParaView 5.12-RC1 uses `~/.local` folder for python library instead of bundle...2024-03-07T20:23:59-05:00Francois MazenParaView 5.12-RC1 uses `~/.local` folder for python library instead of bundled python libsUsing the binary release of 5.12-RC1 of ParaView, it looks like the internal python runtime uses libraries from `~/.local` instead of the libraries available in the ParaView installation folder.
It's visible for the matplotlib path in t...Using the binary release of 5.12-RC1 of ParaView, it looks like the internal python runtime uses libraries from `~/.local` instead of the libraries available in the ParaView installation folder.
It's visible for the matplotlib path in the about dialog:
![image](/uploads/397b510ffe2eb436cacfad8d78fe9335/image.png)
When I remove my `~/.local` folder the expected lib is loaded:
![image](/uploads/478369cc715d4154b05895929bdb31ad/image.png)
When using the local libraries, it creates weird errors when using the FindData panel:
```
Error: Failed to evaluate Expression '(mag(B_A) == 0)'. The following exception stack should provide additional developer specific information. This typically implies a malformed expression. Verify that the expression is valid.
Warning: In vtkPythonSelector.cxx, line 104
vtkPythonSelector (0xa2d9380): Could not invoke 'python_selector.execute()'
Traceback (most recent call last):
File "/home/francois/Documents/Paraview/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64/lib/python3.10/site-packages/paraview/detail/python_selector.py", line 80, in execute
maskArray = calculator.compute(inputs, query, ns=elocals)
File "/home/francois/Documents/Paraview/ParaView-5.12.0-RC1-MPI-Linux-Python3.10-x86_64/lib/python3.10/site-packages/paraview/detail/calculator.py", line 167, in compute
retVal = eval(subEx, globals(), mylocals)
File "<string>", line 1, in <module>
NameError: name 'B_A' is not defined
Generic Warning: In vtkSelection.cxx, line 752
No values to evaluate because there was an error in the selection evaluator.
ERROR: In vtkExecutive.cxx, line 729
vtkPVCompositeDataPipeline (0x8dd5320): Algorithm vtkPVExtractSelection (0x94b0d50) returned failure for request: vtkInformation (0xa2b9b70)
Debug: Off
Modified Time: 1243144
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
I can't reproduce this issue with official binary of 5.11.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22381Error message if there is a Client/Server miss-match is reversed.2024-03-07T20:23:57-05:00Phil SmithError message if there is a Client/Server miss-match is reversed.If the Client and Server try and connect using different versions of ParaView, the error message is opposite of what it should be. It is reporting the client as the server and the server as the client. Please see the error below for an e...If the Client and Server try and connect using different versions of ParaView, the error message is opposite of what it should be. It is reporting the client as the server and the server as the client. Please see the error below for an example. Notice that the Client reports as version 5.11, however, I started version 5.12 as the client. I discovered the server was at 5.11, and that was the problem.
This is version 5.12.0-RC1-kw of ParaView.
PV_INSTALL_DIR is /snip/5.12.0-RC1-kw/Linux-cee-rhel7-x86_64
[1] 97892
Rendering in Hardware!
VisRTX 0.1.6, using devices:
0: GRID V100S-4Q (Total: 4.3 GB, Available: 2.6 GB)
Accepting connection(s): snip:11111
Accepting connection(s): snip:11111
( 284.763s) [paraview ]vtkTCPNetworkAccessMana:553 ERR| vtkTCPNetworkAccessManager (0xba7450): Client and server are different ParaView versions. Client reports version: 5.11 but server is version 5.12
( 284.767s) [paraview ]vtkTCPNetworkAccessMana:322 ERR| vtkTCPNetworkAccessManager (0xba7450):
**********************************************************************
Connection failed during handshake. The server has a different ParaView version than the client.
**********************************************************************5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/22372OptiX/VisRTX Raytracing Crashes in v5.12.0-RC12024-03-07T20:23:57-05:00Ryan Krattigerryan.krattiger@kitware.comOptiX/VisRTX Raytracing Crashes in v5.12.0-RC1Related issue: https://gitlab.kitware.com/paraview/paraview/-/issues/20991
Using the VisRTX ray tracer leads to crashes in ParaView. This behavior was a previously a known issues when using OSMesa off-screen rendering. This behavior now...Related issue: https://gitlab.kitware.com/paraview/paraview/-/issues/20991
Using the VisRTX ray tracer leads to crashes in ParaView. This behavior was a previously a known issues when using OSMesa off-screen rendering. This behavior now (as of 5.12.0-RC1) also leads to crashes when using the NVidia EGL server which was previously able to run the OptiX ray tracer in 5.11.
Steps to reproduce:
1. Download/extract/start ParaView with EGL server (or osmesa or client builtin server)
2. Create a sphere (defaults)
3. Enable raytracing
4. Select OptiX Raytracer (defaults)
This error prints until ParaView crashes
```console
( 366.059s) [paraview ] FrameBuffer.h:79 ERR| VISRTX Error: Could not get color texture.
( 366.059s) [paraview ] FrameBuffer.h:92 ERR| VISRTX Error: Could not get depth texture.
```
---
System and Software
* GPU: Quadro T2000 Mobile / Max-Q
* NVidia Drivers (from nvidia-smi)
```console
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.23.06 Driver Version: 545.23.06 CUDA Version: 12.3 |
|-----------------------------------------+----------------------+----------------------+
```
* OS: Ubunutu 20.04 LTS
CC: @cory.quammen @vbolea5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22369ParaView 5.12.0-RC1: Incorrect time information and a 'question mark' next to...2024-03-07T20:23:57-05:00Jaswant Panchumarti (Kitware)ParaView 5.12.0-RC1: Incorrect time information and a 'question mark' next to time step value1. Download any Windows ParaView 5.12 RC1 from https://www.paraview.org/files/v5.12/
2. Go to Help -> Example Visualizations
3. Click on the first example named "Exodus II file with timesteps, Clip filter"
4. After it loads, see the time...1. Download any Windows ParaView 5.12 RC1 from https://www.paraview.org/files/v5.12/
2. Go to Help -> Example Visualizations
3. Click on the first example named "Exodus II file with timesteps, Clip filter"
4. After it loads, see the time toolbar, it shows incorrect time step and a question mark.
Surprisingly, I see the issue even in 5.11.2 on Linux.
![question-mark-in-time-combo-box](/uploads/91f32e6f66bed64863936ea25a9548d8/question-mark-in-time-combo-box.png)5.13 (Summer 2024)https://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/22183Descriptive Statistics hangs in parallel2024-03-07T20:23:57-05:00W. Alan ScottDescriptive Statistics hangs in parallelDescriptive Statistics is hanging when run in parallel. Here is how to replicate.
* Linux, master (I don't have access to my code right now) 6/15/2023, remote server (16 ranks).
* can.exo. Apply.
* Filters/ Alphabetical/ Descriptive St...Descriptive Statistics is hanging when run in parallel. Here is how to replicate.
* Linux, master (I don't have access to my code right now) 6/15/2023, remote server (16 ranks).
* can.exo. Apply.
* Filters/ Alphabetical/ Descriptive Statistics. Apply
It will never return.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22181Exodus writer is deprecated. Move to a plugin2024-03-07T20:23:57-05:00W. Alan ScottExodus writer is deprecated. Move to a pluginThe Exodus Writer is deprecated. This functionality has been moved to the IOSS writer. Although the IOSS writer is still being filled out, it is already head and sholders more complete than the Exodus writer.
Please move the Exodus ...The Exodus Writer is deprecated. This functionality has been moved to the IOSS writer. Although the IOSS writer is still being filled out, it is already head and sholders more complete than the Exodus writer.
Please move the Exodus writer to be a plugin. Default off. Thus, the IOSS writer will be the default writer for Exodus.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22128Colormap opacity enabled after switch to categorical and back2024-03-07T20:23:57-05:00Aron HelserColormap opacity enabled after switch to categorical and backOn current PV master, 5/3/2023, with the new colormapping UI reorganization, there is an unexpected behavior enabling opacity mapping.
To reproduce:
* load Source .. Data Objects .. HyperTreeGrid (or any dataset with something that can b...On current PV master, 5/3/2023, with the new colormapping UI reorganization, there is an unexpected behavior enabling opacity mapping.
To reproduce:
* load Source .. Data Objects .. HyperTreeGrid (or any dataset with something that can be a categorical color map)
* color by `vtkEdgeFlags`
* show the Color Map Editor. Notice "Enable Opacity Mapping for Surfaces" is disabled
* enable "Interpret Values as Categories". Immediately disable.
* "Enable Opacity Mapping for Surfaces" is now enabled, and my surface has disappeared.
Note that if I now explicitly disable "Enable Opacity Mapping for Surfaces" at this point, it sticks - I can switch to categorical and back without a problem. Maybe this points to default value handling somehow?
I also see that when "Interpret Values as Categories" is on, an "Enable Opacity Mapping for Surfaces" option is present and enabled by default.
CC @jaswant.panchumarti @cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22126Using a programable filter after a scalar clip will not return min/max in a t...2024-03-07T20:23:56-05:00Phil SmithUsing a programable filter after a scalar clip will not return min/max in a table**To reproduce this error perform the following:**
**Manual reproduction:**
- Open spcta_a.0*; Apply
- Select all cell arrays; Apply
- Perform a clip
- Select Scalar
- Select Temperature (ev)
- Select reset using current data values
-...**To reproduce this error perform the following:**
**Manual reproduction:**
- Open spcta_a.0*; Apply
- Select all cell arrays; Apply
- Perform a clip
- Select Scalar
- Select Temperature (ev)
- Select reset using current data values
- Unselect Invert; Apply
- Add a programmable filter:
- Set Output Data Set Type to vtkTable
- Select Copy Arrays
- within the script window use the following:
```
from paraview.vtk.numpy_interface import algorithms as np
input0 = inputs[0]
array = input0.CellData['Mass (g) - 2']
val = np.mean(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (mean)')
val = np.std(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (std)')
val = np.min(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (min)')
val = np.max(array)
if type(val).__name__ == "VTKNoneArray":
val = -100
output.RowData.append(val, 'T - 1 (max)')`
```
- Apply
**I get this error:**
```
Traceback (most recent call last):
File "<string>", line 22, in <module>
File "<string>", line 15, in RequestData
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 399, in min
return _global_func(MinImpl(), array, axis, controller)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 184, in _global_func
res = impl.serial_composite(array, axis)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 387, in serial_composite
res = _apply_func2(algs.min, array, (axis,))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 48, in _apply_func2
res.append(func(a, *args))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 397, in min
ans = numpy.min(narray, axis)
File "<__array_function__ internals>", line 5, in amin
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 2879, in amin
return _wrapreduction(a, np.minimum, 'min', axis, None, out,
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/Snip/lib/python3.9/site-packages/numpy/core/_methods.py", line 44, in _amin
return umr_minimum(a, axis, None, out, keepdims, initial, where)
ValueError: zero-size array to reduction operation minimum which has no identity
```
**As stated above, I have copied the arrays from the clip to the programable filter, but the programable filter does not show the arrays that are in the clip, or a min and max that should be derived from the clip by using this filter. It does show a mean and an std value, so it should show a min and a max. It shouldn't through an error eather. This is wrong.**
In each of the following scripts I have placed 'snip' for the path, so they will have to be modified to be used.
**Here is another way to reproduce an error(Slightly different, but the same idea) using a script:
Run this script(no_min_after_scalarclip). : [no_min_after_scalarclip.py](/uploads/b31330bfc8e98ae9ee76f62b42069bc7/no_min_after_scalarclip.py)
It will not show a T-1 (max) 0r a T-1(min), but will produce these errors:**
```
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x2919f780): Algorithm vtkPVGeometryFilter (0x2917fbe0) returned failure for request: vtkInformation (0x291a0c20)
Debug: Off
Modified Time: 2830306
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x28e04e20): Algorithm vtkPVGeometryFilter (0x28dec3e0) returned failure for request: vtkInformation (0x28e062c0)
Debug: Off
Modified Time: 2830481
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
Traceback (most recent call last):
File "<string>", line 22, in <module>
File "<string>", line 15, in RequestData
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 399, in min
return _global_func(MinImpl(), array, axis, controller)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 184, in _global_func
res = impl.serial_composite(array, axis)
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 387, in serial_composite
res = _apply_func2(algs.min, array, (axis,))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/algorithms.py", line 48, in _apply_func2
res.append(func(a, *args))
File "/Snip/lib/python3.9/site-packages/vtkmodules/numpy_interface/internal_algorithms.py", line 397, in min
ans = numpy.min(narray, axis)
File "<__array_function__ internals>", line 5, in amin
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 2879, in amin
return _wrapreduction(a, np.minimum, 'min', axis, None, out,
File "/Snip/lib/python3.9/site-packages/numpy/core/fromnumeric.py", line 84, in _wrapreduction
return reduction(axis=axis, out=out, **passkwargs)
File "/Snip/lib/python3.9/site-packages/numpy/core/_methods.py", line 44, in _amin
return umr_minimum(a, axis, None, out, keepdims, initial, where)
ValueError: zero-size array to reduction operation minimum which has no identity
**However when this script is run: [min_after_planarclip.py](/uploads/da0453a970dba5188d2cab4f63a34774/min_after_planarclip.py), it will produce the min and the max, but will give theses errors:**
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x24a7f3d0): Algorithm vtkPVGeometryFilter (0x24a5f830) returned failure for request: vtkInformation (0x24a80870)
Debug: Off
Modified Time: 2532788
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
ERROR: In vtkExecutive.cxx, line 741
vtkCompositeDataPipeline (0x249fec80): Algorithm vtkPVGeometryFilter (0x249e5fe0) returned failure for request: vtkInformation (0x24a00120)
Debug: Off
Modified Time: 2532963
Reference Count: 1
Registered Events: (none)
Request: REQUEST_DATA_OBJECT
FROM_OUTPUT_PORT: 0
ALGORITHM_AFTER_FORWARD: 1
FORWARD_DIRECTION: 0
```
**This is still wrong, because it should not show theses errors at all.**
**I modified the pipeline for each of the examples above to include the Redistribute Data filter before the programable filter as a work-around. This should not have to be done.**5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22112Tracing Multiblock Inspector is not working properly with more than one Rende...2024-03-07T20:23:56-05:00Phil SmithTracing Multiblock Inspector is not working properly with more than one RenderViewWhen using the trace function to produce a python script, if Multiblock Inspector is used it does not reliably reproduce all the steps with more than one RenderView. To reproduce this perform the following:
1. Start Trace
2. Open can.ex2...When using the trace function to produce a python script, if Multiblock Inspector is used it does not reliably reproduce all the steps with more than one RenderView. To reproduce this perform the following:
1. Start Trace
2. Open can.ex2
3. Open the Miltiblock Inspector
4. Turn off all except block one in RenderView1
5. Open another RenderView(RenderView2)
6. Click on the eye next to can.ex2 ( The Multiblock Inspector will show all the blocks in this view)
7. Turn off all except block two for RenderView2
8. Select Extract Blocks within the Multiblock inspector
Everything looks good at this point.
Stop and save the Trace as a script
Reset the session and replay the script you just saved
RenderView2 will be empty at the end of the run. It should show block two. This is a bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21843client-server connection arguments should be quoted (or something changed)2024-03-07T20:23:56-05:00Andrew Bauerclient-server connection arguments should be quoted (or something changed)When setting the ssh command in the client-server window we should add in quotes or something else to avoid issues with spaces in paths. The example below is for Putty's `plink` executable which was installed to `C:\Program Files\HPCMP K...When setting the ssh command in the client-server window we should add in quotes or something else to avoid issues with spaces in paths. The example below is for Putty's `plink` executable which was installed to `C:\Program Files\HPCMP Kerberos\plink.exe`. The spaces in this path are an example of the problem with creating a client-server connection. A user can currently get around this by adding quotes at the beginning and end of the full path but users can easily forget to do this. Diagnosing and correcting the problem is beyond many user's knowledge of ParaView and should be fixed automatically internally to ParaView.
![B188B04A-9086-46CC-B25F-E6D160C6DA37](/uploads/60c357fa25c94c45a41b67f94792374f/B188B04A-9086-46CC-B25F-E6D160C6DA37.jpeg)
Initially assigning this to @cory.quammen, really just to notify him of this issue. This seems like a simple fix so I'm hoping that it can go into the v5.12 release. It's not critical to be in v5.12 though.5.13 (Summer 2024)Jaswant Panchumarti (Kitware)Jaswant Panchumarti (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/21830Tasks for the IOSS writer2024-03-07T20:23:56-05:00W. Alan ScottTasks for the IOSS writerGeneral requests:
* For all tasks below, write mesh, point and cell data
* Output of the IOSS writer will target post processing. Currently it is envisioned that this output will not be used for input to simulation codes. Output files ...General requests:
* For all tasks below, write mesh, point and cell data
* Output of the IOSS writer will target post processing. Currently it is envisioned that this output will not be used for input to simulation codes. Output files will read cleanly into ParaView.
* IOSS Writer will be able to seamlessly process restart files read into ParaView.
* IOSS Writer will never be expected to split datasets into restarts.
Here is a list of issues needed for a first pass of the IOSS writer.
- [x] Exodus file format.
- [x] Parallel writer. Match one rank to one output file. (i.e., if we have 32 input files read by 4 ranks, write out 4 files.)
- [x] Write dataset that was read in.
- [x] Write out data and mesh that is a subset of dataset read in. No new cells will be created. Example is output of the threshold filter.
- [x] Write out data and mesh that does not match the input mesh. Examples are output of the Slice, Clip, isoVolume, Contour and Extract Surface filter.
- [x] Preseve blocks.
- [x] Write global IDs correctly. Not necessary (yet) to create Pedigree IDs for created cells.
- [ ] #22146 IOSS Writer dialog cleanup
Here is a list of issues needed for the second pass of the IOSS writer.
- [ ] CGNS file format. For all bullets below, write mesh, point and cell data.
- [ ] Allow writer to follow Redistribute Dataset filter. If we have 16 ranks, and want to move to 8 files out, run the Redistribute Dataset filter.
- [ ] Allow writer to write out global data.
- [x] Allow writer to output side sets and node sets. This includes variable data on these sets.
- [ ] Write pedigree IDs for datasets that include created cells. Examples of filters are the list of Slice, Cliip, etc. above.
- [x] Allow control over timesteps written. This includes start timestep, stop timestep and stride. (This is a secondary need as the ExtractTimeSteps filter replicates this feature.)
- [x] Allow variable data to be selectively written.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21728Contour filter is failing on CTH AMR2024-03-07T20:23:55-05:00W. Alan ScottContour filter is failing on CTH AMRThe Contour filter is failing on CTH AMR data. This is critical to get fixed. Here is how to replicate it.
* 5.11.0, builtin server, Linux.
* Load the four file spcta_a.[0-3] dataset. I believe it's called "Dave's Small CTH" or someth...The Contour filter is failing on CTH AMR data. This is critical to get fixed. Here is how to replicate it.
* 5.11.0, builtin server, Linux.
* Load the four file spcta_a.[0-3] dataset. I believe it's called "Dave's Small CTH" or something like that. Turn all variables on. Apply.
* Cell Data to Point Data filter. Apply. (Needed because Contour only works on point data.)
* Contour. Temperature (ev). Reset using current data values. Apply.
Contour fails, and writes out the following:
ERROR: In vtkAlgorithm.cxx, line 639
vtkPVContourFilter (0x27dc5080): Attempt to get point or cell data from a data object
There is a hack that works. Add a clip filter between the Cell Data to Point Data filter. This really should be fixed for 5.12.0.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21717Create a "how to create a filter" procedure2024-03-07T20:23:55-05:00W. Alan ScottCreate a "how to create a filter" procedureCory created a Perlin Noise filter a few years ago. When I asked how he figured it out and the steps he used, he gave me the following steps. I think these should be added to the ParaView Reference Manual, along with other tips. At le...Cory created a Perlin Noise filter a few years ago. When I asked how he figured it out and the steps he used, he gave me the following steps. I think these should be added to the ParaView Reference Manual, along with other tips. At least this is a good start! From Cory:
Here's roughly how I figured it out:
* check that there is a VTK class named vtkPerlinNoise. There is! Hmm, but it's not a filter.
* check if there is a VTK class that produces Perline noise on a grid. Nope, nothing else named Perlin.
* look at vtkPerlinNoise again. Hmm, it's a vtkImplicitFunction subclass. That means it is used in a context where points in a dataset are passed to it, and something is done with the resulting value. What other filters exposed in ParaView do something similar? The Clip filter is one. So now I have a model of how to do this.
* What is a filter that takes a vtkImplicitFunction and evaluates it at all points in a VTK dataset? Anything with the name Implicit in it? Indeed! vtkSampleImplicitFunctionFilter.
* Start creating the XML needed for vtkSampleImplicitFunctionFilter. There are not many options in this class, so that is pretty simple.
* Last part - how do I create a vtkPerlinNoise object and get it to the vtkSampleImplicitFunctionFilter? Look to the "Clip" filter. It has a ProxyProperty called ClipFunction. A ProxyProperty is a property that takes another ParaView proxy - in this case, we want it to take a proxy object representing a vtkPerlinNoise object. Using the example of "Clip", we can tell the Clip proxy that its ClipFunction property can be one of the proxies in a list of proxies representing implicit functions. Now I know I have to do the same for the vtkSampleImplicitFunctionFilter proxy, but I need only provide one implicit function, the Perlin noise function.
* Before I can tell the vtkSampleImplicitFunctionFilter proxy about the Perlin noise implicit function, I have to write some XML to describe it. I look for the "Cylinder" implicit function to use as a model and find it in misc_utilities.xml. Here I see that I need to describe properties of the implicit function. In the case of Perlin noise, there are just a couple to expose. Plus, I need to make sure the XML for the Perlin noise function is in the right ProxyGroup - in this case that group is "implicit_functions". It could be anything, really - it just has to match what I put in the XML for the vtkSampleImplicitFunctionFilter proxy.
* Now I am ready to define the property in the vtkSampleImplicitFunctionFilter proxy that is the Perlin noise source. I once again use the "Clip" filter as my model and see that I need to list the Perlin noise proxy in the group of possible proxies for this property.
* Yadda yadda yadda, I've got an XML filter.
So you see, it wasn't that easy. At least, it wouldn't be very easy to write up. On the other hand, including it as an example on the plugins HOWTO isn't far-fetched. People who learn by pattern matching (like me) will be able to use it as a basis for some XML plugins.
@cory.quammen5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21675Python. Function CreationRepresentation -> Registering Error ?2024-03-07T20:23:55-05:00Camille YvinPython. Function CreationRepresentation -> Registering Error ?I have a library that use the function CreateRepresentation from servermanager
In Paraview 5.6.0, the following minimal example works :
```python
from paraview.simple import *
from paraview.servermanager import *
rv = GetRenderView()
...I have a library that use the function CreateRepresentation from servermanager
In Paraview 5.6.0, the following minimal example works :
```python
from paraview.simple import *
from paraview.servermanager import *
rv = GetRenderView()
box = sources.Box(registrationGroup="sources", Center=[2., 2., 2.])
display = CreateRepresentation(box, rv, registrationGroup='representations')
display.SetRepresentationType('Surface')
```
In Paraview 5.10.0, the previous example does not work. I have this message :
```python
File "<string>", line 7, in <module>
File "/home/applis/paraview/5.10.0/lib/python3.9/site-packages/paraview/servermanager.py", line 2332, in CreateRepresentation
setattr(proxy, items[0], items[1])
NameError: name 'items' is not defined
```
So I corrected the lines 2331 and 2332 of servermanager.py from
```
for param in extraArgs.items():
setattr(proxy, items[0], items[1])
```
to
```
for param in extraArgs.items():
setattr(proxy, param[0], param[1])
```
Then when I run the minimal example, I have the following message:
```
Traceback (most recent call last):
File "<string>", line 7, in <module>
File "/home/applis/paraview/5.10.0/lib/python3.9/site-packages/paraview/servermanager.py", line 2332, in CreateRepresentation
setattr(proxy, param[0], param[1])
File "/home/applis/paraview/5.10.0/lib/python3.9/site-packages/paraview/servermanager.py", line 489, in __setattr__
raise AttributeError("Attribute %s does not exist. " % name +
AttributeError: Attribute registrationGroup does not exist. This class does not allow addition of new attributes to avoid mistakes due to typos. Use add_attribute() if you really want to add this attribute.
````
The proxy does not seem to have the attribute `registrationGroup`. In the documentation of the function, it seems possible to use this attribute :
```python
def CreateRepresentation(aProxy, view, **extraArgs):
"""Creates a representation for the proxy and adds it to the render
module.
This method can also be used to initialize properties by passing
keyword arguments where the key is the name of the property.In addition
registrationGroup and registrationName (optional) can be specified (as
keyword arguments) to automatically register the proxy with the proxy
manager.
This method tries to create the best possible representation for the given
proxy in the given view. Additionally, the user can specify proxyName
(optional) to create a representation of a particular type."""
global rendering
if not aProxy:
raise RuntimeError ("proxy argument cannot be None.")
if not view:
raise RuntimeError ("view argument cannot be None.")
if "proxyName" in extraArgs:
display = CreateProxy("representations", extraArgs['proxyName'], None)
del extraArgs['proxyName']
else:
display = view.SMProxy.CreateDefaultRepresentation(aProxy.SMProxy, 0)
if display:
display.UnRegister(None)
if not display:
return None
proxy = _getPyProxy(display)
proxy.Input = aProxy
for param in extraArgs.items():
setattr(proxy, param[0], param[1])
proxy.UpdateVTKObjects()
view.Representations.append(proxy)
return proxy
```
When I delete the 'registrationGroup' keyword when I called the function CreateRepresentation in the minimal example, it is okay but I have the following message when I exit Paraview (this message appears only when I called the function CreateRepresentation) :
```
# Loguru caught a signal: SIGABRT
# Stack trace:
# 8 0x152dc69dc073 /home/applis/paraview/5.10.0/bin/../lib/../lib/libvtkIOGeometry-pv5.10.so.1(+0x38073) [0x152dc69dc073]
# 7 0x152deabb6037 __cxa_finalize + 247
# 6 0x152dea774136 std::vector<std::string>::~vector() + 198
# 5 0x152deabfeeec /lib64/libc.so.6(+0x82eec) [0x152deabfeeec]
# 4 0x152deabfd5ec /lib64/libc.so.6(+0x815ec) [0x152deabfd5ec]
# 3 0x152deabf64e7 /lib64/libc.so.6(+0x7a4e7) [0x152deabf64e7]
# 2 0x152deab9ddb5 abort + 295
# 1 0x152deabb337f gsignal + 271
# 0 0x152deabb3400 /lib64/libc.so.6(+0x37400) [0x152deabb3400]
# ( 317.581s) [paraview ] :0 FATL| Signal: SIGABRT
```
I think that when the Representation is created, it is not corectly registered which explains this SIGABRT signal. Is someone have an idea of the way that I can correct it ?
Best regards
Camille5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21660Unsupported topology sphere2024-03-07T20:23:54-05:00W. Alan ScottUnsupported topology sphereMy user has a dataset that is failing. He wrote this up with the following comments:
The SIERRA/SM code represents “rigid body” blocks using a point/element of type “sphere.” Opening a file with such element types produces this messag...My user has a dataset that is failing. He wrote this up with the following comments:
The SIERRA/SM code represents “rigid body” blocks using a point/element of type “sphere.” Opening a file with such element types produces this message in Paraview 5.11.0-RC1:
```
( 14.973s) [paraview ] vtkIOSSUtilities.cxx:393 ERR| Element of topology 'sphere' with 1 nodes is not supported.
( 14.974s) [paraview ] vtkIOSSReader.cxx:2686 ERR| Error reading entity block (or set) named 'rigidbodyoutputpart' from '/snip/global.e'; skipping. Details: Unsupported topology sphere
```
As a result, the location and fields defined on this part can’t be visualized.
* Linux, master (and 5.11.0-RC2), builtin server.
* Open gears-DoNotRelease.e. Only turn on block ridigbodyoutputpart. Apply
An error is seen in the terminal window. Further, as stated, information tab shows no cells or points.
To see what it should look like, turn on and use the LegacyExodusReader in Tools/ Manage Plugins. You should see 5 points. (If needed, do a Reset and rubber band select of the screen. You will see them. Further, you can see them in the information tab.
I will send data to Cory. Data is gears-DoNotRelease.e. OK to share with anyone at Kitware.5.13 (Summer 2024)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/21648Save Screenshot fails in Catalyst trace.2024-03-07T20:23:54-05:00W. Alan ScottSave Screenshot fails in Catalyst trace.My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews a...My user created a Catalyst State file. It created three renderviews. He did an extract image for each of the renderviews, which worked correctly. Next, he used a trace to get the commands to save screenshot for all three renderviews at one time, cut and pasted that into the Catalyst State file, and ran that. Catalyst said the .png could not be written.
Error was:
```
[pvbatch.0 ] vtkPNGWriter.cxx:254 ERR| vtkPNGWriter (0x2a144d20): Unable to open file ./catalyst_output/panel_
{timestep:06d} {camera}
.png
[pvbatch.0 ] vtkImageWriter.cxx:481 ERR| vtkPNGWriter (0x2a144d20): Ran out of disk space; deleting file(s) already written
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21647Catalyst 2 scripts need to account for data operations internal to readers2024-03-07T20:23:54-05:00Cory Quammencory.quammen@kitware.comCatalyst 2 scripts need to account for data operations internal to readersWhen creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it...When creating Catalyst scripts from readers that perform certain data operations such as selecting only some blocks to read and applying a displacement field to points, we are missing those data operations in the recorded script. When it is used in a Catalyst run, the data comes in untransformed, leading to incorrect data. We need to capture the data transformations inside the reader in the Catalyst pipeline somehow.5.13 (Summer 2024)