Different Xvoxsize ans Yvoxsize in Compute3DNorm!

Questions about BrainVisa usage and installation

Moderators: denghien, riviere

Post Reply
as_dub
Posts: 59
Joined: Fri Aug 19, 2005 4:09 pm
Location: Cleveland, Ohio

Different Xvoxsize ans Yvoxsize in Compute3DNorm!

Post by as_dub »

Hello everybody,

I have a problem in the bias correction process (error message below). I think it is due to voxels size :
[0.97560999999999998, 0.97656299999999996, 0.97656299999999996, 1]

Do you know how I can fix it ? Thank you !!!

Anne-Sophie



------------------------------
! VIP Warning:
Different Xvoxsize ans Yvoxsize in Compute3DNorm!
------------------------------

------------------------------
! VIP Warning:
Different Xvoxsize ans Yvoxsize in Extract3DExtrema!
------------------------------

------------------------------
!! VIP Error:
Not enough memory...
------------------------------
Error while allocating Vip3DPoint_S16BIT vector
------------------------------
!! VIP Error:

Execution aborted in function '(Vip_alloc.c)VipMalloc'.

------------------------------

------------------------------
!! VIP Error:

Execution aborted in function 'VipMalloc3DBucket_S16BIT'.

------------------------------

------------------------------
! VIP Warning:
Empty bucket list in VipGetNthBiggest3DBucket_S16BIT
------------------------------

------------------------------
! VIP Warning:
Nothing is left in VipConnexVolumeFilter
------------------------------
Can't allocate memory - no memory left.
St9bad_alloc
Can't allocate memory - no memory left.

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.



in 1 - T1 Bias Correction 3 RuntimeError: System command exited with non null value : 3

neuroProcesses.py (1641) in _processExecution:
result = process.execution( self )
T1BiasCorrection.py (108) in execution:
context.system('VipT1BiasCorrection', '-i', self.mri.fullName(), '-o', self.mri_corrected.fullName() , '-Fwrite', self.write_field, '-field', self.field.fullName(), '-Wwrite', self.write_wridges, '-wridge', self.white_ridges.fullName(),'-Kregul', self.field_rigidity, '-sampling', self.sampling, '-Grid', self.ngrid, '-ZregulTuning', self.zdir_multiply_regul, '-vp',self.variance_fraction,'-e',edge, '-eWrite', self.write_edges, '-ename', self.edges.fullName(), '-vWrite', self.write_variance, '-vname', self.variance.fullName(), '-mWrite',self.write_meancurvature, '-mname', self.meancurvature.fullName(), '-hWrite', self.write_hfiltered, '-hname', self.hfiltered.fullName(), '-Last', self.delete_last_n_slices )
neuroProcessesGUI.py (932) in system:
ret = apply( ExecutionContextGUI.system, (self,) + args, kwargs )
neuroProcesses.py (1721) in system:
raise RuntimeError( _t_( 'System command exited with non null value : %s' ) % str( ret ) )

Process 1 - T1 Bias Correction 3 finished on 2006/05/01 10:58 (20 seconds)
User avatar
Jean-Francois Mangin
Posts: 337
Joined: Mon Mar 01, 2004 10:24 am
Location: Neurospin, CEA, France
Contact:

Post by Jean-Francois Mangin »

This is just a warning, not the origin of your problem I think...
denghien
Posts: 209
Joined: Mon Apr 05, 2004 1:35 pm
Location: IFR49 / SHFJ Orsay
Contact:

Post by denghien »

Hi,

In fact, it seem that it is a problem of memory.

Code: Select all

Can't allocate memory - no memory left.
St9bad_alloc
Can't allocate memory - no memory left. 
Did you find the solution ?

Isa
as_dub
Posts: 59
Joined: Fri Aug 19, 2005 4:09 pm
Location: Cleveland, Ohio

Post by as_dub »

not yet :cry:
I have many different data with different problems. There must be something more than a memory problem because I have 2G of RAM..
I will try other things (if you have ideas of what can I test.. I'm interessted ! ), if I find any solution I will let you know ! Thank you
Post Reply