SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

Installing and Using ROOT

Release: 8.6.0 and greater

Installing the correct version of ROOT at a remote site

  • First see which version you need for a particular SRT release
  • For release 8.3.3 and beyond the version is 2.23-09
>grep ROOTVER $BFDIST/releases/<release>/SoftRelTools/arch_spec_ROOT.mk
  • Create tar file at SLAC for the architecture you're interested in
(at SLAC)

>cd $BFROOT/package/root/<version>/$BFARCH
>gtar --dereference --gzip -cf ~/root.tar.gz ./

  • Now you've created a file called root.tar.gz in your home directory at SLAC
  • Copy this file to your remote site and untar it in whichever directory you wish to have your local root installation.  I recommend

    $BFROOT/package/root/<version>/$BFARCH 

    in order to mimic the SLAC structure.
(at remote site)

>cd $BFROOT/package/root/<version>/$BFARCH
>gtar --gunzip -xf root.tar.gz


Customize SRT for your local ROOT installation

  • Go to your test release (let's call it myRel) and checkout the SiteConfig package
>cd ~/myRel
>addpkg -h SiteConfig
>cd SiteConfig/<mySite>/SoftRelTools
  • Here <mySite> is the name used for your local site in SiteConfig.  If you don't already have one set up for your site, you should probably do it soon (look in Computing/Tools web pages for information about how to do it).
  • Create a new file called arch_spec_ROOT.mk+ with the following line:

  • ROOTPATH := $(BFROOT)/package/root/

  • Check these changes into CVS, so in the future you won't need to check out SiteConfig.
>cvs add arch_spec_ROOT.mk+
>cvs commit -m "<some comment>" arch_spec_ROOT.mk+
  • Now you should be able to compile and link jobs against your local ROOT installation.
Minimal Setup Required for Running a KanGa Job

  • The minimal files you need to actually run a KanGa job locally are:  the conditions file and some data.
  • So, simply copy over the latest version of SLAC's conditions file to your local site (you'll have to create the directories kanga/CondDB under $BFROOT)
>cd $BFROOT
>mkdir kanga
>cd kanga
>mkdir CondDB
>cd CondDB
>cp /afs/slac.stanford.edu/g/babar/kanga/CondDB/BaBarConditions.root .
  • You want to update this file every time you bring over a new SRT release
  • Now you can run a job on a KanGa file
Running BetaApp on a KanGa file

  • Go to your test release and specify the name of a KanGa file you wish to run on.  You can find KanGa files for BaBar data at SLAC under the directory tree $BFROOT/kanga/EventStore.
>cd ~/myRel
>gmake BetaApp.all
>cd workdir
>setenv RooInputCollection <KanGa Filename>
  • Note that when setting RooInputCollection you leave off the -micro.root from the filename.
  • Hopefully everything works!

Page author: Carlo Dallapiccola