Difference: HowToUseCondor (1 vs. 18)

Revision 1831 Jul 2008 - brodbd

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Changed:
< <	You need to create a submit description file telling Condor how to run your program. For example, let's say we have a program called `CGI foobar` that accepts input on stdin, produces output on stdout, and accepts a few command line arguments. To run this program normally, you might do something like this:
> >	You need to create a submit description file (sometimes referred to as a submit script) telling Condor how to run your program. For example, let's say we have a program called `CGI foobar` that accepts input on stdin, produces output on stdout, and accepts a few command line arguments. To run this program normally, you might do something like this:
	`CGI foobar -a -n <foobar.in >foobar.out` Here's a sample Condor submit file (let's call it `CGI foobar.cmd`) that does the same thing:

Revision 1721 Feb 2008 - brodbd

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 73 to 73
	If you want to put input, output, or error files on a non-shared filesystem such as /tmp, you can add `CGI stream_input=true`, `CGI stream_output=true`, and/or `CGI stream_error=true` to your submit file. This tells Condor to pipe the output back to the original submitting system instead of creating the file on the node.
Changed:
< <	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.
> >	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Additionally, processes on patas itself are limited to no more than 2 GB of RAM. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.

Changed:
< <	-- brodbd - 01 Feb 2008
> >	-- brodbd - 21 Feb 2008

Revision 1601 Feb 2008 - brodbd

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 51 to 51
	Additionally, CondorView provides status graphs, updated every 15 minutes. Advanced options
Changed:
< <	It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. See `CGI /condor/condor-6.8.5/examples/loop.cmd` for a good, well-documented example of this.
> >	It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. See `CGI /condor/examples/loop.cmd` for a good, well-documented example of this.
	Multiple submissions can also be automated; for example, if we wanted to run the above job three times, with input files named "foobar.in0" through "foobar.in2", we could do the following:
Line: 75 to 75
	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.
Changed:
< <	-- DavidBrodbeck - 11 Jan 2008
> >	-- brodbd - 01 Feb 2008

Revision 1511 Jan 2008 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 28 to 28
	Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea. Input, output, and error files can go to your home directory. transfer_executable = false tells Condor it does not need to copy the executable file to the compute node. This is usually the case, since the cluster nodes share a common filesystem.
Changed:
< <	`CGI /condor/condor-6.8.5/examples` contains some sample jobs. You may want to examine some of the submit description files there to get a better feel for how this works in different situations.
> >	`CGI /condor/examples` contains some sample jobs. You may want to examine some of the submit description files there to get a better feel for how this works in different situations.
	Note: If your email address is not of the form username@u.washington.edu, or if your cluster login and your University netid don't match, you should add a notify_user line to the submit description file to tell condor where to send mail. For example:
Line: 75 to 75
	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.
Changed:
< <	-- DavidBrodbeck - 26 Nov 2007
> >	-- DavidBrodbeck - 11 Jan 2008

Revision 1426 Nov 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 69 to 69
	`CGI $(Process)` is a variable substitution; it will be replaced by the process number of each process that's queued. Consult the condor_submit manpage (`CGI man condor_submit`) for more details. Things to keep in mind
Changed:
< <	Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, /projects, /NLP_TOOLS, and /corpora are shared; however, /tmp is not. Condor will automatically transfer executables, input, and output files, but not necessarily libraries, modules, or additional files your software tries to open. Make sure these items are located on one of the shared filesystems.
> >	Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, /projects, /NLP_TOOLS, and /corpora are shared; however, /tmp is not. Make sure everything your job needs is located on one of the shared filesystems. If you want to put input, output, or error files on a non-shared filesystem such as /tmp, you can add `CGI stream_input=true`, `CGI stream_output=true`, and/or `CGI stream_error=true` to your submit file. This tells Condor to pipe the output back to the original submitting system instead of creating the file on the node.
	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.
Changed:
< <	-- DavidBrodbeck - 11 Oct 2007
> >	-- DavidBrodbeck - 26 Nov 2007

Revision 1311 Oct 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 20 to 20
	A few of these lines require explanation.
Added:
> >	The Executable line tells Condor what program we want to run. The default path is the current directory. If the executable is somewhere else, you need to supply the full path -- Condor will not search for it the way the shell does. If you need to know the full path to a program that's in your default path, use the `CGI which` command at a shell prompt. For example: `CGI which lexparser.csh`
	Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; and `CGI java`, for running Java programs directly. See the Condor manual for more information about these universes. The `CGI PVM` universe is not currently supported, but see the PVMOnPatas Wiki page for information on how to run PVM directly. getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries. Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea. Input, output, and error files can go to your home directory.
