Hi, Joy-

What happened in the lines just preceding that ERROR message? My guess is that failure occurs because a previous step in the script failed (is there a "killed" message, perhaps, of running out of memory?), so that an expected file wasn't created and therefore caused this error. That is, this cascade of error messages probably started with some earlier woe, but I'm not sure...

Sidenote:
It can be useful to capture the output of scripts/commands while they run, so you don't have to copy+paste from a terminal; you can search more easily in text files, and/or send them in when you have a question. To do *that*, you first have to know what shell you use in a terminal. To discover that, type:

echo $0

(that last character is a zero), and see whether the output is:
+ "bash" or or "-bash" (in which case you have a "bash" terminal shell)
+ "tcsh" or or "-tcsh" (in which case you have a "tcsh" terminal shell), or "csh" (which is "csh" close enough to "tcsh" to be treated the same here)
+ or something else (which I will ignore here, because of my own ignorance).

Then, consider you have a COMMAND to run, such as "@SSwarper -input ...", and you want to put a *copy* of everything that shows up in the terminal into a text file as well. For a *bash* shell, you can do this:

COMMAND 2>&1 | tee o.command_copy.txt

and for a *tcsh* shell, you can do this:

COMMAND |& tee o.command_copy.txt

(There is nothing special about the *.txt filename after the command "tee"; you can/should make it something meaningful.)

This doesn't help retrospectively, but can be useful, esp. as you try out new script commands that produce lots of outputs.

-pt