Glad to hear it
Bruce



On Jun 13, 2012, at 7:30 AM, Anders Hougaard <ahougaard@dadlnet.dk> wrote:

Hi Bruce,

That actually seems to do the trick. Thank you very much!

Best,
Anders

2012/6/12 Bruce Fischl <fischl@nmr.mgh.harvard.edu>
try symlinking the ?h.white surfaces to the ?h.smoothwm and see if that solves your problem

cheers
Bruce

On Tue, 12 Jun 2012, Anders Hougaard wrote:

Dear Dr. Bock,
I get the same error in FS 5.1.0 when running  recon-all -s <subject>
-label_v1.

Did you find a solution?

Best regards,

Anders Hougaard, MD
Danish Headache Center
Dept. of Neurology
Glostrup Hospital
Copenhagen
Denmark

2011/11/11 Andrew Bock <abock@u.washington.edu>
     Hello,

     I am having a similar problem to one described on the freesurfer
     mail archive, where I receive the following error when trying to
     identify V1 using the Hinds method (i.e. recon-all -s <subject>
     -label_v1):

     processing subject V1_average...
     MRISreadVertexPosition(white): could not open file
     /usr/local/freesurfer/subjects/V1_average/surf/rh.white
     No such file or directory
     MRISreadOriginalProperties: could not read surface file white
     No such file or directory
     could not read surface positions from white
     No such file or directory


     As Prof. Krish Singh indicated in July, it appears the problem
     occurs when trying to open rh.white (or lh.white) from the surf
     subdirectory in V1_average, which doesn't exist.

     I have run recon-all -s <subject> -make all, but it returns
     "make: Nothing to be done for `all'."

     Any help you can provide would be greatly appreciated!

     Thanks in advance,

     Andrew

     --
     Andrew Bock, Ph.D.
     Department of Psychology
     University of Washington
     Seattle, WA 98195
     Tel: 206.543.3817
     Fax: 206.685.3157
     abock@u.washington.edu

_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom
it is
addressed. If you believe this e-mail was sent to you in error and the
e-mail
contains patient information, please contact the Partners Compliance
HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you
in error
but does not contain patient information, please contact the sender
and properly
dispose of the e-mail.