Line: 70 to 73
	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.
Changed:
< <	-- DavidBrodbeck - 24 Sep 2007
> >	-- DavidBrodbeck - 11 Oct 2007

Revision 1224 Sep 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 15 to 15
	error = foobar.error Log = /tmp/brodbd/foobar.log arguments = "-a -n"
Added:
> >	transfer_executable = false
	Queue
Line: 22 to 23
	Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; and `CGI java`, for running Java programs directly. See the Condor manual for more information about these universes. The `CGI PVM` universe is not currently supported, but see the PVMOnPatas Wiki page for information on how to run PVM directly. getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries. Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea. Input, output, and error files can go to your home directory.
Added:
> >	transfer_executable = false tells Condor it does not need to copy the executable file to the compute node. This is usually the case, since the cluster nodes share a common filesystem.
	`CGI /condor/condor-6.8.5/examples` contains some sample jobs. You may want to examine some of the submit description files there to get a better feel for how this works in different situations.
Line: 45 to 47
	Additionally, CondorView provides status graphs, updated every 15 minutes.
Deleted:
< <	Reducing startup time By default, Condor will automatically copy your executable file to the compute node. If you know that the executable files are already accessible to the node (e.g., files in your home directory, which is on a shared filesystem) you can reduce the amount of time needed to start your job by telling Condor not to transfer those files. You can do this by adding the following line to your submit file, above the queue line: transfer_executable = false This also greatly reduces the load on the file server, which tends to be a choke point when queueing a large number of jobs simultaneously. Most of the time you will want this line in your submit file. All of the nodes have the same software load, and /home, /opt, /project, and /NLP_TOOLS are shared by all nodes. Generally speaking you should start with transfer_executable set to false, and only set it to true if you have problems.
	Advanced options It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. See `CGI /condor/condor-6.8.5/examples/loop.cmd` for a good, well-documented example of this.
Line: 77 to 70
	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive.
Changed:
< <	-- DavidBrodbeck - 23 Aug 2007
> >	-- DavidBrodbeck - 24 Sep 2007

Revision 1123 Aug 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 75 to 75
	Things to keep in mind Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, /projects, /NLP_TOOLS, and /corpora are shared; however, /tmp is not. Condor will automatically transfer executables, input, and output files, but not necessarily libraries, modules, or additional files your software tries to open. Make sure these items are located on one of the shared filesystems.
Changed:
< <	-- DavidBrodbeck - 17 Aug 2007
> >	To keep the cluster responsive, long-running processes run on patas itself will automatically have their CPU priority lowered. Processes submitted to Condor are not affected by this, so you should try to use Condor for anything CPU-intensive. -- DavidBrodbeck - 23 Aug 2007

Revision 1022 Aug 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 46 to 46
	Additionally, CondorView provides status graphs, updated every 15 minutes. Reducing startup time
Changed:
< <	By default, Condor will automatically copy your executable file to the compute node. If you know that the executable files are already accessible to the node (e.g., files in your home directory, which is on a shared filesystem) you can greatly reduce the amount of time needed to start your job by telling Condor not to transfer those files. You can do this by adding the following line to your submit file, above the queue line:
> >	By default, Condor will automatically copy your executable file to the compute node. If you know that the executable files are already accessible to the node (e.g., files in your home directory, which is on a shared filesystem) you can reduce the amount of time needed to start your job by telling Condor not to transfer those files. You can do this by adding the following line to your submit file, above the queue line:
	transfer_executable = false

Revision 917 Aug 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 45 to 45
	Additionally, CondorView provides status graphs, updated every 15 minutes.
Added:
> >	Reducing startup time By default, Condor will automatically copy your executable file to the compute node. If you know that the executable files are already accessible to the node (e.g., files in your home directory, which is on a shared filesystem) you can greatly reduce the amount of time needed to start your job by telling Condor not to transfer those files. You can do this by adding the following line to your submit file, above the queue line: transfer_executable = false This also greatly reduces the load on the file server, which tends to be a choke point when queueing a large number of jobs simultaneously. Most of the time you will want this line in your submit file. All of the nodes have the same software load, and /home, /opt, /project, and /NLP_TOOLS are shared by all nodes. Generally speaking you should start with transfer_executable set to false, and only set it to true if you have problems.
	Advanced options It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. See `CGI /condor/condor-6.8.5/examples/loop.cmd` for a good, well-documented example of this.
