Hi guys, I wanted to hear your opinion regarding two possible ways of reducing memory requirements in handling segmentations in MITK.
So far, a separate binary image is used to handle each segmentation, right?. This in principle means a lot of memory waste, as each segmentation has to have the same size as the reference image (also in RAM). The pixel size is 8bits, but still, a lot of memory. The option of cropping the segmentation (e.g. by the AutoCrop filter) to a reduced size is always present; but this is not optimal as the user may want to continue segmenting in other regions in a new work session. A way of reducing this memory burden could be to use 1-bit binary images: http://insight-journal.org/browse/publication/646. Do you think it's feasible to adapt mitkImage to cope with itkSingleBitBinaryImage? Another solution would be to have all segmentations into a single labeled image (like e.g. in Amira). The classes contributed to ITK in http://insight-journal.org/browse/publication/176 look very promising to this aim. What do you think? Do you see other approaches? thanks for the great job sebastian ------------------------------------------------------------------------------ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
