Difference: Erasmus (1 vs. 9)

Revision 92011-01-12 - AndrewPowell

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 54 to 54
 
  • PhysFit/DAfsRooFit. Fitter used for DAfs analysis.
  • RootTools/SimpleTools. Simple manipulation of ntuples with precompiled and fast root code.
  • RootTools/MoreSimpleTools. Optimization of cut-based selections with event-by-event weighting.
Added:
>
>
  • PIDCalib. Software for performing PID performance and calibration studies.
 

This section of the page is likely to be out of date, so for a full list of packages you can either check the Erasmus webpage, or the SVN repository. The SVN repository can be browsed online using WebSVN or Trac.

Revision 82010-07-06 - RobLambert

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 50 to 50
 
  • L0HadronConfirmation. Study of L0 Hadron Confirmation with 2009 collision data.
  • OfflineSelections (and packages therein). Offline selections used for the different analyses.
  • MvaSelections. This is planned to be added and it contains Fisher based selections for Bs2DsK and Bs2DsPi. More info in MultiVariateSelections .
Added:
>
>
  • PhysSel/Bs2DsMuX. Selections used for B0q2DplusMuNu analysis.
  • PhysFit/DAfsRooFit. Fitter used for DAfs analysis.
  • RootTools/SimpleTools. Simple manipulation of ntuples with precompiled and fast root code.
  • RootTools/MoreSimpleTools. Optimization of cut-based selections with event-by-event weighting.
  This section of the page is likely to be out of date, so for a full list of packages you can either check the Erasmus webpage, or the SVN repository. The SVN repository can be browsed online using WebSVN or Trac.

Revision 72010-06-14 - SajanEaso

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 49 to 49
 
  • BsKstKst. Software used for BsKst0Kst0 analysis
  • L0HadronConfirmation. Study of L0 Hadron Confirmation with 2009 collision data.
  • OfflineSelections (and packages therein). Offline selections used for the different analyses.
Added:
>
>
  • MvaSelections. This is planned to be added and it contains Fisher based selections for Bs2DsK and Bs2DsPi. More info in MultiVariateSelections .
  This section of the page is likely to be out of date, so for a full list of packages you can either check the Erasmus webpage, or the SVN repository. The SVN repository can be browsed online using WebSVN or Trac.

Revision 62010-05-06 - PhilipHunt

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 23 to 23
 To use another Gaudi project such as DaVinci, you must add it to the runtime environment. For example, if you are using Erasmus v1r3, and want to use packages from DaVinci v25r2p3, then you would do the following:
Changed:
<
<
SetupProject Erasmus v1r3 --runtime-project DaVinci v25r2p3
>
>
SetupProject Erasmus v1r3 --runtime-project DaVinci v25r2p3 --use DaVinciSys
 

It's also possible to add Erasmus to the runtime environment for another Gaudi package:

Line: 32 to 32
 SetupProject DaVinci v25r2p3 --runtime-project Erasmus v1r3 --use ErasmusSys
Changed:
<
<
The option --use ErasmusSys is needed in order to keep the environment variables of Erasmus.
>
>
If the two projects are compiled using a different version of Gaudi, then this will produce an error.
 
Changed:
<
<
If the two projects are compiled using a different version of Gaudi, then this would produce an error.
>
>
The option --use DaVinciSys or --use ErasmusSys is needed in the above commands in order to gain access to the environment variables of DaVinci/Erasmus. To add another Gaudi project to the runtime environment, replace --use DaVinciSys with the name of the main package for the project. This is can be found by looking at the main requirements file for the project. Generally, it will be the name of the project appended by Sys.
 
Changed:
<
<
Erasmus is distributed on the GRID.
>
>
As with the standard Gaudi packages, Erasmus is distributed on the GRID.
 

Packages

Line: 54 to 54
 

Create your package

Changed:
<
<
1) Have a look at SVNUsageGuidelines.