Line: 64 to 73
	`CGI $(Process)` is a variable substitution; it will be replaced by the process number of each process that's queued. Consult the condor_submit manpage (`CGI man condor_submit`) for more details. Things to keep in mind
Changed:
< <	Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, and /corpora are shared; however, /tmp is not, so if you need to place input or output files there you'll need to investigate the `CGI should_transfer_files` option, described in the condor_submit manpage and in the Condor user manual.
> >	Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, /projects, /NLP_TOOLS, and /corpora are shared; however, /tmp is not. Condor will automatically transfer executables, input, and output files, but not necessarily libraries, modules, or additional files your software tries to open. Make sure these items are located on one of the shared filesystems.

Changed:
< <	-- DavidBrodbeck - 19 Jul 2007
> >	-- DavidBrodbeck - 17 Aug 2007

Revision 819 Jul 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 43 to 43
	`CGI condor_hold` and `CGI condor_rm` put a job on hold and delete it from the queue, respectively. All of these commands have manual pages that may be displayed with the `CGI man` command.
Added:
> >	Additionally, CondorView provides status graphs, updated every 15 minutes.
	Advanced options It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. See `CGI /condor/condor-6.8.5/examples/loop.cmd` for a good, well-documented example of this.

Revision 719 Jul 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 21 to 21
	A few of these lines require explanation. Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; and `CGI java`, for running Java programs directly. See the Condor manual for more information about these universes. The `CGI PVM` universe is not currently supported, but see the PVMOnPatas Wiki page for information on how to run PVM directly. getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries.
Changed:
< <	Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea.
> >	Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea. Input, output, and error files can go to your home directory.
	`CGI /condor/condor-6.8.5/examples` contains some sample jobs. You may want to examine some of the submit description files there to get a better feel for how this works in different situations.
Line: 64 to 64
	Things to keep in mind Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, and /corpora are shared; however, /tmp is not, so if you need to place input or output files there you'll need to investigate the `CGI should_transfer_files` option, described in the condor_submit manpage and in the Condor user manual.
Changed:
< <	-- DavidBrodbeck - 11 Jul 2007
> >	-- DavidBrodbeck - 19 Jul 2007

Revision 618 Jul 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 34 to 34
	Now that you have a description file, submitting it is as simple as: `CGI condor_submit foobar.cmd`
Changed:
< <	The job will be queued and run on the first available machine. You will receive an email message when it completes.
> >	The job will be queued and run on the first available machine. You will receive an email message when it completes, either at your UW address or at the one you specified in the `CGI notify_user` line in the submit file.
	Managing jobs
Changed:
< <	The easiest way to track the progress of your job is to check the logfile. The following commands are also helpful:
> >	The easiest way to track the progress of your job is to check its logfile. The following commands are also helpful:
	`CGI condor_status` lists available nodes and their status. `CGI condor_q` lists the job queue. `CGI condor_hold` and `CGI condor_rm` put a job on hold and delete it from the queue, respectively.

Revision 513 Jul 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 19 to 19
	A few of these lines require explanation.
Changed:
< <	Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; `CGI java`, for running Java programs directly. See the Condor manual for more information about these universes. The `CGI PVM` universe is not currently supported, but see the PVMOnKong Wiki page for information on how to run PVM directly.
> >	Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; and `CGI java`, for running Java programs directly. See the Condor manual for more information about these universes. The `CGI PVM` universe is not currently supported, but see the PVMOnPatas Wiki page for information on how to run PVM directly.
	getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries. Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea.

Revision 412 Jul 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 25 to 25
	`CGI /condor/condor-6.8.5/examples` contains some sample jobs. You may want to examine some of the submit description files there to get a better feel for how this works in different situations.
Added:
> >	Note: If your email address is not of the form username@u.washington.edu, or if your cluster login and your University netid don't match, you should add a notify_user line to the submit description file to tell condor where to send mail. For example: notify_user = jdoe@example.com
	Submitting the job Now that you have a description file, submitting it is as simple as: `CGI condor_submit foobar.cmd`

Revision 312 Jul 2007 - DavidBrodbeck

Line: 1 to 1
	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file
Line: 19 to 19
	A few of these lines require explanation.
Changed:
< <	Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; `CGI java`, for running Java programs directly; and `CGI PVM`, for PVM applications. See the Condor manual for more information about these universes.
> >	Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; `CGI java`, for running Java programs directly. See the Condor manual for more information about these universes. The `CGI PVM` universe is not currently supported, but see the PVMOnKong Wiki page for information on how to run PVM directly.
	getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries. Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea.

