Hi Eliz,
you're better of using stable for exactly this reason - we've tested it
extensively and it works quite well. Dev is on the other hand definitely
*not* stable.
Bruce
On Tue, 21 Mar 2006, Elizabeth Fenstermacher wrote:
Hey Bruce,
I had been using the dev environment, but I'm rerunning them now in the
stable per Nick's suggestion.
I didn't realize that it was an established, if relatively new, bug because I
hadn't had problems before.
Eliz
On Tue, 21 Mar 2006, Bruce Fischl wrote:
what version are you using?
On Tue, 21 Mar 2006, Elizabeth Fenstermacher wrote:
Yes that's exactly what's happening. Well I'm sorry to hear that this is
endemic now :(, but I'm glad I'm not crazy ...
On Tue, 21 Mar 2006, Bruce Fischl wrote:
Hi Eliz,
are they faulting in the middle of mri_ca_register? We've just started to
have this problem (despite successfully running it on our 80 hemisphere
test set!), and I'm tracking it down.
sorry :<
Bruce
On Tue, 21 Mar 2006, Elizabeth Fenstermacher wrote:
Hey All,
I have a few scans that I've been attempting to process that fail during
autorecon2. I've eliminated all scan acquisitions that looked
potentially problematic and attempted to rerun them. They both seem to
go through autorecon1 without incident. The errors I'm getting are the
somewhat ambiguous segmentation fault so I'm really not sure what manaul
interventions should be attempted or might be useful to get them to run.
Any suggestions would be greatly appreciated.
Scans:
/autofs/space/elvin_007/users/mci1/mci1_recon/batch2/991101rl-new/
/autofs/space/elvin_007/users/mci1/mci1_recon/batch2/991122so-new/
Thanks
Eliz
_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
