Hi Allison,
Could this be due to lack of Field Of View in the
inferior region? It is known that FIRST can be
sensitive to this when segmenting the brainstem. You
can check this by running it without the brainstem
by adding the option:
-s
L_Accu
,L_Amyg
,L_Caud
,L_Hipp
,L_Late
,L_Pall
,L_Puta,L_Thal,R_Accu,R_Amyg,R_Caud,R_Hipp,R_Late,R_Pall,R_Puta,R_Thal
which will do this list of structures (which does
not include the brainstem).
Let us know whether this fixes it or not.
All the best,
Mark
On 31 Jul 2010, at 02:21, Allison Nugent wrote:
> Hello,
>
> I'm writing because I'm experiencing what seems to be a known issue:
>
> https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind0803&L=FSL&P=R38933&1=FSL&9=A&J=on&d=No+Match%3BMatch%3BMatches&z=4
>
> I was wondering if there was any fix found besides switching to a 64-
> bit machine.
>
> Only certain images cause this segmentation fault, while other
> images of identical resolution and file size run just fine, which
> seems to argue against a memory problem. In my case, it seems that
> images acquired more recently are the problematic ones, while older
> images run just fine.
>
> Thanks!
>
> Allison
>
|