ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2023-04-23T04:32:34-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/22110SaveExtractsUsingCatalystOptions does not replace {timestep:06d} correctly2023-04-23T04:32:34-04:00Alexandre MinotSaveExtractsUsingCatalystOptions does not replace {timestep:06d} correctlyIf I specify a filename using `pNG1.Writer.FileName = 'image_{timestep:06d}.png'` then `SaveExtractsUsingCatalystOptions(options)` replaces {timestep:06d} by 000000 no matter what the time step is.If I specify a filename using `pNG1.Writer.FileName = 'image_{timestep:06d}.png'` then `SaveExtractsUsingCatalystOptions(options)` replaces {timestep:06d} by 000000 no matter what the time step is.https://gitlab.kitware.com/paraview/paraview/-/issues/22109Provide option to disable automatic extractions when catalyst_execute is called2023-11-08T21:12:52-05:00Alexandre MinotProvide option to disable automatic extractions when catalyst_execute is calledTake the following python code from a possible ParaView Catalyst user script:
```
def catalyst_execute(info):
SaveExtractsUsingCatalystOptions(options)
```
This script will have extractors triggered twice. Once by the `SaveExtracts...Take the following python code from a possible ParaView Catalyst user script:
```
def catalyst_execute(info):
SaveExtractsUsingCatalystOptions(options)
```
This script will have extractors triggered twice. Once by the `SaveExtractsUsingCatalystOptions(options)` call, and once automatically by `internals.ExtractsController->Extract(internals.Extractors);` from `bool vtkCPPythonScriptV2Helper::CatalystExecute()`.
Could an option be provided to disable the second extract?
A bit of background as to why a user might want to manually trigger extractions. I my case, I use a for loop inside `def catalyst_execute` to show / save / hide objects in a single renderView. After my for loop, I get an unwanted write from the `internals.ExtractsController->Extract(internals.Extractors)`.
Many thanks,
Alexandrehttps://gitlab.kitware.com/paraview/paraview/-/issues/21856Link Objects: does not work correctly for Render Views2023-06-15T08:11:24-04:00Julien FaustyLink Objects: does not work correctly for Render Views## Problem statement
When using the "Link Manager" to link objects in ParaView, one can link two filters, sources or representations together (i.e. link all their properties) but you cannot do the same thing for "Render Views". The link...## Problem statement
When using the "Link Manager" to link objects in ParaView, one can link two filters, sources or representations together (i.e. link all their properties) but you cannot do the same thing for "Render Views". The link manager shows an `Unknown` entry in properties:
![image](/uploads/3bd9a13fb42d336b20608ebad026f7ad/image.png)
This link between "Render Views" links the cameras of the two views without linking any of their properties.https://gitlab.kitware.com/paraview/paraview/-/issues/21854Crash on volume rendering when attempting to use separate color maps (ParaVie...2023-06-01T05:36:57-04:00jgrimeCrash on volume rendering when attempting to use separate color maps (ParaView 5.11.0 under Windows 10 Enterprise)ParaView 5.11.0 crashes when rendering a trivial volume and trying to use a separate color map.
I've attached a simple .nrrd input file (generated in FIJI) to illustrate the issue. Load the .nrrd file, set "Representation" to "Volume", ...ParaView 5.11.0 crashes when rendering a trivial volume and trying to use a separate color map.
I've attached a simple .nrrd input file (generated in FIJI) to illustrate the issue. Load the .nrrd file, set "Representation" to "Volume", then click on the "Use Separate Color Map" button. Boom, crash.
This happens on both my desktop workstation, and my laptop (both running ParaView 5.11.0).
[HyperStack.nrrd](/uploads/63f1fe1ddba48c9eeea0f9989b1c6070/HyperStack.nrrd)https://gitlab.kitware.com/paraview/paraview/-/issues/21853Paraview 5.11 seems to be incompatible with FLuent .case and .dat2023-04-23T04:32:50-04:00Tao ZhangParaview 5.11 seems to be incompatible with FLuent .case and .datHi, I'm a Ph.D. student studying mechanical engineering. Most of my research work is related to CFD conducted on the AnsysFLuent platform. I've been trying to use Paraview as the post-processing tool, but unfortunately, Paraview always b...Hi, I'm a Ph.D. student studying mechanical engineering. Most of my research work is related to CFD conducted on the AnsysFLuent platform. I've been trying to use Paraview as the post-processing tool, but unfortunately, Paraview always breaks down when I read fluent .case and .dat files. I'm not sure what is the problem. Maybe Paraview doesn't support hex-poly mesh or something else. I am wondering if there is some other way to fix this issue. Looking forward to hearing from your technical staff.https://gitlab.kitware.com/paraview/paraview/-/issues/21851OpenGL errors while running Demo1 and Demo2 custom application on Mac2023-04-23T04:32:55-04:00Muhammad Saad AtiqueOpenGL errors while running Demo1 and Demo2 custom application on MacI can build Demo0, Clone1 and Clone2. But when building Demo1 and Demo2 I get these errors:
```
( 2.505s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b448c4d0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2....I can build Demo0, Clone1 and Clone2. But when building Demo1 and Demo2 I get these errors:
```
( 2.505s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b448c4d0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.505s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b108b000): Could not set shader program
( 2.505s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b108b000): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.506s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b5004ed0):
( 2.509s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b5004ed0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.509s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c000): Could not set shader program
( 2.509s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c000): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.510s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b448c4d0):
( 2.510s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b448c4d0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.510s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c600): Could not set shader program
( 2.510s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c600): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.512s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b448c4d0):
( 2.513s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b448c4d0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.513s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b108b600): Could not set shader program
( 2.513s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b108b600): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.514s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b5004ed0):
( 2.515s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b5004ed0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.516s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c000): Could not set shader program
( 2.516s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c000): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.517s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b448c4d0):
( 2.518s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b448c4d0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.519s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c600): Could not set shader program
( 2.519s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b208c600): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.520s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b448c4d0):
( 2.521s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b448c4d0): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.521s) [paraview ]vtkOpenGLPolyDataMapper:2581 ERR| vtkOpenGLPolyDataMapper (0x7fb8b1072200): Could not set shader program
( 2.521s) [paraview ]vtkOpenGLPolyDataMapper:2593 ERR| vtkOpenGLPolyDataMapper (0x7fb8b1072200): failed after UpdateShader 1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.554s) [paraview ] vtkOpenGLState.cxx:930 WARN| Error glActiveTexture1 OpenGL errors detected
( 2.581s) [paraview ] vtkOpenGLState.cxx:930 WARN| Error glActiveTexture1 OpenGL errors detected
0 : (1282) Invalid operation
( 2.590s) [paraview ] vtkShaderProgram.cxx:438 ERR| vtkShaderProgram (0x7fb8b42b6d60): ( 2.590s) [paraview ] vtkShaderProgram.cxx:439 ERR| vtkShaderProgram (0x7fb8b42b6d60): ERROR: 0:1: ‘’ : version ‘150’ is not supported
( 2.590s) [paraview ]vtkOpenGLVertexArrayObj:266 ERR| vtkOpenGLVertexArrayObject (0x7fb8b42b6fc0): attempt to add attribute without a program for attribute ndCoordIn
( 2.590s) [paraview ]vtkOpenGLQuadHelper.cxx:71 WARN| Error binding ndCoords to VAO.
vtkMemberFunctionCommand::Execute(vtkObject*, unsigned long, void*) + 288
( 2.590s) [paraview ] :0 FATL| Signal: SIGSEGV
[1] 38231 segmentation fault ./DemoApp1
```https://gitlab.kitware.com/paraview/paraview/-/issues/21848Unstructured Grid Volume Rendering with OSPRay is almost transparent2023-04-23T04:33:01-04:00lkalyUnstructured Grid Volume Rendering with OSPRay is almost transparentSee here for more info:
https://discourse.paraview.org/t/how-to-render-a-model-with-material-and-data-volume-render-at-the-same-time/11725/8
Problem: when I use the volume rendering and OSPRay, the data will disappear.
![image](/uploa...See here for more info:
https://discourse.paraview.org/t/how-to-render-a-model-with-material-and-data-volume-render-at-the-same-time/11725/8
Problem: when I use the volume rendering and OSPRay, the data will disappear.
![image](/uploads/31a61ff38ab14812bf574a2f05d6281b/image.png)
[test.vtk](/uploads/01f970951041420252c0cf704a04e397/test.vtk)
Answer form Kenneth Moreland:
It looks like when ParaView uses the projected tetrahedra method for volume rendering (the default for unstructured data like [test.vtk]([test.vtk](/uploads/01f970951041420252c0cf704a04e397/test.vtk))) the OSPray render is rendering the volume much more transparent than OpenGL. I don’t know why, but there are a couple things you can do to correct it.
One thing you can do is to change the volume rendering mapper from Projected tetrahedra to `Resample To Image`. The image volume rendering seems equivalent between OSPray and OpenGL. You may have to play with the sampling dimensions to get a good image.
![image](/uploads/aa277f4545049a2acba97161affbadb2/image.png)
If you need the details of the unstructured grid and must render it directly, you can alternately lower the `Scalar Opacity Unit Distance` parameter. (I don’t know why OSPray is interpreting this parameter differently than OpenGL. This might be related to [bug #18890](https://gitlab.kitware.com/paraview/paraview/-/issues/18890), but I’m not sure.) If you crank that value down to 0.1, I can see the middle (opaque) part of the volume clearly. That said, the results look very speckled. OSPRay must be using some kind of trapdoor transparency for rendering. You can correct that by increasing the `Progressive Passes` and/or `Samples Per Pixel` parameters for OSPRay. That will increase the rendering time though.
![image](/uploads/597e271f5faccb3f32f7f0f1177c1e4e/image.png)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 Tsalikishttps://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/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/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/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/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/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/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/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/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/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/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/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. -> Crash