Difference: LHCbWithEclipseBasics (9 vs. 10)

Revision 102011-09-23 - MarcoClemencic

Line: 1 to 1
 
META TOPICPARENT name="LHCbSoftwareTutorials"
<!-- Note to editors of this page: The following TWiki Variables are defined for this page: GAUDIVERSION and DAVINCIVERSION -->
<!-- They correspond to the last version for which these instructions have been verified, and should be consistent with each other -->
<!-- To change their value, exit edit and go to "More topic actions" -> "Edit settings" -->
Line: 75 to 75
 
xlogo
  • Check the group associated with your account by giving the command:
    echo $GROUP
Deleted:
<
<
  • Check that you can start eclipse:
    eclipse &
  For an account in the LHCb group the result should be z5.
  • Check which shell you are using, for example using:
    echo $0
Line: 82 to 80
 
echo $0
or
echo $SHELL
Deleted:
<
<
 
  • Check that the standard LHCb environment has been set. If it has, then you will have seen a message at login time about your CMT settings, and the result of the command:
    env
Deleted:
<
<
 should contain a number of variables with prefix LHCB ( LHCBHOME, LHCBRELEASES and so on), and with prefix CMT ( CMTROOT, CMTCONFIG and so on). If this isn't the case then you need to setup the environment yourself.
Added:
>
>
  • Check that you can start eclipse:
    eclipse &
 

Organisation of LHCb software

Line: 305 to 303
  size="75%" }%
Changed:
<
<
* Please note that the version on the screenshot might be outdated :)*
>
>
Please note that the version on the screenshot might be outdated smile
 
  • Look at the cmt/project.cmt file that was created: in the Project Explorer View navigate to DaVinci_v29r0 > cmt > project.cmt. You can expand an item by double-clicking on it, or click on the little arrow at the left of the name.
Line: 372 to 370
  The environment in which you build and run an application is fully determined by choosing which CMT project you wish to work with, and the value of the CMTPROJECTPATH environment variable.
Changed:
<
<
The SetupProject script removes the need to set these variables explicitly. It uses CMT to fully define the run time enviroment for a given version of an LHCb application. See also the SetupProject user guide and FAQ.
>
>
The SetupProject script removes the need to set these variables explicitly. It uses CMT to fully define the run time environment for a given version of an LHCb application. See also the SetupProject user guide and FAQ.
  Once the environment is set, the application is executed by simply typing the executable name, giving the name of a job options file as argument. The job options control what the application actually does when it runs. Controlling what happens when the application is run means knowing how to add new code and understanding the job options.
Line: 394 to 392
 In the new window, double click on Program in the left list. In the main view, enter SetupProject and Run as the Name. The Location must be
${env_var:SHELL}
Under Working Directory, click Browse Workspace and select the project you are currently working with (should be DaVinci _v29r0). Then, set this as the arguments:
Changed:
<
<
-c "SetupProject DaVinci v28r1p1
gaudirun.py $DAVINCIROOT/options/DaVinci-Default.py $APPCONFIGOPTS/DaVinci/DataType-2010.py"
>
>
-c "SetupProject DaVinci v29r0
gaudirun.py $DAVINCIROOT/options/DaVinci-Default.py $APPCONFIGOPTS/DaVinci/DataType-2010.py"
 
Changed:
<
<
This will execute the released DaVinci application, with default job options. The SetupProject command sets up all the necessary environment to run the application. Once you have chosen a version and set up the enviroment, the behaviour of the application is determined by the job options file that you supply as the argument of the gaudirun.py command.
>
>
This will execute the released DaVinci application, with default job options. The SetupProject command sets up all the necessary environment to run the application. Once you have chosen a version and set up the environment, the behavior of the application is determined by the job options file that you supply as the argument of the gaudirun.py command.
  Hit Apply and Run (or Close).
Line: 411 to 409
  The project will then be built, and the commands provided above will be launched in a new console usually right below the editor.
Added:
>
>
Note: you can configure the external tool execution so that it skips the build using the build tab in the configuration window.
 Notice also that you can keep any number of different job options files in your own area, each describing a different configuration of the application (e.g. different cuts), without having to rebuild the standard application. This is recommended if your analysis can be carried out simply by modifying job options (i.e. if you do not need to write your own C++ algorithms).
Changed:
<
<
gaudirun.py is a generic Gaudi application written in python. It is used as main program for all LHCb applications. The specific behaviour of the application is defined by the options file(s) provided as argument(s). Options files can be written either in the old Gaudi native syntax (.opts) or using python syntax. The python syntax is recommended.
>
>
gaudirun.py is a generic Gaudi application written in python. It is used as main program for all LHCb applications. The specific behavior of the application is defined by the options file(s) provided as argument(s). Options files can be written either in the old Gaudi native syntax (.opts) or using python syntax. The python syntax is recommended.
 

Exercise 5

 
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