Hi, Mrinmayi-
Thanks, I have started looking at this now. As with most things (and particularly with afni_proc.py), Rick's suggestion will probably be the best way forward.
NB: If you could use a more uptodate AFNI version, that would reeeallly be recommendable.
Even if the official server one is managed by someone else, coudl you just put a copy of the binaries in your own home directory, and put that location into your $PATH ahead of the other version? That way, you know that the OS is set up to run AFNI already (because the server can run it), but you have your own, updatable version?
You appear to be using the OpenMP_64 version, and assuming that you do *not* already have a copy of AFNI binaries (or anything else) in a directory "~/abin", you could do the following to go to your home directory, download the binaries there, unpack them, and move them into ~/abin:
cd
wget [afni.nimh.nih.gov]
tar -xf linux_openmp_64.tgz
mv linux_openmp_64 abin
... and then edit your ~/.bashrc and ~/.cshrc files to have this "$HOME/abin" location first in your path.
If you then open a new terminal or source the ~/.*rc file of your current shell, you could then check that "which afni" shows *that* path location, and you can use this one.
That might be what I would do in order to keep up wtih a modern AFNI versioning, if that seems reasonable. You should even be able to stay uptodate by just running "@update.afni.binaries -d" as usual, because this new version will be your AFNI of choice.
--pt
