ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-03-09T05:09:57-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21810empty plots with pvbatch because of wrong order of operations in python trace2023-03-09T05:09:57-05:00Arianna Formentiempty plots with pvbatch because of wrong order of operations in python traceHi all!
I'm trying to save an animation from terminal using `pvbatch`.
To do so, I follow this workflow:
1. generate a state file with the desired plotting configuration (say, `state.pvsm`)
2. reset session
3. start a python trace
4. ...Hi all!
I'm trying to save an animation from terminal using `pvbatch`.
To do so, I follow this workflow:
1. generate a state file with the desired plotting configuration (say, `state.pvsm`)
2. reset session
3. start a python trace
4. load `state.pvsm`
5. save animation
6. abort
7. save trace (say, `trace.py`)
8. run `pvbatch` with `trace.py` as input
I'm using ParaView 5.11 (ParaView-5.11.0-MPI-Linux-Python3.9-x86_64).
The issue I have found is that `pvbatch` generates empty plots (e.g. white .png files) if I use `trace.py` as is.
With @ax3l's help, I was able to solve the problem by switching two blocks of code.
The original`trace.py` file which does not work reads:
```
from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
animationScene1 = GetAnimationScene()
timeKeeper1 = GetTimeKeeper()
renderView1 = FindViewOrCreate('RenderView1', viewtype='RenderView')
LoadState('state.pvsm')
# continues...
```
The modified `trace.py` script which seems to work reads:
```
from paraview.simple import *
paraview.simple._DisableFirstRenderCameraReset()
LoadState('state.pvsm')
animationScene1 = GetAnimationScene()
timeKeeper1 = GetTimeKeeper()
renderView1 = FindViewOrCreate('RenderView1', viewtype='RenderView')
# continues...
```
(To be precise, I also had to remove two lines like this one:\
`layout1.SetSize(1919, 909)`\
from `trace.py` because they raise an attribute error.)
It seems like the state should be loaded before generating the render view.
Does this make sense? Do you think it could be fixed?
Pinging @berkgeveci and @ax3l since I know you may talk about this soon enough.https://gitlab.kitware.com/paraview/paraview/-/issues/21816[Feature Request] Ship ParaView with a mangled VTK2023-03-15T13:17:55-04:00Julien Fausty[Feature Request] Ship ParaView with a mangled VTK## Problem Statement
When including ParaView into applications that already compile and link to VTK, collisions between ParaView's VTK version and the application's can occur at runtime leading to a crash if the VTK versions are incompa...## Problem Statement
When including ParaView into applications that already compile and link to VTK, collisions between ParaView's VTK version and the application's can occur at runtime leading to a crash if the VTK versions are incompatible.
As an example, this can happen when using ParaView's `Catalyst` implementation in a code that already links to an external system VTK.
## Proposed Solution
Given that it is much more likely for another application that already links VTK to develop a dependency on ParaView than it is for ParaView to develop a dependency on another application using VTK, it seems only natural that it should be ParaView's responsibility to mangle its internal VTK libraries using the relatively new `VTK_ABI_NAMESPACE` feature developed in https://gitlab.kitware.com/vtk/vtk/-/merge_requests/8993 (discourse here: https://discourse.vtk.org/t/new-feature-in-vtk-vtk-abi-namespace/9421).
This functionality wraps all of VTK in a compile time defined namespace. The symbols are then "sealed" against collision.
Thoughts?https://gitlab.kitware.com/paraview/paraview/-/issues/21819Selecting points on a line rendered as tubes crashes ParaView2023-03-14T09:40:06-04:00Kenneth MorelandSelecting points on a line rendered as tubes crashes ParaViewWhen you try to select points on line elements that are being rendered as tubes with enough thickness, ParaView crashes (observed in 5.11, Mac). To replicate, do the following.
1. Create as `Line` source. `Apply`.
2. Change the `Line Wi...When you try to select points on line elements that are being rendered as tubes with enough thickness, ParaView crashes (observed in 5.11, Mac). To replicate, do the following.
1. Create as `Line` source. `Apply`.
2. Change the `Line Width` to `5`.
3. Turn on `Render Lines as `Tubes`.
4. Click `Select Points On` and select some region of the line. -> Crashhttps://gitlab.kitware.com/paraview/paraview/-/issues/21820ParaView Simple import into Python fails on Linux2023-03-15T07:04:58-04:00CoryParaView Simple import into Python fails on LinuxWhen trying to import ```paraview.simple``` into my Python script, I get the following error:
```
Traceback (most recent call last):
File "/home/cory/git-repos/MachLine/dev/helper_scripts/paraview_functions.py", line 3, in <module>
...When trying to import ```paraview.simple``` into my Python script, I get the following error:
```
Traceback (most recent call last):
File "/home/cory/git-repos/MachLine/dev/helper_scripts/paraview_functions.py", line 3, in <module>
import paraview.simple as pvs
File "/home/cory/Paraview/lib/python3.9/site-packages/paraview/simple.py", line 41, in <module>
from paraview import servermanager
File "/home/cory/Paraview/lib/python3.9/site-packages/paraview/servermanager.py", line 60, in <module>
from paraview.modules.vtkRemotingApplication import *
ImportError: /lib/x86_64-linux-gnu/libp11-kit.so.0: undefined symbol: ffi_type_pointer, version LIBFFI_BASE_7.0
```
I am running Linux Mint 20.2 Cinnamon 64-bit.https://gitlab.kitware.com/paraview/paraview/-/issues/21821Axis labels/titles carry shadow in LineChartView2023-03-16T11:42:26-04:00PfiffikusAxis labels/titles carry shadow in LineChartViewAs depicted in the screenshot at the bottom of the axis annotations mysterious pixels occur; visible on Windows/linux version of 5.11.0
![LabelShadow](/uploads/4910b7b60427a9a620cdceda8d66999f/LabelShadow.png)As depicted in the screenshot at the bottom of the axis annotations mysterious pixels occur; visible on Windows/linux version of 5.11.0
![LabelShadow](/uploads/4910b7b60427a9a620cdceda8d66999f/LabelShadow.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21823Catalyst 2: Live Trigger do not update pipeline2023-11-08T21:14:22-05:00Nicolas VuailleCatalyst 2: Live Trigger do not update pipeline### Problem
In Catlyst 2 the `CatalystLiveTrigger` is not used to trigger the pipeline update. Only extractors do.
When `CatalystLiveTrigger.Frequency` has a match, the conduit sources should be updated with current time.
This is not th...### Problem
In Catlyst 2 the `CatalystLiveTrigger` is not used to trigger the pipeline update. Only extractors do.
When `CatalystLiveTrigger.Frequency` has a match, the conduit sources should be updated with current time.
This is not the case, as mentioned in [vtkCPPythonScriptV2Helper::DoLive]( https://gitlab.kitware.com/paraview/paraview/-/blob/d66f44fee151a548a3fa48d2041667debb910231/Clients/PythonCatalyst/vtkCPPythonScriptV2Helper.cxx#L724).
### Workaround
To update the live visu when no extractor is updating, one may add this method in the python script:
```python
def catalyst_execute(info):
global grid
grid.UpdatePipeline(info.time)
```
Where `grid` is the input source of the pipeline. The pipeline will be then updated depending on the `GlobalTrigger.Frequency` option.i
### Testing
I used the Catalyst2/CxxFullExample with the following custom script [cata.py](/uploads/53f80991df89dd7f3fd2bf76eb191ff7/cata.py).
In this script, a PNG extractor is created with `Frequency=4`, Live is enabled.https://gitlab.kitware.com/paraview/paraview/-/issues/21825Pick Center on Surface representation didn't work in 5.112023-03-21T07:12:46-04:00Lucas GivordPick Center on Surface representation didn't work in 5.11Using the `Pick Center` then click on the surface didn't change the position of the mark with paraview 5.11 (tested on windows, it may be relevant) when the representation setted is the `Surface`.
However the position of the mark is co...Using the `Pick Center` then click on the surface didn't change the position of the mark with paraview 5.11 (tested on windows, it may be relevant) when the representation setted is the `Surface`.
However the position of the mark is correclty updated when the representation is `Surface With Edges`:
![image](/uploads/7eccd1823fd3aa43637e8f105c9b8245/image.png)
On ParaView 5.9.1, the pick center is correctly updated, maybe it's a regression.
Step to reproduce:
- open ParaView 5.11.O
- create a Wavelet
- set the representation to `Surface`
- click on `Pick Center`
- click on the surface
- nothing happen, **the center isn't changed**
- now, set the representation to ``Surface with Edges`
- click on `Pick Center`
- click on the surface
- the center is changed
Tested on Windows with ParaView 5.9.1 and ParaView 5.11.0https://gitlab.kitware.com/paraview/paraview/-/issues/21826feature request: Python Editor does _not_ notice script modification by exter...2023-03-21T05:22:53-04:00Pfiffikusfeature request: Python Editor does _not_ notice script modification by external editor e.g.When an opened script is manipulated by any external programme, the script editor runs nevertheless the outdated version of the script :disappointed:
What about to ask for a refresh when the editor gets focus again?
Alternatively a man...When an opened script is manipulated by any external programme, the script editor runs nevertheless the outdated version of the script :disappointed:
What about to ask for a refresh when the editor gets focus again?
Alternatively a manual refresh should be supported; currently closing & reopening of the obsolete version is necessary ...!?
Or could the workflow be optimized somewhere else?https://gitlab.kitware.com/paraview/paraview/-/issues/21827output messages prevents main window to be maximized in Debian112023-03-21T11:25:39-04:00Pfiffikusoutput messages prevents main window to be maximized in Debian11With a minimized main window a macro runs from script editor. If the macro cause some errors and opens the (detached) output message window, there is no(?) way to maximize the main window immediately:
The icon offers 2 windows (main wind...With a minimized main window a macro runs from script editor. If the macro cause some errors and opens the (detached) output message window, there is no(?) way to maximize the main window immediately:
The icon offers 2 windows (main window & script editor), but as long as the output message view is detached, main window could not be maximized. After attaching or closing output message window the main can be maximized.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/21831Hyper Tree Grid (HTG) Source: Issue Tracker2023-03-23T05:34:26-04:00Julien FaustyHyper Tree Grid (HTG) Source: Issue Tracker## Context
The "Hyper Tree Grid" source (`vtkHyperTreeGridSource`) serves to transform a string literal descriptor of a Hyper Tree Grid into a `vtkHyperTreeGrid` data object. It would seem that it has a certain number of robustness prob...## Context
The "Hyper Tree Grid" source (`vtkHyperTreeGridSource`) serves to transform a string literal descriptor of a Hyper Tree Grid into a `vtkHyperTreeGrid` data object. It would seem that it has a certain number of robustness problems. This issue is an attempt to start tracking them.
## Problems
- [ ] Setting one of the "Dimensions" properties to `0` (i.e. trying to generate a 2D HTG) results in a crash with the following output:
```
( 24.311s) [paraview ]vtkHyperTreeGridSource.:834 ERR| vtkHyperTreeGridSource (0x55bbb0a59980): String level descriptor . has cardinality 1 which is not expected value of 4294967295
```
The "Dimensions" property must be set to 1 to generate a 2D object.
- [ ] The `MaxDepth` property serves almost no purpose since the number of levels can be deduced from the descriptor
- [ ] The documentation regarding the format of string descriptor is non-existent in the thumbnails and in the dedicated documentation accessible from ParaView
- [ ] Once a mistake has been made in editing the "Descriptor" property, the source becomes frozen and will not generate an output even after correcting the mistake. It must be deleted and recreated in order to try again.https://gitlab.kitware.com/paraview/paraview/-/issues/21832Line rendering is not working as expected on MacOS2023-04-04T14:54:47-04:00W. Alan ScottLine rendering is not working as expected on MacOSMacs are not rendering lines correctly when they have a width greater than 1. This appears to only be true when painted by a variable. Linux works correctly. Here is how to replicate.
* MacOS, 5.11.0, builtin server.
* Open dataset fro...Macs are not rendering lines correctly when they have a width greater than 1. This appears to only be true when painted by a variable. Linux works correctly. Here is how to replicate.
* MacOS, 5.11.0, builtin server.
* Open dataset from https://discourse.paraview.org/t/cell-values-partly-disappear-when-editing-width-on-mac/11666. Apply.
* Render by surface. Paint by pipe_id.
* Advanced property tab/ change line width to 5. The vertical lines disappear.
Attached screenshot has the data read in twice. The white data is correct, the data painted with cool to warm is incorrect, and is missing vertical lines. Note the incorrect dataset has been translated left and up so the correct and incorrect data aren't drawn on each other.
@cory.quammen How critical do you think this is?
![Screenshot_2023-03-22_at_4.15.23_PM](/uploads/80e75f7389ac73438a7063d9e8d6769e/Screenshot_2023-03-22_at_4.15.23_PM.png)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/21836MPI issue while building Paraview on Mac2023-03-26T22:08:36-04:00Muhammad Saad AtiqueMPI issue while building Paraview on MacI am trying to build Paraview on mac. I ran ninja command and got the following error.
![image](/uploads/a31d77a664d3e0f4775c43cd23950f3c/image.png)
![image](/uploads/5df7829ed5026ab8d90eb7706541b1b5/image.png)I am trying to build Paraview on mac. I ran ninja command and got the following error.
![image](/uploads/a31d77a664d3e0f4775c43cd23950f3c/image.png)
![image](/uploads/5df7829ed5026ab8d90eb7706541b1b5/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21837TemporalParticlesToPathlines Filter Should Support Composite Datasets2023-03-25T18:35:25-04:00Axel HueblTemporalParticlesToPathlines Filter Should Support Composite DatasetsIn https://gitlab.kitware.com/paraview/paraview/-/issues/21162#note_1109104, we realized that the implementation of the `TemporalParticlesToPathlines` filter, which uses `vtkTemporalPathLineFilter`, does not yet support composite dataset...In https://gitlab.kitware.com/paraview/paraview/-/issues/21162#note_1109104, we realized that the implementation of the `TemporalParticlesToPathlines` filter, which uses `vtkTemporalPathLineFilter`, does not yet support composite datasets (`vtkMultiBlockDataSets`).
As a work-around, we need to apply the `MergeBlocks` filter first.
This affects the openPMD reader and the AMReX plotfile reader.
cc @berkgevecihttps://gitlab.kitware.com/paraview/paraview/-/issues/21840Generate Quadrature Scheme Dictionary - crash with hexahedrons2023-03-28T05:57:19-04:00FEA-engGenerate Quadrature Scheme Dictionary - crash with hexahedronsParaView crashes when the Generate Quadrature Scheme Dictionary filter is used on data with hexahedron elements not supported by this filter yet.
Forum discussion: https://discourse.paraview.org/t/generate-quadrature-scheme-dictionary-c...ParaView crashes when the Generate Quadrature Scheme Dictionary filter is used on data with hexahedron elements not supported by this filter yet.
Forum discussion: https://discourse.paraview.org/t/generate-quadrature-scheme-dictionary-crash/11721/2https://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/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/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/21846prism plugin needs select cells through2023-04-23T04:33:04-04:00W. Alan Scottprism plugin needs select cells throughThere is going to be demand for the prism view to allow select cells through. I know this is hard, and will be time consuming, but want to get it written up. Here it is. Requested by Greg W.There is going to be demand for the prism view to allow select cells through. I know this is hard, and will be time consuming, but want to get it written up. Here it is. Requested by Greg W.Spiros TsalikisSpiros Tsalikis