Page Comparison

...

1. Redirect standard output and standard error streams as follows:

   1. If you don't want to examine the streams, you can discard them both: join error into output and send output to /dev/null by using -j y -o /dev/null. (If you have the -o option already defined in your job script, you will need to use this instead.)

   2. If you do want to examine one or both streams, first redirect the corresponding files into /localscratch while the job is running. Then at the end of the job, move the file(s) to network storage for accessible outside your job script for later review or processing.

      To keep standard error, redirect the .e file to /localscratch using -e /localscratch. Otherwise join it into the .o file using -j y or discard it using -e /dev/null.
      To keep standard output, redirect the .o file to /localscratch using -o /localscratch. Otherwise discard it using -o /dev/null.

      At the end of the job, move whatever files you didn't discard off the compute node's /localscratch drive into a location you can access later by adding the line below to the end of your script. In this example, I am collecting the .o and .e files into a subdirectory under my home directory called "output", but you can move them wherever you prefer:

      Code Block
      title for non-merged output
      mv $SGE_STDOUT_PATH ~/output mv $SGE_STDERR_PATH ~/output

      Note: If you merge the error stream into the output stream (that is, you specified the -j y option), there will be no .e file, so you only need to move the .o at the end of the job.

2. If your high throughput jobs need to read or write a large number of files, you should add commands to your job script to first copy any input files to /localscratch, accordingly modify the location where each processing step or program in the job expects input files and writes its intermediate and final result files, and add commands at the end of the job script to clean up and collect result files onto network storage (typically your home directory). The details depend on what your job needs to do, which programs it uses, and generally how it operates. If you would like further advice or assistance, please email us at research-computing@uiowa.edu.

...