our pleasure (most of the time)
On Thu, 29 Jun 2006, Sebastian Moeller
wrote:
Hi Nick, hi Bruce,
On 29. Jun 2006, at 00:39 Uhr, Nick Schmansky wrote:
The dev build is not posted on the web anymore, rather, bug fixes and
tested minor enhancements get folded into the stable build and release
Hi Nick, hi Bruce,
On 29. Jun 2006, at 00:39 Uhr, Nick Schmansky wrote:
The dev build is not posted on the web anymore, rather, bug fixes and
tested minor enhancements get folded into the stable build and released
periodically (so far, it seems about every six weeks).
Which, I might add, is re
The dev build is not posted on the web anymore, rather, bug fixes and
tested minor enhancements get folded into the stable build and released
periodically (so far, it seems about every six weeks).
A new stable release (v3.0.4) will be forthcoming, and I'll make sure
that the --conform flag of mr
yeah, I know. That's Doug vs. me (you can always tell the difference
based on whether the help is useful (Doug) or not (me)).
sorry,
Bruce
On Mon, 26 Jun
2006, Sebastian Moeller wrote:
Hi Bruce,
On 26. Jun 2006, at 16:49 Uhr, Bruce Fischl wrote:
yeah, sorry, that's on our list of things t
Hi Bruce,
On 26. Jun 2006, at 16:49 Uhr, Bruce Fischl wrote:
yeah, sorry, that's on our list of things to fix.
This will make a great tool even greater, thnanks. Then again, for the
smaller monkey brains the "fake the resolution to be 1mm isotropic"
does the trick nicely, once you know it, t
yeah, sorry, that's on our list of things to fix.
I just added a --conform to mri_info so that it will return "yes" or "no"
(also --type). Will be live in dev tomorrow. Nick: does the dev build go on
the web every day?
Bruce
On Mon, 26 Jun 2006,
Sebastian Moeller wrote:
Hi Bruce,
On 26.
Hi Bruce,
On 26. Jun 2006, at 16:15 Uhr, Bruce Fischl wrote:
it should - consider it a bug.
On a related note, is there an easy way to convince mri_info to just
spit out the type (UCHAR FLOAT etc.) so I can easily script whether the
conform step is necessary or not (instead of making the te
it should - consider it a bug. Have you tried mri_convert -cm (conform
to min)? That will make it 8 bit and isotropic, but at the highest linear
resolution it finds. I think that's what people here use when they're doing
monkey recons.
Bruce
On Mon, 26 Jun 2006, Sebastian Moeller wrote:
Hi
Hi Bruce,
On 26. Jun 2006, at 02:30 Uhr, Bruce Fischl wrote:
Hi Sebastian,
why do you want to run mri_normalize on non-conformed volumes? It
wasn't really built for it.
Well I have monkey data, which I feed into freesurfer, so only few of
the automatic step actually work for me. Therefore I
Hi Sebastian,
why do you want to run mri_normalize on non-conformed volumes? It wasn't
really built for it.
Bruce
On Sun, 25 Jun 2006, Sebastian Moeller wrote:
Hi List,
as the subject line says I am having problems running mri_normalize (on suse
9.3 x86_64, freesurfer centos4 x86_64 3.0.2
Hi List,
as the subject line says I am having problems running mri_normalize (on
suse 9.3 x86_64, freesurfer centos4 x86_64 3.0.2 release). When feeding
in slightly unconformed volumes (like 1mm isotropic 256 by 256 by 256
of type 3 (float)) mri_normalize's "-conform" argument fails (fully
un
11 matches
Mail list logo
