Instead of using our inhouse float field class, it might be useful to adopt http://www.openvdb.org/ for image storage. This is worth further investigation.
Further, it might help Cleaver play nice with other applications venues than medical imaging (in particular vfx and film). These areas produce 3d simulations and often want meshing capabilities to go with them
Instead of using our inhouse float field class, it might be useful to adopt http://www.openvdb.org/ for image storage. This is worth further investigation.
Further, it might help Cleaver play nice with other applications venues than medical imaging (in particular vfx and film). These areas produce 3d simulations and often want meshing capabilities to go with them