http://cswiki.wlu.edu/dokuwiki/ 2026-04-29T07:39:51+00:00 http://cswiki.wlu.edu/dokuwiki/ http://cswiki.wlu.edu/dokuwiki/lib/exe/fetch.php/wiki/dokuwiki-128.png text/html 2011-08-05T16:02:22+00:00 Anonymous (anonymous@undisclosed.example.com) http://cswiki.wlu.edu/dokuwiki/doku.php/condor/submit/checkpointing?rev=1312560142&do=diff Checkpointing Programs Benefits of Using condor_compile In order to run jobs in the “standard” universe, which supports special Condor features like checkpointing and I/O redirection. “Checkpointing” means that if Condor has to stop your job for any reason and move your job to another computer, such as if a person logged on to the computer, Condor can save the state of your program and use that state to start your program on another computer from where it left off. So, if you have a program … text/html 2012-07-27T18:32:40+00:00 Anonymous (anonymous@undisclosed.example.com) http://cswiki.wlu.edu/dokuwiki/doku.php/condor/submit/first?rev=1343413960&do=diff Submitting Your First Job For starters, Condor is good for running batch jobs. The jobs that are run with Condor are jobs that are submitted as one program with various sets of command line arguments that tell the program at runtime what its job is. For example, if you have a large set of data that needs to be processed by a program called text/html 2013-10-07T02:59:10+00:00 Anonymous (anonymous@undisclosed.example.com) http://cswiki.wlu.edu/dokuwiki/doku.php/condor/submit/module?rev=1381114750&do=diff Condor Python Module I have created a Python Module called condor to make it easy to submit jobs to a Condor cluster without having to deal with the complicated Condor submission scripts. The module can be downloaded or forked from the condor-py-scripting GitHub repository. text/html 2011-08-02T15:49:35+00:00 Anonymous (anonymous@undisclosed.example.com) http://cswiki.wlu.edu/dokuwiki/doku.php/condor/submit/troubleshoot?rev=1312300175&do=diff Troubleshooting Job Submissions Job Stays on Queue If your job appears to stay on the queue for a long time and you think there are execution machines that it should be able to run on, it may be that your program is executing on a machine but then encounters an error that causes it to be immediately killed. When this happens, the job is put back on the queue fast enough that you probably can't tell that it ever left.