ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2022-01-12T04:49:49-05:00https://gitlab.kitware.com/paraview/paraview/-/issues/21166Display artefact depending on fields in the file2022-01-12T04:49:49-05:00Fredrik EkreDisplay artefact depending on fields in the fileCopied from [this discourse post](https://discourse.paraview.org/t/display-artefact-depending-on-fields-in-the-file/6998), as suggested.
---
I ran into a strange display artifact where some fields display incorrectly. I attach two file...Copied from [this discourse post](https://discourse.paraview.org/t/display-artefact-depending-on-fields-in-the-file/6998), as suggested.
---
I ran into a strange display artifact where some fields display incorrectly. I attach two files: [`bad.vtu`](https://discourse.paraview.org/uploads/short-url/so8sMey7StpFbQwkPbT9EGesz8f.vtu) (partly broken) and [`good.vtu`](https://discourse.paraview.org/uploads/short-url/1t60QdPCgtm4F9XpII0pXrL7TmF.vtu) which works as expected.
The difference between the files is that `bad.vtu` has an additional field `u` which is not in the `good.vtu` file. The existence of this field breaks visualization of _some but not all other fields_ in the file, see screenshots.
##### good.vtu, second field (Visco-plastic strain 11 mode: 2)
![good](/uploads/98e8f00e8a2464e1f749fb73d941e7dc/good.png)
##### bad.vtu, second field (Visco-plastic strain 11 mode: 2)
Note in particular that the first field still displays correctly (not included as a screenshot).
![bad](/uploads/4a6e43a3b3d90de1a0d7c7566413afce/bad.png)
##### bad.vtu, second field (Visco-plastic strain 11 mode: 2) with field u deactivated
Note that the u field is deactivated, which "fixes" the display.
![bad-deactivate-u](/uploads/44f9de1bedcecb68997c5daeef3682dc/bad-deactivate-u.jpg)
What could be the problem here? Is the file misformed?
I thought it might be some scaling issue or similar, but there is only a factor of 100 between the fields, and it is strange it only happens with some fields.
I discovered this first in ParaView 5.9.0, and just confirmed it still happens in ParaView 5.10.0. Have not tried earlier versions.https://gitlab.kitware.com/paraview/paraview/-/issues/21128Fields in "Properties" panel are unnecessarily wide, making the UI difficult ...2022-07-20T19:34:53-04:00Amin SadeghiFields in "Properties" panel are unnecessarily wide, making the UI difficult to work withOS: Ubuntu 20.04.3 LTS
ParaView Version: 5.10.0-RC1
Qt Version: 5.12.9
---
The data fields in the "Properties" panel are unnecessarily wide, thus making the panel "scrollable", which makes it difficult to work with the UI (either I nee...OS: Ubuntu 20.04.3 LTS
ParaView Version: 5.10.0-RC1
Qt Version: 5.12.9
---
The data fields in the "Properties" panel are unnecessarily wide, thus making the panel "scrollable", which makes it difficult to work with the UI (either I need to scroll every now and then), or resize the "Properties" panel to the point that makes the scroll bars go away, in which case it takes an unnecessarily huge portion of the screen.
Btw, I have a 4k monitor, in case it's relevant to the issue I'm reporting.
Thank you so much!
# ParaView's default "Properties" width
![image](/uploads/fd8c2103d32a361f63eb281e10f39a93/image.png)
# Expanding "Properties" panel to get rid of scroll bars
![image](/uploads/cda9ae4dfbf12a10e311ec643a8303b0/image.png)https://gitlab.kitware.com/paraview/paraview/-/issues/21047Widget handle-placement picking is unreliable2022-08-04T08:05:05-04:00David ThompsonWidget handle-placement picking is unreliableWhen using picking to place a widget handle (such as and endpoint of the line source), the point is frequently misplaced and not on the surface of an object.
To reproduce:
1. Create a Box source
2. Create a Line source
3. Use the `1` an...When using picking to place a widget handle (such as and endpoint of the line source), the point is frequently misplaced and not on the surface of an object.
To reproduce:
1. Create a Box source
2. Create a Line source
3. Use the `1` and `2` keys to place the line endpoints on the box.
4. Move the mouse to a new location on the box (neither existing endpoint) and press the `1` key repeatedly without moving the mouse. You can see in both the 2-D and 3-D view that the picked point moves significantly along the line underneath the mouse. Often, the endpoint handle ping-pongs between the correct point on the surface of the box and a point on no surface.
May be related to #14506 ?https://gitlab.kitware.com/paraview/paraview/-/issues/21038New ExtractBlock Causes UI Issues2024-03-07T20:23:46-05:00Theodore BaltisNew ExtractBlock Causes UI IssuesDiscovered in 5.10.0-RC1 (Windows MPI exe)
With the new ExtractBlock filter in the pipeline (anywhere), when changing the timestate the currently selected filter acts as if its properties have been updated. The text becomes bold and the...Discovered in 5.10.0-RC1 (Windows MPI exe)
With the new ExtractBlock filter in the pipeline (anywhere), when changing the timestate the currently selected filter acts as if its properties have been updated. The text becomes bold and the "Apply" button pops up. The data doesn't actually seem to reset or change in anyway, appears to only be a bug in the UI.
Steps to reproduce:
1. Load can.ex2
2. Add ExtractBlock and make a selection
3. Add Clip (or any other filter) to ExtractBlock
4. Change timestate and look at the currently highlighted filter in the pipeline
5. Change your pipeline (change input of the Clip to can.ex2, add another filter, etc.) and repeat.
6. Click other filters/sources and repeat5.13 (Summer 2024)Spiros TsalikisSpiros Tsalikishttps://gitlab.kitware.com/paraview/paraview/-/issues/21030Paraview5.9 can not visualize the FVCOM netcdf file using the VisItNetCDFFVCO...2021-10-14T05:07:40-04:00site291Paraview5.9 can not visualize the FVCOM netcdf file using the VisItNetCDFFVCOM_MTSDReaderI can load the FVCOM netcdf file using the VisItNetCDFFVCOM_MTSDReader, but when I click the apply button, I can not get anything. While I use the Paraview5.6.2, I can get the figure. I can only load this data, but the paraview can not r...I can load the FVCOM netcdf file using the VisItNetCDFFVCOM_MTSDReader, but when I click the apply button, I can not get anything. While I use the Paraview5.6.2, I can get the figure. I can only load this data, but the paraview can not render it while I apply it.[](https://discourse.paraview.org/t/display-of-fvcom-data-broken-in-recent-nightlies/1896/8?u=sitepan)https://gitlab.kitware.com/paraview/paraview/-/issues/20999MaterialEditor: Compilation error when enabling/disabling it after first conf...2023-10-19T11:13:23-04:00Paul LafoixMaterialEditor: Compilation error when enabling/disabling it after first configureWhen changing the value of `PARAVIEW_ENABLE_RAYTRACING` or `VTK_ENABLE_OSPRAY` the material editor is activated / deactivated. The linking step of the compilation then fails and we must touch the `Qt/ApplicationComponents/CMakeLists.txt`...When changing the value of `PARAVIEW_ENABLE_RAYTRACING` or `VTK_ENABLE_OSPRAY` the material editor is activated / deactivated. The linking step of the compilation then fails and we must touch the `Qt/ApplicationComponents/CMakeLists.txt` to regenerate the automatic_moc and to link successfully
[A closed MR](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5235) tried to resolve this issue but without successhttps://gitlab.kitware.com/paraview/paraview/-/issues/20951XDMF reader produces error "vtkImageSliceRepresentation(0x19ffe1f0) is of typ...2021-09-10T09:12:06-04:00baloeXDMF reader produces error "vtkImageSliceRepresentation(0x19ffe1f0) is of type vtkRectilinearGrid, but a vtkImageData is required"When loading state files where an xmf-file is referenced I keep getting the error message
```
vtkDemandDrivenPipeline:760 ERR| vtkPVDataRepresentationPipeline (0x1a96d3c0): Input for connection index 0 on input port index 0 for algor...When loading state files where an xmf-file is referenced I keep getting the error message
```
vtkDemandDrivenPipeline:760 ERR| vtkPVDataRepresentationPipeline (0x1a96d3c0): Input for connection index 0 on input port index 0 for algorithm vtkImageSliceRepresentation(0x19ffe1f0) is of type vtkRectilinearGrid, but a vtkImageData is required.
```
Even without ever creating anything other than the xdmf.
It is really annoying, but at least everything still seems to functions right.https://gitlab.kitware.com/paraview/paraview/-/issues/20931data out of range using pvtr file2021-09-03T05:17:42-04:00Yann Fraigneaudata out of range using pvtr fileHi,
I have some problem with the latest versions of Paraview (from 5.8 at least) . When I load data from a pvtr file, data are out of range (-1E+38 , 1E+38). All is right when I directly load data from vtr files (files present in the pv...Hi,
I have some problem with the latest versions of Paraview (from 5.8 at least) . When I load data from a pvtr file, data are out of range (-1E+38 , 1E+38). All is right when I directly load data from vtr files (files present in the pvtr file, which are in binary format).
The problem occurs with different OS (MacOS, Linux).
Loading data from my .pvtr file works well with an oldest version of Paraview (5.0.1 64).
Please, could you help me to understand and solve this problem ?
Here you find a tar archive with every files required (res*.pvtr, res*vtr). They contain computational fluid dynamics data about a 2D flow around a heated cylinder (a snapshot of velocity and temperature fields split into 4 sbdomains).
[test_pvtr.tar](/uploads/afa315acef75db65828817923eaa174d/test_pvtr.tar)
Thank you for your help.https://gitlab.kitware.com/paraview/paraview/-/issues/20928Paraview crashes when opening vtk file2021-09-03T12:40:42-04:00Emily LParaview crashes when opening vtk fileI have a simplified wire frame bridge model that I am trying to visualize using Paraview. I am running Paraview 5.9.1 on Windows 10, and my file will try to open but then the system crashes. I attached my code below and a snip of how the...I have a simplified wire frame bridge model that I am trying to visualize using Paraview. I am running Paraview 5.9.1 on Windows 10, and my file will try to open but then the system crashes. I attached my code below and a snip of how the model should look with the node connections.
![image](/uploads/b5cd73cc3ad93ed683d3e383ff921baa/image.png)
[prototypebridge.vtk](/uploads/b5e78733bce9170d673068f4c2aaaa65/prototypebridge.vtk)https://gitlab.kitware.com/paraview/paraview/-/issues/20924Remote rendering/processing in PV 5.9.1 crashes on unconnected datasets2021-09-03T18:33:43-04:00Patrick KopperRemote rendering/processing in PV 5.9.1 crashes on unconnected datasetsLoading a `.vtu` dataset containing unconnected points/vertices above the Remote Rendering Threshold into a parallel `pvserver` and performing an action involving `GenerateCuts` crashes the server. I did not systematically test operation...Loading a `.vtu` dataset containing unconnected points/vertices above the Remote Rendering Threshold into a parallel `pvserver` and performing an action involving `GenerateCuts` crashes the server. I did not systematically test operations involving other VTK calls.
The same dataset is handled without issues when running `pvserver` in serial mode. Please also let me know if there is another workaround to avoid the `GenerateCuts` call.
**Tested in Paraview 5.9.1 (binary and source, both server and client). Server running either on CentOS 7.9 or Ubuntu 18.04.5, client running on Arch Linux 2021.09.01.** The same dataset is handled without issues on ParaView 5.6 and 5.8.
### Steps to reproduce
1. Start a parallel `pvserver` (preferably on 32+ cores) and connect a client
2. Set the Remote Render Threshold to `0` (or any value smaller than the geometry size)
3. Load the attached `.vtu` `vtkUnstructuredGrid`
4. Change the representation type to `Point Gaussian`
- Depending on the dataset and configuration, also filters (e.g. `Clip`) will crash
### Dataset
The attached dataset contains unconnected vertices in an `vtkUnstructuredGrid`. The same issue happens when writing the point cloud using `vtkPolyData`. [vtkUnstructuredGrid_Vertices.vtu](/uploads/7f43b467249cfe6c7a84af8030aaf476/vtkUnstructuredGrid_Vertices.vtu)
### Crash Log
```
Client connected.
terminate called after throwing an instance of 'std::runtime_error'
what(): -2147483648 -nan -0.0189998
Loguru caught a signal: SIGABRT
Stack trace:
32 0x401667 /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/pvserver-real() [0x401667]
31 0x2b05d2bba555 __libc_start_main + 245
30 0x4015b0 /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/pvserver-real() [0x4015b0]
29 0x2b05d51820b2 vtkTCPNetworkAccessManager::ProcessEventsInternal(unsigned long, bool) + 690
28 0x2b05d61db475 vtkMultiProcessController::ProcessRMIs(int, int) + 597
27 0x2b05d61dad13 vtkMultiProcessController::ProcessRMI(int, void*, int, int) + 291
26 0x2b05d483e4a0 vtkPVSessionServer::OnClientServerMessageRMI(void*, int) + 272
25 0x2b05d48342e5 vtkPVSessionBase::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 53
24 0x2b05d48352bb vtkPVSessionCore::ExecuteStream(unsigned int, vtkClientServerStream const&, bool) + 59
23 0x2b05d4835482 vtkPVSessionCore::ExecuteStreamInternal(vtkClientServerStream const&, bool) + 242
22 0x2b05d55c8ddd vtkClientServerInterpreter::ProcessStream(vtkClientServerStream const&) + 29
21 0x2b05d55c8b3e vtkClientServerInterpreter::ProcessOneMessage(vtkClientServerStream const&, int) + 1294
20 0x2b05d55c840d vtkClientServerInterpreter::ProcessCommandInvoke(vtkClientServerStream const&, int) + 1229
19 0x2b05d55c7da9 vtkClientServerInterpreter::CallCommandFunction(char const*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&) + 345
18 0x2b05d32e65d8 vtkPVRenderViewCommand(vtkClientServerInterpreter*, vtkObjectBase*, char const*, vtkClientServerStream const&, vtkClientServerStream&, void*) + 8312
17 0x2b05dab38bf1 vtkPVRenderView::StillRender() + 97
16 0x2b05dab44503 vtkPVRenderView::Render(bool, bool) + 659
15 0x2b05dab498a2 vtkPVRenderViewDataDeliveryManager::RedistributeDataForOrderedCompositing(bool) + 4850
14 0x2b05ea9ff090 vtkDIYKdTreeUtilities::GenerateCuts(std::vector<vtkDataObject*> const&, int, bool, vtkMultiProcessController*, double const*) + 512
13 0x2b05ea9fd153 vtkDIYKdTreeUtilities::GenerateCuts(std::vector<vtkSmartPointer<vtkPoints>, std::allocator<vtkSmartPointer<vtkPoints> > > const&, int, vtkMultiProcessController*, double const*) + 3699
12 0x2b05ea9fbd44 /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/../lib/libvtkFiltersParallelDIY2-pv5.9.so.1(+0x2ad44) [0x2b05ea9fbd44]
11 0x2b05eaa2475b /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/../lib/libvtkFiltersParallelDIY2-pv5.9.so.1(+0x5375b) [0x2b05eaa2475b]
10 0x2b05eaa10814 /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/../lib/libvtkFiltersParallelDIY2-pv5.9.so.1(+0x3f814) [0x2b05eaa10814]
9 0x2b05ea9ef96f /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/../lib/libvtkFiltersParallelDIY2-pv5.9.so.1(+0x1e96f) [0x2b05ea9ef96f]
8 0x2b05ea9f5690 /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/../lib/libvtkFiltersParallelDIY2-pv5.9.so.1(+0x24690) [0x2b05ea9f5690]
7 0x2b05ea9fb291 /apps/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/bin/../lib/../lib/libvtkFiltersParallelDIY2-pv5.9.so.1(+0x2a291) [0x2b05ea9fb291]
6 0x2b05d8adcc53 /lib64/libstdc++.so.6(+0x5ec53) [0x2b05d8adcc53]
5 0x2b05d8adca33 /lib64/libstdc++.so.6(+0x5ea33) [0x2b05d8adca33]
4 0x2b05d8adca06 /lib64/libstdc++.so.6(+0x5ea06) [0x2b05d8adca06]
3 0x2b05d8adea95 __gnu_cxx::__verbose_terminate_handler() + 357
2 0x2b05d2bcfa78 abort + 328
1 0x2b05d2bce387 gsignal + 55
0 0x2b05d2bce400 /lib64/libc.so.6(+0x36400) [0x2b05d2bce400]
( 76.248s) [pvserver.0 ] :0 FATL| Signal: SIGABRT
( 76.298s) [pvserver.8 ] vtkMPICommunicator.cxx:68 WARN| MPI had an error
------------------------------------------------
Unknown error class, error stack:
PMPI_Iprobe(123)..........................: MPI_Iprobe(src=MPI_ANY_SOURCE, tag=0, comm=0x84000004, flag=0x7ffc7fa0a1c0, status=0x7ffc7fa0a230) failed
MPIDI_CH3i_Progress_test(114).............: an error occurred while handling an event returned by MPIDI_CH3I_Sock_Wait()
MPIDI_CH3I_Progress_handle_sock_event(479):
MPIDI_CH3I_Socki_handle_read(4014)........: connection failure (set=0,sock=4,errno=104:Connection reset by peer)
------------------------------------------------
application called MPI_Abort(comm=0x84000004, 203011159) - process 8
```https://gitlab.kitware.com/paraview/paraview/-/issues/20732Selection in ColumnBasedSelection chart with multiple sources behave incorrectly2021-05-21T06:21:34-04:00Mathieu Westphal (Kitware)Selection in ColumnBasedSelection chart with multiple sources behave incorrectlyWhen selecting a line in a column based selection chart, ParaView behave incorrectly which provide unexpected results.
Steps to reproduce:
- Run ParaView
- Load BagPlotAndViewsFilters plugin (only ColumnBasedSelection chart in native p...When selecting a line in a column based selection chart, ParaView behave incorrectly which provide unexpected results.
Steps to reproduce:
- Run ParaView
- Load BagPlotAndViewsFilters plugin (only ColumnBasedSelection chart in native paraview)
- Open [sineWaves.csv](/uploads/e82ffdde581e0783b7f627f94c92a807/sineWaves.csv), Apply
- Filters -> ExtractBagPlots -> Apply
- Filters -> PassArray, select only y11, Apply
- click on ExtractBagPlots in pipeline browser to make it active
- Filters -> PassArray, select only y12, Apply
- In a functionnalBagChartView, show only PassArrays1 and PassArrays2
- in PassArrays1, show y11
- in PassArrays2, show y12
- Select ExtractBagPlots as active source in pipeline browser
- Create an empty selection using rectangle selection
- PassArrays2 is selected, **unexpected**
- Select ExtractBagPlots as active source in pipeline browser
- Create a selection of y11 using rectangle selection
- PassArrays2 become active and a y12 appears selected, **unexpected**
- in PassArrays2, hide y12
- repeat selection steps, behavior is the same, **still unexpected**
- in Pipelinebroswer, hide PasseArrays2
- Create an empty selection using rectangle selection
- PassArrays1 is selected, **unexpected**
- Select ExtractBagPlots as active source in pipeline browser
- Create a selection of y11 using rectangle selection
- PassArrays1 become active and a y11 appears selected, **expected**
All this behavior is caused by a "non-selecting" loop in pqContextView::setSelection, where the last representation is considered to be selected, not the actual selected representation.
https://gitlab.kitware.com/paraview/paraview/-/blob/master/Qt/Core/pqContextView.cxx#L204
The selection failure of this issue may be related to functionnalBagPlot code specifically, but the active source change is not.https://gitlab.kitware.com/paraview/paraview/-/issues/20711FindData failure with NaN2024-03-07T20:23:45-05:00Jean M. FavreFindData failure with NaNParaView 5.9.1-RC2
if my data has some NaN values, FindData silently fails to find "data is max", "data is min", and prints error messages with "data is greater/less than mean"
```
/local/apps/ParaView/5.9.1/lib/python3.8/site-packages...ParaView 5.9.1-RC2
if my data has some NaN values, FindData silently fails to find "data is max", "data is min", and prints error messages with "data is greater/less than mean"
```
/local/apps/ParaView/5.9.1/lib/python3.8/site-packages/vtkmodules/numpy_interface/dataset_adapter.py:254: RuntimeWarning: invalid value encountered in greater_equal
return getattr(numpy.ndarray, attr_name)(l[0], l[1])
/local/apps/ParaView/5.9.1/lib/python3.8/site-packages/vtkmodules/numpy_interface/dataset_adapter.py:254: RuntimeWarning: invalid value encountered in less_equal
return getattr(numpy.ndarray, attr_name)(l[0], l[1])
```
the attached Python script sets up the data to test. Use FindData on the "result" scalar array.[pvFindDataIssue.py](/uploads/d790964d9a23342ea37049ddff3e4138/pvFindDataIssue.py)5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/20631PassArrays filter cannot remove arrays in field data associated with root nod...2023-08-01T04:54:48-04:00Utkarsh AyachitPassArrays filter cannot remove arrays in field data associated with root node for a composite dataset* Load [canvtm.tgz](/uploads/d563cf0f25d2c87bba85a1c446218c36/canvtm.tgz), all variables, Apply
* Apply **Pass Arrays**, uncheck **TimeValue**, Apply -- TimeValue will still be present in the output (verify by looking at the Information ...* Load [canvtm.tgz](/uploads/d563cf0f25d2c87bba85a1c446218c36/canvtm.tgz), all variables, Apply
* Apply **Pass Arrays**, uncheck **TimeValue**, Apply -- TimeValue will still be present in the output (verify by looking at the Information tab).
The issue is that vtkPassArrays does not process fielddata on non-leaf nodes. Hence it doesnt' touch the TimeValue array present on the root node.https://gitlab.kitware.com/paraview/paraview/-/issues/20598Volume rendering rectilinear grids can miss the top-most layer of cells2021-03-24T13:55:02-04:00Cory Quammencory.quammen@kitware.comVolume rendering rectilinear grids can miss the top-most layer of cellsWith the this [data set](https://gitlab.kitware.com/paraview/paraview/uploads/4f616f457e75c60473a4515005c059ff/geom.vtr), volume rendering misses the highest layer of grid cells.
![image](/uploads/795b6daa066188964c6bee49c440b4ce/image....With the this [data set](https://gitlab.kitware.com/paraview/paraview/uploads/4f616f457e75c60473a4515005c059ff/geom.vtr), volume rendering misses the highest layer of grid cells.
![image](/uploads/795b6daa066188964c6bee49c440b4ce/image.png)
Issue originally reported by @p.eisenlohr in #20364.
/cc @sankheshhttps://gitlab.kitware.com/paraview/paraview/-/issues/20573Animation Python track neither saved in python state, nor in Trace2023-05-24T08:11:52-04:00Nicolas VuailleAnimation Python track neither saved in python state, nor in TraceIn animation view, Python tracks are not saved in python state file and not tracked by the python trace.
- start Trace with `All Properties` and `Fully trace supplemental Proxies`
- Create a python track
- stop trace -> python track doe...In animation view, Python tracks are not saved in python state file and not tracked by the python trace.
- start Trace with `All Properties` and `Fully trace supplemental Proxies`
- Create a python track
- stop trace -> python track does not appears
- save as python state, with `All properties` and without `Skip` options -> python track does not appear
- save as pvsm -> python track is writtenhttps://gitlab.kitware.com/paraview/paraview/-/issues/20572glTFReader properties are not correctly set in parallel2021-03-24T09:43:04-04:00Mathieu Westphal (Kitware)glTFReader properties are not correctly set in parallelglTFReader properties are not correctly set in parallel
Steps to reproduce:
- mpirun -np 2 ./bin/pvserver &
- ./bin/paraview
- connect to localhost server
- open [InterpolationTest.glb](/uploads/0bee757165c33237e45a5f13f557e644/Interpo...glTFReader properties are not correctly set in parallel
Steps to reproduce:
- mpirun -np 2 ./bin/pvserver &
- ./bin/paraview
- connect to localhost server
- open [InterpolationTest.glb](/uploads/0bee757165c33237e45a5f13f557e644/InterpolationTest.glb)
- check "Linear Translation" animation
- mode to time values 0.5
- uncheck "Linear Translation" animation
- cube appears two times, one for each processor, one processor does not know that "Linear Translation" has been unchecked
![image](/uploads/e7ec22e5f421f6c3bb02e6aae0e20cd8/image.png)
This is a bit worrying as this behavior rely on information properties mechanism that are used in other places in ParaView.
FYI @utkarsh.ayachit @michael.migliore @adrien.boucaudhttps://gitlab.kitware.com/paraview/paraview/-/issues/20570python shell does not find proxies of plugins loaded after shell initialization2021-03-24T09:39:43-04:00Nicolas Vuaillepython shell does not find proxies of plugins loaded after shell initializationIf the python shell is initialized before loading plugins, the proxies from those plugins are not available from the python shell.
Steps:
- click in the python shell (so it executes `from paraview.simple import *`)
- load plugin ArrowGl...If the python shell is initialized before loading plugins, the proxies from those plugins are not available from the python shell.
Steps:
- click in the python shell (so it executes `from paraview.simple import *`)
- load plugin ArrowGlyphFilter
- in python shell:
```
>>> ArrowGlyphFilter()
NameError: name 'ArrowGlyphFilter' is not defined
```
But the filter is accessible and can be used correctly through the GUI.https://gitlab.kitware.com/paraview/paraview/-/issues/20566Programmable Filter CopyArrays parameter needs to be set before the first app...2021-03-24T09:40:10-04:00Mathieu Westphal (Kitware)Programmable Filter CopyArrays parameter needs to be set before the first apply to copy NormalsProgrammable Filter CopyArrays parameter needs to be set before the first apply to copy Normals, if not, Normals are not copied:
Steps to reproduce:
- run ParaView
- Sphere, Apply
- ProgrammableFilter, (copy arrays is not checked), Appl...Programmable Filter CopyArrays parameter needs to be set before the first apply to copy Normals, if not, Normals are not copied:
Steps to reproduce:
- run ParaView
- Sphere, Apply
- ProgrammableFilter, (copy arrays is not checked), Apply
- There is no data arrays and of course no normals visible on the output, expected
- Check copy arrays, Apply
- There is a "normals" array but the output does not have normals
Checking the CopyArrays before applying behave correctlyhttps://gitlab.kitware.com/paraview/paraview/-/issues/20565Line integral convolution (Surface-LIC): Vector normalization doesn't work co...2022-07-21T05:09:39-04:00Carsten ThorenzLine integral convolution (Surface-LIC): Vector normalization doesn't work correctlyDepending on the checkbox "Normalize Vectors", the length of the LIC-streaks should either be constant in all of the picture or depend on the vector magnitude.
This doesn't work, the checkbox has no influence on the LIC-streaks.
Repro...Depending on the checkbox "Normalize Vectors", the length of the LIC-streaks should either be constant in all of the picture or depend on the vector magnitude.
This doesn't work, the checkbox has no influence on the LIC-streaks.
Reproduce:
- Load plugin "SurfaceLIC"
- Load attached state file
- Toggle "Normalize Vectors" with no effect
(Tested with 5.8.1. It crashes on 5.9.0 for me on different machines!)
Best regards,
Carsten
[paraview_lic_test_581.pvsm](/uploads/4ea1d8f742c42bf9b982088b83d05656/paraview_lic_test_581.pvsm)https://gitlab.kitware.com/paraview/paraview/-/issues/20563Wrong tab information for HTG2023-01-03T12:08:12-05:00Yohann Bearzi (Kitware)Wrong tab information for HTGThe information tab for HTG has one wrong value (see screenshot below). `Number of Vertices` should not be 0. As a first guess, the problem could come from a wrongly initialized / updated attribute inside `vtkHyperTreeGrid`.
![image](/u...The information tab for HTG has one wrong value (see screenshot below). `Number of Vertices` should not be 0. As a first guess, the problem could come from a wrongly initialized / updated attribute inside `vtkHyperTreeGrid`.
![image](/uploads/519aa394154eba025fdba1207adb4097/image.png)
cc @patchett2002 @sebastien.jourdain @utkarsh.ayachit @mwestphal