Hi,
I am really grateful for the FSL package and the great support. Thank
you so much for providing it for free and also giving such a thorough
support.
However, nothing can't be perfect and there is always space for
improvements. One aspect that I encounter pretty often when doing some
scripting is a inconsistency of function arguments between different
tools. I think this is most clear when comparing flirt and fnirt. While
flirt uses the '-' convention with a space before the next argument,
fnirt uses '--' with only '=' between the argument. Furthermore, some
arguments seem to be named differently, eg 'nn' and 'nearestneighbour'
for the interpolation method. I am currently writing a small wrapper
script that switches between fnirt and flirt, and I need to build in
some ad hoc correction routines that translate the arguments. It would
be great, if such workarounds could be avoided by using the arguments in
a consistent manner between the various tools.
I guess that such inconsistencies are rare and a result of the
development history, but whenever I encounter them they disturb my
workflow quiet a bit :'( . So I just wanted to make this suggestion.
Please don't feel offended, since I really do like working with the FSL
tools.
thanks,
wolf
|