Revision 211 Jul 2007 - DavidBrodbeck

  How do I use it?  A quick Condor tutorial 
 How do I set up a job? 
 Creating a submit description file 
You need to create a submit description file telling Condor how to run your program.  For example, let's say we have a program called CGI foobar that accepts input on stdin, produces output on stdout, and accepts a few command line arguments.  To run this program normally, you might do something like this:
CGI foobar -a -n <foobar.in >foobar.out
-<
<
+Here's a sample Condor submit file that does the same thing:
->
>
+Here's a sample Condor submit file (let's call it CGI foobar.cmd) that does the same thing:
 Executable = foobar
Universe   = vanilla
  getenv = true transfers all the environment variables that are set in the submitter's shell.  This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries.
  Log indicates where the Condor log file for this job should go.  Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea.
->
>
+CGI /condor/condor-6.8.5/examples contains some sample jobs.  You may want to examine some of the submit description files there to get a better feel for how this works in different situations.
  Submitting the job 
Now that you have a description file, submitting it is as simple as:
CGI condor_submit foobar.cmd
  Managing jobs 
The easiest way to track the progress of your job is to check the logfile.  The following commands are also helpful:
-<
<
+ CGI condor_status lists available nodes and their status
->
>
+ CGI condor_status lists available nodes and their status.
  CGI condor_q lists the job queue.
  CGI condor_hold and CGI condor_rm put a job on hold and delete it from the queue, respectively.
->
>
+All of these commands have manual pages that may be displayed with the CGI man command.
  Advanced options
-<
<
+It's possible to submit multiple jobs with one submit file, using multiple Queue lines.  Each submission can have different parameters.  This can also be automated; for example, if we wanted to run the above job three times, with input files named "foobar.in0" through "foobar.in2", we could do the following:
->
>
+It's possible to submit multiple jobs with one submit file, using multiple Queue lines.  Each submission can have different parameters.  See CGI /condor/condor-6.8.5/examples/loop.cmd for a good, well-documented example of this.

Multiple submissions can also be automated; for example, if we wanted to run the above job three times, with input files named "foobar.in0" through "foobar.in2", we could do the following:
 Executable = foobar
Universe   = vanilla
 Queue 3
-<
<
+Consult the condor_submit manpage (CGI man condor_submit) for more details.
->
>
+CGI $(Process) is a variable substitution; it will be replaced by the process number of each process that's queued.  Consult the condor_submit manpage (CGI man condor_submit) for more details.
  Things to keep in mind
-<
<
+Because the job will actually be run on a compute node, it's important to make sure that it will be able to access all the files it needs.  Home directories, /opt, and /corpora are shared; however, /tmp is not, so if you place input or output files there you'll need to investigate the CGI should_transfer_files option, described in the condor_submit manpage and in the Condor user manual.
->
>
+Because the job will actually be run on a compute node, not on the system you're logged into, it's important to make sure that it will be able to access all the files it needs.  Home directories, /opt, and /corpora are shared; however, /tmp is not, so if you need to place input or output files there you'll need to investigate the CGI should_transfer_files option, described in the condor_submit manpage and in the Condor user manual.
-<
<
+-- DavidBrodbeck - 10 Jul 2007
->
>
+-- DavidBrodbeck - 11 Jul 2007

Revision 111 Jul 2007 - DavidBrodbeck

Line: 1 to 1

Line: 1 to 1
Added:
> >	How do I use it? A quick Condor tutorial How do I set up a job? Creating a submit description file You need to create a submit description file telling Condor how to run your program. For example, let's say we have a program called `CGI foobar` that accepts input on stdin, produces output on stdout, and accepts a few command line arguments. To run this program normally, you might do something like this: `CGI foobar -a -n <foobar.in >foobar.out` Here's a sample Condor submit file that does the same thing: Executable = foobar Universe = vanilla getenv = true input = foobar.in output = foobar.out error = foobar.error Log = /tmp/brodbd/foobar.log arguments = "-a -n" Queue A few of these lines require explanation. Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include `CGI standard`, for programs that are linked with the Condor libraries and support checkpointing and restarting; `CGI java`, for running Java programs directly; and `CGI PVM`, for PVM applications. See the Condor manual for more information about these universes. getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries. Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea. Submitting the job Now that you have a description file, submitting it is as simple as: `CGI condor_submit foobar.cmd` The job will be queued and run on the first available machine. You will receive an email message when it completes. Managing jobs The easiest way to track the progress of your job is to check the logfile. The following commands are also helpful: `CGI condor_status` lists available nodes and their status `CGI condor_q` lists the job queue. `CGI condor_hold` and `CGI condor_rm` put a job on hold and delete it from the queue, respectively. Advanced options It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. This can also be automated; for example, if we wanted to run the above job three times, with input files named "foobar.in0" through "foobar.in2", we could do the following: Executable = foobar Universe = vanilla getenv = true input = foobar.in$(Process) output = foobar.out$(Process) error = foobar.error$(Process) Log = /tmp/brodbd/foobar.log arguments = "-a -n" Queue 3 Consult the condor_submit manpage (`CGI man condor_submit`) for more details. Things to keep in mind Because the job will actually be run on a compute node, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, and /corpora are shared; however, /tmp is not, so if you place input or output files there you'll need to investigate the `CGI should_transfer_files` option, described in the condor_submit manpage and in the Condor user manual. -- DavidBrodbeck - 10 Jul 2007

