atlas_maneframe
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
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** | **Acknowledgement Policy** | ||
- | During the period July - December | + | During the period July 2015 - December |
We do not ask for acknowledgement in public papers, conference notes, or presentations; | We do not ask for acknowledgement in public papers, conference notes, or presentations; | ||
Line 211: | Line 211: | ||
INPUT=ThisIsYourInputFileDirectoryPATH | INPUT=ThisIsYourInputFileDirectoryPATH | ||
- | OUTPUT=/ | + | OUTPUT=/ |
EXECUTABLE=" | EXECUTABLE=" | ||
EMAIL=" | EMAIL=" | ||
Line 360: | Line 360: | ||
} // main | } // main | ||
</ | </ | ||
- | ===== 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: | ||
+ | < | ||
+ | #!/bin/bash | ||
- | There is a known effect that, while doing builds, you get a lot of "clock skew" warnings. | + | SOURCE=() |
+ | TARGET=~This/ | ||
+ | i=0 | ||
+ | # find all the .root files of interest | ||
+ | while IFS= read -r file; do | ||
+ | SOURCE[i]=$file | ||
+ | ((i++)) | ||
+ | done < <(find / | ||
- | ===== Questions or Problems? ===== | + | hadd $TARGET ${SOURCE[*]} |
+ | </ | ||
- | Please email both of the following people with questions, comments, suggestions, | + | === Using the EventLoop (EL) SlurmDriver === |
- | * Stephen Sekula | + | As of about November of 2016, AnalysisBase releases |
- | * Amit Kumar (ahkumar@smu.edu) - SMU Scientific Computing Administrator | + | |
- | Or just fill out the form below, which will result | + | The present EL:: |
- | <form> | + | <code> |
- | Action mail ssekula@smu.edu ahkumar@smu.edu | + | |
- | Thanks | + | driver.SetJobName(" |
+ | driver.SetAccount(" | ||
+ | | ||
+ | driver.SetRunTime(" | ||
+ | driver.SetMemory("2G" | ||
+ | driver.SetConstrain("" | ||
+ | </ | ||
- | textarea "Your Name" x2 | + | When you create an EL:: |
- | select " | + | |
- | textarea "Your Comments" | + | |
- | email "Your E-Mail Address" | + | * The Job Name (appears in squeue and labels your individual jobs) |
+ | * Account | ||
+ | * Partition - the name of the partition where jobs will run, e.g. serial or development, | ||
+ | * 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 " | + | ==== Clock Skew Warnings During Builds ==== |
- | submit | + | |
- | </ | + | There is a known effect that, while doing builds, you get a lot of "clock skew" |
+ | |||
+ | |||
+ | ===== 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 |
atlas_maneframe.txt · Last modified: 2018/10/28 10:28 by sekula