#!/bin/csh -f # #PBS -N tux #PBS -r n #PBS -o tux.out #PBS -e tux.err #PBS -j oe #PBS -m abe #PBS -M <ADD EMAIL ADDRESS HERE!> #PBS -q firstname.lastname@example.org #PBS -l nodes=1:ppn=2 #PBS -l pmem=400mb #PBS -l walltime=2:00:00 set EXE = /apps/blender/2.44/blender cd /home/jka/ $EXE -b Tux.blend -f 1 -x 1 -t 2
Note that you should add your address to the appropriate line in this case. Also note that the walltime has been set to 2 hours. You will have to figure out through trial and error what the most appropriate amount of time for a rendering should be. In this particular example:
- Blender will render the first frame of either a static or dynamic animation.
- It will use two threads to perform this operation, hence defining that PBS should use two processors on a single node.
- The output of the frame will be wherever it was defined in the blend file that was originally saved.
Setting the proper path for the output in the blend file is critical, as this is a batch based system and you will have no idea which computational node actually does the processing. Be sure to set the output path to a known location in the global filesystem, either /scratch/ufhpc or /home/<username>. The default in linux is to set this to /tmp, which will simply dump the output to that directory on the local computational node, which means you will not get the results.