Added:

>
>

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

You need to create a submit description file telling Condor how to run your program. For example, let's say we have a program called CGI foobar that accepts input on stdin, produces output on stdout, and accepts a few command line arguments. To run this program normally, you might do something like this: CGI foobar -a -n <foobar.in >foobar.out

Here's a sample Condor submit file that does the same thing:

Executable = foobar
Universe   = vanilla
getenv     = true
input      = foobar.in
output     = foobar.out
error      = foobar.error
Log        = /tmp/brodbd/foobar.log
arguments  = "-a -n"
Queue

A few of these lines require explanation.

Universe = vanilla indicates that this is an ordinary program that does not support checkpointing. Other possibilities include CGI standard, for programs that are linked with the Condor libraries and support checkpointing and restarting; CGI java, for running Java programs directly; and CGI PVM, for PVM applications. See the Condor manual for more information about these universes.
getenv = true transfers all the environment variables that are set in the submitter's shell. This is what you want most of the time; much of our software depends on environment variables to locate binaries and libraries.
Log indicates where the Condor log file for this job should go. Condor complains if this is located on an NFS filesystem, so putting it in a subdirectory of /tmp is a good idea.

Submitting the job

Now that you have a description file, submitting it is as simple as: CGI condor_submit foobar.cmd

The job will be queued and run on the first available machine. You will receive an email message when it completes.

Managing jobs

The easiest way to track the progress of your job is to check the logfile. The following commands are also helpful:

CGI condor_status lists available nodes and their status
CGI condor_q lists the job queue.
CGI condor_hold and CGI condor_rm put a job on hold and delete it from the queue, respectively.

Advanced options

It's possible to submit multiple jobs with one submit file, using multiple Queue lines. Each submission can have different parameters. This can also be automated; for example, if we wanted to run the above job three times, with input files named "foobar.in0" through "foobar.in2", we could do the following:

Executable = foobar
Universe   = vanilla
getenv     = true
input      = foobar.in$(Process)
output     = foobar.out$(Process)
error      = foobar.error$(Process)
Log        = /tmp/brodbd/foobar.log
arguments  = "-a -n"
Queue 3

Consult the condor_submit manpage (CGI man condor_submit) for more details.

Things to keep in mind

Because the job will actually be run on a compute node, it's important to make sure that it will be able to access all the files it needs. Home directories, /opt, and /corpora are shared; however, /tmp is not, so if you place input or output files there you'll need to investigate the CGI should_transfer_files option, described in the condor_submit manpage and in the Condor user manual.

-- DavidBrodbeck - 10 Jul 2007

View topic | History: r18 < r17 < r16 < r15 | More topic actions...

Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback

Difference: HowToUseCondor (1 vs. 18)

Revision 1831 Jul 2008 - brodbd

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Revision 1721 Feb 2008 - brodbd

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Revision 1601 Feb 2008 - brodbd

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Advanced options

Revision 1511 Jan 2008 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Revision 1426 Nov 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Things to keep in mind

Revision 1311 Oct 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Revision 1224 Sep 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Reducing startup time

Advanced options

Revision 1123 Aug 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Things to keep in mind

Revision 1022 Aug 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Reducing startup time

Revision 917 Aug 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Reducing startup time

Advanced options

Things to keep in mind

Revision 819 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Advanced options

Revision 719 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Things to keep in mind

Revision 618 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Managing jobs

Revision 513 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Revision 412 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Submitting the job

Revision 312 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial

How do I set up a job?

Creating a submit description file

Revision 211 Jul 2007 - DavidBrodbeck

How do I use it? A quick Condor tutorial