Hi,
I am back with the strange extent/bounds problem (see other threads...)
I want to process FFT-based image convolution in ParaView. Thus I
enabled different VTK filters in ParaView so that I can implement the
following pipeline :
- Read an image and pad it to include
- built a kernel (eg. Wave
I found this thread from about a year ago... I'm keen to find out if
there was any progress on it.
The problem is that on image-to-image type filters where the extent of
the output is greater than the extent of the input, the output image is
cropped.
For example, if I have an input of extent [0
Which filter is exhibiting this issue?
One potential source for such behavior could be that the filter in
question is not updating the WHOLE_EXTENT key in its RequestInformation
implementation, and/or not updating UPDATE_EXTENT correctly in its
REQUEST_DATA implementation. As a result ParView
Hi,
A related thread can be found here:
http://www.mail-archive.com/paraview@paraview.org/msg02225.html
where I also gave some links to previous threads.
Briefly, the problem is not that simple to solved: ParaView has rules about
how data are organized in order to achieve efficient parallel vi
I was informed that a feature will be added in the next release to at
option correctly interpret extents at the price of potential
additional IO.
http://paraview.org/Bug/view.php?id=12298
Dominik
On Wed, Jun 29, 2011 at 8:53 PM, Jérôme wrote:
> Hi,
>
> A related thread can be found here:
> h
Thanks for the info, Dominik. Issue monitored -- looking forward to testing!
Jerome
2011/6/29 Dominik Szczerba
> I was informed that a feature will be added in the next release to at
> option correctly interpret extents at the price of potential
> additional IO.
>
> http://paraview.org/Bug/view
: [Paraview] Image Padding : extent problem again
*** WARNING ***
This message has originated outside your organisation,
either from an external partner or the Global Internet.
Keep this in mind if you answer this message.
Thanks for the info, Dominik. Issue monitored
