condor_submit {condor}

Condor Submit

Description

Submit a Condor job.

Usage

condor_submit(local.dir = ".", run.dir = NULL, top.dir = "condor",
  exclude = "condor_mfcl|tar.gz|End", session = NULL)

Arguments

local.dir

local directory containing a Condor *.sub file and any other files necessary to run the job.

run.dir

name of a Condor run directory to create inside top.dir.

top.dir

top directory on submitter machine that contains Condor run directories.

exclude

pattern identifying files in local.dir that should not be submitted to Condor.

session

optional object of class ssh_connect.

Details

The default value of run.dir = NULL runs the Condor job in top.dir/local.dir. For example, if local.dir = "c:/yft/run01" then the default run.dir becomes "condor/run01".

It can be practical to organize Condor runs inside the default top.dir = "condor" directory, to keep Condor runs separate from other directories inside the user home. To organize Condor runs directly in the home folder on the submitter machine, pass top.dir = "".

The default value of session = NULL looks for a session object in the user workspace. This allows the user to run Condor functions without explicitly specifying the session.

Value

Remote directory name with the job id as a name attribute.

Note

This function performs two core tasks: (1) upload files from local.dir to submitter machine, and (2) execute shell command condor_submit on submitter machine to launch the Condor job.

Author(s)

Arni Magnusson.

See Also

condor_submit, condor_q, condor_dir, and condor_download provide the main Condor interface.

condor_rm stops Condor jobs and condor_rmdir removes directories on the submitter machine.

condor-package gives an overview of the package.

Examples

## Not run: 

# General workflow
session <- ssh_connect("servername")

condor_submit()
condor_q()
condor_dir()
condor_download()  # after job has finished

# Alternatively, submit a specific run
condor_submit("c:/myruns/01_this_model")

## End(Not run)