Thank you for your response. I’m having trouble finding apropos examples of RequestInformation and RequestUpdateExtent so I’m trying to figure it out. I have two follow up questions.
- RequestUpdateExtent seems to exist to communicate up the pipeline, to the parent, that this filter needs a different extent provided or a different time step. I don’t want to get different extents from the parent and the filter will be incapable of dynamically changing subextents as output as well. Is RequestUpdateExtent still required?
- I started looking at RequestInformation and tried to explicitly set the whole_extent:
# Code for 'RequestInformation Script'.
executive = self.GetExecutive()
outInfo = executive.GetOutputInformation(0)
outInfo.Set(executive.WHOLE_EXTENT(), 0, 1025, 0, 512, 0, 0)
This actually produces the correct grid as viewed in the render window. but does throw an error:
ERROR: In /opt/glr/paraview/paraview-ci/build/superbuild/paraview/src/VTK/Common/ExecutionModel/vtkStreamingDemandDrivenPipeline.cxx, line 878
vtkPVPostFilterExecutive (0x6000018e3640): The update extent specified in the information for output port 0 on algorithm vtkPVPostFilter(0x6000012683f0) is 0 1025 0 512 0 0, which is outside the whole extent 0 1024 0 512 0 0.
Which references the whole extent from the upstream filter, which might be an issue with not having a RequestUpdateExtent? I tried setting UPDATE_EXTENT and WHOLE_EXTENT in the
RequestInformation and/or RequestUpdateExtent without success. In the meantime I found Berk’s VTK Pipeline Primer from 2014 which I’ll peruse to try and understand better…