muratmaga Here are my thoughts with regards to the images from MorphoSource. The attached images below show a MorphoSource skull with matcap-modulated volume rendering (left), pure-matcap volume rendering (center) and matcap-based surface rendering (right, Surfice)
- These are very high resolution images, but typically they only have a single hard surface boundary (e.g. bone vs air). This case seems ideally suited for using mesh-based surface rendering instead of volume rendering. For example, the Surfice function “Convert voxelwise volume to mesh” will convert a voxel-based image to an iso-surface mesh, alternatively you can use Slicer’s interactive Editor (I would suggest saving to any format except STL which is unable to share vertices). For large volumes, volume rendering will tend to be much slower than Surface rendering.
- The quality of the DICOM headers varies for different images available on MorphoSource. Many convert with any tool without any problems. On the other hand, some lack instance numbers which will disrupt conversion. You can download and compile the developmental branch of dcm2niix from Github for a version that should salvage these images.
- In my experience, most graphics cards are unable to handle any texture that exceeds 2Gb. So the resolution number of rows x columns x slices x 4 (XxYxZx4) must be less than 2Gb. Slicer’s “Crop Volume” or the “Resize Image (BRAINS)” functions are ideally suited to both crop and rescale volumes.
