Hi
I am a new freesurfer user so I apologize in advance for the basic
questions.
If I already have my MPRAGE images in mgz format (i.e I don't need to
convert the raw dicom data with mri_convert), what changes to the
command line (below) do I need so that the all the correct data
directories
HI Stephen,
not quite raw image space, but mostly. Definitely not tal coords. We
resample into a 256^3 volume aligned with the native scanner coords.
cheers,
Bruce
On Wed,
30 Jul 2008, Stephen Rose wrote:
Hi
I am a new freesurfer user so I apologize in advance for the basic
questions.
If
Hi Stephen,
To follow up, your command line should work just fine, and will set up the
directories you need.
Jenni
On Wed, Jul 30, 2008 at 6:56 AM, Bruce Fischl <[EMAIL PROTECTED]>wrote:
> HI Stephen,
>
> not quite raw image space, but mostly. Definitely not tal coords. We
> resample into a 256
Dear all,
I wanted to open qdec for the first time and experienced an error that was
posted some days ago...
( RE: [Freesurfer] qdec ERROR: Rendering vtkXOpenGLRenderWindow ; Juranek,
Jenifer )
" ERROR: In
/usr/pubsw/packages/vtk/5.0.4/src/VTK/Rendering/vtkXOpenGLRenderWindow.cxx,
line 219 vtkX
Dorit,
Which OS are you using? How is the X-server configured?
The solution to the problem posted by Jenifer (the error message 'Could
not find a decent visual') was to change the color depth from the 16bits
to 24bits in the /etc/xorg.conf file.
What error message is issued when it can't read
Hi,
Has anyone encountered this before? I have a few volumes for which
mri_watershed output volumes are fine apart from some non-zero voxels
near the edges (which are not connected to the brain). The volumes are
in transverse format and the most noticeable effect is some inferior
slices (ne
Hi Ian,
mri_watershed minimizes a risk functional in which we weigh the cost of
leaving non-brain voxels to be much less than stripping true brain ones,
so it does sometimes leave stuff around. Is this causing any problems?
Bruce
On
Wed, 30 Jul 2008, Ian Malone wrote:
Hi,
Has anyone enco
Do the vertex numbers mean anything significant or can they be any number?
Also, it appears that there are two different sets of vertices in an
mris_convert asc file of ?h.inflated. What are these vertices and what do
they mean?
___
Freesurfer mailing l
Hi Aaron,
no, they don't really mean anything. They are a side effect of a number
of algorithms (tesselation and topology correction). The .asc lists all the
vertices, then all the faces:
int
MRISwriteAscii(MRI_SURFACE *mris, char *fname)
{
int vno, fno, n ;
VERTEX *v ;
FACE*fa
