I'm still playing around with Cygwin/FSL, and I'm using CamBA (from the
BMU in Cambridge) and FSL (from FMRIB in Oxford), both in text-mode.
They both work like a dream!!!
Both these programs have GUIs, but getting those to work in CygWin is
quite a feat (no pun intended).
The reason I keep using FSL is the fact that you can do so many things
that are simple, but very time-comsuming in other programs (masking,
conversion from NIFTI to ANALYZE and back, etc) and the avw* utilities
do them in one command line.
The reason I want to use CamBA is to be able to use (nonparametric)
permutation tests on all levels of the fMRI analysis.
In command-line mode, both of these work brilliantly in Cygwin. I would
recommend (or even SCP) them to anyone.
I know that the GUIs of both programs could easily be separated from the
computing code, although the script/log that (eg) the FEAT GUI produces
is not runnable straight from the shell prompt.
Getting their GUIs to run is problematic. Maybe it is an idea to
separate the GUI bit from the computing bit, so that it is possible to
compile the computing bit without having any Tcl/Tk or java code, and
for those who want it, compile the GUI after that?
Another reason for doing it like this is that the Cygwin part of your
harddisk is much smaller, because the Tcl/Tk (reasonably large) and Java
(huge) do not need to be on there.
Any thoughts on that?
bw
Alle Meije Wink
Paul Macey wrote:
> Hi
>
> I find the cygwin very handy for making calls from matlab scripts, which
> lets me combine the useful features of FSL/SPM... so I would vote for a
> cygwin release! I have installed VMPlayer, and it took quite a while to
> get it running properly; it is certainly more complicated to install
> than cygwin, even with having to use the 2005 cygwin release.
>
> Best wishes,
> Paul
|