James has an automatic script that will (re)process all your data after they have been collected.
The script uses a minimal number of processor nodes, and could take a day to complete
If you do NOT use dials for processing, run the script with dials option OFF, as shown in the example below.
     The default is ON, and will make for Much longer processing times.
here's what to do:

### get on to a fast computer
 > ssh octamus1

### cd into your processing directory, e.g.
 > cd inst/PI/dyMONyear
 > mkdir rollup
 > cd rollup
 > xds_rollup.com /data/mcfuser/inst/PI/dyMONyear  nodials  >! rollup.log &

###  IF you like you can watch the output of the log file like this:
 > tail -111f rollup.log    #####   <cntrl> C to quit "tailing" the output

###  you can exit from octamus1 anytime and the processing will continue on
 > exit

###  hours, or the nextday, later ...
### you can see/access your processed data from any machine, No need to be on octamus1:
 > cd inst/PI/dyMONyear/rollup/

## The xds_rollup.com script creates a directory for every wedge of data and names them wedge0001, wedge0002, etc. ...
## and also creates symbolic links with names that are more meaningful, based on the prefix, directory, and run_number.
## To see the directories do this:

 > ls -lrt | grep lrwx
lrwxrwxrwx 1 mcfuser 831_user    9 MON da 08:36 A_1_A1 -> wedge0001
lrwxrwxrwx 1 mcfuser 831_user    9 MON da 08:42 A_1_A1_2 -> wedge0002..

## Each of these directories will have a sub directory, "xds", look in there for your processed data.
### If you left the dials option ON then there will also be a directory named "dials"
## E.g., if you want to see if there's a CORRECT.LP in the output from Wedge A_1_A1  do this:

 >  cd A_1_A1/xds
 >  ls -lrt | grep CORRECT.LP
 -rw-r--r-- 1 mcfuser 831_user    123384 MON da 08:40 CORRECT.LP