From: zorze...@hotmail.com
To: freesurfer@nmr.mgh.harvard.edu
Subject:
Date: Thu, 6 Aug 2015 07:42:40 +0200
Hi,
The recon pipeline outputed an apparently correct file, which happen to confuse
freesurfer reading functions.
I attached a slightly-altered file named lh.data_crash which have t
Hi,
The recon pipeline outputed an apparently correct file, which happen to confuse
freesurfer reading functions.
I attached a slightly-altered file named lh.data_crash which have the same
problem. The other file named lh.data_nocrash seems to be parsed fine, despite
differing by only 1 float-
> # I've tested it, but (obviously, things can go
> wrong). If so, you can > restore from your backup:> cd
> $FREESURFER_HOME/fsfast/toolbox> cp temp/* .> > Let me know how it goes> >
> doug> > > Lionel zorzevic wrote:> > >Dear Dr Greve
Dear Dr Greve,
As I tried to introduce time-point exclusions in an analysis, selxavg3-sess
returned the following error:
ERROR: time points in
/.automount/space3/newfspace/070630_METRAPI_TM05/bold/001/spike.txt exceed
nframes (91)
91 corresponds to run length in TR (but not in seconds)
Dear Dr Greve,
As I tried to introduce time-point exclusions in an analysis, selxavg3-sess
returned the following error:
ERROR: time points in
/.automount/space3/newfspace/070630_METRAPI_TM05/bold/001/spike.txt exceed
nframes (91)
91 corresponds to run length in TR (but not in seconds)
