Check out GlaNtp

Introduction

We plan to check out the GlaNtp package.

ssh -Y ppepc137.physics.gla.ac.uk

Then open an xterm terminal.

xterm

We assume that you have moved to the new /afs home area. This will work with GlaNtp version 65 or later. To check if you have this home area do

pwd

You should see something like

/afs/phas.gla.ac.uk/user/a/abuzatu

Inside you should see a folder "private" (for things no one else should be able to see), a folder "public" (for things that anyone at Glasgow and on a CERN network should see) and a folder "public_ppe" (for things anyone at Glasgow and only them should see). We will use this latter folder for the GlaNtp installation.

cd public_ppe

In your scripts you will call often the "$HOME" variable, which looks like this

echo $HOME
/afs/phas.gla.ac.uk/user/a/abuzatu

Since before the convention was that GlaNtp is intalled in hour "$HOME", but not it is in "$HOME/public_ppe", you have to replace in your scripts the "$HOME" with "$HOME/public_ppe".

Also copy the .subversion folder from your old home area to your new home area.

Getting prepared

At Glasgow, the package is set up so that it should be checked out in the /home/${USER} folder. Also here a scripts folder will be checked out, so please make sure at this stage this folder does not already exist.

First setup the svn grid proxy

source /data/ppe01/sl44/i386/grid/glite-ui/latest/external/etc/profile.d/grid-env.sh
svn-grid-proxy-init

Let's see first what is the latest stable frozen tag of GlaNtp.

svn ls https://ppesvn.physics.gla.ac.uk/svn/atlas/GlaNtp

We will see an output like this

branches/
tags/
trunk/

First we need to check out a script that will be used to checkout the rest of the GlaNtp package. But we can not check out a single file from SVN, as you get an error.

svn co https://ppesvn.physics.gla.ac.uk/svn/atlas/GlaNtp/trunk/scripts/GlaNtpScript.sh
svn: URL 'https://ppesvn.physics.gla.ac.uk/svn/atlas/GlaNtp/trunk/scripts/GlaNtpScript.sh' refers to a file, not a directory

Therefore we checkout the entire directory called "scripts". First we remove this directory if it already exists to the same name to which we attach the desired tag (suggested date)

export BACKUP_SUFFIX=120624
mv scripts scripts_$BACKUP_SUFFIX
svn co https://ppesvn.physics.gla.ac.uk/svn/atlas/GlaNtp/trunk/scripts

The output is like this

A    scripts/TreatHist.sh
A    scripts/SimpleBuild.sh
A    scripts/GlaNtpScript.sh
A    scripts/testGenericUtility.sh
A    scripts/TreeSpecFromMakeClass.sh
A    scripts/validationfiles.txt
A    scripts/setup_glantp.sh
Checked out revision 1205.

Now we create a folder that will contain all the GlaNtp stuff called "GlaNtpPackage". If the folder already exists from an older installation, we will move the folder to a new one using the same backup suffix.

mv GlaNtpPackage GlaNtpPackage_$BACKUP_SUFFIX
mkdir GlaNtpPackage

Check out a tagged version

From this we learn to look into the folder tags

svn ls https://ppesvn.physics.gla.ac.uk/svn/atlas/GlaNtp/tags

We will see an output like this

GlaNtp--00-00-35/
GlaNtp-00-00-01/
GlaNtp-00-00-02/
GlaNtp-00-00-03/
GlaNtp-00-00-04/
...
GlaNtp-00-00-65/
GlaNtp-00-00-66/
GlaNtp-GlaNtp-00-00-16/
GlaNtp-GlaNtp-00-00-24/

From this we learn that the latest stable frozen version is "GlaNtp-00-00-66". It is this one that we will check out. In order to have this string later on so that we do not update the twiki page at every update, let's set an environment variable.

export GLANTP_TAG=00-00-66

Now we run the script that checks out the GlaNtp package by giving as an argument the tag that we want, namely "$GLANTP_TAG". The "GlaNtpScript.sh" will call the "setup_glantp.sh" on its own, so there is no need and you should not source the setup script of your own. If you do, the envirornment values will be available in your xterm after the check out and build and you do not want that.

./scripts/GlaNtpScript.sh -G $HOME/public_ppe/scripts -v $GLANTP_TAG 

This will check out the package, and then also run a few validations (do not worry if not all validations are successful). We get this output.

Done with core tests
testTMVAVar1 ok
testTMVAVar2 ok
testTMVAVar3 ok
Result of UtilBase                          validation:  NOT DONE: NEED
Result of Steer                             validation:  OK
Result of StringStringSet                   validation:  OK
Result of StringIntMap                      validation:  OK
Result of ItemCategoryMap                   validation:  OK
Result of FlatSystematic                    validation:  OK
Result of LJMetValues                       validation:  OK
Result of PhysicsProc                       validation:  OK
Result of FlatNonTriggerableFakeScale       validation:  OK
Result of FlatProcessInfo                   validation:  OK
Result of PaletteList                       validation:  OK
Result of CutInterface                      validation:  NOT DONE: NEED
Result of NNWeight                          validation:  NOT DONE: NEED
Result of FlatFileMetadata                  validation:  OK
Result of FlatFileMetadataContainer         validation:  OK
Result of Masks                             validation:  NOT DONE: NEED
Result of FFMetadata                        validation:  OK
Result of RUtil                             validation:  NOT DONE: NEED
Result of HistHolder                        validation:  NOT DONE: NEED
Result of GlaFlatFitCDF                     validation:  OK
Result of GlaFlatFitBigSysTableCDF          validation:  OK
Result of GlaFlatFitBigSysTableNoScalingCDF validation:  OK
Result of GlaFlatFitATLAS                   validation:  OK
Result of FlatTuple                         validation:  OK
Result of FlatReWeight                      validation:  OK
Result of FlatReWeight_global               validation:  OK
Result of FlatReWeightMVA                   validation:  OK
Result of FlatReWeightMVA_global            validation:  OK
Result of TreeSpecGenerator                 validation:  OK
Result of FlatAscii                         validation:  OK
Result of FlatAscii_global                  validation:  OK
Result of FlatTRntp                         validation:  OK

This output is also saved automatically by the script and can be read from this file

emacs -nw GlaNtpsummary_1335176868.txt

Check out the trunk (also called head)

If you want to check out the GlaNtp the trunk (SVN terminology) or head (CVS terminology), then you do not need the "-v" version, as the default version will do it. The "GlaNtpScript.sh" will call the "setup_glantp.sh" on its own, so there is no need and you should not source the setup script of your own. If you do, the envirornment values will be available in your xterm after the check out and build and you do not want that.

./scripts/GlaNtpScript.sh -G $HOME/public_ppe/scripts

This is equivalent with calling the script

./scripts/GlaNtpScript.sh -G $HOME/public_ppe/scripts -v h

Next step for GlaNtp developpers: AdrianBuzatuZHFrameworkGlasgowGlaNtpModify.

Next step for GlaNtp users, how to use the package along the HiggsAnalysis package in order to do the VH analyses: AdrianBuzatuZHFrameworkGlasgowGlaNtpRunVH.

Get to mother page: AdrianBuzatuZHFrameworkGlasgowGlaNtp.

-- AdrianBuzatu - 05-Mar-2012 -- AdrianBuzatu - 06-Mar-2012

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r11 - 2020-08-19 - TWikiAdminUser
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback