A thought on OPTICKS-1456. My understanding is that the current plan is to have Opticks take ownership of a block of raw data, wrapping it in a RasterElement. I am aware of a case where we wouldn’t want it to take ownership. If I have a block of data that I want to give to an algorithm plug-in for processing and that plug-in takes a RasterElement, I would like to wrap my block of data in a RasterElement, pass it to the plug-in, and then destroy the RasterElement when the plug-in is done. In this case, the RasterElement serves as an adapter between the third party input and the Opticks plug-in.
This message and any enclosures are intended only for the addressee. Please
notify the sender by email if you are not the intended recipient. If you are
not the intended recipient, you may not use, copy, disclose, or distribute this
message or its contents or enclosures to any other person and any such actions
may be unlawful. Ball reserves the right to monitor and review all messages
and enclosures sent to or from this email address.