| 1 |
=====================================================================
|
| 2 |
README file in the ProofAnalysisFramework package
|
| 3 |
|
| 4 |
Developers: Ana Yaiza Rodriguez Marrero, Isidro Gonzalez Caballero
|
| 5 |
|
| 6 |
Additional documentation: http://www.hep.uniovi.es/mediawiki-1.12.0/index.php/ProofAnalysisFramework#PROOF_Analysis_Framework
|
| 7 |
=====================================================================
|
| 8 |
|
| 9 |
OUTLINE:
|
| 10 |
* SETTING THE ENVIRONMENT
|
| 11 |
* HOW TO RUN A BASIC PROOF ANALYSIS
|
| 12 |
- THE ANALYSIS FILE
|
| 13 |
- USING PROOF-LITE
|
| 14 |
- USING PROOF CLUSTER
|
| 15 |
* CLEANNING THE ENVORONMENT
|
| 16 |
* FOR THE INPATIENT USER
|
| 17 |
|
| 18 |
=====================================================================
|
| 19 |
|
| 20 |
SETTING THE ENVIRONMENT
|
| 21 |
|
| 22 |
The first time you get this PROOF framework we need to set a few
|
| 23 |
things. Please run setup.sh to build packages and set the appropriate
|
| 24 |
links
|
| 25 |
|
| 26 |
[host] > ./setup.sh
|
| 27 |
|
| 28 |
|
| 29 |
-----------------------------------------------------------
|
| 30 |
|
| 31 |
HOW TO RUN A BASIC PROOF ANALYSIS
|
| 32 |
|
| 33 |
- THE ANALYSIS FILE
|
| 34 |
|
| 35 |
Two default analysis classes have been created related to the two tree
|
| 36 |
types we handle: MyAnalysisMiniTrees and MyAnalysisTESCO. More
|
| 37 |
documentation to be added soon...
|
| 38 |
|
| 39 |
- USING PROOF LITE
|
| 40 |
|
| 41 |
ProofLite mode allows you to profit from your multicore architecture
|
| 42 |
transparently. No special installation is needed and PROOF will use
|
| 43 |
all the cores available.
|
| 44 |
|
| 45 |
Edit the file Run.prooflite.C to set various parameters: input data
|
| 46 |
sample, output file name, etc... Then just run this macro:
|
| 47 |
|
| 48 |
[host] > root -l
|
| 49 |
[host] > .x Run.prooflite.C
|
| 50 |
|
| 51 |
- USING PROOF CLUSTER
|
| 52 |
|
| 53 |
ProofCluster mode allows you to run your analysis in many more nodes
|
| 54 |
by using the batch cluster available at your site. Users need to
|
| 55 |
perform an extra step, but most of the procedure has been
|
| 56 |
automatized.
|
| 57 |
|
| 58 |
Edit the Run.startproof.C to set various parameters: input data
|
| 59 |
sample, output file name, etc... You need to add the path to the PROOF
|
| 60 |
Cluster installation to your PATH variable.
|
| 61 |
|
| 62 |
[host] > export PATH=$PATH:/gpfs/csic_projects/cms/PROOF #bash
|
| 63 |
|
| 64 |
or
|
| 65 |
|
| 66 |
[host] > setenv PATH "${PATH}:/gpfs/csic_projects/cms/PROOF" #tcsh
|
| 67 |
|
| 68 |
Then start the proof session for a given number of workers.
|
| 69 |
|
| 70 |
[host] > startproof 10 #Start PROOF for 10 workers
|
| 71 |
|
| 72 |
Finally, just run the macro:
|
| 73 |
|
| 74 |
[host] > root -l
|
| 75 |
[host] > .x Run.startproof.C
|
| 76 |
|
| 77 |
|
| 78 |
-----------------------------------------------------------
|
| 79 |
|
| 80 |
CLEANING THE ENVIRONMENT
|
| 81 |
|
| 82 |
If you change some of the core packages or get some inestability on the system, you may need to reset the proof environment. In such a case, please run resetproof.sh.
|
| 83 |
|
| 84 |
[host] > ./resetproof.sh
|
| 85 |
|
| 86 |
|
| 87 |
-----------------------------------------------------------
|
| 88 |
|
| 89 |
FOR THE INPATIENT USER
|
| 90 |
|
| 91 |
- PROOF LITE
|
| 92 |
[host] > ./setup.sh
|
| 93 |
[host] > root -l
|
| 94 |
[host] > .x Run.prooflite.C
|
| 95 |
|
| 96 |
- PROOF CLUSTER
|
| 97 |
[host] > ./setup.sh
|
| 98 |
[host] > export PATH=$PATH:/gpfs/csic_projects/cms/PROOF #bash
|
| 99 |
[host] > startproof 10
|
| 100 |
[host] > root -l
|
| 101 |
[host] > .x Run.startproof.C #Don't forget to change the user name
|
