Hello Martin,
Can you modify this section in $FSLDIR/bin/atlasquery:
if [ `uname` = "Darwin" ] ; then
DYLD_LIBRARY_PATH=${FSLDIR}/bin/fslview.app/Contents/Frameworks
export DYLD_LIBRARY_PATH
${FSLDIR}/bin/atlasquery_bin "$1" "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9" "$10”
fi
to:
if [ `uname` = "Darwin" ] ; then
DYLD_LIBRARY_PATH=${FSLDIR}/bin/fslview.app/Contents/Frameworks
DYLD_FALLBACK_LIBRARY_PATH=/opt/X11/lib
export DYLD_LIBRARY_PATH DYLD_FALLBACK_LIBRARY_PATH
${FSLDIR}/bin/atlasquery_bin "$1" "$2" "$3" "$4" "$5" "$6" "$7" "$8" "$9" "$10”
fi
and let me know if that fixes the issue?
Kind Regards
Matthew
--------------------------------
Dr Matthew Webster
FMRIB Centre
John Radcliffe Hospital
University of Oxford
> On 22 Aug 2017, at 11:17, Martin Domin <[log in to unmask]> wrote:
>
> Hi Mark,
>
> thanks for the fast answer! The problem is, autoaq is using atlasquery, too, so the same segmentation faults are happening here.
> And, the problem existed with the pre-FSLeyes version, too. I hoped, an update would solve it, but it seems to be a more severe issue.
> Could there be an incompatibility of the dynlibs used by atlasquery? Version problems in QT or associated libraries?
>
> Best,
> Martin
>
> 2017-08-22 11:47 GMT+02:00 Mark Jenkinson <[log in to unmask]>:
> Hi,
>
> Others have also reported this and it seems to be related to the change from FSLView to FSLeyes. I recommend that you try the new tool autoaq - as that should do what you need with masks. If you want to use a coordinate, then just prepare an input mask for that with std2imgcoord and fslmaths with the -roi option (or use FSLeyes interactively).
>
> All the best,
> Mark
>
>
> > On 22 Aug 2017, at 10:26, Martin Domin <[log in to unmask]> wrote:
> >
> > Hello,
> >
> > as the subject already mentions the problem, I'm getting a segmentation fault during the use of atlasquery. It happens during the query step, not while e.g. requesting the available atlases.
> > I'm working on a MacPro, 10.10.5 (Yosemite) with the most current version of FSL (updated yesterday) - build 416.
> >
> > Are there perhaps any ideas that could help identifying the cause? Thank you in advance!
> >
> > Best,
> > Martin
>
|