Hi all,
I'm playing with BrainVisa 4, and trying the T1 Pipeline 2007. Having entered commissure coordinates, I'm finding that the software still does not seem to find the coordinates.

in T1 Pipeline 2007 8 argument Commissure_coordinates is mandatory
Exception
neuroProcesses.py (1950) in _processExecution:
result = process.execution( self )
neuroProcesses.py (749) in execution:
return self._executionNode.run( context )
neuroProcesses.py (1322) in run:
return self._run( context )
neuroProcesses.py (1508) in _run:
result.append( node.run( context ) )
neuroProcesses.py (1322) in run:
return self._run( context )
neuroProcesses.py (1435) in _run:
return context.runProcess( self._process )
neuroProcesses.py (1765) in runProcess:
apply( self._setArguments, (_process,)+args, kwargs )
neuroProcesses.py (1750) in _setArguments:
_process.checkArguments()
neuroProcesses.py (418) in checkArguments:
o.checkValue( p, getattr( self, p, None ) )
writediskitem.py (49) in checkValue:
Parameter.checkValue( self, name, value )
neuroData.py (93) in checkValue:
raise Exception( HTMLMessage(_t_('argument <em>%s</em> is mandatory') % name) )
Process T1 Pipeline 2007 8 finished on 2010/07/08 15:29 (0 seconds)
BV4-T1 Pipeline: not finding Commissure_coordinates properly
- riviere
- Site Admin
- Posts: 1361
- Joined: Tue Jan 06, 2004 12:21 pm
- Location: CEA NeuroSpin, Saint Aubin, France
- Contact:
Re: BV4-T1 Pipeline: not finding Commissure_coordinates properly
Hi Michel,
The Commissure_coordinates parameters is the filename where the AC/PC coords will be written, not the coordinates values themselves. So if the filename is not filled, even if the AC/PC positions are correctly entered, you will still get this error. Now why does it not fill automatically, did you setup and use a database in the usual way ? Is there an ambiguity somewhere in your database ? Did you update the database after switching to BV 4.0 ? It must be a little thing like that...
Denis
The Commissure_coordinates parameters is the filename where the AC/PC coords will be written, not the coordinates values themselves. So if the filename is not filled, even if the AC/PC positions are correctly entered, you will still get this error. Now why does it not fill automatically, did you setup and use a database in the usual way ? Is there an ambiguity somewhere in your database ? Did you update the database after switching to BV 4.0 ? It must be a little thing like that...
Denis