Differences

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

--- atlas_maneframe [2016/03/31 14:53] – [SLURM and Resource Management] Add example ManeFrameRun.sh mcf
+++ atlas_maneframe [2018/10/28 10:28] (current) – sekula
@@ Line 31: / Line 31: @@
 **Acknowledgement Policy**
-During the period July - December 2015, we request that any external collaborator who uses ManeFrame please acknowledge your use of the system in any results that are shown //internally within ATLAS//. We suggest a line on the concluding slide of any presentation or in an internal ATLAS supporting document: **"We gratefully acknowledge SMU's Center for Scientific Computation for their support and for the use of the SMU ManeFrame Tier 3 ATLAS System."**
+During the period July 2015 - December 2016, we request that any external collaborator who uses ManeFrame please acknowledge your use of the system in any results that are shown //internally within ATLAS//. We suggest a line on the concluding slide of any presentation or in an internal ATLAS supporting document: **"We gratefully acknowledge SMU's Center for Scientific Computation for their support and for the use of the SMU ManeFrame Tier 3 ATLAS System."**
 We do not ask for acknowledgement in public papers, conference notes, or presentations; only in internal documents, where permitted.
@@ Line 211: / Line 211: @@
 INPUT=ThisIsYourInputFileDirectoryPATH
-OUTPUT=/scratch/users/YourUserName/_small/YourProjectName/Processed/
+OUTPUT=/scratch/users/<USERNAME>/_small/YourProjectName/Processed/
 EXECUTABLE="testRun submitDir input.txt"
 EMAIL="YourEmail@smu.edu"
@@ Line 360: / Line 360: @@
 } // main
 </code>
-===== Known Issues =====
-==== Clock Skew Warnings During Builds ====
+=== Combining Output Files ===
+When maneframe-run submits your jobs to ManeFrame it will do so in batches. Each of these will run on ManeFrame and each batch will return output to the OUTPUT directory you passed to maneframe-run. You will now want to combine these outputs to be able to look at the combined results in a single file. The following script will use ROOT's hadd utility to produce a single root file (location and name given by the user) as output:
+<code>
+#!/bin/bash
-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
+SOURCE=()
+TARGET=~This/Is/The/PATH/To/Your/Desired/OutputFile.root
+i=0
+# find all the .root files of interest
+while IFS= read -r file; do
+	SOURCE[i]=$file
+	((i++))
+done < <(find /scratch/users/$USER/ -print | grep -i '.*data.*/' | sort)
-===== Questions or Problems? =====
+hadd $TARGET ${SOURCE[*]}
+</code>
-Please email both of the following people with questions, comments, suggestions, or any other matters that arise:
+=== Using the EventLoop (EL) SlurmDriver ===
-  * Stephen Sekula (ssekula@smu.edu) - SMU ATLAS Computational Physics Liaison
+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.
-  * Amit Kumar (ahkumar@smu.edu) - SMU Scientific Computing Administrator
-Or just fill out the form below, which will result in us receiving an email.
+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:
-<form>
+<code>
-Action mail ssekula@smu.edu ahkumar@smu.edu
+  EL::SlurmDriver driver;
-Thanks "Your information has been sent to Stephen Sekula and Amit Kumar. You should expect a response shortly."
+  driver.SetJobName("MyAnalysis");
+  driver.SetAccount("default");
+  driver.SetPartition("serial");
+  driver.SetRunTime("00:60:00");
+  driver.SetMemory("2G");
+  driver.SetConstrain("");
+</code>
-textarea "Your Name" x2
+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:
-select "Category" "Comment|Request|Suggestion|Question|Urgent Matter"
-textarea "Your Comments" x10 !
-email "Your E-Mail Address"
+  * The Job Name (appears in squeue and labels your individual jobs)
+  * 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 =====
-Fieldset "Submit your message"
+==== Clock Skew Warnings During Builds ====
-submit "Submit"
-</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
+===== Questions or Problems? =====
-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