Hi, Mark.
Though FSL4.1.4 has one invwarp in /fsl/bin file ,i.e "invwarp",
FSL4.1.5 has two invwarp , i.e "invwarp" and "invwarp_exe".
When I exchanged "invwarp" for "invwarp_exe" in tbss_deproject(FSL4.1.5) as
below,
tbss_deproject was executed without trouble.
You might understand this difference.
** tbss_deproject(FSL4.1.5) **
......
for g in $list ; do
echo "processing ${g}:"
nextvol=`$FSLDIR/bin/imglob ../stats/${IN}_to_all_FA_tmp0* | awk '{print $1}'`
warp=${g}_to_${target}_warp
if [ `$FSLDIR/bin/imtest ${warp}_inv` = 0 ] ; then
# $FSLDIR/bin/invwarp -w $warp -o ${warp}_inv -r $g
$FSLDIR/bin/invwarp_exe -w $warp -o ${warp}_inv -r $g
fi
......
I hope this is useful.
kenji
On Mon, 8 Feb 2010 21:33:43 +0000, Mark Jenkinson <[log in to unmask]> wrote:
>Hi,
>
>We are unaware of any unresolved bugs with invwarp and tbss.
>Can you please be more specific about what happens?
>
>All the best,
> Mark
>
>
>On 8 Feb 2010, at 19:04, Kenji wrote:
>
>> Hi FSL experts,
>>
>> I have recently discovered a bug in the "tbss_deproject grot 2" in
>> FSL 4.1.5.
>> I think this error might be due to a bug in the invwarp script.
>>
>> When I use the invwarp in FSL4.1.4 instead of it in FSL4.1.5,
>> I could execute "tbss_deproject grot 2" in FSL4.1.5.
>>
>> Maybe, has the bug already been corrected ?
>>
>> Kenji
>>
