[vtkusers] re-using allocated memory in image algorithm
beekmaarten at yahoo.com
Mon Aug 25 10:42:12 EDT 2014
Problem solved: De memory address of the scalars did change but because the ReleaseData flag was On...
What would be best practice in a pipeline of about 6 image algorithms that all update during interaction: ReleaseData flag On or Off?
(because that must have been the reason to put the flag to on a couple of months ago).
Thanks - Maarten
On Friday, August 22, 2014 4:31:14 PM, Maarten Beek via vtkusers <vtkusers at vtk.org> wrote:
Thanks David for your reply.
I'll check allocateScalars() and also make sure this is the function used by my algorithm...
Printing the memory address is of course a good check.
Thanks - Maarten
On Friday, August 22, 2014 3:39:59 PM, David Gobbi <david.gobbi at gmail.com> wrote:
The VTK image algorithms automatically reuse their memory unless the
data type or the size changes. For more info, look at the code for
AllocateScalars in vtkImageData.cxx. Also, I recommend printing out
the memory address after each Execute so that you can verify that it
On Fri, Aug 22, 2014 at 8:04 AM, Maarten Beek via vtkusers
<vtkusers at vtk.org> wrote:
> Hi all,
> Is there a way to preserve the allocate memory of the put of an image
> Looking at the source code, I have the feeling that algorithms in vtk
> allocate memory for their output each time ExecuteData() is called. I
> created an image algorithm that updates almost continuously, but the image
> size doesn't change. So once the output is created and memory is allocated,
> I could just keep using this output (just calling output->Modified() after
> the data in the exiting memory is replaced). How would I do this?
> Thanks - Maarten
Powered by www.kitware.com
Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the VTK FAQ at: http://www.vtk.org/Wiki/VTK_FAQ
Follow this link to subscribe/unsubscribe:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtkusers