Hi Sarah,

According to the errors, the scripts have shell errors in them (not necessarily AFNI errors). However, you may have already fixed some of them, since I do not see the same errors that would lead to the given error messages.

But error messages to be aware of:

a. XXX: Command not found.

This means that the shell does not know of program XXX (in your PATH), for whatever "XXX" program is in question.
This error usually means that there is are bad or simply missing line continuation characters (\).
Since your message says "-dset: Commmand not found" after the line "-dset 1 1376-006_stats+tlrc[20]", it is likely there is a missing '\' at the end of that line.

If there are apparent '\' characters at the ends of all lines and this error still appears, try something like:

file_tool -test -infile MY_SCRIPT.txt -prefix FIXED.txt

to fix or suggest lines that need fixing.

Note also that there is a "-dataTable: Command not found." error, suggesting a missing backslash in that script, too.


b. XXX: No match

This is also a shell error, and means there is a wildcard failure somewhere, due to characters like *?[.
It tends to mean that you need "quotes" around some sub-brick selectors. The 3dMVM command seems to be missing quotes around all inputs. Note that if the data table is in an external file that you pass to 3dMVM, the quotes are not needed.

Does that seem reasonable?

- rick