#  moo.condor
#
#  Modified:
#
#    02 March 2006
#
#  Discussion:
#
#    This is a simple example of a condor submit description file
#    appropriate when a COMPILED PROGRAM (written in C, C++ or
#    FORTRAN) is to be run on a single processor.
#
#    The "universe" is "vanilla".  This environment is only suitable
#    for programs which do not need checkpointing, remote system calls
#    and other features provided by the CONDOR library.  A shell
#    script is a very simple example of such a program.
#
#    The "initial directory" tells CONDOR the name of the working
#    directory.  Note that the actual directory I wanted to specify
#    is
#      /a/fs.csit.fsu.edu/u8/users/burkardt/phoenix_test
#    (which failed) but on advice of counsel, I changed this to
#      /home/u8/users/burkardt/phoenix_test
#
#    The "executable" is the compiled version of "moo.c".  
#    I had to compile this program on PHOENIX, and submit my CONDOR
#    job from Phoenix, in order to guarantee that the compiled
#    program would run on the type of machine it was suitable for.
#
#    No platform is specified, so the default will be used, that is,
#    the job will be run on a machine which has the same architecture
#    and operating system as the machine from which the job was submitted.
#
#    The output command specifies a file into which the output from
#    the program will be written.
#
#    A log file "moo.log" will be produced, containing events that
#    occur during the execution of the job.
#
universe = vanilla
initialdir = /home/u8/users/burkardt/phoenix_test
executable = moo
log = moo.log
output = moo.output
queue