Hi all,
I am facing the same problem with CentOS 5 and tksurfer.Is there any fix
for this problem?
Thank you,
-Dhruman
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nick
Schmansky
Sent: Tuesday, February 19, 2008 10:03 AM
To: [EMAIL PROTECTED]
Cc: Freesu
Hi Dhruman,
I had this problem with a Debian (Etch) system with an ATI card, and
the way I got it to work was to install the fglrx driver for the ATI
card. I also was missing a bunch of OpenGL stuff, too, but I think the
driver was the main issue. I'm unfamiliar with CentOS but these
inst
i just fixed something like this on ubuntu 7.10 with an ati radeon
x600. the latest drivers run on aiglx which conflicts with the
previous versions which run on xgl. this sometimes even caused X to
crash when running tksurfer and even glxgears.
on my system this was resolved by simply remov
When FreeSurfer performs the average of 2 or more scans to create rawavg.mgz,
is the 001.mgz used as the target to which all other scans are moved
/averaged to or is there some between-space alignment amongst the scans?
-Joel
___
Freesurfer mailing list
001.mgz is used as the target. If you have other scanns in orig (eg,
002.mgz, 003.mg, etc), then those are aligned to 001.mgz, then all are
averaged together.
doug
joel bruss wrote:
When FreeSurfer performs the average of 2 or more scans to create
rawavg.mgz, is the 001.mgz used as the
Hello,
We are beginning to explore the applicability of FreeSurfer for our
research. Having done some initial runs, we have the following
questions that I was hoping you might be able to address.
1.) For stats output, it seems there are two atlases for
parcellation, resulting in ?h.aparc
thanks Ray:
1. There were two different parcellation schemes, by different
neuroanatomists (one by Christophe Destrieux, and one by Rahul Desikan and
Ron Killiany).
2. The unknown in the desikan/killiany atlas is medial wall and
unfortunately much of the insula, which Ron is working on fixin
It looks like you have an awful lot of null in there
(6+7+8+6+7+8+11)*2 = 106 sec of stimulation
The total run length is 130*2 = 260 sec
Leaving 260-106 = 154 sec for null.
There are only 7*2=14 events total,
so the average null will be 154/14 = 11 sec
I'm surprised that one null was 75 sec, but
It should not be happening. Does it happen everytime you make an edit
and re-run with autorecon2-cp?
Teddy Youn wrote:
Hi all,
another quick question. I don't know if anyone else has encountered this
problem, but after making pial, wm and cp edits our group don't seem to retain
all our edi
