When creating a programmable filter from two inputs with different extents I get the following, very annoying error message.
(5977.475s) [paraview ]vtkStreamingDemandDrive:878 ERR| vtkPVPostFilterExecutive (0x1b7cbb80): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter(0x7f6488011cf0) is 0 2304 0 127 0 202, which is outside the whole extent 0 0 0 127 0 202.
Within the programmable filter I do take care of the fact that the discretizations of the two inputs don’t match and am well aware of the fact that the discretization of the output corresponds to that of the first input.
Here is a very basic example:
# trace generated using paraview version 5.11.1 #import paraview #paraview.compatibility.major = 5 #paraview.compatibility.minor = 11 from paraview.simple import * paraview.simple._DisableFirstRenderCameraReset() renderView1 = GetActiveViewOrCreate('RenderView') wavelet1 = Wavelet(registrationName='Wavelet1') wavelet1.WholeExtent = [-10, 10, -10, 10, -10, 10] wavelet1Display = Show(wavelet1, renderView1, 'UniformGridRepresentation') wavelet2 = Wavelet(registrationName='Wavelet2') wavelet2.WholeExtent = [-10, 10, -10, 10, 0, 0] wavelet2Display = Show(wavelet2, renderView1, 'UniformGridRepresentation') programmableFilter1 = ProgrammableFilter(registrationName='ProgrammableFilter1', Input=[wavelet1, wavelet2]) programmableFilter1Display = Show(programmableFilter1, renderView1, 'UniformGridRepresentation') renderView1.Update()
In actual applications, the data produced by the programmable filter is fine despite the nonsense error message.
However, I do observe spurious color bars popping up in batch-renderings, and I suspect this to be a weird consequence of this issue.
I went ahead and opened an issue: