Hi Michelle, this almost surely means that the surfaces are
out-of-synch. You can try
recon-all -s subject -make all -dontrun
on one of your subjects.
If everything is in synch, then it should print
make: Nothing to be done for `all'.
If not, it should print out the steps that it would have
Hey Doug and Freesurfers,
At the bottom is the output showing what steps didn't run.
1) Do you think I did the whole recon-all pipeline wrong? Here's what i did
after I originally ran recon-all -all -label_v1:
I made edits with talairach registration edits with tkregister2 and ran
recon-all
The gcareg step depends on the talairach registration, so if that is
changed, it thinks that the gcareg needs to change. If the gcareg needs
to change, then the canorm needs to change, and so on. This does not
mean that anything really needs to be updated. This is strictly looking
at the time
Hi Doug and Freesurfers,
I ran the -vno-check and the number of vertices matches for left and right
hemispheres (see below):
Since all there are an equal number of vertices, how is the mismatch error
occurring in fieldsign-sess and how do I get it to run?
Thanks for all your help.
Michelle
Dear Freesurfers,
This is related to my retinotopy analysis tksurfer-sess dimension
mismatch error message.
So another subject had these errors come up during fieldsign-sess
selxavg3-sess -a rtopy.self.lh -s sjXX -force
(which ran without error)
then I ran fieldsign
fieldsign-sess -a
Is the occip patch out of synch with the subject? Does it run if you use
-sphere instead of -occip?
doug
Michelle Umali wrote:
Dear Freesurfers,
This is related to my retinotopy analysis tksurfer-sess dimension
mismatch error message.
So another subject had these errors come up during
Hi Doug,
I get the same MRISripZeros() and MRIScopyMRI Surf/src mismatch error
when I use -sphere and not -occip in fieldsign-sess.
What else should I try?
Thank you.
Michelle
On Tue, Sep 27, 2011 at 8:51 PM, Douglas N Greve
gr...@nmr.mgh.harvard.edu wrote:
Is the occip patch out of synch
