Difference between revisions of "CSC Ntuple production"

From Atlas Wiki
Jump to navigation Jump to search
Line 33: Line 33:
  
 
===GridModules===
 
===GridModules===
GridModules are packages which will be installed in <tt>/grid/atlas/users/<username>/gpm</tt>. These packages reside on the SE (<tt>tbn18.nikhef.nl</tt>) and can be used for jobs. This prevents submitting (too) large jobs, note that there is a limit on the input sandbox of ~ 20-50 MB.
+
GridModules are packages which will be installed in <tt>/grid/atlas/users/${USER}/gpm</tt>. These packages reside on the SE (<tt>tbn18.nikhef.nl</tt>) and can be used for jobs. This prevents submitting (too) large jobs, note that there is a limit on the input sandbox of ~ 20-50 MB.
  
 
GridModules are available from CVS:
 
GridModules are available from CVS:

Revision as of 10:35, 6 July 2007

Setting up Grid tools

This wiki describes how to set things up for ntuple production on the Grid. You need a Grid certificate [1] and some patience ;-)

    Two tips:
  • use voms-proxy-init instead of grid-proxy-init
  • use bash for shell scripts

GridTools

Wouter wrote some very nice tools to submit/retrieve jobs from the Grid. They can be obtained from the Nikhef CVS:

cvs -d /project/atlas/cvs co GridTools

The GridTools package contains a few shell scripts:

dmgr
to manage datasets on the Grid
gpm
to set up packages on the SE for Grid jobs (to prevent jobs sizes > input sandbox)
gridmgr
main tool to manage Grid jobs (submit/retrieve/cancel/monitor)
gridinfo
a funny tool (lcg-infosites seems more useful)
jobmgr
to define Grid jobs (with the possibility to run them locally for testing)

dmgr and gpm possibly need to be adjusted:

LFC_HOST = lfc03.nikhef.nl
GRID_SE  = tbn18.nikhef.nl

GridModules

GridModules are packages which will be installed in /grid/atlas/users/${USER}/gpm. These packages reside on the SE (tbn18.nikhef.nl) and can be used for jobs. This prevents submitting (too) large jobs, note that there is a limit on the input sandbox of ~ 20-50 MB.

GridModules are available from CVS:

cvs -d /project/atlas/cvs co GridModules

A few examples of modules are present (interesting study material).

make_package
with this tool, a directory is tarred and stored on the SE. Note that the file ~/.gpmrc keeps track of which modules have been installed. When running jobs locally, it will use the locally available package instead of the one installed on the SE.

Be careful not to include the slash '/' when making the package!

DataManager
AtlasRelease
TopView module

http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/PAT/EventView/

wget http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/PAT/EventView/EventView-12.0.6.8.tar.gz

strip unnescessary files InstallArea, PhysicsAnalysis Little complication: if incorrect version is in package. Compile libraries locally and copy them to InstallArea. tar cvzf EventView-12.0.6.8_nikhef.tar.gz EVTags-12.0.6.8/ check run scripts in module (adjust version numbers) make_package TopViewAODtoNtuple-00-12-13-03

Ganja