Differences

This shows you the differences between two versions of the page.

--- atlas_maneframe [2016/09/26 18:06] – [Acknowledgement by External Users] sekula
+++ atlas_maneframe [2018/10/28 10:28] (current) – sekula
@@ Line 378: / Line 378: @@
 hadd $TARGET ${SOURCE[*]}
 </code>
-===== Known Issues =====
-==== Clock Skew Warnings During Builds ====
+=== Using the EventLoop (EL) SlurmDriver ===
-There is a known effect that, while doing builds, you get a lot of "clock skew" warnings. This is under investigation. It appears to be harmless
+As of about November of 2016, AnalysisBase releases (after 2.4.21) contained a new driver in the EventLoop package, SlurmDriver. Like the other drivers for running code locally or on other batch management systems, the EL::SlurmDriver allows you to execute your analysis binary and have it submit and manage jobs on the SLURM queue management system. This frees you from having to write sbatch scripts or your own independent scripts for submitting Framework-bases xAOD analysis jobs.
+The present EL::SlurmDriver code submits one job per ROOT file processed by your code. To setup the driver in, for instance, your standalone executable main() function declaration:
-===== Questions or Problems? =====
+<code>
+  EL::SlurmDriver driver;
+  driver.SetJobName("MyAnalysis");
+  driver.SetAccount("default");
+  driver.SetPartition("serial");
+  driver.SetRunTime("00:60:00");
+  driver.SetMemory("2G");
+  driver.SetConstrain("");
+</code>
-Please email both of the following people with questions, comments, suggestions, or any other matters that arise:
+When you create an EL::SlurmDriver, you MUST configure all of its options. You can leave some of them blank, but all of them have to be defaulted to something. The above are examples of setting the following options:
-  * Stephen Sekula (ssekula@smu.edu) - SMU ATLAS Computational Physics Liaison
+  * The Job Name (appears in squeue and labels your individual jobs)
-  * Amit Kumar (ahkumar@smu.edu) - SMU Scientific Computing Administrator
+  * Account - this is always "default", unless a special account has been setup to allow you to use a protected partition on SLURM
+  * Partition - the name of the partition where jobs will run, e.g. serial or development, etc.
+  * RunTime - the maximum running time of the job. Here, the example code uses 30 minutes in HH:MM:SS format
+  * Memory - the memory limit for your job
+  * Constrain - this will constrain your job to specific resources, if there are multiple resource options in the partition.
+===== Known Issues =====
-Or just fill out the form below, which will result in us receiving an email.
+==== Clock Skew Warnings During Builds ====
-<form>
+There is a known effect that, while doing builds, you get a lot of "clock skew" warnings. This is under investigation. It appears to be harmless
-Action mail ssekula@smu.edu ahkumar@smu.edu
-Thanks "Your information has been sent to Stephen Sekula and Amit Kumar. You should expect a response shortly."
-textarea "Your Name" x2
-select "Category" "Comment|Request|Suggestion|Question|Urgent Matter"
-textarea "Your Comments" x10 !
-email "Your E-Mail Address"
+===== Questions or Problems? =====
-Fieldset "Submit your message"
-submit "Submit"
-</form>
-We welcome suggestions and feedback on how to make the ManeFrame/ATLAS experience better.  We are grateful for your interest in using our Tier 3 resources to advance ATLAS research and development activities.
+Please contact the SMU scientific computing team with questions or comments. Learn more: http://faculty.smu.edu/csc/documentation/usage.html