Difference: UCSDUserDocPCF (18 vs. 19)

Revision 192017/01/25 - Main.MartinKandes

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 10 to 10
  The UCSD Physics Computing Facility (PCF) provides access to multiple high-throughput computing resources that are made available to students, faculty, and staff in the Department of Physics as well as those in the broader scientific community at UCSD. This document describes how to get an account on PCF and begin submitting jobs to its computing resources.
Added:
>
>
Please note that this documentation is currently under construction and may not be complete in some parts.
 This document follows the general Open Science Grid (OSG) documentation conventions:

  1. A User Command Line is illustrated by a green box that displays a prompt:
     [user@client ~]$ 
Line: 67 to 69
  request_disk = 8000000 request_memory = 1024 +ProjectName = "PCFOSGUCSD"
Changed:
<
<
+local = TRUE +site_local = FALSE
>
>
+local = FALSE +site_local = TRUE
  +sdsc = FALSE
Changed:
<
<
+uc = FALSE
>
>
+uc = TRUE
  queue 10

The first line here

 # A sample HTCondor submit description file 
is simply a comment line in the submit description file. Any comments in a submit description file should be placed on their own line.
Line: 100 to 102
 HTCondor allows users (and system administrators) to append custom attributes to any job at the time of submission. On PCF, a set of custom attributes are used to mark jobs for special routing and accounting purposes. For example,
 +ProjectName = "PCFOSGUCSD" 
is a job attribute used by the Open Science Grid (OSG) for tracking resource usage by group. All jobs submitted to PCF, including yours, should contain this +ProjectName = "PCFOSGUCSD" attribute, unless directed otherwise.

The next set of custom job attributes in the sample submit description file

Changed:
<
<
 +local = TRUE
 +site_local = FALSE

>
>
 +local = FALSE
 +site_local = TRUE

  +sdsc = FALSE
Changed:
<
<
+uc = FALSE
>
>
+uc = TRUE
 are a set of boolean job routing flags that allow you to explicitly target where your jobs may run. Each one of these boolean flags is associated with one of the different computing resources accessible from PCF. When you set the value of one of these resource flags to TRUE, you permit your jobs to run on the system associated with that flag. In contrast, when you set the value of the resource flag to FALSE, you prevent your jobs from running on that system. The relationship between each job routing flag and computing resource is provided in the following table.

Job Routing Flag Default Value Computing Resource Accessibility
Line: 112 to 114
 
+sdsc FALSE Comet Supercomputer Open only to PCF users with an XSEDE allocation on Comet
+uc FALSE Open Science Grid Open to all PCF users
Changed:
<
<
We see here that the sample submit description file is only targeted to run the job locally on PCF itself.
>
>
We see here that the sample submit description file has targeted the job to run either at the CMS Tier 2 Cluster or out on the Open Science Grid.
  Finally, the sample submit description file ends with the queue command, which as shown here simply places an integer number of copies (10) of the job in the HTCondor queue upon submission. If no integer value is given with the queue command, the default value is 1. Every submit description file must contain at least one queue command.
Deleted:
<
<
requirements
 
Added:
>
>
requirements
 It is important to note here that the name of this shell script was not chosen randomly. While other batch systems like SLURM and PBS use standard shell scripts annotated with directives for both communicating the requirements of a batch job to their schedulers and how the job's executable should be run, HTCondor does not work this way. In general, an HTCondor submit description file separates the directives (or commands) to the scheduler from how the executable should be run (e.g., how it would look if run interactively from the command line). As such, it is often the case that HTCondor users will need to wrap their actual (payload) executable within a shell script as shown here in this sample submit description file. Here, that executable is represented by job.x in the transfer_input_files command.

Job Status

Line: 245 to 247
 

Job Removal

Changed:
<
<
Occasionally, you you may need remove a job that has already been submitted to the PCF queue. For example, maybe the job has been misconfigured in some way or goes held for some reason. To remove a job in the queue, you can use the condor_rm command. To remove a job from the queue, provide the both the ClusterId and ProcId of the job you would like to remove.
>
>
Occasionally, you may need remove a job that has already been submitted to the PCF queue. For example, maybe the job has been misconfigured in some way or goes held for some reason. To remove a job in the queue, you can use the condor_rm command. To remove a job from the queue, provide the both the ClusterId and ProcId of the job you would like to remove.
 
 [youradusername@pcf-osg ~]$ condor_q youradusername

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