Hi Marcel, You would ned at least twice as much. Also, is there a specific reason for you to use the --m3d flag? That will result in writing out uncompressed morph files which will take up a lot of space.
Lilla

On Tue, 9 Jul 2013, Marcel Falkiewicz wrote:

Dear FreeSurfers,
 I'm trying to use mri_cvs_register, however the process can't complete and I get the following error:
[...]
loading transform id string =
 data size = 18728074
 uilen = 6
 loading transform id string =
 data size = 19845421
 uilen = 6
 loading transform id string =
 data size = 19120776
 uilen = 6
 loading transform id string =
 data size = 71
 uilen = 7
 loading transform id string =
 saveTransform code
 writing transform size = 117019458
 saveTransform code
 writing transform size = 117019458
 saveTransform code
 writing transform size = 16
 saveTransform code
 writing transform size = 21339696
 saveTransform code
 writing transform size = 21092930
 saveTransform code
 writing transform size = 20795616
 saveTransform code
 writing transform size = 20591898
 saveTransform code
 requested buffer size = 436643894
 Exception caught while saving morph
 ZlibStringCompressor::setBufferSize - Caught std::bad_alloc

My command line was: mri_cvs_register --mov subject01 --mni --openmp 8 --m3d

At the time of crash all RAM is consumed by createMorph process (10 GB). Is this crash related to the ammount of RAM on my machine (12 GB)? If so, how much RAM is needed to complete mri_cvs_register?

Best regards,
 Marcel

The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.