What steps will reproduce the problem?
1. Create a probeFilter with its two inputs, "input" and "source"
The "input" should be chosen so that its extent (number of voxels)
exceeds that of the the "source"'s in any cardinal direction
2. Execute the probe filter.
We expect this to work, because the "extent" has no direct relation to an image
volumes' bounds. And even if the input exceeds the source's bounds the filter
should (and does) just return zeroes for these locations.
However, the above procedure causes the filter to crash with the following
message (e.g.):
Unable to execute part 0 of module dvm4 (probeFilter): ERROR: In
..\..\..\archive\VTK\Filtering\vtkStreamingDemandDrivenPipeline.cxx, line 878
vtkStreamingDemandDrivenPipeline (000000000DAC7340): The update extent
specified in the information for output port 0 on algorithm
vtkTrivialProducer(000000000D6F5050) is 0 213 0 197 0 319, which is outside the
whole extent 0 516 0 516 0 285.
A known workaround is the re-sample the source so that its extent is large
enough, but this is cumbersome and theoretically unnecessary.
Original issue reported on code.google.com by fma...@gmail.com on 6 Dec 2011 at 12:41
Original issue reported on code.google.com by
fma...@gmail.com
on 6 Dec 2011 at 12:41