[Camino-users] Problem with image2voxel

[Philip A Cook]

Although, things will often get internally converted to double before being written out, so you might need more RAM temporarily. Try

export CAMINO_HEAP_SIZE=1500

On Mar 22, 2012, at 11:05 AM, Philip A Cook wrote:

> Hi,
> 
> You can allow Camino to use more RAM by setting its maximum heap size, in megabytes
> 
>  export CAMINO_HEAP_SIZE=1000
> 
> ought to do it.
> 
> On Mar 22, 2012, at 9:22 AM, Ed Gronenschild wrote:
> 
>> Hi,
>> 
>> I entered the following command:
>> 
>> image2voxel -4dimage DTI.nii.gz -outputfile dwi.Bfloat
>> 
>> upon which I got an error:
>> 
>> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>> 	at data.ScannerOrderDataSource.init(ScannerOrderDataSource.java:169)
>> 	at data.ScannerOrderDataSource.<init>(ScannerOrderDataSource.java:134)
>> 	at data.ScannerOrderScaledDataSource.<init>(ScannerOrderScaledDataSource.java:52)
>> 	at imaging.Nifti1Dataset.getImageDataSource(Nifti1Dataset.java:2606)
>> 	at apps.ImageToVoxel.execute(ImageToVoxel.java:105)
>> 	at apps.EntryPoint.main(EntryPoint.java:269)
>> 
>> So there seems to be  a memory problem.
>> The DTI.nii.gz data file consists of 129 volumes of 70 slices each 128 x 128 voxels.
>> This corresponds to about 591 MByte, well below the 2 GByte limit.
>> I'm on a Mac, OSX 10.5.8 running in 32 bits mode.
>> Is there some kind of workaround?
>> 
>> Cheers,
>> Ed
>> 
>> 
>> _______________________________________________
>> Camino-users mailing list
>> Camino-users at www.nitrc.org
>> http://www.nitrc.org/mailman/listinfo/camino-users
> 
> _______________________________________________
> Camino-users mailing list
> Camino-users at www.nitrc.org
> http://www.nitrc.org/mailman/listinfo/camino-users