2) Create you own svn package.

3) Ask to include it in the next Erasmus release.

4) You are welcome to update this webpage accordingly :).

>
>
Instructions on creating a new Gaudi package can be found here. Once you have created and imported your Erasmus package to SVN, you should contact the maintainer of the Erasmus package (check the latest Erasmus requirements file for the current maintainer), and request that your package be included in the next release of Erasmus.
 

Submission through Ganga

Revision 52010-05-05 - PhilipHunt

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 8 to 8
 

Erasmus is the high-level physics analysis software repository for the LHCb experiment.

Changed:
<
<
Erasmus is just a collection of packages used by various workig groups. The structure is rather free. It does not depend on anything but Gaudi. That implies that if your package depends on ROOT, you have to specify it in the requirements file:
>
>
Erasmus is just a collection of packages used by various working groups. The structure is rather free. It does not depend on anything but Gaudi. This means that in most cases, you will only need to add one extra line to your requirements file:
 
Added:
>
>
use GaudiPolicy v*

If your package uses any external tools such as ROOT or the Boost libraries, then you must explicitly require that your package depend on it. For example, to require that your package depend on ROOT, you must add the following line in the requirements file:

 use ROOT v* LCG_Interfaces
Added:
>
>
 
Changed:
<
<
You may want to also use DaVinci (and/or Bender), for this you might have to do
>
>
To use another Gaudi project such as DaVinci, you must add it to the runtime environment. For example, if you are using Erasmus v1r3, and want to use packages from DaVinci v25r2p3, then you would do the following:
 
Changed:
<
<
SetupProject Erasmus v1r0 --runtime-project DaVinci v24r7
>
>
SetupProject Erasmus v1r3 --runtime-project DaVinci v25r2p3
 
Changed:
<
<
or
>
>
It's also possible to add Erasmus to the runtime environment for another Gaudi package:
 
Changed:
<
<
SetupProject DaVinci v24r7 --runtime-project Erasmus v24r7 --use ErasmusSys
>
>
SetupProject DaVinci v25r2p3 --runtime-project Erasmus v1r3 --use ErasmusSys
 
Changed:
<
<
The --use ErasmusSys is needed in order to keep the environment variables of Erasmus.
>
>
The option --use ErasmusSys is needed in order to keep the environment variables of Erasmus.
 
Changed:
<
<
Make sure the two version numbers are compatible, i.e. are based on the same Gaudi.
>
>
If the two projects are compiled using a different version of Gaudi, then this would produce an error.
 
Changed:
<
<
Erasmus is distributed in the GRID.
>
>
Erasmus is distributed on the GRID.
 

Packages

The current packages included in Erasmus are:

Changed:
<
<
>
>
  • P2VV. Package containing the source code for the P2VV analysis package.
  • P2VVPython. Package containing example scripts of how to use the P2VV package
  • P2VVProducion. Package containing scripts to prepare (MC) data for analysis with P2VV.
  • BsMuMuPy. Software used for BsMuMu analysis.
  • BsKstKst. Software used for BsKst0Kst0 analysis
  • L0HadronConfirmation. Study of L0 Hadron Confirmation with 2009 collision data.
  • OfflineSelections (and packages therein). Offline selections used for the different analyses.

This section of the page is likely to be out of date, so for a full list of packages you can either check the Erasmus webpage, or the SVN repository. The SVN repository can be browsed online using WebSVN or Trac.

 

Create your package

Changed:
<
<
1) Have a look at SVNUsageGuidelines.
>
>
1) Have a look at SVNUsageGuidelines.
  2) Create you own svn package.

3) Ask to include it in the next Erasmus release.

Changed:
<
<
4) You are wellcome to update this webpage accordingly :).
>
>
4) You are welcome to update this webpage accordingly :).
 
Changed:
<
<

Submision through Ganga

>
>

Submission through Ganga

  The following example works when submitted to Local() backend:
