How Farm Executables are built

H. Schellman

December 16, 2000

Introduction

This document describes the procedure for creating a farm executable from a d0 release. The farm executable is a tar file which contains the D0reco and RecoAnalyze executables and the associated RCP databases.

1. Making the Executable

1. Log onto one of the build machines (d0lxbld1-3)
2. setup the version you wish to run

        newrel -t <version> <version>

3. go into the <version> directory you just made
4. check out the latest version of the d0reco scripts from that branch

addpkg d0reco <branch> // for production
addpkg -h d0reco // for test

(normally pNN-br)
5. type d0setwa to set your working area
6. type

 buildfarmreco test LOCAL

The LOCAL uses the latest version of d0reco scripts you just checked out. If they are stable, you can omit the LOCAL and the scripts will come from the release <version>.
7. This will make 2 things:
• A local standalone reco in test- <version>
• A tarfile which can be moved to the farms
8. To test the release
1. go into the test- <version> directory
2. Do the following

unsetup D0RunII
setup TestData
runboth $raw_ttbar_10 10

This should process 10 events through reco and reco_analyze.
 
 
9. To get the executable to the farm

scp <version>.tar d0farm@d0bbin:~/d0reco/.

2. Sam interface

You will need sam to know about your code

1. check the SAM Application page to see if this version is in the DB yet.
2. If not, send an email to sam-admin requesting:

family/name/version

reconstruction d0reco <version>
analysis reco_analyze <version>

recon_root recon_root <version>

be put into the prd and int databases.

3. Appendix - what buildfarmreco does

You can find the buildfarmreco source at: d0reco/scripts/buildfarmreco

What it does:

1. Gets the executables from the release
2. Copies the rcp databases from the release
3. Gets the files in package rundata/d0reco
4. Gets some files like ptable and hmatrix which are accessed via environmentals
5. Gets the run scripts from d0reco/scripts
6. Puts them all into a subdirectory called <$1>- <version>
7. Tars it all up into <version>.tar.

4. What the run scripts do

runboth has 2 arguments, input data file and number of events. You can find runboth at:d0reco/scripts/runboth It can run D0 code standalone.

1. Hacks environmentals for RCP access
2. Hacks environmentals for hmatrix
3. Parses the input file name and chooses the correct rcp file to run
4. Runs D0reco and reco_analyze, returns error code which depends on which failed.

About this document ...

How Farm Executables are built

 This document was generated using the LaTeX2HTML translator Version 99.1 release (March 30, 1999)

Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds.
Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.

The command line arguments were:
latex2html -split 0 -show_section_numbers farm_creation

The translation was initiated by WWW Server Account on 2000-12-16

2000-12-16