Y_Martel

Bonjour Iassoan, O.K. I'll try to put an NRRD export in there... But, I may need some help testing it. This may sound strange, but as far as possible I try not to look at what other software are doing and how their interface work. That way I am not influence when I design my own interfaces, and I solve the different interaction the way I think is the easiest for the user. Of course most user interfaces are just basic good sense, so I guess there's not that many differences, but still I prefer to do things my way. I've been doing this for the past 30 years and I'm still in business, so I may not be completely wrong... This mean that I do not have 3D slicer, or any such software, on my system (I actually never even look at 3D slicer's web pages until a few days ago). So I have no way of testing if my NRRD files correct. Would it be possible to send you a few files to make sure I got it right? Yves

Bonjour Iassoan, I'm afraid my software does not export in one of these formats. But is does save the volume in a very simple format (a simple ASCII header, followed by the voxels in 32 bits IEEE float) so a converter would be easy to do. Actually I have a few university clients who use the software only as converter to be able to access the proprietary spherical ultrasound datasets created on Ge and Samsung scanners in their research projects... I was not aware of nrrd, but looking at it, it is very similar to what I do! So I guess I should also offer an export in that format Now I understand that other software also do VR visualisation, but what I do is actually edition of the volume in VR. When I first wrote that VR module, to be honest, I though it would be a gadget... until I actually used it! Doing the edition of a volume in VR is so much easier than on a 2D screen. The stereoscopy of these goggles is so good, you have the model a few inches in front of you and you sculpt it directly in 3D... Of course maintaining 90 fps needed for good VR is a bitch, that's why the software only run on computer equipped with Nvidia graphic cards (I do almost all the computation inside the GPU). Yves

Bonjour Giovanni, The short answer is: yes, the software will enable you to make 3D STL models from your data-sets. You will be able to load the models, in any variation of the MVL format, with either Cartesian or spherical voxels (you are better to export in Spherical an let my software re-slice the data). The software will also enable you to edit the model to remove any ultrasound artefacts, either directly on the screen, or in VR with an Oculus Rift headset (and that is at least 10 time faster!) In the FAQ section of my web site there's some info on how to save the volumes on Ge and Samsung systems. But I don't want to go in to much details here, these kind of forums are usually not the place to discuss commercial products... If you want more information, I would suggest you contact me directly at martel(at)tomovision.com. Yves

Bonjour Giovanni, Indeed the Accuvix will export the 3D/4D data in ".mvl" (Medison Volume) format. The data inside these files can be either spherical or Cartesian. MVL is not DICOM or even a variation on DICOM. It is a proprietary format developed by Medison. Actually there's 2 variation of the MVL format, the one used by the Accuvix I call "version 221" is a lot more complex than the "old" variation. You can see a list of the 3D ultrasound file format I have encounter up-to-now on my web site: http://www.tomovision.com/products/format_image.html Also, do not forget that 4D files usually have a lower resolution than 3D. So if you want to do models from the datasets, you are better with the 3D. Yves

Bonjour, Let me jump in... Because of the way the images are generated, 3D ultrasound data have voxels that are expressed in a spherical system. DICOM (as it stand now) only support voxels in a Cartesian system. So the manufacturers have a few choices: - They can save the data in proprietary format (Kretzfile for Ge, MVL for Samsung) . - They can save the data in private tags inside a DICOM file (Ge, Hitachi, Philips) - They can re-format the voxels to be in Cartesian, but then the data has been transformed and nobody like that. And anyway, since they also need to save the original (untransformed) data, the companies that do offer Cartesian voxels, usually save them in the same way as the original, so they are not saved in normal DICOM tags, but in their proprietary version. So most of the standard software that can do 3D from CT or MR will not be able to cope with the data files. (Let alone the fact that ultrasound datasets are inherently very noisy!) I do have a product that will read most of the 3D ultrasound files and create an STL model directly from the datasets (spherical or Cartesian). It is called "Baby SliceO": http://www.tomovision.com/products/baby_sliceo.html Unfortunately, it is not free, but you can try it without any licenses. Give it a try and let me know if you like it...