Changed:
<
<
er = GaudiPython(project="Bender",version="v14r0p2",script = '/afs/cern.ch/user/d/diegoms/cmtuser/Erasmus_v2r0/Phys/BsMuMuPy/python/pyV02009/V0.py',setupProjectOptions=' --runtime-project Erasmus v1r3 --use ErasmusSys') #### script is the one you want to execute
>
>
er = GaudiPython( project="Bender"
                  , version="v14r0p2"
                  , script = '/afs/cern.ch/user/d/diegoms/cmtuser/Erasmus_v2r0/Phys/BsMuMuPy/python/pyV02009/V0.py' ## script is the one you want to execute
                  , setupProjectOptions=' --runtime-project Erasmus v1r3 --use ErasmusSys')   
  j = Job(application=er)

j.submit()

Changed:
<
<
>
>
  -- DiegoMartinezSantos - 16-Mar-2010 \ No newline at end of file
Added:
>
>
-- PhilipHunt - 05-May-2010

Revision 42010-04-13 - DiegoMartinezSantos

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 19 to 19
  or
Changed:
<
<
SetupProject Erasmus v1r0; SetupProject DaVinci v24r7
>
>
SetupProject DaVinci v24r7 --runtime-project Erasmus v24r7 --use ErasmusSys
 
Changed:
<
<
(this last one is effectively SetupProject DaVinci v24r7, but keeping the environment variables defined inside Erasmus)
>
>
The --use ErasmusSys is needed in order to keep the environment variables of Erasmus.
  Make sure the two version numbers are compatible, i.e. are based on the same Gaudi.
Line: 49 to 49
  4) You are wellcome to update this webpage accordingly :).
Added:
>
>

Submision through Ganga

The following example works when submitted to Local() backend:

er = GaudiPython(project="Bender",version="v14r0p2",script = '/afs/cern.ch/user/d/diegoms/cmtuser/Erasmus_v2r0/Phys/BsMuMuPy/python/pyV02009/V0.py',setupProjectOptions=' --runtime-project Erasmus v1r3 --use ErasmusSys') #### script is the one you want to execute

j = Job(application=er)

j.submit()

  -- DiegoMartinezSantos - 16-Mar-2010

Revision 32010-03-21 - DaanVanEijkExCern

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 31 to 31
  The current packages included in Erasmus are:
Changed:
<
<
>
>
  • P2VV fit. Package containing the source code for the P2VV analysis package.
  • P2VVPython. Package containing example scripts of how to use the P2VV package
  • P2VVProducion. Package containing scripts to prepare (MC) data for analysis with P2VV.
 

Revision 22010-03-18 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Line: 34 to 34
 
Added:
>
>
 

Revision 12010-03-16 - DiegoMartinezSantos

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbComputing"

Erasmus (Analyses Repository)

Introduction

Erasmus is the high-level physics analysis software repository for the LHCb experiment. Erasmus is just a collection of packages used by various workig groups. The structure is rather free. It does not depend on anything but Gaudi. That implies that if your package depends on ROOT, you have to specify it in the requirements file:

use ROOT v* LCG_Interfaces

You may want to also use DaVinci (and/or Bender), for this you might have to do

SetupProject Erasmus v1r0 --runtime-project DaVinci v24r7

or

SetupProject Erasmus v1r0; SetupProject DaVinci v24r7

(this last one is effectively SetupProject DaVinci v24r7, but keeping the environment variables defined inside Erasmus)

Make sure the two version numbers are compatible, i.e. are based on the same Gaudi.

Erasmus is distributed in the GRID.

Packages

The current packages included in Erasmus are:

Create your package

1) Have a look at SVNUsageGuidelines.

2) Create you own svn package.

3) Ask to include it in the next Erasmus release.

4) You are wellcome to update this webpage accordingly :).

-- DiegoMartinezSantos - 16-Mar-2010

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