“Could not load: - as a 48 frames MultiVolume by ImagePositionPatient+AcquisitionTime as a MultiVolume”
Just received that error trying to load the DICOM information from an ecography. 3D/4D data in “.mvl” (Medison Volume) format.
Anyone can help, new to the software here.
Best Regards and thanks in advance
Operating system: MACOSX HIGH SIERRA
Slicer version: 4.8.1
Expected behavior: load dicom ecography
Actual behavior: Could not load: - as a 48 frames MultiVolume by ImagePositionPatient+AcquisitionTime as a MultiVolume
As far as I know Medison MVL format is a closed, proprietary format, not even DICOM. If sufficient number of input files are available then probably the format can be reverse-engineered (as it was done by TomoVision developers), but it would take a couple of weeks of work, which would require dedicated funding.
I would recommend trying the followings:
Check if you can export to Cartesian DICOM file format and then try to import it as @fedorov recommended above. If you don’t find an option like that then ask your Medison representative about what export options are available.
Try import using TomoVision. If import works, contact TomoVision developers, asking for image export in NRRD format.
It is important to make ultrasound manufacturers aware that they are hurting researchers by using closed, proprietary file formats. When you buy a new ultrasound system make sure you buy one that can export images in a format that can be freely accessed - preferably in DICOM format.
I guess I figured out that there was a lot of files inside the directory and that lead me to open files individually…sorry for my lack of knowledge…learning over this.
The thing is that I opened a single file and the R view shows it ok…but the Y and G shows what it should be other dimensions views but they are really shrinked…
The pictures above show just secondary captures (screenshots). Probably the 3D image information is stored in private DICOM fields in the same files. If you can share anonymized data sets then we can have a look at them to confirm.
Hi everyone. I’m in the same boat. The USS machine I used was a Samsung UGEO_HM70A. Tried with Tomovision Babysliceo(demo) and I could see the baby and edit everything but it’s quite expensive for a couple of mvl files I want to edit/use.
If anyone is working on these kind of files (mvl), feel free to get all of them from my dropbox. All of them are anonimyzed and exported as 3d volume, default mode.
Thanks for sharing the data. It is easy to load these images once you know the image geometry (pixel start position and x y z size and spacing) just by creating a .nhdr header file for it. The geometry values can be determined by trial and error. One of the projects for the Slicer project week (that starts tomorrow) will be about automating this process - your data sets will be perfect test data for this.
For example, you can load one of your data sets by creating a “DAN 1_0000.nhdr” file in the same folder with the content below and then loading the .nhdr file into Slicer:
NRRD0004
# Complete NRRD file format specification at:
# http://teem.sourceforge.net/nrrd/format.html
type: unsigned char
dimension: 3
space: left-posterior-superior
sizes: 376 124 158
space directions: (-0.30,0,0) (0,-0.60,0) (0,0,0.90)
kinds: domain domain domain
endian: little
encoding: raw
space origin: (0,0,0)
byte skip: 620919
data file: DAN 1_0000.mvl
After applying masking (to remove some reflections that would occlude the face), casting to double, and applying anisotropic filtering, you get this volume rendering result:
Thank you so much for your explanation and I’m really glad that you found useful these data sets for the Slicer project week.
On the other hand I tried doing myself following your steps and using the same file and when I import or drag the nhdr file I created I’m still getting 3 black screens. Do I need any specific extension? I tried importing as a volume, sequence of volumes, etc without success.
Create the nhdr in the same folder as the .mvl file. If the image does not load correctly then please post the application log (menu: Help / Report a bug).
It seems that the file that you created is not valid (maybe end-of-line character is not what is expected or a new-line is missing from the end of the file, etc). You can download a working header file from here: https://1drv.ms/u/s!Arm_AFxB9yqHtuR5XyPS9kbrOrCPIA
I followed along with your instructions to create the .nhdr file which I can now at least get the .mvl file from our Samsung RS85 loaded in as a volume. Question is what’s the easiest way to figure out the proper pixel start position and x y z size and spacing? I’ve tried just randomly changing the image spacing and origin with no success. Just see a bunch of white lines and dots. Any help is appreciated. Thanks!
Is there a trick to getting that extension loaded? I downloaded the rawimageguessmaster.zip and tried loading it in the extension manager. I keep getting an error:
No extension description found in archive ‘C:/Users/en12283/Downloads/SlicerRawImageGuess-master.zip’
I also extracted the files and tried that and it’s still not working. I’m sure I’m doing something wrong. Thanks again!
@e36alpine following the instructions is quite easy. You have to extract that zip wherever you want, and add the folders where every py file is from slicer/application settings/modules/aditional module paths. Restart slicer and that is.
By the way, I need some help using this module… How can we open mvl files with this module? I mean, when I load with this module ie the uss I’ve uploaded previously I get nothing on the screen even playing with the sliders and setting the same parameters of the nrrd file created. A couple of weeks ago I remembered I could see the images without touching any setting but know is impossible. I tried reinstalling everything again without success.
Slicer currently cannot automatically load Samsung .mvl ultrasound files. Request your Samsung representative to provide you with an option to save images in DICOM or other open standard data format; or release specification of their proprietary file format.
