1 / 25

CMT Tutorial How to use CMT in Atlas Christian Arnault arnault@lal2p3.fr

CMT Tutorial How to use CMT in Atlas Christian Arnault arnault@lal.in2p3.fr http://www.lal.in2p3.fr/SI/CMT/CMT.htm. Introduction. Presentation of the tutorial It is composed of three short lectures (~ 20’ each) The Atlas work model and conventions Working on Atlas packages

ouida
Download Presentation

CMT Tutorial How to use CMT in Atlas Christian Arnault arnault@lal2p3.fr

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CMT Tutorial How to use CMT in Atlas Christian Arnault arnault@lal.in2p3.fr http://www.lal.in2p3.fr/SI/CMT/CMT.htm 1

  2. Introduction • Presentation of the tutorial • It is composed of three short lectures (~ 20’ each) • The Atlas work model and conventions • Working on Atlas packages • Advanced features • It includes materials for documented examples (rather than exercises) with screen dumps • Goal, scope • It is really aimed at Atlas context rather than being a general purpose CMT tutorial • The expected audience ranges from the normal software operator up to the more expert developer • Announce • CMT workshop at LAL Feb-28/March-01 2002 2

  3. Plan • Lecture #1 :The Atlas work model and conventions • Introduction • Work model, conventions • How to setup CMT • The CMT user interface • The CMT architecture • Lecture #2 : Working on Atlas packages • Working with a package • Creating a new package • Running an application • Examples in Atlas • Lecture #3 : Advanced features • Policy and patterns in Atlas • Package types and areas • Details on configuration parameters 3

  4. Lecture #1The Atlas work model and conventions 4

  5. Work model, conventions (1) • The roles • So far, we only consider “developers” and “package coordinators” • Developers work (edit, commit, tag, test, register) on individual packages • Package coordinators accumulate package tags and validate • The scenarios • Working on a package in a private development area • Connecting to the official release • We are talking about the current practices in Atlas rather than the standard or the final definitions (since this is not yet fully defined / understood / adopted). A working group is currently being setup to define : • the roles (developer, coordinators, librarian, etc…) • the scenarios (developing, tagging, testing, integrating, installing, deploying, …) 5

  6. Work model, conventions (2) • The software organization • The software base is a hierarchy of packages: LArCalorimeter LArCalorimeter/LArBookkeeping LArCalorimeter/LArCellRec LArCalorimeter/LArClusterRec LArCalorimeter/LArCnv LArCalorimeter/LArCnv/LArAthenaRoot LArCalorimeter/LArCnv/LArHitZebraCnv LArCalorimeter/LArConditions LArCalorimeter/LArDetDescr LArCalorimeter/LArDetDescrObjyDDL LArCalorimeter/LArDigitization LArCalorimeter/LArEvent LArCalorimeter/LArEventObjyDDL LArCalorimeter/LArExample LArCalorimeter/LArExample/LArBookkeepingExample LArCalorimeter/LArExample/LArConditionsExample LArCalorimeter/LArExample/SimpleCellBuilder LArCalorimeter/LArExample/TestLArDigit LArCalorimeter/LArExample/TestLArHardwareID containers 6

  7. Work model, conventions (3) • The software organisation • Packages may have particular semantics • Normal packages provide software or documents • Container packages manage other packages • Policy packages hold Atlas specific conventions, policies, patterns • Interfacesconvert conventions and policies of external packages • We must differentiate • The physical hierarchy (the directory structure) • The logical hierarchy (relationships between packages) • Those two hierarchies are totally independent with each other • A release is the unique and exhaustive set of all [package-version] duets validated as consistently built and cooperating. (see next screen) • It is materialized by one container package AtlasRelease 7

  8. use InDetSpacePoint InDetSpacePoint-00-01-10 InnerDetector/InDetRec use SiClusterization SiClusterization-00-01-03 InnerDetector/InDetRec use SiTrackerCluster SiTrackerCluster-02-01-00 InnerDetector/InDetRec use SiTrackerSpacePoint SiTrackerSpacePoint-01-00-08 InnerDetector/InDetRec use TRT_Rec TRT_Rec-00-00-28 InnerDetector/TRT use LArBookkeeping LArBookkeeping-00-00-05 LArCalorimeter use LArCellRec LArCellRec-01-01-06 LArCalorimeter use LArClusterRec LArClusterRec-01-01-03 LArCalorimeter use LArAthenaRoot LArAthenaRoot-00-01-05 LArCalorimeter/LArCnv use LArHitZebraCnv LArHitZebraCnv-00-00-07 LArCalorimeter/LArCnv use LArConditions LArConditions-00-00-04 LArCalorimeter use LArDetDescr LArDetDescr-00-02-01 LArCalorimeter use LArDetDescrObjyDDL LArDetDescrObjyDDL-00-00-01 LArCalorimeter use LArDigitization LArDigitization-00-00-15 LArCalorimeter use LArEvent LArEvent-00-00-15 LArCalorimeter use LArEventObjyDDL LArEventObjyDDL-00-00-01 LArCalorimeter use LArBookkeepingExample LArBookkeepingExample-00-00-06 LArCalorimeter/LArExample use LArConditionsExample LArConditionsExample-00-00-04 LArCalorimeter/LArExample use SimpleCellBuilder SimpleCellBuilder-01-00-04 LArCalorimeter/LArExample use TestLArDigit TestLArDigit-00-00-12 LArCalorimeter/LArExample use TestLArHardwareID TestLArHardwareID-00-00-06 LArCalorimeter/LArExample use TestLArHECTBCnv TestLArHECTBCnv-00-00-09 LArCalorimeter/LArExample use TestLArTBCnv TestLArTBCnv-00-00-08 LArCalorimeter/LArExample use LArGraphics LArGraphics-00-00-12 LArCalorimeter use LArROD LArROD-01-00-03 LArCalorimeter use LArSim LArSim-00-01-06 LArCalorimeter use LArHECTBAna LArHECTBAna-00-00-03 LArCalorimeter/LArTestBeam use LArHECTBCnv LArHECTBCnv-00-00-12 LArCalorimeter/LArTestBeam use LArHECTBPed LArHECTBPed-00-00-03 LArCalorimeter/LArTestBeam use LArTBCnv LArTBCnv-00-00-10 LArCalorimeter/LArTestBeam use MagneticFieldAge MagneticFieldAge-01-00-07 MagneticField use MagneticFieldAgeHeader MagneticFieldAgeHeader-01-00-07 MagneticField use MagneticFieldAthena MagneticFieldAthena-01-00-07 MagneticField use MagneticFieldAthenaHeader MagneticFieldAthenaHeader-01-00-07 MagneticField use MagneticFieldCore MagneticFieldCore-01-00-07 MagneticField use MagneticFieldCoreHeader MagneticFieldCoreHeader-01-00-07 MagneticField use MagneticFieldStand MagneticFieldStand-01-00-07 MagneticField 8

  9. Work model, conventions (4) • The software organisation • A release can be frozen or under development • The latter will likely become the integration release • Releases are maintained in ATLAS_DIST_AREA/ATLAS_RELEASE • Where • ATLAS_DIST_AREA takes one specific value per site where the Atlas software is installed (CERN, LBL, LBNL, laptops, …) • ATLAS_RELEASE is a 3-number tag describing the release level %ls /afs/cern.ch/atlas/software/dist/ 1.0.1 1.1.6 1.2.2 1.3.2 1.3.5 2.0.1 2.1.1 2.3.1 1.1.4 1.2.0 1.3.0 1.3.3 1.3.7 2.0.2 2.2.0 2.4.0 1.1.5 1.2.1 1.3.1 1.3.4 2.0.0 2.1.0 2.3.0 2.4.1 9

  10. Work model, conventions (5) • The internal work model of CMT • Each package is identified by a triplet [package - version - location] • Packages are located and searched for in package areas • The search list for all possible areas is specified in one path-like environment variable named CMTPATH Gaudi area software/dist/2.4.0 %cmt show path # Add path /afs/cern.ch/atlas/offline/external/Gaudi/0.8.3 from ${CMTPATH} # Add path /afs/cern.ch/atlas/software/dist/2.4.0 from ${CMTPATH} # Add path /afs/cern.ch/sw/contrib from default path # /afs/cern.ch/atlas/offline/external/Gaudi/0.8.3:/afs/cern.ch/atlas/software/dist/2.4.0:/afs/cern.ch/sw/contrib software/dist/2.4.0 %echo $CMTPATH /afs/cern.ch/atlas/offline/external/Gaudi/0.8.3:/afs/cern.ch/atlas/software/dist/2.4.0 Release area 10

  11. Work model, conventions (6) • The internal work model of CMT • Version specification accepts a semantics based on a 3-level identifier scheme: <letters><major-id>[<letters><minor-id>[<letters><patch-id>]] • Major-id describes major evolutions (that imply code change to client packages) • Minor-id describes minor evolutions (backward compatible change to the interface, only imply re-compilation) • Patch-id describes simple patches (i.e. no change to any interface) v1 v10 v10r1 v13r10 v1r0 v1r24p0 v1r6p2 v2 v2001 v2r0p2 LArDetDescrObjyDDL-00-00-01 LArDigitization-00-00-15 LArEvent-00-00-15 LArEventObjyDDL-00-00-01 LArBookkeepingExample-00-00-06 LArConditionsExample-00-00-04 SimpleCellBuilder-01-00-04 TestLArDigit-00-00-12 11

  12. Work model, conventions (7) • The internal work model of CMT • The resulting directory structure of a package reflects this organization: Header files LArCalorimeter/LArCellRec/ LArCalorimeter/LArCellRec/LArCellRec-01-01-06 LArCalorimeter/LArCellRec/LArCellRec-01-01-06/LArCellRec LArCalorimeter/LArCellRec/LArCellRec-01-01-06/ChangeLog LArCalorimeter/LArCellRec/LArCellRec-01-01-06/PACKAGE LArCalorimeter/LArCellRec/LArCellRec-01-01-06/configure LArCalorimeter/LArCellRec/LArCellRec-01-01-06/src LArCalorimeter/LArCellRec/LArCellRec-01-01-06/cmt LArCalorimeter/LArCellRec/LArCellRec-01-01-06/cmt/Makefile LArCalorimeter/LArCellRec/LArCellRec-01-01-06/cmt/requirements LArCalorimeter/LArCellRec/LArCellRec-01-01-06/share LArCalorimeter/LArCellRec/LArCellRec-01-01-06/Linux-gcc-dbg LArCalorimeter/LArCellRec/LArCellRec-01-01-06/Linux-gcc-opt Version Sources Package CMT Branches Location Binary files 12

  13. Work model, conventions (8) • The internal work model of CMT • Each package holds its own entire configuration specification into one single text file named requirements • This file must reside in the cmt sub-directory • By default everything belonging to the package (source files, or generated files) will stay within the context of the package • Customizations are possible (eg to install generated files elsewhere) • There is one single relationship established between packages, qualified by the use concept. (see next screens) • CMT relies on this structure to address used packages, resolving complete address from • The name • The required version expression • The possible access paths from CMTPATH 13

  14. LArCellRec/LArCellRec-01-01-06/cmt %cat requirements package LArCellRec author RD Schaffer <R.D.Schaffer@cern.ch> author Srini Rajagopalan <srini@sun2.bnl.gov> use AtlasPolicy AtlasPolicy-* use CxxFeatures CxxFeatures-00-* Utilities use GaudiInterface GaudiInterface-01-* External use StoreGate StoreGate-02-* Control use Identifier Identifier-00-* DetectorDescription use AtlasDetDescr AtlasDetDescr-00-* DetectorDescription use EventAthena EventAthena-00-* Event use EventStructure EventStructure-00-* Event use ZebraTDREvent ZebraTDREvent-00-* Event use EventRawData EventRawData-00-* Event use LArDetDescr LArDetDescr-00-* LArCalorimeter use LArEvent LArEvent-00-* LArCalorimeter use LArROD LArROD-01-* LArCalorimeter use LArSim LArSim-00-* LArCalorimeter use CaloRec CaloRec-01-* Calorimeter 14

  15. (Excerpt from the graphical representation of the use hierarchy by CMT) 15

  16. How to setup CMT (1) • The bootstrap operation: how to connect for the very first time with CMT • Call the setup script of CMT itself. • This selects one version of CMT • This only needs to be done once until the next change of CMT version For switching to another version of CMT, see later … user/c/carnault %source/afs/cern.ch/sw/contrib/CMT/v1r10p20011126/mgr/setup.sh user/c/carnault %cmt version V1r10p20011126 user/c/carnault %echo $CMTROOT /afs/cern.ch/sw/contrib/CMT/v1r10p20011126 16

  17. How to setup CMT (2) • Setting up an Atlas environment • Install a HOME requirements file eg. in ${HOME}/cmtdir • Install in this file: • The site identification (CMTSITE) • The location to the distribution area (ATLAS_DIST_AREA) • The selected release level (ATLAS_RELEASE) • The connection to the standard AtlasSettings definitions • … user/c/carnault %mkdir cmtdir user/c/carnault %cd cmtdir user/c/carnault/cmtdir %vi requirements set CMTSITE CERN macro ATLAS_DIST_AREA "/afs/cern.ch/atlas/software/dist“ #macro ATLAS_RELEASE "2.3.1" macro ATLAS_RELEASE "2.4.0" use AtlasSettings v* $(ATLAS_DIST_AREA) 1 2-a 2-b 2-c 2-d 17

  18. How to setup CMT (3) • Setting up Atlas environment in various sites • Change or select CMTSITE • Provide the possible values for ATLAS_DIST_AREA (some sites are already defined) • A proper SITEROOT env. variable is expected for other sites. This will provide logical root entry point towards various software ${SITEROOT}/cern => Cernlib ${SITEROOT}/external => Atlas external software ${SITEROOT}/ROOT => ROOT ${SITEROOT}/sw => CERN Anaphe etc… ${SITEROOT}/software => Atlas software user/c/carnault/cmtdir %vi requirements set CMTSITE CERN #set CMTSITE BNL #set CMTSITE LBNL #set CMTSITE EXTSITE macro ATLAS_DIST_AREA "/afs/cern.ch/atlas/software/dist" \ CERN "/afs/cern.ch/atlas/software/dist" \ BNL "/afs/rhic/usatlas/software/dist" \ LBNL "/auto/atlas/local/software/dist" \ EXTSITE "${SITEROOT}/software/dist“ 18

  19. How to setup CMT (4) • Setting up an Atlas environment … 3. Configure for CMT by cmt config (this creates the setup and cleanup scripts) 4. Apply the setup script (only this last step has to be redone at each session startup). c/carnault/cmtdir %cmt config ------------------------------------------ Configuring environment for standalone package. CMT version v1r10p20011126. System is Linux-gcc-dbg ------------------------------------------ Creating setup scripts. Creating cleanup scripts. user/c/carnault/cmtdir %source setup.sh 3 4 19

  20. How to setup CMT (5) • Setting up an Atlas environment … 5. Declare a private development area into the HOME requirements file 6. Create if needed the development area 7. Apply this definition to upgrade CMTPATH c/carnault/cmtdir %vi requirements ... path_remove CMTPATH ${HOME} path_prepend CMTPATH ${HOME}/devarea user/c/carnault/cmtdir %mkdir –p ../devarea user/c/carnault/cmtdir %source setup.sh user/c/carnault/cmtdir %cd ../devarea 5 6 7 20

  21. How to setup CMT (6) • Understanding what is the current settings • cmt version(the version of CMT) • cmt show path(the CMTPATH entries) • cmt show tags(the active configuration tags) • cmt show packages | grep dist(all reachable package-versions) c/carnault/cmtdir %cmt version v1r10p20011126 c/carnault/cmtdir %cmt show path # Add path /afs/cern.ch/atlas/offline/external/Gaudi/0.8.3 from initialization # Add path /afs/cern.ch/atlas/software/dist/2.4.0 from initialization # Add path /afs/cern.ch/sw/contrib from default path # /afs/cern.ch/atlas/offline/external/Gaudi/0.8.3:/afs/cern.ch/atlas/software/dist/2.4.0:/afs/cern.ch/sw/contrib c/carnault/cmtdir %cmt show tags Linux (from uname) package AtlasSettings implies [gcc debug] i386_linux22 (from CMTCONFIG) package CMT implies [Linux] CERN (from CMTSITE) debug (from package CMT) package AtlasSettings excludes [opt optimized] Default (from Default) gcc (from package AtlasSettings) excludes [egcs] Linux-gcc-dbg (from package AtlasSettings) package AtlasSettings implies [debug] Linux-gcc (from CMTCONFIG in package AtlasSettings) 1 2 3 21

  22. The CMT user interface • Principle : one command driver : cmt • All CMT actions are operated via this command line driver • gmake internally makes a wide use of it • Basic syntax cmt <verb> [ -<option>=<value> <parameters…> ] • Main commands cmt config re-configure a package cmt create … create a new package cmt show … monitors configuration parameters cmt broadcast … launch shell command over several packages cmt checkout … interface to CVS’ checkout operation cmt help get the list of possible commands source cleanup.sh undo the source setup 22

  23. The CMT user interface • Parameter monitoring cmt show … path package search paths uses the use tree macros all macro definitions sets all set and path definitions tags currently active tags macro <macro-name> complete definition for a macro set <set-name> complete definition for a set constituents all constituents for this package fragments all available make fragments clients all direct clients of this package packages all reachable packages 23

  24. The CMT architecture • The database • The requirements file • It is the unique source of configuration parameters for all packages • CMT automatically connects requirements files of all used packages (belonging to the current use tree) • The use relationship • The unique relationship between packages managed by CMT • Parameterized by the version • Similar to inheritance (includes private or public qualification) • The configuration parameters • Inherited parameters • Use relationships : relate packages to each other • Symbols : define make macros, environment variables, aliases • Tags : define value selectors for symbols • Patterns : factor out recurrent configuration schemes • Make fragments : extend the CMT behaviour • Local definitions (never inherited) • Constituents : for libraries, applications, document generators 24

  25. End of lecture #1 25

More Related