My plugin needs to build and output a very large image - 1GB would
not be surprising. The contents of the image are gradually
accumulated as many images are produced by the detector driver. I'm
not sure how I can make this 'fit' the NDArray/NDArrayPool
architecture. If I make the accumulator image a private area of
memory then I could copy to an output NDArray when required - but
that requires even more memory.
My ideal approach would be for my plugin to allocate the accumulator
array (a 'worker' class currently encapsulates this), and only when
the output is required would a pointer to this memory be used to
'publish' the result through an NDArray.
If I created a private NDArray and set its pData pointer to my
accumulator image, could I then pass this to
doCallbacksGenericPointer instead of the usual this->pArrays[0]?
If so, that call would presumably be inexpensive unless/until a
client subscribed to the output port?
Thanks,
Phil
-- Pixel
Analytics is a limited company registered in England.
Company number: 7747526; Registered office: 93A New Road,
Haslingfield, Cambridge CB23 1LP