<p style="margin: 0px; padding: 0px;">We have a 64-bit OS with 4 GB of RAM, but we are working on the 32-bit version of MRtrix because it's the only available for Windows (isn't it?).</p><p style="margin: 0px; padding: 0px;">We will try to use the analyse file without converting it; if there will be again problems of memory, we will move to the Linux 64-bit version.</p><p style="margin: 0px; padding: 0px;"><br></p><p style="margin: 0px; padding: 0px;">Thanks</p><p style="margin: 0px; padding: 0px;">Matteo and Marco</p><p style="margin: 0px; padding: 0px;"><br></p>
<blockquote>
----Messaggio originale----<br>
Da: d.tournier@brain.org.au<br>
Data: 21/06/2011 2.55<br>
A: "Thijs Dhollander"<thijs.dhollander@uzleuven.be><br>
Cc: "mrtrix-discussion"<mrtrix-discussion@public.nitrc.org><br>
Ogg: Re: [Mrtrix-discussion] Conversion of 4D analyze file into mif DWi dataset<br>
<br>
Hello Matteo & Marco,<div><br></div><div>Thijs is probably right, it's most likely that the filesize is too large to be mapped into your RAM. It's a little annoying that the OS doesn't provide anything more informative about the error than "no error", but at least we know it's a failed memory-mapping. I'm surprised this happened with a filesize of 1GB though. </div>
<div><br></div><div>Can you tell us:</div><div>- how much RAM you have installed, and how much swap (type 'free' in a terminal if using Linux). </div><div>- whether you're running the 32-bit or 64-bit version.</div>
<div> </div><div>On some platforms, the 32-bit version will only handle a maximum of 2GB of memory mapping, and since you're copying data from a 1GB dataset into another 1GB dataset, that will probably be enough to go over the limit. Shouldn't happen on a 64-bit system, unless potentially you run out of physical memory...</div>
<div><br></div><div>On a separate note: why are you trying to convert the file to mif format? All MRtrix commands will happily handle your 4D analyse file directly (memory permitting)...</div><div> </div><div>Cheers,</div>
<div><br></div><div>Donald.</div><div><br></div><div><br><br><div class="gmail_quote">On 20 June 2011 18:23, Thijs Dhollander <span dir="ltr"><<a href="mailto:thijs.dhollander@uzleuven.be" mce_href="mailto:thijs.dhollander@uzleuven.be">thijs.dhollander@uzleuven.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" mce_style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Matteo & Marco,<br>
<br>
I think you might be right about it being a memory error. I remember getting the same error in a different -but then again similar- situation: I was performing TDI, but at a pretty high resolution. The final mif file also got created (at what seemed to be the right filesize), but then it gave me the same "no error" error.<br>
<br>
What you could try in your situation (apart from getting more memory :-)), is to import parts of it along some dimensions... if that makes sense for what is in your data and what you want to do with it. For instance, if your images have a very high resolution, you could import the upper and lower half of them separately. Or if you just acquired many different b-shells, you could import one of them. Or if you acquired many repetitions, you could import them separately and then average them, etc...<br>
<br>
Kind regards,<br>
<br>
Thijs Dhollander<br>
PhD Student<br>
<br>
<a href="mailto:thijs.dhollander@uz.kuleuven.ac.be" mce_href="mailto:thijs.dhollander@uz.kuleuven.ac.be">thijs.dhollander@uz.kuleuven.ac.be</a><br>
tel. +32 16 34 90 37<br>
gsm. +32 475 36 44 27<br>
<br>
Medical Image Computing (K.U.Leuven, ESAT/PSI, MIC)<br>
Medical Imaging Research Center | UZ Gasthuisberg | Herestraat 49 - bus 7003 | B-3000 Leuven | <a href="http://www.medicalimagingcenter.be" mce_href="http://www.medicalimagingcenter.be" target="_blank">http://www.medicalimagingcenter.be</a><br>
<div><div></div><div class="h5"><br>
-----Original Message-----<br>
From: <a href="mailto:mrtrix-discussion-bounces@public.nitrc.org" mce_href="mailto:mrtrix-discussion-bounces@public.nitrc.org">mrtrix-discussion-bounces@public.nitrc.org</a> [mailto:<a href="mailto:mrtrix-discussion-bounces@public.nitrc.org" mce_href="mailto:mrtrix-discussion-bounces@public.nitrc.org">mrtrix-discussion-bounces@public.nitrc.org</a>] On Behalf Of Matteo Figini<br>
Sent: vrijdag 17 juni 2011 20:14<br>
To: mrtrix-discussion<br>
Cc: Marco Castelli<br>
Subject: [Mrtrix-discussion] Conversion of 4D analyze file into mif DWi dataset<br>
<br>
Hello<br>
<br>
We have a problem in the import of 4D analyze (hdr/img) images into mrtrix<br>
<br>
We used the following string:<br>
mrconvert name.img dwi.mif<br>
but we received the following error:<br>
mrconvert: memmory mapping filed for file 'dwi.mif': No error<br>
<br>
A dwi.mif file of the same size of the img was generated but when we checked it with mrview we can't see any image.<br>
We point out that our img file is about 1GB and we wonder if this could generate a memory error.<br>
<br>
Matteo and Marco<br>
<br>
<br>
_______________________________________________<br>
Mrtrix-discussion mailing list<br>
<a href="mailto:Mrtrix-discussion@www.nitrc.org" mce_href="mailto:Mrtrix-discussion@www.nitrc.org">Mrtrix-discussion@www.nitrc.org</a><br>
<a href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" mce_href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" target="_blank">http://www.nitrc.org/mailman/listinfo/mrtrix-discussion</a><br>
_______________________________________________<br>
Mrtrix-discussion mailing list<br>
<a href="mailto:Mrtrix-discussion@www.nitrc.org" mce_href="mailto:Mrtrix-discussion@www.nitrc.org">Mrtrix-discussion@www.nitrc.org</a><br>
<a href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" mce_href="http://www.nitrc.org/mailman/listinfo/mrtrix-discussion" target="_blank">http://www.nitrc.org/mailman/listinfo/mrtrix-discussion</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jacques-Donald Tournier (PhD)<br>Brain Research Institute, Melbourne, Australia<br>Tel: +61 (0)3 9035 7033<br>
</div>
<br>
</blockquote><p><br></p><div style="position: absolute; left: -10000px; top: 0px; width: 1px; height: 1px; overflow: hidden;" id="_mcePaste"> </div>