ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2024-03-07T20:23:56-05:00https://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/22120Rotational extrusion filter throws an error when AMR data is used as a source2023-04-25T16:58:00-04:00Phil SmithRotational extrusion filter throws an error when AMR data is used as a sourceTo replicate:
Open Sources->AMR GaussianPulse Source; Apply
Filters-> clean to grid
Perform a slice on the data
Apply the Rotational extrusion filter
At this point an error pops up saying:
ERROR: In vtkRotationalExtrusionFilter.cxx...To replicate:
Open Sources->AMR GaussianPulse Source; Apply
Filters-> clean to grid
Perform a slice on the data
Apply the Rotational extrusion filter
At this point an error pops up saying:
ERROR: In vtkRotationalExtrusionFilter.cxx, line 84
vtkRotationalExtrusionFilter (0xd52f010): No data to extrude!
However the data looks fine. I have attached a picture
If the same steps are performed on an Exodus file(can.ex2), the result looks the same, however, the error does not appear.
![image](/uploads/dabe6f4920b418788a2dc9ee60d701c0/image.png)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/22114Add TET10 support to the Mesh Quality filter2023-04-12T14:42:58-04:00W. Alan ScottAdd TET10 support to the Mesh Quality filterThere was a discussion a year ago about the Mesh Quality filter. This filter uses the Verdict library. The discussion was here: https://gitlab.kitware.com/paraview/paraview/-/issues/20805. Tet10's are not totally supported in the Ver...There was a discussion a year ago about the Mesh Quality filter. This filter uses the Verdict library. The discussion was here: https://gitlab.kitware.com/paraview/paraview/-/issues/20805. Tet10's are not totally supported in the Verdict library, so we decided to return a Quality of nan. It turns out that many quality values for tet10s ARE calculated in the Verdict library. Please enable these options, and when tet10's are not supported, default to tet4s. Here is how to reproduce the issue:
* 5.11.1, Linux, builtin server
* Sources/ UnstructuredCellTypes. Quadratic Tet. Apply.
* Filters/ Mesh Quality. Tet Quality Measure = Scaled Jacobian.
Everything will be yellow. This is because the Mesh Quality filter is returning nan's for Tet10's (Quadratic Tets).
Here is the thread from the user and Clint Stimpson, the project manager of Verdict explaining what we should be doing:
From user (Kevin M):
Verdict already supports some quality metrics for TET10 without reverting to a TET4 equivalent. “Normalized Inradius” is one of them. Surely there are others? I’m just asking that ParaView interface with the already-available verdict metrics in some meaningful way.
As best I can tell, ParaView does not interface with verdict at all for any TET10 quality measures – everything I check reports as NaN. It would be a much better solution, in my opinion, to interface with Verdict for all available Tet10 metrics and to revert to an equivalent TET4 for those metrics which are not fully supported – supplemented with an appropriate warning. In many cases the TET4 equivalent metric is probably identical to the TET10 metric when midside nodes are centered and unkinked, so there is still a lot of value to be added there.
From Clint:
We have tet10 support with inradius, normalized inradius, mean ratio, distortion, jacobian and volume.
It seems possible to support tet10 for a few more without too much trouble (scaled jacobian, for example).
And then there are several more metrics where I don’t think anyone has considered whether or how they could be implemented for tet10.
Whether they are implemented for tet10 probably depends on the meaning of the metric in relation to the analysis.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/22111Multiblock inspector showing blocks that are not loaded2023-04-23T04:32:31-04:00W. Alan ScottMultiblock inspector showing blocks that are not loadedThe multiblock inspector is showing and allowing changes to blocks that are not loaded. This is very confusing and needs to be fixed. Here is how to replicate.
* ParaView 5.11.1, builtin server, Mac
* Load bake.e. Turn off all blocks,...The multiblock inspector is showing and allowing changes to blocks that are not loaded. This is very confusing and needs to be fixed. Here is how to replicate.
* ParaView 5.11.1, builtin server, Mac
* Load bake.e. Turn off all blocks, then turn on only block_100 and block_101. Apply.
* View/ Multiblock inspector.
Notice that we are showing all blocks, not just selected ones. This is a bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21845Output messages width is way too wide2023-04-23T04:33:06-04:00W. Alan ScottOutput messages width is way too wideThe View/ Output Messages width is way too large. The primary problem comes if the output messages is docked behind the properties tab on the left, or the color map editor on the right. The properties tab then increases in width around...The View/ Output Messages width is way too large. The primary problem comes if the output messages is docked behind the properties tab on the left, or the color map editor on the right. The properties tab then increases in width around 3X.
Please make the output message so it can become much narrower. Add a horizontal scroll bar at the bottom. Allow the controls at the bottom of the output view to be stacked two rows high, thus halving the required width.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/21841pvserver interactive points -> tag missmatch -> exit2023-03-28T21:48:46-04:00Dani Schmidpvserver interactive points -> tag missmatch -> exitI use a ParaView 5.11 client (windows/linux give same result) and pvserver on a linux machine. Generally works very well, but with certain types of interactions such as ‘Hover Points On’ I get tag missmatch and pvserver exits. This issue...I use a ParaView 5.11 client (windows/linux give same result) and pvserver on a linux machine. Generally works very well, but with certain types of interactions such as ‘Hover Points On’ I get tag missmatch and pvserver exits. This issues is confirmed by mwestphal (see https://discourse.paraview.org/t/pvserver-interactive-points-tag-missmatch-exit). I have not found a way to reproduce this with a synthetic dataset, so I provide an example dataset. Here are the steps to reproduce the issue:
1. Get the example dataset from https://www.dropbox.com/s/o8pomdziflyfypu/test.tar.gz?dl=1
2. Start pvserver on linux and connect from windows 5.11 ParaView
3. Load pvd data file. 3D model, quite a few variables, several timesteps
4. ‘Hover Points On’ works at this stage
5. I have two materials in my model, the respective domains are marked by phase=0 and phase=1. I only want to see the parts of the model with phase=1 and use a threshold filter set to 0.1 and 1.
6. If I now try to use ‘Hover Points On’ on the shown phase=1 part of the model then I get the tag missmatch. pvserver then states ‘Exiting…’ but gets stuck. Using Ctrl-C at this stage spits out a stack trace. You find the whole command line output below.
Thanks
Dani
```
Client connected.
( 572.906s) [pvserver ]vtkSocketCommunicator.c:849 ERR| vtkSocketCommunicator (0x1268d70): Tag mismatch: got 1, expecting 10.
( 572.942s) [pvserver ]vtkSocketCommunicator.c:849 ERR| vtkSocketCommunicator (0x1268d70): Tag mismatch: got 1, expecting 41235.
( 572.942s) [pvserver ]vtkSocketCommunicator.c:849 ERR| vtkSocketCommunicator (0x1268d70): Tag mismatch: got 1, expecting 41235.
( 585.484s) [pvserver ]vtkSocketCommunicator.c:783 ERR| vtkSocketCommunicator (0x1268d70): Could not receive tag. 1
( 585.484s) [pvserver ]vtkTCPNetworkAccessMana:295 ERR| vtkTCPNetworkAccessManager (0x1178c60): Some error in socket processing.
Exiting…
^C
Loguru caught a signal: SIGINT
Stack trace:
21 0x40196d /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40196d]
20 0x7f5af397ad0a __libc_start_main + 234
19 0x40188e /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/pvserver-real() [0x40188e]
18 0x7f5af24e5654 vtkInitializationHelper::Finalize() + 100
17 0x7f5af13a8ae2 vtkProcessModule::Finalize() + 98
16 0x7f5aedd199fa /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/libvtkCommonCore-pv5.11.so.1(+0x6ae9fa) [0x7f5aedd199fa]
15 0x7f5aedbc0b29 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
14 0x7f5aeb3131b6 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libvtkRemotingViews-pv5.11.so.1(+0x1e81b6) [0x7f5aeb3131b6]
13 0x7f5ad7b44a89 vtkOSOpenGLRenderWindow::~vtkOSOpenGLRenderWindow() + 9
12 0x7f5ad7b44a1c vtkOSOpenGLRenderWindow::~vtkOSOpenGLRenderWindow() + 28
11 0x7f5ad7b449e3 vtkOSOpenGLRenderWindow::Finalize() + 83
10 0x7f5ad7b44914 vtkOSOpenGLRenderWindow::DestroyOffScreenWindow() + 36
9 0x7f5ad610866b OSMesaDestroyContext + 27
8 0x7f5ad61373e8 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0x1a93e8) [0x7f5ad61373e8]
7 0x7f5ad6135e38 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0x1a7e38) [0x7f5ad6135e38]
6 0x7f5ad6c33acb /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xca5acb) [0x7f5ad6c33acb]
5 0x7f5ad6ade9c5 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xb509c5) [0x7f5ad6ade9c5]
4 0x7f5ad6d9b544 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xe0d544) [0x7f5ad6d9b544]
3 0x7f5ad6c611a5 /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xcd31a5) [0x7f5ad6c611a5]
2 0x7f5ad6c34a6b /home/schmid/ParaView-5.11.0-RC2-osmesa-MPI-Linux-Python3.9-x86_64/bin/…/lib/…/lib/libOSMesa.so.8(+0xca6a6b) [0x7f5ad6c34a6b]
1 0x7f5aed6577b2 pthread_cond_wait + 482
0 0x7f5af398fd60 /lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f5af398fd60]
( 613.056s) [pvserver ] :0 FATL| Signal: SIGINT
```5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21835Rendering Erorrs with Paraview + Ospray2023-03-24T04:50:20-04:00Phil SmithRendering Erorrs with Paraview + OsprayTo Reproduce on 5.11.1-RC1
1. Select Sources->Wavelet
2. In the properties panel, set Whole Extent to 0,5000; 0,500; 0, 20
3. Apply
4. Set Representation to Volume
5. Set Coloring to RTData
6. Under Volume Rendering, set Volume Rendering...To Reproduce on 5.11.1-RC1
1. Select Sources->Wavelet
2. In the properties panel, set Whole Extent to 0,5000; 0,500; 0, 20
3. Apply
4. Set Representation to Volume
5. Set Coloring to RTData
6. Under Volume Rendering, set Volume Rendering Mode to OSPRay Based
7. Perform a box zoom at the right end go the Wavelet
You will see this:
https://discourse.paraview.org/uploads/default/original/2X/4/40767cd64d245091a587310d610b7573aacfb37e.jpeg
Please see the original write-up at https://discourse.paraview.org/t/rendering-erorrs-with-paraview-ospray/116755.13 (Summer 2024)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/21806File Open Set reader as defaults fails with CGNS files2023-03-07T22:43:22-05:00W. Alan ScottFile Open Set reader as defaults fails with CGNS filesThe Set Reader as Default is failing with the CGNS file reader. Replicate as follows:
* 5.11.0, builtin server, Linux.
* File/ Open/ SomeCGNSFile.cgns. Open Data Dialog opens. Select IOSS reader. Set Reader as Default. Dialog will cl...The Set Reader as Default is failing with the CGNS file reader. Replicate as follows:
* 5.11.0, builtin server, Linux.
* File/ Open/ SomeCGNSFile.cgns. Open Data Dialog opens. Select IOSS reader. Set Reader as Default. Dialog will close. Note - I used sparc.cgns.4.[0-3].
* Delete cgns file.
* File/ Open/ SomeCGNSFile.cgns.
The Open Data Dialog will open again. This is a bug.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21803Clean up Prism plugin log scale axis grid2023-03-10T15:57:19-05:00W. Alan ScottClean up Prism plugin log scale axis gridThe Prism plugin displays objects in pressure/temperature/density phase space. These spaces can be log scaled. Current log scaling is correct, but confusing. The tick locations should not be linearly placed, but placed along a log spac...The Prism plugin displays objects in pressure/temperature/density phase space. These spaces can be log scaled. Current log scaling is correct, but confusing. The tick locations should not be linearly placed, but placed along a log space. See the Color Legend, log scaled, for correct behavior.
@spiros.tsalikis5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21800Add a quick toggle for precision on the information tab2023-03-07T07:39:16-05:00W. Alan ScottAdd a quick toggle for precision on the information tabPlease add a quick toggle for precision displayed on the information tab.
Idea came from discourse post here: https://discourse.paraview.org/t/data-arrays-ranges-in-the-information-tab-may-be-at-too-high-precision/11561Please add a quick toggle for precision displayed on the information tab.
Idea came from discourse post here: https://discourse.paraview.org/t/data-arrays-ranges-in-the-information-tab-may-be-at-too-high-precision/115615.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21794Move plink to be secondary2023-03-01T13:40:19-05:00W. Alan ScottMove plink to be secondaryPlease move plink.exe to be the secondary communications program attempted for client/server connections on Windows. Primary should be ssh.exe, which is now standard on Windows 11.
The issue with plink.exe is it is included in a lot of...Please move plink.exe to be the secondary communications program attempted for client/server connections on Windows. Primary should be ssh.exe, which is now standard on Windows 11.
The issue with plink.exe is it is included in a lot of old software packages. I had a user that kept rebuilding his Windows box because ParaView wouldn't work. He would dutifully then install an old package (from something like the year 2000), which included plink. Plink was broken, thus ParaView always failed.
We should always use the OS solution if available, and not be dependent on what the PATH variable randomness includes.
Thought I had written this up before, but cannot find it.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21793Select Blocks Through2024-01-30T08:45:00-05:00W. Alan ScottSelect Blocks ThroughPlease add a "Select Blocks Through" selection functionality. Access it through an icon next to Select Blocks.Please add a "Select Blocks Through" selection functionality. Access it through an icon next to Select Blocks.5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21775Find data panel does not support search of string values in a vtkStringArray2023-02-16T15:53:47-05:00Spiros TsalikisFind data panel does not support search of string values in a vtkStringArrayFind data panel does not support search of string values in a vtkStringArray. This is not possible because
a vtkStringArray cannot be mapped to a NumPy array which is used by the python selector, which is then used by the Find Data Pane...Find data panel does not support search of string values in a vtkStringArray. This is not possible because
a vtkStringArray cannot be mapped to a NumPy array which is used by the python selector, which is then used by the Find Data Panel. This mapping cannot be performed (as of now) because a vtkStringArray is a special array where the memory size of each value is dynamic.
This issue is the result of the following discussion:
https://discourse.paraview.org/t/interpret-values-as-categories-not-working-for-string-properties-pv-5-11-0-rc2/11155
@wascott @cory.quammen @francois.mazen5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21773Crash with ResetSession2023-02-20T11:01:50-05:00W. Alan ScottCrash with ResetSessionWe have a crash with python ResetSession. Here is how to replicate.
* 5.11.0, MacOS (reports are Windows also crashes), builtin server.
* View/ Python Shell.
* ResetSession()
* Before ResetSession completes, hit the Enter key a few tim...We have a crash with python ResetSession. Here is how to replicate.
* 5.11.0, MacOS (reports are Windows also crashes), builtin server.
* View/ Python Shell.
* ResetSession()
* Before ResetSession completes, hit the Enter key a few times. Also, reports that mouse clicks into the view does the same thing.
ParaView will freeze for maybe a minute, then die.
Marking as Important, as this really is a rare occurrence.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21751Create CFD mesh quality filter at a wall2023-06-07T21:53:18-04:00W. Alan ScottCreate CFD mesh quality filter at a wallPlease create a CFD mesh quality filter at a wall boundary. Please call it "CFD Boundary Mesh Quality" (unless we figure out a better name). This filter needs to work on unstructured and structured meshes. It will produce two new outp...Please create a CFD mesh quality filter at a wall boundary. Please call it "CFD Boundary Mesh Quality" (unless we figure out a better name). This filter needs to work on unstructured and structured meshes. It will produce two new output variables. They are:
* Create a cell variable "DistanceFromFaceToCellCenter" (or whatever is a better name). (From Ken Moreland), the distance from the cell center to the plane containing the face.
* Create a cell variable "AngleFromFaceCenterToCellCenter" (or whatever is a better name). (From Chris B.), the angle between the face normal on the boundary and the vector from the face centroid to the cell centroid.
Discourse discussion is here: https://discourse.paraview.org/t/cfd-quality-of-mesh-at-boundaries/11243
@spiros.tsalikis5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21744Currently generated ParaView Catalyst Python scripts have no way to modify fi...2023-02-02T09:57:36-05:00Andrew BauerCurrently generated ParaView Catalyst Python scripts have no way to modify filter parameters during calls to CatalystI tested out the ability to set filter properties for Catalyst scripts that vary in time (e.g. having a slice filter output rotate as the simulation proceeds). With the currently GUI generated Catalyst Python scripts (using master on Ja...I tested out the ability to set filter properties for Catalyst scripts that vary in time (e.g. having a slice filter output rotate as the simulation proceeds). With the currently GUI generated Catalyst Python scripts (using master on Jan 18, 2023) the pipeline is created once by Catalyst and not called again. Try out the attached newslice.py script where I've added print statements. If sources in the pipeline were updated every in situ output then the print statement would be called. It would be good for users to be able to edit the GUI generated Catalyst Python scripts to allow filter properties to be updated during every Catalyst output step.
If I modify the Examples/Catalyst/SampleScripts/gridwriter.py script (also attached) and edit the DoCoProcessing() method I can get the slice normal to change with time. This gridwriter.py is the "old style" Catalyst script though and not generated through the GUI.
I think if there was some optional UpdateProperties() like method that was added to the Catalyst scripts where users could modify properties that would be a way to get around this issue. Here, UpdateProperties() would be called every time Catalyst was outputting extracts, images,etc.
[gridwriter.py](/uploads/f9326ff8e208a8cb13341c8dae416547/gridwriter.py)
[newslice.py](/uploads/e352eb44a96e301e1fa28ab56ef1bdbb/newslice.py)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/21742Optionally set state using dictionaries in traces and state files2024-03-26T13:44:10-04:00W. Alan ScottOptionally set state using dictionaries in traces and state filesAdd the option to set state using dictionaries in traces, ParaView python state and Catalyst state files. Make this option default off. An example was created by Cory as an original file and one using dictionaries. I will add the two ...Add the option to set state using dictionaries in traces, ParaView python state and Catalyst state files. Make this option default off. An example was created by Cory as an original file and one using dictionaries. I will add the two examples to this bug.5.13 (Summer 2024)