ParaView issueshttps://gitlab.kitware.com/paraview/paraview/-/issues2021-03-23T18:43:47-04:00https://gitlab.kitware.com/paraview/paraview/-/issues/18292Threshold filter has no progress2021-03-23T18:43:47-04:00Utkarsh AyachitThreshold filter has no progressSteps:
1. Wavelet, set extent to (-128, 128, -128, 128, -128, 128), Apply
2. Threshold, Apply. -- no progress till the threshold is completed :(.Steps:
1. Wavelet, set extent to (-128, 128, -128, 128, -128, 128), Apply
2. Threshold, Apply. -- no progress till the threshold is completed :(.https://gitlab.kitware.com/paraview/paraview/-/issues/18304Coloring by "Solid Color" is not recorded by python trace2018-09-10T21:26:43-04:00Jeremias GonzalezColoring by "Solid Color" is not recorded by python traceColoring by "Solid Color" is not recorded by python trace.
Steps to reproduce :
* Run ParaView
* Source->Wavelet, Apply
* Color By "RTData"
* Representation "Surface"
* Tools -> Start Trace, Show incremental, ok
* Color By "Solid ...Coloring by "Solid Color" is not recorded by python trace.
Steps to reproduce :
* Run ParaView
* Source->Wavelet, Apply
* Color By "RTData"
* Representation "Surface"
* Tools -> Start Trace, Show incremental, ok
* Color By "Solid Color"
* No python code related to color by is recorded on the trace.
This was originally reported in my thread here: https://discourse.paraview.org/t/solid-color-option-not-recorded-in-trace/3255.6 (Fall 2018)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18311Connect() python method fails with a segfault in case of timeout2023-06-15T11:50:30-04:00Mathieu Westphal (Kitware)Connect() python method fails with a segfault in case of timeoutConnect() python method fails with a segfault in case of timeout
How to reproduce :
* Open ParaView
* View->python Shell, click on it
* Connect("localhost")
* wait 60s for the timeout
* segfaultConnect() python method fails with a segfault in case of timeout
How to reproduce :
* Open ParaView
* View->python Shell, click on it
* Connect("localhost")
* wait 60s for the timeout
* segfaulthttps://gitlab.kitware.com/paraview/paraview/-/issues/18337Extract Bag Plots hangs in parallel2021-03-23T18:54:10-04:00Cory Quammencory.quammen@kitware.comExtract Bag Plots hangs in parallel* Start pvserver with `mpiexec -np 3`
* Start client, connect to server
* Open `sineWaves.csv` from ParaView Data
* Apply the **Extract Bag Plots** filter. ParaView hangs.
The client is waiting to receive a response from the server. It ...* Start pvserver with `mpiexec -np 3`
* Start client, connect to server
* Open `sineWaves.csv` from ParaView Data
* Apply the **Extract Bag Plots** filter. ParaView hangs.
The client is waiting to receive a response from the server. It looks to be an MPI communication routine mismatch. Relevant portions of stack traces from the server processes are as follows:
**Process 1**
```
frame #0: 0x0000000112e57965 libopen-pal.20.dylib`opal_progress + 167
frame #1: 0x000000010f1f091d libmpi.20.dylib`ompi_request_default_wait_all + 178
frame #2: 0x000000010f259a88 libmpi.20.dylib`ompi_coll_base_barrier_intra_bruck + 216
frame #3: 0x000000010f1ff080 libmpi.20.dylib`MPI_Barrier + 170
frame #4: 0x0000000108424f58 libvtkParallelMPI-pv5.5.1.dylib`vtkMPICommunicatorDebugBarrier(handle=0x00007fdef3e1b220) + 24 at vtkMPICommunicator.cxx:39
frame #5: 0x0000000108425c80 libvtkParallelMPI-pv5.5.1.dylib`vtkMPICommunicator::AllGatherVoidArray(this=0x00007fdef3e1b920, sendBuffer=0x00007fff5b6e7fc0, recvBuffer=0x00007fdefd134360, length=1, type=6) + 48 at vtkMPICommunicator.cxx:1323
frame #6: 0x000000010d96a963 libvtkFiltersParallelStatistics-pv5.5.1.dylib`vtkCommunicator::AllGather(this=0x00007fdef3e1b920, sendBuffer=0x00007fff5b6e7fc0, recvBuffer=0x00007fdefd134360, length=1) + 83 at vtkCommunicator.h:767
frame #7: 0x000000010d993b29 libvtkFiltersParallelStatistics-pv5.5.1.dylib`vtkPMultiCorrelativeStatistics::GatherStatistics(curController=0x00007fdef3c29cb0, sparseCov=0x00007fdefaa6d340) + 633 at vtkPMultiCorrelativeStatistics.cxx:116
frame #8: 0x000000010d9a172a libvtkFiltersParallelStatistics-pv5.5.1.dylib`vtkPPCAStatistics::Learn(this=0x00007fdefaa59370, inData=0x00007fdefaa58450, inParameters=0x0000000000000000, outMeta=0x00007fdefaa64400) + 154 at vtkPPCAStatistics.cxx:80
frame #9: 0x0000000110d286ea libvtkFiltersStatistics-pv5.5.1.dylib`vtkStatisticsAlgorithm::RequestData(this=0x00007fdefaa59370, (null)=0x00007fdefaa5b490, inputVector=0x00007fdefaa5b6b0, outputVector=0x00007fdefaa5abe0) + 298 at vtkStatisticsAlgorithm.cxx:240
frame #10: 0x00000001087fd1da libvtkCommonExecutionModel-pv5.5.1.dylib`vtkTableAlgorithm::ProcessRequest(this=0x00007fdefaa59370, request=0x00007fdefaa5b490, inputVector=0x00007fdefaa5b6b0, outputVector=0x00007fdefaa5abe0) + 122 at vtkTableAlgorithm.cxx:58
frame #11: 0x000000010879d750 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkExecutive::CallAlgorithm(this=0x00007fdefaa5ac70, request=0x00007fdefaa5b490, direction=1, inInfo=0x00007fdefaa5b6b0, outInfo=0x00007fdefaa5abe0) + 176 at vtkExecutive.cxx:773
frame #12: 0x0000000108791a5d libvtkCommonExecutionModel-pv5.5.1.dylib`vtkDemandDrivenPipeline::ExecuteData(this=0x00007fdefaa5ac70, request=0x00007fdefaa5b490, inInfo=0x00007fdefaa5b6b0, outInfo=0x00007fdefaa5abe0) + 141 at vtkDemandDrivenPipeline.cxx:490
frame #13: 0x0000000108782cb0 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkCompositeDataPipeline::ExecuteData(this=0x00007fdefaa5ac70, request=0x00007fdefaa5b490, inInfoVec=0x00007fdefaa5b6b0, outInfoVec=0x00007fdefaa5abe0) + 2032 at vtkCompositeDataPipeline.cxx:171
frame #14: 0x0000000108790d6f libvtkCommonExecutionModel-pv5.5.1.dylib`vtkDemandDrivenPipeline::ProcessRequest(this=0x00007fdefaa5ac70, request=0x00007fdefaa5b490, inInfoVec=0x00007fdefaa5b6b0, outInfoVec=0x00007fdefaa5abe0) + 1359 at vtkDemandDrivenPipeline.cxx:273
frame #15: 0x00000001087f5872 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkStreamingDemandDrivenPipeline::ProcessRequest(this=0x00007fdefaa5ac70, request=0x00007fdefaa5b490, inInfoVec=0x00007fdefaa5b6b0, outInfoVec=0x00007fdefaa5abe0) + 2834 at vtkStreamingDemandDrivenPipeline.cxx:328
frame #16: 0x0000000108791837 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkDemandDrivenPipeline::UpdateData(this=0x00007fdefaa5ac70, outputPort=0) + 1175 at vtkDemandDrivenPipeline.cxx:440
frame #17: 0x00000001087f5c58 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkStreamingDemandDrivenPipeline::Update(this=0x00007fdefaa5ac70, port=0, requests=0x0000000000000000) + 424 at vtkStreamingDemandDrivenPipeline.cxx:403
frame #18: 0x00000001087f5aa6 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkStreamingDemandDrivenPipeline::Update(this=0x00007fdefaa5ac70, port=0) + 38 at vtkStreamingDemandDrivenPipeline.cxx:365
frame #19: 0x00000001087765b2 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkAlgorithm::Update(this=0x00007fdefaa59370, port=0) + 50 at vtkAlgorithm.cxx:1456
frame #20: 0x0000000108776578 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkAlgorithm::Update(this=0x00007fdefaa59370) + 72 at vtkAlgorithm.cxx:1450
frame #21: 0x000000010d206f16 libvtkPVVTKExtensionsDefault-pv5.5.1.dylib`vtkPSciVizPCAStats::LearnAndDerive(this=0x00007fdefaa4dc30, modelDO=0x00007fdefaa57d50, inData=0x00007fdefaa58450) + 326 at vtkPSciVizPCAStats.cxx:55
frame #22: 0x000000010d2d1379 libvtkPVVTKExtensionsDefault-pv5.5.1.dylib`vtkSciVizStatistics::RequestData(this=0x00007fdefaa4dc30, outData=0x00007fdefaa58030, outModel=0x00007fdefaa57d50, inData=0x00007fdef3d7d8b0, inModel=0x0000000000000000) + 2553 at vtkSciVizStatistics.cxx:461
frame #23: 0x000000010d2cfb26 libvtkPVVTKExtensionsDefault-pv5.5.1.dylib`vtkSciVizStatistics::RequestData(this=0x00007fdefaa4dc30, (null)=0x00007fdefaa4f6f0, input=0x00007fdefaa4f980, output=0x00007fdefaa4ef10) + 1638 at vtkSciVizStatistics.cxx:290
frame #24: 0x00000001087fd1da libvtkCommonExecutionModel-pv5.5.1.dylib`vtkTableAlgorithm::ProcessRequest(this=0x00007fdefaa4dc30, request=0x00007fdefaa4f6f0, inputVector=0x00007fdefaa4f980, outputVector=0x00007fdefaa4ef10) + 122 at vtkTableAlgorithm.cxx:58
frame #25: 0x000000010d2cf165 libvtkPVVTKExtensionsDefault-pv5.5.1.dylib`vtkSciVizStatistics::ProcessRequest(this=0x00007fdefaa4dc30, request=0x00007fdefaa4f6f0, input=0x00007fdefaa4f980, output=0x00007fdefaa4ef10) + 165 at vtkSciVizStatistics.cxx:160
frame #26: 0x000000010879d750 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkExecutive::CallAlgorithm(this=0x00007fdefaa4ee20, request=0x00007fdefaa4f6f0, direction=1, inInfo=0x00007fdefaa4f980, outInfo=0x00007fdefaa4ef10) + 176 at vtkExecutive.cxx:773
frame #27: 0x0000000108791a5d libvtkCommonExecutionModel-pv5.5.1.dylib`vtkDemandDrivenPipeline::ExecuteData(this=0x00007fdefaa4ee20, request=0x00007fdefaa4f6f0, inInfo=0x00007fdefaa4f980, outInfo=0x00007fdefaa4ef10) + 141 at vtkDemandDrivenPipeline.cxx:490
frame #28: 0x0000000108782cb0 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkCompositeDataPipeline::ExecuteData(this=0x00007fdefaa4ee20, request=0x00007fdefaa4f6f0, inInfoVec=0x00007fdefaa4f980, outInfoVec=0x00007fdefaa4ef10) + 2032 at vtkCompositeDataPipeline.cxx:171
frame #29: 0x0000000108790d6f libvtkCommonExecutionModel-pv5.5.1.dylib`vtkDemandDrivenPipeline::ProcessRequest(this=0x00007fdefaa4ee20, request=0x00007fdefaa4f6f0, inInfoVec=0x00007fdefaa4f980, outInfoVec=0x00007fdefaa4ef10) + 1359 at vtkDemandDrivenPipeline.cxx:273
frame #30: 0x00000001087f5872 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkStreamingDemandDrivenPipeline::ProcessRequest(this=0x00007fdefaa4ee20, request=0x00007fdefaa4f6f0, inInfoVec=0x00007fdefaa4f980, outInfoVec=0x00007fdefaa4ef10) + 2834 at vtkStreamingDemandDrivenPipeline.cxx:328
frame #31: 0x0000000108791837 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkDemandDrivenPipeline::UpdateData(this=0x00007fdefaa4ee20, outputPort=0) + 1175 at vtkDemandDrivenPipeline.cxx:440
frame #32: 0x00000001087f5c58 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkStreamingDemandDrivenPipeline::Update(this=0x00007fdefaa4ee20, port=0, requests=0x0000000000000000) + 424 at vtkStreamingDemandDrivenPipeline.cxx:403
frame #33: 0x00000001087f5aa6 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkStreamingDemandDrivenPipeline::Update(this=0x00007fdefaa4ee20, port=0) + 38 at vtkStreamingDemandDrivenPipeline.cxx:365
frame #34: 0x00000001087765b2 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkAlgorithm::Update(this=0x00007fdefaa4dc30, port=0) + 50 at vtkAlgorithm.cxx:1456
frame #35: 0x0000000108776578 libvtkCommonExecutionModel-pv5.5.1.dylib`vtkAlgorithm::Update(this=0x00007fdefaa4dc30) + 72 at vtkAlgorithm.cxx:1450
frame #36: 0x000000010d255aa1 libvtkPVVTKExtensionsDefault-pv5.5.1.dylib`vtkPVExtractBagPlots::RequestData(this=0x00007fdefaa11040, (null)=0x00007fdef7bd4e90, inputVector=0x00007fdefaa1c5a0, outputVector=0x00007fdefaa17a60) + 2673 at vtkPVExtractBagPlots.cxx:270
```
**Process 2**
```
frame #0: 0x0000000119030561 mca_btl_vader.so`mca_btl_vader_component_progress + 60
frame #1: 0x0000000115e469d8 libopen-pal.20.dylib`opal_progress + 282
frame #2: 0x00000001121ed91d libmpi.20.dylib`ompi_request_default_wait_all + 178
frame #3: 0x0000000112256a88 libmpi.20.dylib`ompi_coll_base_barrier_intra_bruck + 216
frame #4: 0x00000001121fc080 libmpi.20.dylib`MPI_Barrier + 170
frame #5: 0x000000010b405f58 libvtkParallelMPI-pv5.5.1.dylib`vtkMPICommunicatorDebugBarrier(handle=0x00007f9f1da00290) + 24 at vtkMPICommunicator.cxx:39
frame #6: 0x000000010b405ecf libvtkParallelMPI-pv5.5.1.dylib`vtkMPICommunicator::BroadcastVoidArray(this=0x00007f9f1da00220, data=0x00007fff58702c20, length=128, type=6, root=0) + 47 at vtkMPICommunicator.cxx:1157
frame #7: 0x000000010b44a56a libvtkParallelCore-pv5.5.1.dylib`vtkCommunicator::Broadcast(this=0x00007f9f1da00220, data=0x00007fff58702c20, length=128, srcProcessId=0) + 90 at vtkCommunicator.h:309
frame #8: 0x000000010b45d87a libvtkParallelCore-pv5.5.1.dylib`vtkMultiProcessController::BroadcastProcessRMIs(this=0x00007f9f1d81bec0, (null)=1, dont_loop=0) + 138 at vtkMultiProcessController.cxx:521
frame #9: 0x000000010b45dffc libvtkParallelCore-pv5.5.1.dylib`vtkMultiProcessController::ProcessRMIs(this=0x00007f9f1d81bec0, reportErrors=1, dont_loop=0) + 92 at vtkMultiProcessController.cxx:648
frame #10: 0x000000010b45df8c libvtkParallelCore-pv5.5.1.dylib`vtkMultiProcessController::ProcessRMIs(this=0x00007f9f1d81bec0) + 28 at vtkMultiProcessController.cxx:640
frame #11: 0x0000000107506eab pvserver`RealMain(argc=1, argv=0x00007fff58703438, type=PROCESS_SERVER) + 827 at pvserver_common.h:95
frame #12: 0x0000000107506b57 pvserver`main(argc=1, argv=0x00007fff58703438) + 39 at pvserver.cxx:27
frame #13: 0x00007fff935ee5ad libdyld.dylib`start + 1
frame #14: 0x00007fff935ee5ad libdyld.dylib`start + 1
```
**Process 3**
```
frame #0: 0x00007fff8cf7d356 libsystem_kernel.dylib`mach_absolute_time + 35
frame #1: 0x000000011e0a78da libopen-pal.20.dylib`opal_progress + 28
frame #2: 0x000000011a46291d libmpi.20.dylib`ompi_request_default_wait_all + 178
frame #3: 0x000000011a4cba88 libmpi.20.dylib`ompi_coll_base_barrier_intra_bruck + 216
frame #4: 0x000000011a471080 libmpi.20.dylib`MPI_Barrier + 170
frame #5: 0x000000011367ff58 libvtkParallelMPI-pv5.5.1.dylib`vtkMPICommunicatorDebugBarrier(handle=0x00007fe1a4905240) + 24 at vtkMPICommunicator.cxx:39
frame #6: 0x000000011367fecf libvtkParallelMPI-pv5.5.1.dylib`vtkMPICommunicator::BroadcastVoidArray(this=0x00007fe1a49051e0, data=0x00007fff5049ac20, length=128, type=6, root=0) + 47 at vtkMPICommunicator.cxx:1157
frame #7: 0x00000001136c656a libvtkParallelCore-pv5.5.1.dylib`vtkCommunicator::Broadcast(this=0x00007fe1a49051e0, data=0x00007fff5049ac20, length=128, srcProcessId=0) + 90 at vtkCommunicator.h:309
frame #8: 0x00000001136d987a libvtkParallelCore-pv5.5.1.dylib`vtkMultiProcessController::BroadcastProcessRMIs(this=0x00007fe1a27125c0, (null)=1, dont_loop=0) + 138 at vtkMultiProcessController.cxx:521
frame #9: 0x00000001136d9ffc libvtkParallelCore-pv5.5.1.dylib`vtkMultiProcessController::ProcessRMIs(this=0x00007fe1a27125c0, reportErrors=1, dont_loop=0) + 92 at vtkMultiProcessController.cxx:648
frame #10: 0x00000001136d9f8c libvtkParallelCore-pv5.5.1.dylib`vtkMultiProcessController::ProcessRMIs(this=0x00007fe1a27125c0) + 28 at vtkMultiProcessController.cxx:640
frame #11: 0x000000010f76eeab pvserver`RealMain(argc=1, argv=0x00007fff5049b438, type=PROCESS_SERVER) + 827 at pvserver_common.h:95
frame #12: 0x000000010f76eb57 pvserver`main(argc=1, argv=0x00007fff5049b438) + 39 at pvserver.cxx:27
frame #13: 0x00007fff935ee5ad libdyld.dylib`start + 1
frame #14: 0x00007fff935ee5ad libdyld.dylib`start + 1
```
/cc @jpouderouxhttps://gitlab.kitware.com/paraview/paraview/-/issues/18344NetcdfReader dimensions parameters is not correctly loaded in a state file2021-03-23T18:53:40-04:00Mathieu Westphal (Kitware)NetcdfReader dimensions parameters is not correctly loaded in a state fileWhen loading a statefile containing a a netcdf reader, the dimensions parameters is not set
How to reproduce :
* Open ParaView
* Open a .nc file with multiples dimensions
* set the dimensions to the last value 'Time, South-north, We...When loading a statefile containing a a netcdf reader, the dimensions parameters is not set
How to reproduce :
* Open ParaView
* Open a .nc file with multiples dimensions
* set the dimensions to the last value 'Time, South-north, West-east) , Apply
* Save State pvsm
* Edit Reset sessions
* Load State pvsm
* Dimensions is set in the ui but nothin is visible
* Changing anything in the properties will load the datahttps://gitlab.kitware.com/paraview/paraview/-/issues/15924Change Input doesn't update domains for filters.2018-08-30T22:56:31-04:00Kitware RobotChange Input doesn't update domains for filters.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15924). Further discussion may take place here.**
---
1. Create a wavelet source, apply
2. Add a Glyph filter, the Glyph filter...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15924). Further discussion may take place here.**
---
1. Create a wavelet source, apply
2. Add a Glyph filter, the Glyph filter's Scalars list shows RTData as point data (correct). Apply glyph filter
3. Add a Point Data To Cell Data source to the wavelet, apply
4. Pick Glyph1, Change input, set to PDtoCD
5. The Glyph filter stills show RTData as point data, but RTData as cell data is not available
6. Select PDtoCD filter and create a new Glyph filter. Its Scalars list will now show correctly the cell data RTData.https://gitlab.kitware.com/paraview/paraview/-/issues/15894vtkExodusIIWriter: _ (underscore) added only to 2D data arrays2023-06-15T15:44:18-04:00Kitware RobotvtkExodusIIWriter: _ (underscore) added only to 2D data arrays**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15894). Further discussion may take place here.**
---
When writing 1D or 3D data arrays, the name of the array is preserved in t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15894). Further discussion may take place here.**
---
When writing 1D or 3D data arrays, the name of the array is preserved in the output file. When writing 2D data arrays, however, an underscore (_) is added to the name.
MWE:
```
import numpy
import vtk
from vtk.util import numpy_support
points = [
[0.0, 0.0, 0.0],
[1.0, 0.0, 0.0],
[1.0, 1.0, 0.0],
]
mesh = vtk.vtkUnstructuredGrid()
# set points
vtk_points = vtk.vtkPoints()
# Not using a deep copy here results in a segfault.
vtk_array = vtk.util.numpy_support.numpy_to_vtk(points)
vtk_points.SetData(vtk_array)
mesh.SetPoints(vtk_points)
c = numpy.array([
3,
0, 1, 2,
], dtype=int)
a = vtk.util.numpy_support.numpy_to_vtkIdTypeArray(c)
cell_array = vtk.vtkCellArray()
cell_array.SetCells(1, a)
mesh.SetCells(vtk.VTK_TRIANGLE, cell_array)
# add point data
pd = mesh.GetPointData()
A = numpy.array([7, 3, -2], dtype=float)
array = vtk.util.numpy_support.numpy_to_vtk(A)
array.SetName('A')
pd.AddArray(array)
B = numpy.array([[7, 1], [3, 2], [-2, 0]], dtype=float)
array = vtk.util.numpy_support.numpy_to_vtk(B)
array.SetName('B')
pd.AddArray(array)
C = numpy.array([[7, 1, 3], [3, 2, -2], [-2, 0, 7]], dtype=float)
array = vtk.util.numpy_support.numpy_to_vtk(C)
array.SetName('C')
pd.AddArray(array)
# writer = vtk.vtkUnstructuredGridWriter()
# writer.SetFileName('test.vtk')
writer = vtk.vtkExodusIIWriter()
writer.SetFileName('test.e')
writer.SetInputData(mesh)
writer.Write()
```
Open the file in, e.g., ParaView and observe the difference between A, B_, C.
When using the `vtkUnstructuredGridWriter` to write VTK files (any other file type, in fact), no underscore is added.https://gitlab.kitware.com/paraview/paraview/-/issues/15846Time sequence out of order on VTK file import within ParaView2020-05-06T13:46:12-04:00Kitware RobotTime sequence out of order on VTK file import within ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15846). Further discussion may take place here.**
---
When a user imports the attached data into ParaView, the file import dialo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15846). Further discussion may take place here.**
---
When a user imports the attached data into ParaView, the file import dialogue shows an incorrect numerical order of the vtk files. This happens regardless of file name being
String_integer.vtk
string_string_integer.vtk
In the terminal, the files are in the proper order (see additional screenshot). The integer convention is tied to the real time step value for easy post processing. Screenshots and test data are attached. Also tested on Paraview 4.1https://gitlab.kitware.com/paraview/paraview/-/issues/15832vtkExodusIIWriter: vtk int array converted to double2023-06-15T14:14:21-04:00Kitware RobotvtkExodusIIWriter: vtk int array converted to double**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15832). Further discussion may take place here.**
---
Writing an Int array to an exodus file, the data is incorrectly stored as ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15832). Further discussion may take place here.**
---
Writing an Int array to an exodus file, the data is incorrectly stored as double in the file. An MWE
```
import numpy
import vtk
from vtk.util import numpy_support
points = [
[0.0, 0.0, 0.0],
[1.0, 0.0, 0.0],
[1.0, 1.0, 0.0],
[0.0, 1.0, 0.0]
]
mesh = vtk.vtkUnstructuredGrid()
# set points
vtk_points = vtk.vtkPoints()
# Not using a deep copy here results in a segfault.
vtk_array = vtk.util.numpy_support.numpy_to_vtk(points)
vtk_points.SetData(vtk_array)
mesh.SetPoints(vtk_points)
# TODO use numpy_support here, avoid the copying
c = numpy.array([
3,
0, 1, 2,
3,
0, 2, 3
], dtype=int)
a = vtk.util.numpy_support.numpy_to_vtkIdTypeArray(c)
cell_array = vtk.vtkCellArray()
cell_array.SetCells(2, a)
mesh.SetCells(vtk.VTK_TRIANGLE, cell_array)
# add int point data
X = numpy.array([7, 8, 3, -2], dtype=int)
array = vtk.util.numpy_support.numpy_to_vtk(X)
array.SetName('X')
pd = mesh.GetPointData()
pd.AddArray(array)
writer = vtk.vtkExodusIIWriter()
writer.SetFileName('test.e')
writer.SetInput(mesh)
writer.Write()
```
The array `X` is stored as `double` in `test.e`.https://gitlab.kitware.com/paraview/paraview/-/issues/15717Polygon selection not correctly recorded by record xml test2021-03-23T12:06:00-04:00Kitware RobotPolygon selection not correctly recorded by record xml test**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15717). Further discussion may take place here.**
---
Polygon selections ( points/cells) Are not correctly recorded by record te...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15717). Further discussion may take place here.**
---
Polygon selections ( points/cells) Are not correctly recorded by record test xml.https://gitlab.kitware.com/paraview/paraview/-/issues/15696Selection not working correctly on the edge of a surface2023-06-15T11:30:32-04:00Kitware RobotSelection not working correctly on the edge of a surface**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15696). Further discussion may take place here.**
---
Some visible point cannot be selected using select on surface on the edge ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15696). Further discussion may take place here.**
---
Some visible point cannot be selected using select on surface on the edge of a surface.https://gitlab.kitware.com/paraview/paraview/-/issues/15635vtkProcessIds doesn't have the proper range when doing a trace and then runni...2020-05-06T01:45:44-04:00Kitware RobotvtkProcessIds doesn't have the proper range when doing a trace and then running in batch**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15635). Further discussion may take place here.**
---
Steps to reproduce:
1) Run paraview and connect to a server run with 2 pr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15635). Further discussion may take place here.**
---
Steps to reproduce:
1) Run paraview and connect to a server run with 2 processes
2) Start a trace
3) Create a Wavelet source
4) Switch to the Surface representation and pseudo-color by vtkProcessId
5) Save a screenshot
6) Stop the trace and save the python script
7) Run the python script with pvbatch and more than 2 MPI processes.
8) The outputted image will have a range of [0,1] and there will be a warning:
Warning: In /home/acbauer/Code/ParaView/ParaView/ParaViewCore/ServerManager/Rendering/vtkSMPVRepresentationProxy.cxx, line 280
vtkSMPVRepresentationProxy (0x3a02870): Could not determine array range.
https://gitlab.kitware.com/paraview/paraview/-/issues/15623pvserver is not correctly handling default plugins in PV_PLUGIN_PATH2020-05-12T22:22:44-04:00Kitware Robotpvserver is not correctly handling default plugins in PV_PLUGIN_PATH![2015-08-07-135316_800x600_scrot](/uploads/f06e5528743588e3528895c4a7c1d604/2015-08-07-135316_800x600_scrot.png)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15623). Further d...![2015-08-07-135316_800x600_scrot](/uploads/f06e5528743588e3528895c4a7c1d604/2015-08-07-135316_800x600_scrot.png)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15623). Further discussion may take place here.**
---
When starting pvserver with PV_PLUGIN_PATH pointing to ./lib, the plugin window display strange results.
How to reproduce ( with clean registery) :
PV_PLUGIN_PATH=./lib ./bin/pvserver &
PV_PLUGIN_PATH=./lib ./bin/paraview
connect to server, plugin manager shows up with error.https://gitlab.kitware.com/paraview/paraview/-/issues/15454Gradient background and print background don't work properly2021-06-22T14:44:03-04:00Kitware RobotGradient background and print background don't work properly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15454). Further discussion may take place here.**
---
* Linux, master, local server.
* Sources/ sphere. Apply.
* Change backgro...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15454). Further discussion may take place here.**
---
* Linux, master, local server.
* Sources/ sphere. Apply.
* Change background to gradient.
* File/ Save Screenshot. Use Print Pallet.
The picture won't have a white background, rather it will look like a weird gradient.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/15418Adding an empty selection clears selection2020-10-27T20:52:02-04:00Kitware RobotAdding an empty selection clears selection**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15418). Further discussion may take place here.**
---
1. Open ParaViewData/Data/can.ex2
2. Click on Select Cells On (s)
3. Creat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15418). Further discussion may take place here.**
---
1. Open ParaViewData/Data/can.ex2
2. Click on Select Cells On (s)
3. Create a selection (click and drag to specify a rectangle)
4. Click on Select Cells on (s)
5. While pressing CTRL click and drag to specify a different selection. The cells in the new rectangle are added to the selection.
6. Repeat step 5. but specify a rectangle outside the dataset. The empty set should be added to the set of selected cells, so the selection should be unchanged. However, the selection is cleared.https://gitlab.kitware.com/paraview/paraview/-/issues/15266Problem saving point label format in selection display inspector window2023-06-15T11:55:06-04:00Kitware RobotProblem saving point label format in selection display inspector window**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15266). Further discussion may take place here.**
---
I change the default point label format %-#6.3g by %f and press the save c...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15266). Further discussion may take place here.**
---
I change the default point label format %-#6.3g by %f and press the save current settings values as default button, but when I open a new paraview window the saving doesn't work (the default value is still here, not %f).
The problem doesn't exist on Paraview 4.1 32-bit, win XP.
I can do savings with Color Map Editor for example without any problem.
How can I fix this?https://gitlab.kitware.com/paraview/paraview/-/issues/15208Bug: Warning with Reset Camera to Normal2023-06-15T20:13:39-04:00Kitware RobotBug: Warning with Reset Camera to Normal**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15208). Further discussion may take place here.**
---
A particular case return a warning:
- Create a Sphere
- Apply a Slice filt...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15208). Further discussion may take place here.**
---
A particular case return a warning:
- Create a Sphere
- Apply a Slice filter with normal (0,1,0)
- Set view direction to +Z (in the toolbar "Camera Controls")
- Click on "Reset Camera To Normal" (in the property panel)https://gitlab.kitware.com/paraview/paraview/-/issues/15051Plane in 3d disapears2020-05-06T05:43:57-04:00Kitware RobotPlane in 3d disapears**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15051). Further discussion may take place here.**
---
Windows, 4.2.0 (from Kitware), local server.
* Sources/ Plane. Apply.
...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15051). Further discussion may take place here.**
---
Windows, 4.2.0 (from Kitware), local server.
* Sources/ Plane. Apply.
* Change the view 2d/3d control to 3d.
* Left mouse the view, trying to rotate it in 3d. The plane will go away!
* If you zoom in a whole long way, you eventually will see the plane again.https://gitlab.kitware.com/paraview/paraview/-/issues/15011Slice representation generates lot of warnings in C/S mode2023-06-15T09:36:10-04:00Kitware RobotSlice representation generates lot of warnings in C/S mode**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15011). Further discussion may take place here.**
---
When trying the slice representation (in a 3D view)on a 3D vtkImageData in...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=15011). Further discussion may take place here.**
---
When trying the slice representation (in a 3D view)on a 3D vtkImageData in PV 4.2, two problems were detected:
- warning messages occures on both client and server side
- in slice mode you can select the vtkProcessId field but it does not work and a warning message is displayed. It seems like in slice repr. the image is gathered and does not contain this field any more - nor the Normals field which is not supported by the Slice representation.
The problem does not occur with PV 4.1.https://gitlab.kitware.com/paraview/paraview/-/issues/14929Axes Visibility checkboxes in properties panel not synced with toolbar button2020-10-16T17:01:57-04:00Kitware RobotAxes Visibility checkboxes in properties panel not synced with toolbar button**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14929). Further discussion may take place here.**
---
In the properties panel under View there are checkboxes for Center Axes Vi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14929). Further discussion may take place here.**
---
In the properties panel under View there are checkboxes for Center Axes Visibility and Orientation Axes Visibility. There are also similar toggle buttons in the toolbars. When you click the toolbar button, the corresponding checkbox is appropriately synchronized. However, if you click on the checkbox in the properties panel, the toolbar button remains unchanged.Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/14884ghost cells causing problems in pvti files2020-05-14T21:38:31-04:00Kitware Robotghost cells causing problems in pvti files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14884). Further discussion may take place here.**
---
Ghost cells are causing "cracks" between partitions of the original subdom...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14884). Further discussion may take place here.**
---
Ghost cells are causing "cracks" between partitions of the original subdomains.
Steps to reproduce:
run the following script with pvbatch with 2 processes:
from paraview.simple import *
Wavelet()
g = GradientOfUnstructuredDataSet()
g.ScalarArray = ['POINTS', 'RTData']
w = XMLPImageDataWriter()
w.FileName = "ghosts.pvti"
w.UpdatePipeline()
Load that into paraview and change to surface view.
Berk GeveciBerk Gevecihttps://gitlab.kitware.com/paraview/paraview/-/issues/14868segfault reading triangle grid2021-03-23T11:50:30-04:00Kitware Robotsegfault reading triangle grid**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14868). Further discussion may take place here.**
---
Paraview 4.1 crashes (Segmentation Fault) opening the included file.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14868). Further discussion may take place here.**
---
Paraview 4.1 crashes (Segmentation Fault) opening the included file.https://gitlab.kitware.com/paraview/paraview/-/issues/14786Camera orbit doesn't work when rotating about X axis2020-05-06T05:15:09-04:00Kitware RobotCamera orbit doesn't work when rotating about X axis**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14786). Further discussion may take place here.**
---
Encountered in ParaView master and new MatViz application - when selecting...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14786). Further discussion may take place here.**
---
Encountered in ParaView master and new MatViz application - when selecting the X axis the rotation flips as you move through the series. It does not seem to be possible to rotate about this axis without the flipping artifact.https://gitlab.kitware.com/paraview/paraview/-/issues/14708Index and search features do not work in online help2024-02-06T18:38:20-05:00Kitware RobotIndex and search features do not work in online help**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14708). Further discussion may take place here.**
---
The ParaView online help window has tabs for index and search. The index t...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14708). Further discussion may take place here.**
---
The ParaView online help window has tabs for index and search. The index tab is completely empty. There appear to be no indices. The search tab allows you to supposedly search the help documents for a word, but the search always comes up empty no matter what string I search for.
This is running the Kitware distribution on Mac.5.12 (Winter 2023)https://gitlab.kitware.com/paraview/paraview/-/issues/14657Quad 9 dataset has holes2020-05-04T20:54:58-04:00Kitware RobotQuad 9 dataset has holes**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14657). Further discussion may take place here.**
---
I have a dataset that is quad9's. Dataset should be a closed sphere, but ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14657). Further discussion may take place here.**
---
I have a dataset that is quad9's. Dataset should be a closed sphere, but there are holes all over it. This dataset looks correct with Cubut (a meshing program) and EnSight.
I will give Utkarsh this dataset. Dataset name: sphere10_quad9.exo
https://gitlab.kitware.com/paraview/paraview/-/issues/14549NRRD file without end of line on last line eats all of memory2023-06-15T10:46:42-04:00Kitware RobotNRRD file without end of line on last line eats all of memory**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14549). Further discussion may take place here.**
---
Thank you for making an ASCII NRRD reader! I love it! It is a GREAT bene...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14549). Further discussion may take place here.**
---
Thank you for making an ASCII NRRD reader! I love it! It is a GREAT benefit for my vis class.
On 4.0.1, 4.1RC2 and 4.1 (on Windows and Linux), if you try to open the attached NRRD file, it will eat all of memory and die (maybe taking your machine with it).
You don't need to have the associated file; it hangs even before giving the Accept button. If you add a newline at the end of the file, it is fine.https://gitlab.kitware.com/paraview/paraview/-/issues/14536Recording a test for setting a background image does not work.2020-05-07T09:38:12-04:00Kitware RobotRecording a test for setting a background image does not work.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14536). Further discussion may take place here.**
---
Record a test:
paraview -dr
Tools / Record Test...
Choose the file wher...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14536). Further discussion may take place here.**
---
Record a test:
paraview -dr
Tools / Record Test...
Choose the file where to save the test
Set Background type to 'Image'
Choose 'Load...'
In the file dialog choose ParaView/Data/NE2_ps_bath.png
Press 'Stop recording'
Press 'Disconnect'
Play the test:
Tools / Play Test...
Choose the test file you just saved.
You'll get the following error:
Couldn't find object "pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/ViewFrame/ProxyPanel/BackgroundEditor/stackedWidget/page_1/Color/0QColorDialog0"
Found up to "pqClientMainWindow/propertiesDock/propertiesPanel/scrollArea/qt_scrollarea_viewport/scrollAreaWidgetContents/ViewFrame/ProxyPanel/BackgroundEditor/stackedWidget/page_1/Color"
https://gitlab.kitware.com/paraview/paraview/-/issues/14265Exodus writer fails with polyhedral data2023-06-15T14:07:22-04:00Kitware RobotExodus writer fails with polyhedral data**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14265). Further discussion may take place here.**
---
Local server, master, Linux.
Open dataset fmaego.mesh.case, found in bug r...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14265). Further discussion may take place here.**
---
Local server, master, Linux.
Open dataset fmaego.mesh.case, found in bug report http://paraview.org/Bug/view.php?id=13338. Apply.
File/ Save Data, and write this out as an exodus dataset. ParaView/VTK will output lots of error verbiage, and then write out an empty file.
```
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 42
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 110
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 178
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 382
ERROR: In /projects/viz/paraview/src/ParaView/4.1.0-alan2/ParaView4/VTK/IO/Exodus/vtkExodusIIWriter.cxx, line 1785
vtkPExodusIIWriter (0x49f33d0): Problem adding block with id 450
```W. Alan ScottW. Alan Scotthttps://gitlab.kitware.com/paraview/paraview/-/issues/14236vtkImplicitFunctionToImageStencil doesn't work in ParaView2023-06-15T08:30:17-04:00Kitware RobotvtkImplicitFunctionToImageStencil doesn't work in ParaView**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14236). Further discussion may take place here.**
---
+ Rebuild ParaView with Module_vtkImagingStencil Cmake variable ON
+ Load ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14236). Further discussion may take place here.**
---
+ Rebuild ParaView with Module_vtkImagingStencil Cmake variable ON
+ Load attached XML as a plugin.
+ Try creating the "Implicit-Function To Image-Stencil" source.
+ You'll get errors:
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/DataModel/vtkDataObjectTypes.cxx, line 303
NewDataObject(): You are trying to instantiate DataObjectType "vtkImageStencilData" which does not exist.
ERROR: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 658
vtkPVCompositeDataPipeline (0x20b9d80): Algorithm vtkImplicitFunctionToImageStencil(0x26c9770) did not create output for port 0 when asked by REQUEST_DATA_OBJECT and does not specify a concrete DATA_TYPE_NAME.
Generic Warning: In /home/utkarsh/Kitware/ParaView3/ParaView/VTK/Common/DataModel/vtkDataObjectTypes.cxx, line 303
NewDataObject(): You are trying to instantiate DataObjectType "vtkImageStencilData" which does not exist.https://gitlab.kitware.com/paraview/paraview/-/issues/14024Tab stop in "Sources/Text" does not Work2023-06-15T09:50:23-04:00Kitware RobotTab stop in "Sources/Text" does not Work**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14024). Further discussion may take place here.**
---
When you insert a tab stop in the text field, the display window does not ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14024). Further discussion may take place here.**
---
When you insert a tab stop in the text field, the display window does not apply the tab stop.
Also if you write in the python shell Text1.Text='Hi \t Tab \t stop'
the \t is ignored.https://gitlab.kitware.com/paraview/paraview/-/issues/14022ParaViewWeb security bug: unexpected static content behavior2023-06-15T10:48:44-04:00Kitware RobotParaViewWeb security bug: unexpected static content behavior**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14022). Further discussion may take place here.**
---
When I start up my ParaViewWeb application without passing any "--content"...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=14022). Further discussion may take place here.**
---
When I start up my ParaViewWeb application without passing any "--content" argument, my expectation is that it won't serve any static content at all. However, it is actually serving all of the static content under whatever the working directory was that I invoked python in, and I didn't realize it was doing this until I looked at the code in web.py. A user could easily accidentally be serving up portions of their filesystem that they don't want to be serving.
I propose we change the behavior to: if no --content arg is passed, then no static content is served at all.https://gitlab.kitware.com/paraview/paraview/-/issues/13998Spreadsheet View and Labels can cause errors on occasion.2021-04-16T19:35:54-04:00Kitware RobotSpreadsheet View and Labels can cause errors on occasion.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13998). Further discussion may take place here.**
---
* Open can.ex2, all variables, apply
* Open Find Data dialog and create a ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13998). Further discussion may take place here.**
---
* Open can.ex2, all variables, apply
* Open Find Data dialog and create a cell selection (any selection would do, I just created a global id selection with cell #12)
* Create selection and then label with EQPS.
* Create spread sheet view to show the can.ex2
* Now simply click in the spreadsheet view, on any of the rows to create a new selection, you;ll get the following errors:
Warning: In /Users/utkarsh/Kitware/ParaView/ParaView/VTK/Rendering/Label/vtkLabeledDataMapper.cxx, line 442
vtkLabeledDataMapper (0x126cbe0b0): Could not find label array (EQPS) in input.5.10 (Fall 2021)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/13941Find Data queries applied to time source yield syntax errors2020-05-22T13:38:57-04:00Kitware RobotFind Data queries applied to time source yield syntax errors**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13941). Further discussion may take place here.**
---
3.98.0, 3.98.1 + git/master, Linux x86_64, builtin mode
Sources - Time ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13941). Further discussion may take place here.**
---
3.98.0, 3.98.1 + git/master, Linux x86_64, builtin mode
Sources - Time Source - Apply
Edit - Find Data - Find Cell from TimeSource1 - Global ID is 0 - Run Selection Query
=> the following warning is raised:
---------
Traceback (most recent call last):
File "<string>", line 5, in <module>
File "/ParaView-3.98.1-Linux-64bit/lib/paraview-3.98/site-packages/paraview/extract_selection.py", line 153, in Exec
ds = ExecData(self, inputDO, selection)
File "/ParaView-3.98.1-Linux-64bit/lib/paraview-3.98/site-packages/paraview/extract_selection.py", line 122, in ExecData
mask = eval(selection_node.GetQueryString(), globals(), new_locals)
File "<string>", line 1
Cell Label == 0
^
SyntaxError: invalid syntax
---------
A similar warning is raised for the queries:
* "Cell Label is 0"
* "Cell Value is 0"
* "Cell X is 0.5"
Mathieu Westphal (Kitware)Mathieu Westphal (Kitware)https://gitlab.kitware.com/paraview/paraview/-/issues/13836ProgressHandler - Most filters - are broken2023-06-15T12:17:04-04:00Kitware RobotProgressHandler - Most filters - are broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13836). Further discussion may take place here.**
---
I just tried the Progress Handler with Clip, Slice, Threshold and Glyph. ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13836). Further discussion may take place here.**
---
I just tried the Progress Handler with Clip, Slice, Threshold and Glyph. Placing a break in vtkPVProgressHandler::OnProgressEvent(), at the bottom RefreshProgress line, using z_pinch1.exo.8.[0-7], I see the same behavior for all of these filters. The progress variable bounces between 0 and 1 (nothing in between), and after about 10 calls into this function, the filter returns.
From what I can tell, these filters were never impplemented with the Progress Handler. If they were, since it bounces, it is worthless.
Please implement the progress handler in all common filters.https://gitlab.kitware.com/paraview/paraview/-/issues/13832ProgressHandler - Cell to Point is broken2023-07-12T21:42:01-04:00Kitware RobotProgressHandler - Cell to Point is broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13832). Further discussion may take place here.**
---
Progress handler code in Cell to Point is broken. In file vtkCellDataToPo...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13832). Further discussion may take place here.**
---
Progress handler code in Cell to Point is broken. In file vtkCellDataToPointData.cxx, function vtkCellDataToPointData::RequestData(), update progress gets called many dozens of times (speculation is once per block, which could be millions of times). Each time this code dutifully bounces the UpdateProgress(progress) call from 0.0 to 1.0, in increments of 0.05. I am not even going to try a fix.
Suggested hack would be to comment out the UpdateProgress.
vtkCellDataToPointData.cxx, line 106, should change from:
this->UpdateProgress(static_cast<double>(ptId)/numPts);
to
//this->UpdateProgress(static_cast<double>(ptId)/numPts);Aron HelserAron Helserhttps://gitlab.kitware.com/paraview/paraview/-/issues/13812Comparative View - Overlay doesn't work correctly when animation time.2020-05-06T14:37:18-04:00Kitware RobotComparative View - Overlay doesn't work correctly when animation time.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13812). Further discussion may take place here.**
---
Start a clean ParaView.
* Load can.ex2, Apply
* Close 3D view and crea...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13812). Further discussion may take place here.**
---
Start a clean ParaView.
* Load can.ex2, Apply
* Close 3D view and create comparative view.
* Turn on can's visibility.
* From View menu, turn on "Comparative View Inspector"
* Click "+" next to time to add a default time animation -- the view should update. Everything looks well.
* Now check "Overlay all comparisons" -- observe the image (A)
* Simply pick array to color by or just uncheck and check "Overlay" again. And look at the result (B)
The data from time 0 is not show in (A) but shows up again in (B). That's a bug.
https://gitlab.kitware.com/paraview/paraview/-/issues/13490Cannot slice/contour a data set containg Polyhedron cells where the node valu...2020-05-04T05:47:10-04:00Kitware RobotCannot slice/contour a data set containg Polyhedron cells where the node values are < 1e-6**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13490). Further discussion may take place here.**
---
Slicing or contouring a data set containing polyhedron cells where all the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13490). Further discussion may take place here.**
---
Slicing or contouring a data set containing polyhedron cells where all the nodal vertex locations are less than 1e-6 produces no sliced or contoured results.
I expect there is a problem with contouring or clipping in polyhedron cells. I found a potential problem in VTK source for ver5.10 src/VTK/Filtering/vtkPolyhedron.cxx in the internal section there is a method called RemoveDuplicatedPointsFromFaceArrayAndEdgeTable and within the method a constant value "const double eps = 0.000001;" is used to merge node locations.
I suspect that if all locations are < than this constant all nodes are merged.
I also notices this constant is repeated in several sections through out the vtkPolyhedron.cxx source.
In the uploaded file a single cell polyhedron is given with 6 faces and 4 nodes per face with node values < 1e-6 , when read by Paraview 3.14.1 and sliced, produced no results. If the file is modified where connectivity remains the same but the nodes are changed to 1e-5, then paraview will correctly slice the modifed data set. https://gitlab.kitware.com/paraview/paraview/-/issues/13249StreamTracer segfault on a dataset without 3D cell2024-01-11T08:14:39-05:00Kitware RobotStreamTracer segfault on a dataset without 3D cell**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13249). Further discussion may take place here.**
---
Given the attached csv file I get different segfaults. This is all with PV...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13249). Further discussion may take place here.**
---
Given the attached csv file I get different segfaults. This is all with PV 3.14.1, happens in official binaries, as well as in a custom-compiled RelWithDebInfo build. Ubuntu Lucid, x86_64.
1st situation:
- Open csv file, apply default reader settings, data in table looks good
- Add a Table to Points filter, X column=x, etc
- Interestingly, the data at this point consists of a single cell with 25000 points
- Add a calculator filter, name result array 'v', expression 'vx*iHat+vy*jHat+vz*kHat'
- Newly added vector data looks good in table view
- Add a Mask points filter to the calculator output, #points=200, random sampling
- Add Streamtracer with custom source, input=calculator, source=maskpoints, apply
- SEGFAULT
```
Partial stack trace:
#0 0x00007f0390642976 in _int_malloc (av=0x7f0390945e40, bytes=112) at malloc.c:4635
#1 0x00007f03906437de in *__GI___libc_malloc (bytes=112) at malloc.c:3660
#2 0x00007f0390c2c24d in operator new(unsigned long) () from /usr/lib/libstdc++.so.6
#3 0x00007f0391eba342 in vtkPoints::New (dataType=10) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkPoints.cxx:51
#4 0x00007f0392b8e830 in vtkCell (this=0x330cea0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCell.cxx:24
#5 0x00007f0392d7f94e in vtkVertex (this=0x0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkVertex.cxx:29
#6 0x00007f0392d7fa40 in vtkVertex::New () at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkVertex.cxx:25
#7 0x00007f0392d0c840 in vtkPolyVertex (this=0x3a6f1c0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPolyVertex.cxx:31
#8 0x00007f0392d0c910 in vtkPolyVertex::New () at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPolyVertex.cxx:26
#9 0x00007f0392be49fc in vtkGenericCell::SetCellType (this=0x3a7bde0, cellType=2) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkGenericCell.cxx:364
#10 0x00007f0392cf2a75 in vtkGenericCell::SetCellTypeToPolyVertex (this=0x3a0a260, cellId=<value optimized out>, cell=0x3a7bde0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkGenericCell.h:98
#11 vtkPolyData::GetCell (this=0x3a0a260, cellId=<value optimized out>, cell=0x3a7bde0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPolyData.cxx:396
#12 0x00007f0392b64942 in vtkAbstractInterpolatedVelocityField::FunctionValues (this=0x27daaa0, dataset=0x3a0a260, x=0x2526450, f=0x3a14010) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkAbstractInterpolatedVelocityField.cxx:134
#13 0x00007f0392c82715 in vtkInterpolatedVelocityField::FunctionValues (this=0x27daaa0, x=0x2526450, f=0x3a14010) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkInterpolatedVelocityField.cxx:79
#14 0x00007f0391ecb8f2 in vtkRungeKutta45::ComputeAStep (this=0x28b1380, xprev=0x7fff94dd5c60, dxprev=<value optimized out>, xnext=<value optimized out>, t=<value optimized out>, delT=@0x7fff94dd5cb0, error=<value optimized out>)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkRungeKutta45.cxx:268
#15 0x00007f0391ecbd3f in vtkRungeKutta45::ComputeNextStep (this=0x28b1380, xprev=0x7fff94dd5c60, dxprev=0x0, xnext=0x7fff94dd5c40, t=<value optimized out>, delT=@0x7fff94dd5cb0, delTActual=<value optimized out>, minStep=24, maxStep=0, maxError=39, estErr=@0x7fff94dd5cc8)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkRungeKutta45.cxx:127
#16 0x00007f0391ecc36c in vtkRungeKutta45::ComputeNextStep (this=0x0, xprev=0x4000122c, xnext=<value optimized out>, t=0, delT=<value optimized out>, delTActual=<value optimized out>, minStep=0, maxStep=0, maxError=39, error=<value optimized out>)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Common/vtkRungeKutta45.h:93
#17 0x00007f03944ef742 in vtkStreamTracer::Integrate (this=0x3aef950, input0=<value optimized out>, output=<value optimized out>, seedSource=0x29e8a60, seedIds=<value optimized out>, integrationDirections=<value optimized out>, lastPoint=0x7fff94dd5d80, func=0x27daaa0,
maxCellSize=25000, vecName=0x1da3680 "v", inPropagation=@0x7fff94dd5da8, inNumSteps=@0x7fff94dd5da0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:827
#18 0x00007f03944f106c in vtkStreamTracer::RequestData (this=0x3aef950, inputVector=<value optimized out>, outputVector=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:468
#19 0x00007f03974b62e5 in vtkPStreamTracer::RequestData (this=0x3aef950, request=0x347f9d0, inputVector=0x3b0d920, outputVector=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Parallel/vtkPStreamTracer.cxx:334
#20 0x00007f0392bd7da4 in vtkExecutive::CallAlgorithm (this=0x3af0700, request=0x347f9d0, direction=<value optimized out>, inInfo=0x3b0d920, outInfo=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkExecutive.cxx:747
#21 0x00007f0392bcb71c in vtkDemandDrivenPipeline::ExecuteData (this=0x3af0700, request=0x347f9d0, inInfo=0x3b0d920, outInfo=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:507
#22 0x00007f0392bac711 in vtkCompositeDataPipeline::ExecuteData (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:391
#23 0x00007f0392bce7cb in vtkDemandDrivenPipeline::ProcessRequest (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:279
#24 0x00007f0392d580f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#25 0x00007f0392ba95d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x3af0700, request=0x347f9d0, inInfoVec=0x3b0d920, outInfoVec=0x3af1040) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#26 0x00007f0392baa886 in vtkCompositeDataPipeline::ForwardUpstream (this=0x2a554c0, request=0x347f9d0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:215
#27 0x00007f0392bce775 in vtkDemandDrivenPipeline::ProcessRequest (this=0x2a554c0, request=0x347f9d0, inInfoVec=0x1d75470, outInfoVec=0x3a8f300) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:265
#28 0x00007f0392d580f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x2a554c0, request=0x347f9d0, inInfoVec=0x1d75470, outInfoVec=0x3a8f300) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#29 0x00007f0392ba95d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x2a554c0, request=0x347f9d0, inInfoVec=0x1d75470, outInfoVec=0x3a8f300) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#30 0x00007f0392bce50f in vtkDemandDrivenPipeline::UpdateData (this=0x2a554c0, outputPort=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:449
#31 0x00007f0392d5713b in vtkStreamingDemandDrivenPipeline::Update (this=0x2a554c0, port=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:326
#32 0x00007f03a3364d73 in vtkSISourceProxyCommand (arlu=0x16ac8d0, ob=0x3af78a0, method=<value optimized out>, msg=..., resultStream=...) at /home/paulmlocal/c/paraview-3.14.1-reldebinfo/ParaViewCore/ServerImplementation/vtkSISourceProxyClientServer.cxx:114
#33 0x00007f039936069f in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x16ac8d0, css=..., midx=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:379
#34 0x00007f039935f53e in vtkClientServerInterpreter::ProcessOneMessage (this=0x16ac8d0, css=..., message=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:214
#35 0x00007f039935f68d in vtkClientServerInterpreter::ProcessStream (this=0x16ac8d0, css=...) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:183
```
2nd situation (similar, but using Python calculator):
- Open csv file, apply default reader settings, data in table looks good
- Add a Table to Points filter, X column=x, etc
- Add a Python calculator filter, name result array 'v', expression 'hstack([vx,vy,vz])'
- Newly added vector data looks good in table view
- Add a Mask points filter to the calculator output, #points=200, random sampling
- Add Streamtracer with custom source, input=calculator, source=maskpoints, apply
- SEGFAULT
```
Partial stack trace:
#0 vtkPointLocator::FindClosestPoint (this=0x2aa6b20, x=0x7fffbda168b0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPointLocator.cxx:205
#1 0x00007fd0e433e9bc in vtkPointSet::FindCell (this=0x32f1350, x=0x7fffbda168b0, cell=0x0, gencell=0x40dde40, cellId=-1, tol2=<value optimized out>, subId=@0x7fffbda1665c, pcoords=0x2e57390, weights=0x2e5f020)
at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkPointSet.cxx:291
#2 0x00007fd0e41b97f4 in vtkAbstractInterpolatedVelocityField::FunctionValues (this=0x2e57330, dataset=0x32f1350, x=0x7fffbda168b0, f=0x7fffbda168d0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkAbstractInterpolatedVelocityField.cxx:160
#3 0x00007fd0e42d7715 in vtkInterpolatedVelocityField::FunctionValues (this=0x2e57330, x=0x7fffbda168b0, f=0x7fffbda168d0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkInterpolatedVelocityField.cxx:79
#4 0x00007fd0e5b44323 in vtkStreamTracer::Integrate (this=0x2e2d3e0, input0=0x1, output=<value optimized out>, seedSource=0x40dbb80, seedIds=<value optimized out>, integrationDirections=<value optimized out>, lastPoint=0x7fffbda169d0, func=0x2e57330, maxCellSize=25000,
vecName=0x3eca270 "v", inPropagation=@0x7fffbda169f8, inNumSteps=@0x7fffbda169f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:696
#5 0x00007fd0e5b4606c in vtkStreamTracer::RequestData (this=0x2e2d3e0, inputVector=<value optimized out>, outputVector=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Graphics/vtkStreamTracer.cxx:468
#6 0x00007fd0e8b0b2e5 in vtkPStreamTracer::RequestData (this=0x2e2d3e0, request=0x40daaf0, inputVector=0x2e233b0, outputVector=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Parallel/vtkPStreamTracer.cxx:334
#7 0x00007fd0e422cda4 in vtkExecutive::CallAlgorithm (this=0x2e28a20, request=0x40daaf0, direction=<value optimized out>, inInfo=0x2e233b0, outInfo=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkExecutive.cxx:747
#8 0x00007fd0e422071c in vtkDemandDrivenPipeline::ExecuteData (this=0x2e28a20, request=0x40daaf0, inInfo=0x2e233b0, outInfo=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:507
#9 0x00007fd0e4201711 in vtkCompositeDataPipeline::ExecuteData (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:391
#10 0x00007fd0e42237cb in vtkDemandDrivenPipeline::ProcessRequest (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:279
#11 0x00007fd0e43ad0f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#12 0x00007fd0e41fe5d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x2e28a20, request=0x40daaf0, inInfoVec=0x2e233b0, outInfoVec=0x41150f0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#13 0x00007fd0e41ff886 in vtkCompositeDataPipeline::ForwardUpstream (this=0x2aa7360, request=0x40daaf0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:215
#14 0x00007fd0e4223775 in vtkDemandDrivenPipeline::ProcessRequest (this=0x2aa7360, request=0x40daaf0, inInfoVec=0x411f910, outInfoVec=0x40d6a70) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:265
#15 0x00007fd0e43ad0f9 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x2aa7360, request=0x40daaf0, inInfoVec=0x411f910, outInfoVec=0x40d6a70) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:276
#16 0x00007fd0e41fe5d1 in vtkCompositeDataPipeline::ProcessRequest (this=0x2aa7360, request=0x40daaf0, inInfoVec=0x411f910, outInfoVec=0x40d6a70) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkCompositeDataPipeline.cxx:292
#17 0x00007fd0e422350f in vtkDemandDrivenPipeline::UpdateData (this=0x2aa7360, outputPort=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkDemandDrivenPipeline.cxx:449
#18 0x00007fd0e43ac13b in vtkStreamingDemandDrivenPipeline::Update (this=0x2aa7360, port=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/VTK/Filtering/vtkStreamingDemandDrivenPipeline.cxx:326
#19 0x00007fd0f49b9d73 in vtkSISourceProxyCommand (arlu=0x2370780, ob=0x2e2ccf0, method=<value optimized out>, msg=..., resultStream=...) at /home/paulmlocal/c/paraview-3.14.1-reldebinfo/ParaViewCore/ServerImplementation/vtkSISourceProxyClientServer.cxx:114
#20 0x00007fd0ea9b569f in vtkClientServerInterpreter::ProcessCommandInvoke (this=0x2370780, css=..., midx=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:379
#21 0x00007fd0ea9b453e in vtkClientServerInterpreter::ProcessOneMessage (this=0x2370780, css=..., message=0) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:214
#22 0x00007fd0ea9b468d in vtkClientServerInterpreter::ProcessStream (this=0x2370780, css=...) at /home/paulmlocal/c/ParaView-3.14.1-Source/Utilities/VTKClientServer/vtkClientServerInterpreter.cxx:183
#23 0x00007fd0f43d970c in vtkPVSessionCore::ExecuteStreamInternal (this=0x236aca0, stream=..., ignore_errors=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerImplementation/vtkPVSessionCore.cxx:636
#24 0x00007fd0f43d7368 in vtkPVSessionCore::ExecuteStream (this=0x236aca0, location=1, stream=..., ignore_errors=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerImplementation/vtkPVSessionCore.cxx:606
#25 0x00007fd0f43d49f2 in vtkPVSessionBase::ExecuteStream (this=0x236e920, location=1, stream=..., ignore_errors=false) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerImplementation/vtkPVSessionBase.cxx:173
#26 0x00007fd0f4cfde65 in vtkSMProxy::ExecuteStream (this=<value optimized out>, stream=..., ignore_errors=false, location=1) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerManager/vtkSMProxy.cxx:2091
#27 0x00007fd0f4ce9110 in vtkSMOutputPort::UpdatePipelineInternal (this=0x303b7b0, time=<value optimized out>, doTime=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerManager/vtkSMOutputPort.cxx:211
#28 0x00007fd0f4d49d10 in vtkSMSourceProxy::UpdatePipeline (this=0x303c760, time=<value optimized out>) at /home/paulmlocal/c/ParaView-3.14.1-Source/ParaViewCore/ServerManage
```https://gitlab.kitware.com/paraview/paraview/-/issues/13204components of a 6-element vector cannot be accessed by calculator2021-03-24T15:48:39-04:00Kitware Robotcomponents of a 6-element vector cannot be accessed by calculator**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13204). Further discussion may take place here.**
---
Having a 6-element vector "vec" automatically labels the components
"vec_X...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13204). Further discussion may take place here.**
---
Having a 6-element vector "vec" automatically labels the components
"vec_XX", "vec_YY", "vec_ZZ", "vec_YZ", "vec_XZ" and "vec_XY".
This components cannot be accessed by the calculator, as the parser
reports an error at the second character after the underline
FunctionParser (000000000C52E8B0): Syntax error: operator expected; see position <x>
This happens for three file formats and versions at least 3.10 up to 3.14.
See "[Paraview] programmable access to vector components (via Python)" in
the user mailing list.
In in the appendix it is "mechTensor".
BTW, the component labeling is as for Voigt notation stress and strain, which
does not apply for my vector. _1, ... _6 would be better.https://gitlab.kitware.com/paraview/paraview/-/issues/13156Update XML writers to support new AMR datasets2023-06-15T09:21:42-04:00Kitware RobotUpdate XML writers to support new AMR datasets**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13156). Further discussion may take place here.**
---
The VTK XML Writers dont' support writing the new AMR dataset types.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13156). Further discussion may take place here.**
---
The VTK XML Writers dont' support writing the new AMR dataset types.https://gitlab.kitware.com/paraview/paraview/-/issues/13137Cannot save images created using python calculator2020-05-06T22:31:43-04:00Kitware RobotCannot save images created using python calculator**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13137). Further discussion may take place here.**
---
Cannot save image data that was created using the python calculator. Ofte...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13137). Further discussion may take place here.**
---
Cannot save image data that was created using the python calculator. Often I use paraview to do simple arithmetic on image data, which I then would like to save for further processing. Not being able to do so with the python calculator is quite limiting.
Minimal example, with Paraview 3.14.0 on Ubuntu.
- Load image
- Python calculator:
Expression: inputs[0].PointData['MetaImage'] // i.e. just copy data over
Array Association: point data
Copy arrays: off
- Resulting image looks good
- Select python calculator result, File->Save Data, save as .mhd
- Reload image - data extents are correct, but all values are 0
Somewhat similarly -
If you use the Calculator instead of the Python Calculator, there is no way to turn off "copy arrays", so the output image typically has two data arrays - the original input array, and the result of the calculation. If you save this as .mhd, the result has only one data array - the result of the calculation. I would expect a .mhd with two channels.
https://gitlab.kitware.com/paraview/paraview/-/issues/13084AMR Enzo Reader does not work with save /load state2023-06-15T08:30:00-04:00Kitware RobotAMR Enzo Reader does not work with save /load state**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13084). Further discussion may take place here.**
---
- Open VTKData/Data/AMR/Enzo/DD0010/moving7_0010.hierarchy
- Check x-veloc...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13084). Further discussion may take place here.**
---
- Open VTKData/Data/AMR/Enzo/DD0010/moving7_0010.hierarchy
- Check x-velocity, y-velocity and z-velocity and click Apply
- Save state
- Disconnect and Load state again.
Notice that no data gets loaded. After hitting apply, still no data.https://gitlab.kitware.com/paraview/paraview/-/issues/13002Comparative View: "Visibility" cannot be animated across the comparative view...2020-05-04T04:58:29-04:00Kitware RobotComparative View: "Visibility" cannot be animated across the comparative view correctly**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13002). Further discussion may take place here.**
---
Comparative View: "Visibility" cannot be animated across the comparative v...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=13002). Further discussion may take place here.**
---
Comparative View: "Visibility" cannot be animated across the comparative view correctly
Refer to: http://www.paraview.org/pipermail/paraview/2012-March/024330.htmlhttps://gitlab.kitware.com/paraview/paraview/-/issues/12837Volume rendering is always doing LOD2020-05-04T04:22:26-04:00Kitware RobotVolume rendering is always doing LOD**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12837). Further discussion may take place here.**
---
To reproduce the issue, create a wavelet source and switch the representat...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12837). Further discussion may take place here.**
---
To reproduce the issue, create a wavelet source and switch the representation to volume. The volume rendering for the static object looks good. But if you hold down the left mouse button and drag to rotate the object, the volume rendering would become blurry. After about one second you release the mouse button, the rendering switched back to the non-blurry one. Please see the attached images.
There is no way to disable LOD for volume rendering. The LOD controls in settings only pertain to surface rendering.https://gitlab.kitware.com/paraview/paraview/-/issues/12761CSV Reader leakes or not very efficient2023-08-17T11:01:44-04:00Kitware RobotCSV Reader leakes or not very efficient**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12761). Further discussion may take place here.**
---
Trying to load a 3GB csv file with 64bit ParaView 3.12.0. Crashes after co...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12761). Further discussion may take place here.**
---
Trying to load a 3GB csv file with 64bit ParaView 3.12.0. Crashes after consuming 10GB of memory (System has 12GB).https://gitlab.kitware.com/paraview/paraview/-/issues/12749Paraview VRML reader should not attempt VRML 1.0 files2021-03-24T11:45:39-04:00Kitware RobotParaview VRML reader should not attempt VRML 1.0 files**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12749). Further discussion may take place here.**
---
The VRML loading code in paraview uses VTK's parser class (vtkVRMLImporter...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12749). Further discussion may take place here.**
---
The VRML loading code in paraview uses VTK's parser class (vtkVRMLImporter), which only handles VMRL 2.0. Paraview, however, will allow the user to open a VRML 1 file which, after parsing, produces a diagnostic message that does not point to the root cause (i.e. loading a VRML 1 file).
Suggest that Paraview disallow loading VRML versions other than 2. See mailing-list discussion http://www.paraview.org/pipermail/paraview/2011-November/023393.html
A comment in vtkVRMLSource::CanReadFile() says:
```
// Technically, the header should start with "#VRML V2.0 utf8", but who's
// to say that new versions will not be forward compatible. Let's not be
// perscriptive yet. If some future version of VRML is incompatible, we
// can make this test more strict.
int valid = (strncmp(header, "#VRML ", 6) == 0);
```
It's clear that this test should forbid VRML 1. I think it is also now clear that new versions are NOT forward compatible. VRML has been superceded by X3D (http://www.web3d.org/x3d/specifications/x3d/) which although it does have a VRML encoding (http://www.web3d.org/x3d/specifications/ISO-IEC-19776-X3DEncodings-All-Edition-1/) the header starts with "#X3D V3.0", not "VRML".https://gitlab.kitware.com/paraview/paraview/-/issues/12747show/hide resets zooming factor2021-03-23T07:45:16-04:00Kitware Robotshow/hide resets zooming factor**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12747). Further discussion may take place here.**
---
When there is only one object displayed on the view, hiding it and re-show...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12747). Further discussion may take place here.**
---
When there is only one object displayed on the view, hiding it and re-showing it modifies the zooming factor.
The zooming factor should be reset only if htere is no entry in the pipeline browser and one is created.https://gitlab.kitware.com/paraview/paraview/-/issues/12563parallel coordinates view interaction bugs2020-05-06T10:58:47-04:00Kitware Robotparallel coordinates view interaction bugs**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12563). Further discussion may take place here.**
---
Currently, in ParaView, a selection is created in parallel coordinates thr...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12563). Further discussion may take place here.**
---
Currently, in ParaView, a selection is created in parallel coordinates through mouse interaction. In order to reset the selection, an axis must be clicked without dragging. This is non-intuitive and easy to do by mistake. A "reset" button would be easier to use
Because of how the selection mechanism works, it is only possible to select subsets of the current selection; it is never possible to add to the selection without resetting. This may make it difficult to modify a complex selection mechanism (i.e. one that involves limits on several axes).
Axes may be re-ordered by right-clicking and dragging. When this happens, the user might expect the axes to be evenly spaced in the new order to make a pretty-looking chart. This does not happen.
When axes are re-ordered and the selection is modified or reset, the new ordering is lost. This is not what I expect to happen.https://gitlab.kitware.com/paraview/paraview/-/issues/12530Contour of 2d strips variables2020-05-04T01:51:12-04:00Kitware RobotContour of 2d strips variables**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12530). Further discussion may take place here.**
---
I will use Sources/Mandlebrot, but need to make another variable. Thu...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12530). Further discussion may take place here.**
---
I will use Sources/Mandlebrot, but need to make another variable. Thus, calculator below.
ParaView development (as of about a week ago), local server, windows.
* Sources/Mandlebrot
* Calculator. Iterations*coordsY. Apply.
* Contour. Iterations. 50. Apply.
>> Now, if you try to color by Result (output from the Calculator), it is not availablehttps://gitlab.kitware.com/paraview/paraview/-/issues/12391vti files do not enlarge their domain in the time series (file_1.vti, file_2....2020-04-21T07:42:54-04:00Kitware Robotvti files do not enlarge their domain in the time series (file_1.vti, file_2.vti...)**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12391). Further discussion may take place here.**
---
I produce a time series of vti files (lbm_0.vti, lbm_30.vti ...) which
ch...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12391). Further discussion may take place here.**
---
I produce a time series of vti files (lbm_0.vti, lbm_30.vti ...) which
change their domain size in time. For example, lbm_0.vti has <Piece
Extent="0 60 0 60 0 61"> and lbm_1020.vti has <Piece Extent="0 86 0
86 0 61">. When I load the series into the Paraview, the domain does
not enlarge and stays at its initial size. When I load lbm_1020.vti
separately, it has the correct domain size. I enclose the two sample
files where you can observe the problem.
Comment by Biddiscombe, John A:
Oldrich
I've seen another report of a similar bug.
What must be happening is that when the UPDATE_TIME is changed inside the pipeline, for whatever reason, RequestInformation is not changing the WholeExtent of the output data and so you are not seeing the imagedata change size.
You should file a bug report and attach your observations and my comment.
If you have a dataset that can be shared which I can have a copy of, please contact me off list and I'll try to look at it.
JBhttps://gitlab.kitware.com/paraview/paraview/-/issues/12371Programmable Filter: segfault on python code invalid for selected output data...2020-05-04T01:43:02-04:00Kitware RobotProgrammable Filter: segfault on python code invalid for selected output data set type**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12371). Further discussion may take place here.**
---
Sources - Time Source - Apply
Filters - Programmable Filter
Scri...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12371). Further discussion may take place here.**
---
Sources - Time Source - Apply
Filters - Programmable Filter
Script:
out = self.GetOutput()
newPoint = vtk.vtkPoints()
newPoint.InsertPoint(0, 0,0,0)
out.SetPoints(newPoint)
newCell = vtk.vtkCellArray()
vertex = vtk.vtkVertex()
vertex.GetPointIds().SetId(0,0)
newCell.InsertNextCell(vertex)
out.SetVerts(newCell)
Apply
=> An error is raised "AttributeError: SetVerts" and subsequently ParaView segfaults:
```
Program received signal SIGSEGV, Segmentation fault.
0x00007fffdf13a87e in vtkDataSetSurfaceFilter::InsertQuadInHash (this=0x33d42a0, a=2, b=6, c=7, d=3, sourceId=0)
at ParaView.git/VTK/Graphics/vtkDataSetSurfaceFilter.cxx:1644
1644 if (quad->numPts == 4 && c == quad->ptArray[2])
```
Admittedly, the user is at fault by not changing "Output Data Set Type" to "vtkPolyData" prior to hitting Apply, but ParaView should not segfault for "Same as Input"/"vtkUnstructuredGrid". Indeed, ParaView does handle the related case properly: run the same script as ProgrammableSource and select "vtkUnstructuredGrid" as "Output Data Set Type". Above's error message is raised, but no segfault is caused.
Tested with ParaView 3.10.1 official binary release for Linux 64bit and own Linux 64bit build of git master branch as of now.https://gitlab.kitware.com/paraview/paraview/-/issues/12294Scatter plot not showing Result of Calculator2020-04-08T05:27:11-04:00Kitware RobotScatter plot not showing Result of Calculator**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12294). Further discussion may take place here.**
---
When reproducing the steps as outlined below the field "Result" is not sho...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12294). Further discussion may take place here.**
---
When reproducing the steps as outlined below the field "Result" is not shown in the listing of possible x-axis data.
If you would exchange steps 3 and 2 and apply the Scatter Plot filter not to the object but to the Calculator then you would get Result listed (Step 4 is obviously not necessary then).
Best,
Arno
Steps To Reproduce:
1. Create any object (e.g. Box)
2. Apply Scatter Plot filter to object
3. Apply Calculator to object, do any calculation
4. Change input of Scatter Plot to Calculator
5. Go to Display tab of Scatter Plot
6. Choose "Use Data Array"
7. View listing for possible x-axis data
https://gitlab.kitware.com/paraview/paraview/-/issues/12076Sorting of string array columns in spreadsheet view should be Qt-disabled2020-05-04T01:36:04-04:00Kitware RobotSorting of string array columns in spreadsheet view should be Qt-disabled**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12076). Further discussion may take place here.**
---
According to a private mail thread with Sebastien, sorting the table by a ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12076). Further discussion may take place here.**
---
According to a private mail thread with Sebastien, sorting the table by a vtkStringArray is not feasible. But clicking on the column header in Qt is still possible (as opposed to e.g. the handling of a structured coordinates column). The sort order indicator even changes, but the rows don't. That is misleading to the user.https://gitlab.kitware.com/paraview/paraview/-/issues/11865ParaView crash when no access to a Xorg server.2021-06-08T11:34:39-04:00Kitware RobotParaView crash when no access to a Xorg server.**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11865). Further discussion may take place here.**
---
When run over ssh without any glx capability, paraview aborts. It this is...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11865). Further discussion may take place here.**
---
When run over ssh without any glx capability, paraview aborts. It this is expected behavior, it should not call abort() which generates a core dump, but instead simply exit. If it should be able to run without a glx context this also a bug.
$ paraview
ERROR: In /builddir/build/BUILD/ParaView-3.10.0-RC1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 404
vtkXOpenGLRenderWindow (0x2571fc0): Could not find a decent visual
ERROR: In /builddir/build/BUILD/ParaView-3.10.0-RC1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 404
vtkXOpenGLRenderWindow (0x2571fc0): Could not find a decent visual
X Error: BadValue (integer parameter out of range for operation) 2
Extension: 136 (Uknown extension)
Minor opcode: 3 (Unknown request)
Resource id: 0x21
ERROR: In /builddir/build/BUILD/ParaView-3.10.0-RC1/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 631
vtkXOpenGLRenderWindow (0x2571fc0): Cannot create GLX context. Aborting.
$ glxinfo
name of display: localhost:12.0
Error: couldn't find RGB GLX visual or fbconfighttps://gitlab.kitware.com/paraview/paraview/-/issues/11622Contour - Generate normals, gradients and scalars doesn't do anything2020-04-08T03:53:33-04:00Kitware RobotContour - Generate normals, gradients and scalars doesn't do anything**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11622). Further discussion may take place here.**
---
Local server, windows client, trunk.
Open disk_out_ref.exo.
Contour. I ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=11622). Further discussion may take place here.**
---
Local server, windows client, trunk.
Open disk_out_ref.exo.
Contour. I am contouring on temp, 400 degrees.
Select Generate Normals, Generate Gradients, and Generate Scalars. I don't see anything appear normal wise, gradient wise or scalar wise...
https://gitlab.kitware.com/paraview/paraview/-/issues/10926Custom filters are loaded before plugins, bug if custom filter refers to plug...2023-06-15T08:21:25-04:00Kitware RobotCustom filters are loaded before plugins, bug if custom filter refers to plugin proxy**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10926). Further discussion may take place here.**
---
If you make a custom filter using a proxy that was loaded by a plugin, the...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=10926). Further discussion may take place here.**
---
If you make a custom filter using a proxy that was loaded by a plugin, then the next time you start paraview the custom filter will not work. Paraview fails to load the custom filter definition because it tries to load it before loading the plugins, even if the plugins are set to auto load.https://gitlab.kitware.com/paraview/paraview/-/issues/9958Clip filter not updating when ClipType changed in Python2020-04-10T18:48:13-04:00Kitware RobotClip filter not updating when ClipType changed in Python**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9958). Further discussion may take place here.**
---
When creating and editing a clip filter in Python, the filter does not ...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9958). Further discussion may take place here.**
---
When creating and editing a clip filter in Python, the filter does not update properly after the ClipType is changed. To replicate, enter the following script in the Python shell.
wavelet = Wavelet()
clip = Clip()
clip.InsideOut = 1
clip.ClipType = "Box"
clip.ClipType.Scale = [0.5,0.5,0.5]
Show()
Render()
At this point the filters should all be executed and updated. However, the output of the clip filter is empty.https://gitlab.kitware.com/paraview/paraview/-/issues/18367When Setting the Looking Table in Pyton Shell, the Color Transfer Function Va...2021-03-23T18:52:37-04:00Mathieu Westphal (Kitware)When Setting the Looking Table in Pyton Shell, the Color Transfer Function Values table is not updated.The Color Transfer Function values table rely on Qt signal to get updated, hence is short circuited when using Python Shell.
How to reproduce :
* Open ParaView
* Source -> Wavelet -> Apply
* Color by RTData, show the Color Transfer ...The Color Transfer Function values table rely on Qt signal to get updated, hence is short circuited when using Python Shell.
How to reproduce :
* Open ParaView
* Source -> Wavelet -> Apply
* Color by RTData, show the Color Transfer Function Values
* Views -> PythonShell
* `rTDataLUT = GetColorTransferFunction('RTData')`
* `rTDataLUT.RGBPoints = [37.35310363769531, 0.231373, 0.298039, 0.752941, 157.0909652709961, 0.865003, 0.865003, 0.865003, 200.0909652709961, 0.865003, 0.865003, 0.865003, 276.8288269042969, 0.705882, 0.0156863, 0.14902]`
* Color Transfer Function Values is not updated
* Adding a control point by clicking in the color map editor fix ithttps://gitlab.kitware.com/paraview/paraview/-/issues/12535D3 divde cells mode broken2018-08-28T09:39:49-04:00Kitware RobotD3 divde cells mode broken**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12535). Further discussion may take place here.**
---
The D3 filter has stopped working when in divide cells mode. To repli...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=12535). Further discussion may take place here.**
---
The D3 filter has stopped working when in divide cells mode. To replicate, do the following:
1. Run ParaView client/server or multicore with 8 process. (Less will probably also cause the failure, but I haven't tried.)
2. Open the attached CurvedCylinder.vtu. Apply.
3. Run D3, change to Divide cells boundary mode. Apply. (Note that there is a separate modification bug with D3 where if you change the boundary mode after the first apply, the filter will not re-execute.)
The result is wonky. (See the attached image.) This problem is not in ParaView 3.10, but it is in the latest master branch.5.2 (SC-16)https://gitlab.kitware.com/paraview/paraview/-/issues/18403Exodus data not read correctly?2021-03-29T08:09:37-04:00Nico SchlömerExodus data not read correctly?Here's a funny issue with an Exodus file ([test.e](/uploads/60f24f326cd43b5bae94f44a41d2f61e/test.e)). It contains two triangles, four nodes, and on the four nodes two data points `a` and `b`. The data can be read with, e.g.,
```python
...Here's a funny issue with an Exodus file ([test.e](/uploads/60f24f326cd43b5bae94f44a41d2f61e/test.e)). It contains two triangles, four nodes, and on the four nodes two data points `a` and `b`. The data can be read with, e.g.,
```python
import netCDF4
nc = netCDF4.Dataset("test.e")
names = nc.variables["name_nod_var"]
names.set_auto_mask(False)
point_data_names = [b"".join(c).decode("UTF-8") for c in names[:]]
print(point_data_names)
value1 = nc.variables["vals_nod_var1"]
value1.set_auto_mask(False)
print(value1[:])
value2 = nc.variables["vals_nod_var2"]
value2.set_auto_mask(False)
print(value2[:])
```
Output:
```
['a', 'b']
[[0.5488135 0.71518937 0.60276338 0.54488318]]
[[0.4236548 0.64589411 0.43758721 0.891773 ]]
```
Looks good. Now, when opening the file with ParaView, the node coordinates and the connectivity are read alright, but the data is off:
![off](/uploads/a551246cdbc02a33aa6e10ad21c0e666/off.png)
Is this a ParaView bug?https://gitlab.kitware.com/paraview/paraview/-/issues/18429Near clipping plane error2021-03-23T18:55:49-04:00Golyakov AlexsandrNear clipping plane errorHi,
I am using ParaView 5.5.2 to visualize a volume.
In parallel projection when the near plane is very close to zero, the accuracy of the overall Z depth starts to fall apart and object is clipped.
Аnyone can help me, please.
![err...Hi,
I am using ParaView 5.5.2 to visualize a volume.
In parallel projection when the near plane is very close to zero, the accuracy of the overall Z depth starts to fall apart and object is clipped.
Аnyone can help me, please.
![error2](/uploads/1108068d0e249015226debe9501ccaf9/error2.mp4)![NearPlaneError](/uploads/e657f7ff1759900a13b5313751e7fe62/NearPlaneError.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18439Color map editor/ Mapping data vibrates2018-10-04T18:15:08-04:00W. Alan ScottColor map editor/ Mapping data vibratesI have a state file that shows the color map editor/ mapping data vibrating. The color map is moving left and right, at maybe 20 Hz, and moving about 1 millimeter. State file is attached. After thinking about it, I bet we are seeing w...I have a state file that shows the color map editor/ mapping data vibrating. The color map is moving left and right, at maybe 20 Hz, and moving about 1 millimeter. State file is attached. After thinking about it, I bet we are seeing where the front and back buffer were drawn in slightly different spots, and the "vibration" is just an ongoing buffer swap.
* 5.6.0-rc1, Linux, builtin server. (Originally seen on a remote server.)
* Load the attached state file.
* In the pipeline browser, select the first Clip (Clip1).
You should see the Color Map Editor vibrating. This is a bug.
@utkarsh.ayachit @cory.quammen Can you replicate thus bug? Should we try to fix this for 5.6, or 5.7? (I'm guessing 5.7, but I really hate this bug...)
[vibrateB.pvsm](/uploads/2528000602666a87c743e1ce17570aec/vibrateB.pvsm)5.7 (Summer 2019)Utkarsh AyachitUtkarsh Ayachithttps://gitlab.kitware.com/paraview/paraview/-/issues/18488Numpy Runtime Warning with cinema export2019-06-27T11:46:13-04:00Ethan StamNumpy Runtime Warning with cinema exportTested with 5.6.0-RC2, local MacOS
To recreate:
* Sources -> Wavelet -> apply
* Color by surface and RTData
* File -> export scene
* Keep options default, but change static to phi-theta or azimuth-elevation-roll
* save
The export...Tested with 5.6.0-RC2, local MacOS
To recreate:
* Sources -> Wavelet -> apply
* Color by surface and RTData
* File -> export scene
* Keep options default, but change static to phi-theta or azimuth-elevation-roll
* save
The export finishes, but I get this warning at the end:
/Users/stam/anaconda/lib/python2.7/site-packages/numpy/core/_methods.py:32: RuntimeWarning: invalid value encountered in reduce
<br/> return umr_minimum(a, axis, None, out, keepdims, initial)
/Users/stam/anaconda/lib/python2.7/site-packages/numpy/core/_methods.py:28: RuntimeWarning: invalid value encountered in reduce
<br/> return umr_maximum(a, axis, None, out, keepdims, initial)
<br/>Finished exporting Cinema database!5.7 (Summer 2019)https://gitlab.kitware.com/paraview/paraview/-/issues/18490ospray and embree won't build with cray programming environment in paraview 5.62018-09-27T18:14:14-04:00David E. DeMarleospray and embree won't build with cray programming environment in paraview 5.6Per discourse discussion:
https://discourse.paraview.org/t/building-5-6-0-rc1-on-cray/570
confirmed on theta@anlPer discourse discussion:
https://discourse.paraview.org/t/building-5-6-0-rc1-on-cray/570
confirmed on theta@anl5.6 (Fall 2018)David E. DeMarleDavid E. DeMarlehttps://gitlab.kitware.com/paraview/paraview/-/issues/18495Crash with Contingency Statistics filter2020-05-05T01:10:10-04:00Joachim PouderouxCrash with Contingency Statistics filterContingency Statistics filter requires pairs of attributes. But if input has a single attributes, it just crashes instead of printing an error.
How to reproduce:
- Create a Wavelet
- Apply the Contingency Statistics filter (default se...Contingency Statistics filter requires pairs of attributes. But if input has a single attributes, it just crashes instead of printing an error.
How to reproduce:
- Create a Wavelet
- Apply the Contingency Statistics filter (default settings) => * crash *https://gitlab.kitware.com/paraview/paraview/-/issues/18496Image Gradient filter giving warnings when no active scalars2021-03-23T18:54:53-04:00Kenneth MorelandImage Gradient filter giving warnings when no active scalarsWhen you apply the `Gradient` filter (`vtkImageGradient` under the covers), you get _thousands_ of the following warning if your data does not have an active scalar field (and instead selected from a list).
```
ERROR: In C:\bbd\2d618e80...When you apply the `Gradient` filter (`vtkImageGradient` under the covers), you get _thousands_ of the following warning if your data does not have an active scalar field (and instead selected from a list).
```
ERROR: In C:\bbd\2d618e80\build\superbuild\paraview\src\VTK\Common\DataModel\vtkImageData.cxx, line 1324
vtkImageData (000002942B446150): No Scalar Field has been specified - assuming 1 component!
```
To replicate, do the following.
1. Open `disk_out_ref.ex2`. Load all variables. Apply.
2. Add `Resample To Image` filter. Apply.
3. Add the `Gradient` filter. Apply.
The output messages window will pop up with lots and lots of the aforementioned warning.
This problem was [reported on discourse](https://discourse.paraview.org/t/numerics-of-gradient-of-unstructured-dataset-filter/638/9)https://gitlab.kitware.com/paraview/paraview/-/issues/18497Image Gradient filter loses origin and spacing information2021-03-23T18:54:42-04:00Kenneth MorelandImage Gradient filter loses origin and spacing informationWhen you apply the `Gradient` filter (`vtkImageGradient` under the covers), the resulting image data set does not have its origin and spacing properly set. Instead, they are set to their defaults, which causes the result to potentially b...When you apply the `Gradient` filter (`vtkImageGradient` under the covers), the resulting image data set does not have its origin and spacing properly set. Instead, they are set to their defaults, which causes the result to potentially be translated and scaled.
To replicate, do the following.
1. Open `disk_out_ref.ex2`. Load all variables. Apply.
2. Add `Resample To Image` filter. Apply.
3. Add the `Gradient` filter. Apply.
4. Turn the visibility of the `Resample To Image`filter back on.
You will see that the outline of the `Gradient` filter does not match its input. It is much larger, square, and off center. If you look in the information tab, you will see that, unlike its input, its bounds match its extents because the origin and spacing were not set correctly.
This problem was [reported on discourse](https://discourse.paraview.org/t/numerics-of-gradient-of-unstructured-dataset-filter/638/9).https://gitlab.kitware.com/paraview/paraview/-/issues/18504AutoConvert Properties cannot select converted array2021-07-09T08:01:41-04:00Mathieu Westphal (Kitware)AutoConvert Properties cannot select converted arrayThey are multiple bugs with the AutoConvert Properties Setting :
1. Point and cell arrays with the same name do not allow selection in a combo box if there is more than on point data array.
How to reproduce :
* Open ParaView
* Creat...They are multiple bugs with the AutoConvert Properties Setting :
1. Point and cell arrays with the same name do not allow selection in a combo box if there is more than on point data array.
How to reproduce :
* Open ParaView
* Create a Wavelet, Apply
* Create a Calc, "RTData", Apply
* Use PointDataToCellData, pass PointArray to ON, Apply
* Edit->Settings->AutoConvert Properties to on
* Create a Contour
* Try to select the Cell Array RTData or Result, not possible
This may be related to #18505 and #18506.https://gitlab.kitware.com/paraview/paraview/-/issues/18505AutoConvert properties selecting an converted array has no effet2021-07-09T07:59:23-04:00Mathieu Westphal (Kitware)AutoConvert properties selecting an converted array has no effetWhen selecting a converted array and no non converted array is available in the domain, this has no effect.
How to reproduce :
* Open ParaView
* Create a Wavelet
* Add a calc, RTData/2, Apply
* Add a PointDataToCellData, Apply
* Co...When selecting a converted array and no non converted array is available in the domain, this has no effect.
How to reproduce :
* Open ParaView
* Create a Wavelet
* Add a calc, RTData/2, Apply
* Add a PointDataToCellData, Apply
* Contour, Apply
* Select RTData instead of Result in the contour
* No changes and the filter is not reexecuted.
Due to a check in pqFieldSelectionAdaptor
May be related to #18504 #18506https://gitlab.kitware.com/paraview/paraview/-/issues/18506PassArray is buggy with AutoConvertProperties2021-03-23T18:59:40-04:00Mathieu Westphal (Kitware)PassArray is buggy with AutoConvertPropertiesPassArrays behave strangely when using AutoConvert Properties.
How to reproduce :
* Open ParaView
* Create Wavelet
* Add Calc, "RTData", Apply
* PassArrays
* The two Point Arrays are availableas cell array, which is arguably not co...PassArrays behave strangely when using AutoConvert Properties.
How to reproduce :
* Open ParaView
* Create Wavelet
* Add Calc, "RTData", Apply
* PassArrays
* The two Point Arrays are availableas cell array, which is arguably not correct
* Selecting the cell arrays does not generate them in the output.
may be related to #18504 #18505https://gitlab.kitware.com/paraview/paraview/-/issues/18507RandomAttributes filter do not pass point/cell arrays when generating point/c...2021-03-23T18:59:31-04:00Mathieu Westphal (Kitware)RandomAttributes filter do not pass point/cell arrays when generating point/cell arraysRandomAttributes filter remove input point/cell scalars/vectors when generating point/cell scalars/vectors random arrays
How to reproduce :
* Open ParaView
* Create Wavelet, Apply
* Add a calculator, "RTData", Apply
* "Results" is n...RandomAttributes filter remove input point/cell scalars/vectors when generating point/cell scalars/vectors random arrays
How to reproduce :
* Open ParaView
* Create Wavelet, Apply
* Add a calculator, "RTData", Apply
* "Results" is now the scalars in the output
* Add a RandomAttributes, Generate PointScalars, Apply
* Results is not available in output anymore.
* behavior is the same with vectors and cell data
It actually removes the *Active* scalars or vectors.https://gitlab.kitware.com/paraview/paraview/-/issues/18519video export broken for transparent background2024-03-19T18:41:16-04:00Philip Eisenlohrvideo export broken for transparent backgroundExporting an animation as either AVI or OGV with the option "transparent background" checked does result in output that is strided.
Exemplary [correct](/uploads/9ec6cc02b4b5c1372948dd60a0cc9899/dogbone_stretching.avi) and [broken](/uplo...Exporting an animation as either AVI or OGV with the option "transparent background" checked does result in output that is strided.
Exemplary [correct](/uploads/9ec6cc02b4b5c1372948dd60a0cc9899/dogbone_stretching.avi) and [broken](/uploads/dc5d4aa00941885a53de83a3606e253a/dogbone_stretching_transparent.avi) videos created with 5.6.0 RC2 on macOS Mojave 10.14 are attached.5.13 (Summer 2024)https://gitlab.kitware.com/paraview/paraview/-/issues/18520Some filters duplicate arrays with AutoConvert properties2021-03-23T18:57:17-04:00Mathieu Westphal (Kitware)Some filters duplicate arrays with AutoConvert propertiesWhen enabling auto convert properties, certain filters duplicate converted arrays.
How to reproduce :
* run paraview
* Wavelet, Apply
* RandomAttributes, Enable CellScalars, Apply
* Enable AutoConvert Properties
* Contour, select R...When enabling auto convert properties, certain filters duplicate converted arrays.
How to reproduce :
* run paraview
* Wavelet, Apply
* RandomAttributes, Enable CellScalars, Apply
* Enable AutoConvert Properties
* Contour, select RandomCellScalars, Apply
* RandomCellScalars is now available as a point data as wellhttps://gitlab.kitware.com/paraview/paraview/-/issues/18528[5.6 rc2] Reset Session reset all customized MACROS shortcuts2020-04-30T18:50:02-04:00ym jia[5.6 rc2] Reset Session reset all customized MACROS shortcutsBuild with -G "Visual Studio 12 2013 Win64"
other cmake settings:
* python 3.6.5
* QT 5.9.1
* CMAKE_CXX_MP_FLAG
* BUILD_SHARED_LIBS
Another question:
Could someone tell me where to find saved shortcuts? I want to make shortcuts settin...Build with -G "Visual Studio 12 2013 Win64"
other cmake settings:
* python 3.6.5
* QT 5.9.1
* CMAKE_CXX_MP_FLAG
* BUILD_SHARED_LIBS
Another question:
Could someone tell me where to find saved shortcuts? I want to make shortcuts settings portable, thanks!5.8.1Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18574Undoing a Proxy Deletion does not initialize ProxyListDomain2021-03-23T19:00:43-04:00Mathieu Westphal (Kitware)Undoing a Proxy Deletion does not initialize ProxyListDomainUndoing the deletion of a filter does not initialize its proxy list domain.
How to reproduce :
* Open ParaView
* Create a Wavelet, Apply
* Create a Clip, Apply
* Delete the clip
* Undo
* Click on Clip filter
* ClipType is not ini...Undoing the deletion of a filter does not initialize its proxy list domain.
How to reproduce :
* Open ParaView
* Create a Wavelet, Apply
* Create a Clip, Apply
* Delete the clip
* Undo
* Click on Clip filter
* ClipType is not initialized and the visible result is incorrecthttps://gitlab.kitware.com/paraview/paraview/-/issues/18584Tiled Screenshots/Animations with NVIDIA IndeX + Higher Resolution than Screen2019-10-29T21:25:00-04:00Kelton HalbertTiled Screenshots/Animations with NVIDIA IndeX + Higher Resolution than ScreenWhen saving a screenshot or animation at a higher resolution than the window, the image gets tiled. This is in the latest nightly build (ParaView-5.6.0-RC2-342-gf3429ab-Qt5-MPI-Linux-64bit) using the NVIDIA IndeX plugin to render the ima...When saving a screenshot or animation at a higher resolution than the window, the image gets tiled. This is in the latest nightly build (ParaView-5.6.0-RC2-342-gf3429ab-Qt5-MPI-Linux-64bit) using the NVIDIA IndeX plugin to render the image. This is definitely not an ideal behavior and figured I'd see if anyone here knows about it.
[Screenshot+2018-10-31+04.34.58](/uploads/d000de9234b844ed74dcaf7d00d4519c/Screenshot+2018-10-31+04.34.58.png)
Cheers,
Kelton.5.7 (Summer 2019)Ben BoeckelBen Boeckelhttps://gitlab.kitware.com/paraview/paraview/-/issues/18610Segmentation fault when loading Tecplot binary files2021-03-24T11:30:25-04:00Aquan1412Segmentation fault when loading Tecplot binary filesParaview crashes with a segmentation fault when a Tecplot binary file is imported via the VisIt bridge. More information can be found in the following thread: https://discourse.paraview.org/t/segmentation-fault-when-loading-tecplot-binar...Paraview crashes with a segmentation fault when a Tecplot binary file is imported via the VisIt bridge. More information can be found in the following thread: https://discourse.paraview.org/t/segmentation-fault-when-loading-tecplot-binary-files/764
Information about the system:
- OS: OpenSuse 42.2 64bit
- ParaView Version: 5.5.2 and 5.60-RC2
A exemplary plt file is attached to reproduce the behaviour.[Cylinder_Surface.plt](/uploads/093b5480c49892e120cce57077e1ad02/Cylinder_Surface.plt)https://gitlab.kitware.com/paraview/paraview/-/issues/18614Volume representation is broken when switching arrays for the same representa...2021-03-23T19:05:22-04:00Mathieu Westphal (Kitware)Volume representation is broken when switching arrays for the same representationVolume representation does not manage range correctly when switching arrays for the same representation.
This bug is present in ParaView 5.6, but not in ParaView 5.5.2.
This may be a VTK bug.
How to reproduce :
* Open ParaView
* Wavel...Volume representation does not manage range correctly when switching arrays for the same representation.
This bug is present in ParaView 5.6, but not in ParaView 5.5.2.
This may be a VTK bug.
How to reproduce :
* Open ParaView
* Wavelet, Apply
* Calculator, RTData*10000, Apply
* Select "Results" as an array to show
* Select "Volume Representation" as a representation
* Everything is fine, representation is correct.
* Select "RTData" as an array to show
* Representation is clearly wrong, even though the scalar map range seems correct
* There is no way to fix it except by deleting and recreating a view.
![VolRepFail](/uploads/352ef0812758bb54cbf8ff6120124e14/VolRepFail.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18625Segfault in paraview 5.6.0 when right clicking in renderview on a tube filter...2020-05-12T21:32:25-04:00Thomas BangelsSegfault in paraview 5.6.0 when right clicking in renderview on a tube filter linked to a programmable sourceI have written a macro to read data from our own custom data files, using the programmable source (to reduce data storage). It works very good, except for one specific case.
When I load a line object, put a tube on it and afterwards try...I have written a macro to read data from our own custom data files, using the programmable source (to reduce data storage). It works very good, except for one specific case.
When I load a line object, put a tube on it and afterwards try to right click on the tube, I get a segmentation fault (core dumped).
![image](/uploads/305dfa7b6cb8893dbcfeb0074ea8a3f0/image.png)
However, for other objects (lines, points, spheres, triangles) the right click works as expected.
Notes:
- I'm using paraview 5.6.0 (downloaded as binary package) on Ubuntu 18.04.
- When I load the PolyData line object using .vtp-files instead of the programmable source, then there is no problem. (However, writing vtp's is really not desirable because it takes up a lot of hard drive space.)
- In paraview 5.5.2, everything worked perfectly. (But the scratched OSPRay material is a really big advantage in paraview 5.6.0)
If needed, I can provide my reader macro's and the data files.https://gitlab.kitware.com/paraview/paraview/-/issues/18633Hide Block does not hide BACKFACE2023-08-17T06:03:39-04:00ym jiaHide Block does not hide BACKFACEHide Block works perfectly when Backface Representation Set to "Follow Frontface", but when I use "Surface" to achieve different color between Front/Back face, Hide block only hide front face, which looks weird.
I Grouped two Box() to a...Hide Block works perfectly when Backface Representation Set to "Follow Frontface", but when I use "Surface" to achieve different color between Front/Back face, Hide block only hide front face, which looks weird.
I Grouped two Box() to a multiblock dataset, then hide the left one:
![hide_block](/uploads/168bb9f6a83b0fded1d382f2a982d98b/hide_block.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18634Some multiblock database backface settings cause crash2021-04-01T15:53:24-04:00ym jiaSome multiblock database backface settings cause crash**Backface Representation** values "Points", "Wireframe", "Surface", and "Surface With Edges" cause a crash with multiblock data. To reproduce:
* Run paraview, built-in server
* Add **Plane** source. Apply. Change its **Backface Represe...**Backface Representation** values "Points", "Wireframe", "Surface", and "Surface With Edges" cause a crash with multiblock data. To reproduce:
* Run paraview, built-in server
* Add **Plane** source. Apply. Change its **Backface Representation** to "Points", then "Wireframe", then "Surface", then "Surface With Edges". This works.
* Load `can.ex2` from the examples directory. Apply. Change it's **Backface Representation** to "Points", or "Wireframe", or "Surface", or "Surface With Edges". Crash.
Stack trace excerpt:
```
=================================================================
==62619==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x6020003ef4d4 at pc 0x00010fc01c8c bp 0x7ffee9936a90 sp 0x7ffee9936a88
READ of size 1 at 0x6020003ef4d4 thread T0
#0 0x10fc01c8b in void std::__1::allocator<unsigned char>::construct<unsigned char, unsigned char const&>(unsigned char*, unsigned char const&) memory:1881
#1 0x10fc01c0f in void std::__1::allocator_traits<std::__1::allocator<unsigned char> >::__construct<unsigned char, unsigned char const&>(std::__1::integral_constant<bool, true>, std::__1::allocator<unsigned char>&, unsigned char*, unsigned char const&) memory:1773
#2 0x10fc01b4a in void std::__1::allocator_traits<std::__1::allocator<unsigned char> >::construct<unsigned char, unsigned char const&>(std::__1::allocator<unsigned char>&, unsigned char*, unsigned char const&) memory:1600
#3 0x10fc0159e in void std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >::__construct_one_at_end<unsigned char const&>(unsigned char const&) vector:924
#4 0x10fbbe13e in std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >::push_back(unsigned char const&) vector:1637
#5 0x10fbbd807 in vtkOpenGLPolyDataMapper::AppendCellTextures(vtkRenderer*, vtkActor*, vtkCellArray**, int, std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >&, std::__1::vector<float, std::__1::allocator<float> >&, vtkPolyData*, vtkOpenGLCellToVTKCellMap*) vtkOpenGLPolyDataMapper.cxx:3741
#6 0x10f855d40 in vtkCompositeMapperHelper2::AppendOneBufferObject(vtkRenderer*, vtkActor*, vtkCompositeMapperHelperData*, long long&, std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >&, std::__1::vector<float, std::__1::allocator<float> >&) vtkCompositePolyDataMapper2.cxx:773
#7 0x10f8505e7 in vtkCompositeMapperHelper2::BuildBufferObjects(vtkRenderer*, vtkActor*) vtkCompositePolyDataMapper2.cxx:532
#8 0x10fbbc058 in vtkOpenGLPolyDataMapper::UpdateBufferObjects(vtkRenderer*, vtkActor*) vtkOpenGLPolyDataMapper.cxx:3653
#9 0x10fbb8215 in vtkOpenGLPolyDataMapper::RenderPieceStart(vtkRenderer*, vtkActor*) vtkOpenGLPolyDataMapper.cxx:3393
#10 0x10f84bc3d in vtkCompositeMapperHelper2::RenderPiece(vtkRenderer*, vtkActor*) vtkCompositePolyDataMapper2.cxx:312
#11 0x10f8683db in vtkCompositePolyDataMapper2::Render(vtkRenderer*, vtkActor*) vtkCompositePolyDataMapper2.cxx:1896
#12 0x10f98edda in vtkOpenGLActor::Render(vtkRenderer*, vtkMapper*) vtkOpenGLActor.cxx:104
#13 0x121b8afaf in vtkPVLODActor::Render(vtkRenderer*, vtkMapper*) vtkPVLODActor.cxx:141
...
0x6020003ef4d4 is located 0 bytes to the right of 4-byte region [0x6020003ef4d0,0x6020003ef4d4)
allocated by thread T0 here:
#0 0x11b4011dd in wrap_malloc+0x9d (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x491dd)
#1 0x118d0b9d2 in vtkBuffer<unsigned char>::Allocate(long long) vtkBuffer.h:178
#2 0x119bb43e0 in vtkAOSDataArrayTemplate<unsigned char>::AllocateTuples(long long) vtkAOSDataArrayTemplate.txx:426
#3 0x118e7eb7f in vtkGenericDataArray<vtkAOSDataArrayTemplate<unsigned char>, unsigned char>::AllocateTuples(long long) vtkGenericDataArray.h:337
#4 0x118e7a6a3 in vtkGenericDataArray<vtkAOSDataArrayTemplate<unsigned char>, unsigned char>::Allocate(long long, long long) vtkGenericDataArray.txx:386
#5 0x118e7ad5f in vtkGenericDataArray<vtkAOSDataArrayTemplate<unsigned char>, unsigned char>::SetNumberOfTuples(long long) vtkGenericDataArray.txx:474
#6 0x119a58750 in vtkScalarsToColors::MapScalars(vtkAbstractArray*, int, int, int) vtkScalarsToColors.cxx:292
#7 0x1115f4837 in vtkMapper::MapScalars(vtkDataSet*, double, int&) vtkMapper.cxx:533
#8 0x1115f2bdc in vtkMapper::MapScalars(vtkDataSet*, double) vtkMapper.cxx:427
#9 0x10f854fea in vtkCompositeMapperHelper2::AppendOneBufferObject(vtkRenderer*, vtkActor*, vtkCompositeMapperHelperData*, long long&, std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >&, std::__1::vector<float, std::__1::allocator<float> >&) vtkCompositePolyDataMapper2.cxx:715
#10 0x10f8505e7 in vtkCompositeMapperHelper2::BuildBufferObjects(vtkRenderer*, vtkActor*) vtkCompositePolyDataMapper2.cxx:532
#11 0x10fbbc058 in vtkOpenGLPolyDataMapper::UpdateBufferObjects(vtkRenderer*, vtkActor*) vtkOpenGLPolyDataMapper.cxx:3653
#12 0x10fbb8215 in vtkOpenGLPolyDataMapper::RenderPieceStart(vtkRenderer*, vtkActor*) vtkOpenGLPolyDataMapper.cxx:3393
#13 0x10f84bc3d in vtkCompositeMapperHelper2::RenderPiece(vtkRenderer*, vtkActor*) vtkCompositePolyDataMapper2.cxx:312
#14 0x10f8683db in vtkCompositePolyDataMapper2::Render(vtkRenderer*, vtkActor*) vtkCompositePolyDataMapper2.cxx:1896
```
Note that this doesn't always cause a crash unless you build with asan.
** Original posting **
I have written some filters with vtkMultiblockDataSet output. But it will crash if ActiveVariable set to **vtkBlockColors**.
To reproduce, run following scripts ([vtkBlockColors_crash.py](/uploads/6bbf76ba575f973b7ab9b48b755f1049/vtkBlockColors_crash.py) ) and change **ActiveVariable** of GroupDataSet output to **vtkBlockColors**. My paraview(vs2013 Win64, 5.6) crash 5 times every 10 attempts
![color_crash](/uploads/251cf2232e7232aeed3219150cc9434a/color_crash.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18641VTK_EMPTY_CELL selection crashes paraview2021-04-28T08:33:26-04:00Mathieu Westphal (Kitware)VTK_EMPTY_CELL selection crashes paraviewSelecting a VTK_EMPTY_CELL in ParaView segfaults it.
Steps to reproduce :
* Open [file.vtu](/uploads/ebda60f3b6fdca5464790a105fe54407/file.vtu), Apply
* Show in spreadsheet view, Cell Data
* Click on "Empty" until it crashes
```
Thr...Selecting a VTK_EMPTY_CELL in ParaView segfaults it.
Steps to reproduce :
* Open [file.vtu](/uploads/ebda60f3b6fdca5464790a105fe54407/file.vtu), Apply
* Show in spreadsheet view, Cell Data
* Click on "Empty" until it crashes
```
Thread 1 "paraview" received signal SIGSEGV, Segmentation fault.
vtkDataSetSurfaceFilter::UnstructuredGridExecute (this=0x555559b20550, dataSetInput=0x55555a817f60, output=0x55555a8bfd00)
at /home/glow/work/paraview/paraview/VTK/Filters/Geometry/vtkDataSetSurfaceFilter.cxx:2178
2178 q->ptArray[i] = this->GetOutputPointId(q->ptArray[i], input, newPts, outputPD);
(gdb) bt
#0 vtkDataSetSurfaceFilter::UnstructuredGridExecute (this=0x555559b20550, dataSetInput=0x55555a817f60, output=0x55555a8bfd00)
at /home/glow/work/paraview/paraview/VTK/Filters/Geometry/vtkDataSetSurfaceFilter.cxx:2178
#1 0x00007ffff44f1923 in vtkPVGeometryFilter::UnstructuredGridExecute (this=0x555559b21e00, input=0x55555a817f60, output=0x55555a8bfd00,
doCommunicate=1) at /home/glow/work/paraview/paraview/ParaViewCore/VTKExtensions/Rendering/vtkPVGeometryFilter.cxx:1461
#2 0x00007ffff44ecfde in vtkPVGeometryFilter::ExecuteBlock (this=0x555559b21e00, input=0x55555ab8d200, output=0x55555a8bfd00,
doCommunicate=1, updatePiece=0, updateNumPieces=1, updateGhosts=0, wholeExtent=0x55555863a770)
at /home/glow/work/paraview/paraview/ParaViewCore/VTKExtensions/Rendering/vtkPVGeometryFilter.cxx:497
#3 0x00007ffff44ed2b8 in vtkPVGeometryFilter::RequestData (this=0x555559b21e00, request=0x555559b35a70, inputVector=0x55555a8ba830,
outputVector=0x555559b32e90) at /home/glow/work/paraview/paraview/ParaViewCore/VTKExtensions/Rendering/vtkPVGeometryFilter.cxx:560
#4 0x00007fffee21f524 in vtkDataObjectAlgorithm::ProcessRequest (this=0x555559b21e00, request=0x555559b35a70, inputVector=0x55555a8ba830,
outputVector=0x555559b32e90) at /home/glow/work/paraview/paraview/VTK/Common/ExecutionModel/vtkDataObjectAlgorithm.cxx:86
#5 0x00007fffee229c37 in vtkExecutive::CallAlgorithm (this=0x555559b332e0, request=0x555559b35a70, direction=1, inInfo=0x55555a8ba830,
outInfo=0x555559b32e90) at /home/glow/work/paraview/paraview/VTK/Common/ExecutionModel/vtkExecutive.cxx:773
#6 0x00007fffee2219a3 in vtkDemandDrivenPipeline::ExecuteData (this=0x555559b332e0, request=0x555559b35a70, inInfo=0x55555a8ba830,
outInfo=0x555559b32e90) at /home/glow/work/paraview/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:490
#7 0x00007fffee217267 in vtkCompositeDataPipeline::ExecuteData (this=0x555559b332e0, request=0x555559b35a70, inInfoVec=0x55555a8ba830,
outInfoVec=0x555559b32e90) at /home/glow/work/paraview/paraview/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx:171
#8 0x00007fffee22109d in vtkDemandDrivenPipeline::ProcessRequest (this=0x555559b332e0, request=0x555559b35a70, inInfoVec=0x55555a8ba830,
outInfoVec=0x555559b32e90) at /home/glow/work/paraview/paraview/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx:273
#9 0x00007fffee273cc7 in vtkStreamingDemandDrivenPipeline::ProcessRequest (this=0x555559b332e0, request=0x555559b35a70,
inInfoVec=0x55555a8ba830, outInfoVec=0x555559b32e90)
at /home/glow/work/paraview/paraview/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx:354
```https://gitlab.kitware.com/paraview/paraview/-/issues/18658Clip filter remove duplicated points in polyvertex cells2021-03-23T19:11:30-04:00Mathieu Westphal (Kitware)Clip filter remove duplicated points in polyvertex cellsvtkClipDataSet uses a vtkMergePoints as a locator and since it is used for poly vertex cells.
This merge points which is not an expected behavior of the clip filter.
How to reproduce :
* Open paraview
* Open [polyvertex.vtu](/uploads/...vtkClipDataSet uses a vtkMergePoints as a locator and since it is used for poly vertex cells.
This merge points which is not an expected behavior of the clip filter.
How to reproduce :
* Open paraview
* Open [polyvertex.vtu](/uploads/03d769550bbf101411920d312242695c/polyvertex.vtu), Apply, check number of points (66)
* Add a clip, select Sphere, agment sphere size to englobe all points, Apply
* Check number of points (33 but should be 66)https://gitlab.kitware.com/paraview/paraview/-/issues/18670crash when opening obj file2020-07-24T12:46:55-04:00Studentcrash when opening obj fileParaview crashed when I clicked "apply" button after opening an obj file, which can be opened perfectly using Meshlab.
The file is [paraview-crash.obj](/uploads/c11c818966f62b50f6512249804de284/paraview-crash.obj)
My operating system is...Paraview crashed when I clicked "apply" button after opening an obj file, which can be opened perfectly using Meshlab.
The file is [paraview-crash.obj](/uploads/c11c818966f62b50f6512249804de284/paraview-crash.obj)
My operating system is Linux Mint 18 Cinnamon 64-bit, Cinnamon Version 3.0.7. Linux Kernel is 4.4.0-101-generic. I am using ParaView-5.6.0-RC2-Qt5-MPI-Linux-64bit, which is downloaded from https://www.paraview.org/download/
I think this crash may be caused by a failure of handling the normal of triangles in the mesh.
Thanks in advance.https://gitlab.kitware.com/paraview/paraview/-/issues/18674XML Overriden property belonging in a PropertyGroup are not correctly supported2021-09-21T04:22:22-04:00Mathieu Westphal (Kitware)XML Overriden property belonging in a PropertyGroup are not correctly supportedAn overridden XML property that is part of a PropertyGroup is not displayed in said PropertyGroup and causes a warning.
How to reproduce :
- Open ParaView
- load this XML [plugin](/uploads/b509834c01b499ca9ed35c3950ed8cbb/OverrideXMLOn...An overridden XML property that is part of a PropertyGroup is not displayed in said PropertyGroup and causes a warning.
How to reproduce :
- Open ParaView
- load this XML [plugin](/uploads/b509834c01b499ca9ed35c3950ed8cbb/OverrideXMLOnly.xml)
- Wavelet, Apply
- MyGlyph, Apply
```
Warning: In /home/glow/work/paraview/paraviewThird/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyGroup.cxx, line 197
vtkSMPropertyGroup (0x556628f27190): Failed to locate property 'Stride' for PropertyGroup. Skipping.
Warning: In /home/glow/work/paraview/paraviewThird/paraview/ParaViewCore/ServerManager/Core/vtkSMPropertyGroup.cxx, line 197
vtkSMPropertyGroup (0x55662cdb0150): Failed to locate property 'Stride' for PropertyGroup. Skipping.
```
![2018-12-19-143548_270x121_scrot](/uploads/911d4f5d013d6937d633bb93b257e5ac/2018-12-19-143548_270x121_scrot.png)
(In the image, stride is not part of the same group as Glyph Mode when it should)https://gitlab.kitware.com/paraview/paraview/-/issues/18677Gradient background second color ignored2021-05-11T18:16:39-04:00David ThompsonGradient background second color ignoredIn ParaView 5.6.0 (at least on macos 10.14), choosing a gradient background and setting the second color to a non-default value does not work. The second color (which is counterintuitively used at the top of the screen rather than the bo...In ParaView 5.6.0 (at least on macos 10.14), choosing a gradient background and setting the second color to a non-default value does not work. The second color (which is counterintuitively used at the top of the screen rather than the bottom) is always the default blue.
![Screen_Shot_2018-12-22_at_10.13.50](/uploads/69987c59060fb5af88b7efd826931aec/Screen_Shot_2018-12-22_at_10.13.50.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18694BagPlot selection does not make much sense2021-03-23T19:08:52-04:00Mathieu Westphal (Kitware)BagPlot selection does not make much senseSelecting data in the spreadsheet view does not make much sense when represented in an Functional Bag Plot or Bag Chart View.
How to reproduce :
* Open ParaView
* Open sinewaves.csv, Apply
* ExtractBagPlot, Apply
* Split view in two...Selecting data in the spreadsheet view does not make much sense when represented in an Functional Bag Plot or Bag Chart View.
How to reproduce :
* Open ParaView
* Open sinewaves.csv, Apply
* ExtractBagPlot, Apply
* Split view in two, create spreadsheet view, show ExtractBagPlot row data in it
* Split view in two, create bag chart view, Show ExtractBagPlot in it
* Select line n in SpreadsheetView with n < 30, Yn data is selected in the functionnal bag plot view and in bag chart view, this does not seems right.
* Select line 30 in SpreadsheetView, "95%" data is selectin in the functional bag plot view and a nonexistent point is selected in the bag chart view, that does not seem right.
* Select line 31 in SpreadsheetView, "50%" data is selectin in the functional bag plot view and the same nonexistent point is selected in the bag chart view, that does not seem right.
* Select line 32 in SpreadsheetView, FunctionalBagPlot shows a new vtkOriginalIndices plot, that does not seem right.
@jpouderoux @finetjul
![2019-01-10-173637_1916x1056_scrot](/uploads/bf116baacc8b215be4f719c08c8d2e26/2019-01-10-173637_1916x1056_scrot.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18713Pipeline browser, change input make filters disappear2020-05-05T00:42:25-04:00Charles GueunetPipeline browser, change input make filters disappear**Step to reproduce:**
1. apply: Fast Uniform Grid
1. apply: Contour
1. apply: Contigency Statistics on the fast uniform grid
1. change input on the Contour filte, chose the Assessed Data output as new input
**Bug:**
The folded output...**Step to reproduce:**
1. apply: Fast Uniform Grid
1. apply: Contour
1. apply: Contigency Statistics on the fast uniform grid
1. change input on the Contour filte, chose the Assessed Data output as new input
**Bug:**
The folded outputs of a filters become un-foldable after the change input and so can not be accessed in the pipeline browserhttps://gitlab.kitware.com/paraview/paraview/-/issues/18799Representation Transform with negative values is broken2021-03-23T19:21:27-04:00Matthieu vitseRepresentation Transform with negative values is brokenAn Issue originally reported on discourse :
https://discourse.paraview.org/t/negative-scale-causes-problem-with-volume-rendering/1245/8
Applying a negative scaling to the representation transform breaks certain types of representation....An Issue originally reported on discourse :
https://discourse.paraview.org/t/negative-scale-causes-problem-with-volume-rendering/1245/8
Applying a negative scaling to the representation transform breaks certain types of representation.
How to reproduce :
* Open ParaView
* Create a Wavelet, Apply
* Set the representation transform Y scale to -1
* ** Rendering is incorrect**
* Change Representation to Volume
* ** Rendering is incorrect**
* Change Representation to Surface with edges
* Rendering is correct
FYI, it seems to work correctly with 5.6.0, not with master.https://gitlab.kitware.com/paraview/paraview/-/issues/18807ParaView refresh rate decrease over time with data-varying source2021-03-29T07:35:22-04:00Nick LaurensonParaView refresh rate decrease over time with data-varying sourceWhile using LiveSource in ParaView thanks to the pqLiveSourceBehavior, the refresh rate to call `GetNeedsUpdate()` is increasing over time.
How to reproduce it with [BugLiveSource.zip](/uploads/a3f01c422085b13efdb9f4eb0952925c/BugLiveSo...While using LiveSource in ParaView thanks to the pqLiveSourceBehavior, the refresh rate to call `GetNeedsUpdate()` is increasing over time.
How to reproduce it with [BugLiveSource.zip](/uploads/a3f01c422085b13efdb9f4eb0952925c/BugLiveSource.zip):
- apply the patch `0001-reproduce-bug.patch` on paraview v5.6.0
- compile the plugin and import the plugin to paraview
- create a `Time Source Debug` in ParaView and set the `X Amplitude` property to 1
- after 5 to 10 minute you will see that the the source will move slower.
In this small example, I copy-past the vtkTimeSourceExample class, and transform it to a LiveSource (add the GetNeedsUpdate, remove the RequestInformation). Also I slightly modify the RequestData to generate a new position at each call.
**Edit:** Looks like `pqDoubleVectorPropertyWidget::propertyDomainModified` is leaking observers, widgets and PropertyLinks, causing internal lists to indefinitely grow, hence slowing down ParaView. This happens with multiple calls to `propertyDomainModified`, which is reproduced with a little as just play time-varying data in a loop.https://gitlab.kitware.com/paraview/paraview/-/issues/18808Cannot Load State from python file2021-03-24T15:46:16-04:00Theodore BaltisCannot Load State from python fileWhen trying to Load State from a python-formatted file I find that the indices of any Extract Block filter are reset.
Steps:
1. Open .xmf file using standard XDMF reader
2. Add Extract Block filter and select indices
3. Save state to .p...When trying to Load State from a python-formatted file I find that the indices of any Extract Block filter are reset.
Steps:
1. Open .xmf file using standard XDMF reader
2. Add Extract Block filter and select indices
3. Save state to .py file
4. Reset session
5. Load state from previously saved .py file
Loading data initially, before saving state:
![open_xmf](/uploads/62532c90b37b43adb06a0cbd54cb8662/open_xmf.JPG)
After loading state:
![load_state](/uploads/729603f47332d07be8e31ef51c97a86b/load_state.JPG)https://gitlab.kitware.com/paraview/paraview/-/issues/18816pdf writes are failing2022-05-11T19:52:00-04:00W. Alan Scottpdf writes are failing.pdf writes are failing with error output.
* 5.6.0, Windows, builtin server.
* Open can.exo. Apply.
* File/ Export Scene. Choose .pdf.
* Select Compress output file, Unselect Rasterize 3D geometry. Save.
Following error message ap....pdf writes are failing with error output.
* 5.6.0, Windows, builtin server.
* Open can.exo. Apply.
* File/ Export Scene. Choose .pdf.
* Select Compress output file, Unselect Rasterize 3D geometry. Save.
Following error message appears:
ERROR: In C:\bbd\ecd3383f\build\superbuild\paraview\src\ParaViewCore\VTKExtensions\Rendering\vtkPVGL2PSExporter.cxx, line 123
vtkPVGL2PSExporter (000001F0CAEF29A0): Cannot rename exported graphics file.
I think that the .pdf is actually written. I called it DeleteMeA, it ended up: deleteMeA.pdf.pvtmp.pdfhttps://gitlab.kitware.com/paraview/paraview/-/issues/9489Automatically adjust point/line sizes for screenshots with different resolution2023-06-15T08:16:58-04:00Kitware RobotAutomatically adjust point/line sizes for screenshots with different resolution**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9489). Further discussion may take place here.**
---
If you have points or lines in the scene and you take a screen shot at a hi...**This issue was created automatically from an original [Mantis Issue](http://paraview.org/Bug/view.php?id=9489). Further discussion may take place here.**
---
If you have points or lines in the scene and you take a screen shot at a higher resolution than the current window (say 5000x5000), many of the objects stay the same size (spheres, planes, triangulated meshes) but many objects get much smaller (points, lines). Surely this is because the points and lines are specified in arbitrary units (Point Size = 3, Line Width=2, for example). An example is here:
http://rpi.edu/~doriad/Paraview_List/linesize.jpg
Notice the lines in the screenshot are much thinner.
It would be nice to have theses sizes automatically adjusted to the relative difference between the screenshot size and the render window size, so screenshots will look the same.https://gitlab.kitware.com/paraview/paraview/-/issues/17999System HANG - pvbatch is throwing bazillians of processes when loading state ...2019-07-24T18:41:47-04:00W. Alan ScottSystem HANG - pvbatch is throwing bazillians of processes when loading state fileI have a pvbatch python file that is loading a state file, and then processing over time. Each time through it creates a dozen or so new pvbatch processes. This is running until it kills the blade.
This is a show stopper for a custo...I have a pvbatch python file that is loading a state file, and then processing over time. Each time through it creates a dozen or so new pvbatch processes. This is running until it kills the blade.
This is a show stopper for a customer.
* Linux, 5.4.1 Kitware download.
* Read and implement the README file.
* Basically, copy can.ex2 into this directory.
* Edit the .py and .pvsc file, correcting the directory paths.
* Run as follows: ./pvbatch --use-offscreen-rendering --mesa-llvm save_animation.py
In a separate xterm, run htop. You will notice that there will be dozens of pvbatch processes, and every timestep, more will appear. This will continue until the Linux box dies.
Attaching the .py, .pvsc and README files.
[pvbatch-replicate-bug.tar.gz](/uploads/8f68f6e41eba263e5ae5c80decc620bc/pvbatch-replicate-bug.tar.gz)5.8 (Winter 2020)Cory Quammencory.quammen@kitware.comCory Quammencory.quammen@kitware.comhttps://gitlab.kitware.com/paraview/paraview/-/issues/18840Molecule inside a Multiblock is not rendered2021-03-24T05:06:09-04:00Nicolas VuailleMolecule inside a Multiblock is not renderedSteps to reproduce:
* load a molecule ('porphyrin.cml' from PV test files)
* apply 'group dataset' filter
Results:
* information panel show expected hierarchy and infos
* empty render view
* following error message
```
ERROR: In /h...Steps to reproduce:
* load a molecule ('porphyrin.cml' from PV test files)
* apply 'group dataset' filter
Results:
* information panel show expected hierarchy and infos
* empty render view
* following error message
```
ERROR: In /home/nicolas/ParaView/paraview2/VTK/Common/ExecutionModel/vtkCompositeDataPipeline.cxx, line 164
vtkPVDataRepresentationPipeline (0x55d9ea3fa0b0): Can not execute simple algorithm without output ports
```https://gitlab.kitware.com/paraview/paraview/-/issues/18846pqInteractiveViewLink should be refactored2021-03-24T05:04:05-04:00Utkarsh AyachitpqInteractiveViewLink should be refactoredThe current implementation of X-ray view linking is not robust.
* doesn't work correctly if the two views are not of the same size
* the x-ray window lags behind the linked view is properties like representation type are changed in the ...The current implementation of X-ray view linking is not robust.
* doesn't work correctly if the two views are not of the same size
* the x-ray window lags behind the linked view is properties like representation type are changed in the linked view
* easy to get into odd opengl state messup by just playing with the widget for a while.https://gitlab.kitware.com/paraview/paraview/-/issues/18852Molecule can be saved but can not be read back2021-03-24T05:01:35-04:00Nicolas VuailleMolecule can be saved but can not be read backSteps:
* load porphyrin.cml
* File / Save Data
* only 'vtk Legacy file' format is available.
* set File Type to Ascii
* File / Open select the previously written file
* Pop up appears, asking for the correct reader. The lists is pr...Steps:
* load porphyrin.cml
* File / Save Data
* only 'vtk Legacy file' format is available.
* set File Type to Ascii
* File / Open select the previously written file
* Pop up appears, asking for the correct reader. The lists is pretty big (cf sshot), but none seems working / pertinent.
The written file ( [molecule.vtk](/uploads/0c142dac02f3b4ee104ff496f7e72ffe/molecule.vtk) ) contains the expected values.
![molReaders](/uploads/579291740294265c9479455d78bdea84/molReaders.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18861Block Colors Not Honored When Specified Through The MultiBlock inspector (pyt...2021-03-24T15:05:51-04:00Andrey AndreyevBlock Colors Not Honored When Specified Through The MultiBlock inspector (python state file)When I specify colors through the multi block inspector and save the state file as a python, the block coloring is erased upon load. This is the case when using the state file in pvbatch as well. This may be related to issue
#18808 tha...When I specify colors through the multi block inspector and save the state file as a python, the block coloring is erased upon load. This is the case when using the state file in pvbatch as well. This may be related to issue
#18808 that my colleague submitted. In that issue it does not honor the block selections.
![LimeBlock](/uploads/07f37892dd4ab0951c98e6e8256a161f/LimeBlock.png)
![NotLimeBlock](/uploads/80ec9742cf1965594d427d9d7036b6ed/NotLimeBlock.png)https://gitlab.kitware.com/paraview/paraview/-/issues/18862Record Test does not support Ctrl-Space2021-03-24T05:12:40-04:00Mathieu Westphal (Kitware)Record Test does not support Ctrl-SpaceWhen recording a test via Tools -> Record Test, Ctrl-Space is not recorded in any way. The recorded test will then fail.
How to reproduce :
* Open ParaView
* Tools -> Record Test, select a file.
* Click on ParaView Main Window
* Ct...When recording a test via Tools -> Record Test, Ctrl-Space is not recorded in any way. The recorded test will then fail.
How to reproduce :
* Open ParaView
* Tools -> Record Test, select a file.
* Click on ParaView Main Window
* Ctrl-Space, **no event is recorded**
* Select a filter to add, an event is recorded, but it will fail to play.https://gitlab.kitware.com/paraview/paraview/-/issues/18864RecordTest/PlayTest right click on pipeline browser does not work correctly2021-03-24T05:12:32-04:00Mathieu Westphal (Kitware)RecordTest/PlayTest right click on pipeline browser does not work correctlyWhen playing a test containing a right click on the pipeline browser, it does not work correctly.
How to reproduce :
* Open ParaView
* Create a wavelet, Apply
* Tools -> RecordTest, select a file
* Right Click on the wavelet in the...When playing a test containing a right click on the pipeline browser, it does not work correctly.
How to reproduce :
* Open ParaView
* Create a wavelet, Apply
* Tools -> RecordTest, select a file
* Right Click on the wavelet in the pipeline browser, an event is recorded
* Stop the test
* Tools -> PlayTest, select the same file
* A right click is played but **not on the correct position.**
* The generated event does not contain any kind of position information
```
<pqevent object="pqClientMainWindow/pipelineBrowserDock/pipelineBrowser/qt_scrollarea_viewport" command="contextMenu" arguments="" />
```