The LBSCRIPTS Project
Welcome to the LBSCRIPTS project website

This CMT project is designed to contains all the usefull scripts for the management of the LHCb software.

Announcements

To have access to all the available versions, please follow this link.

This link points to the latest doxygen available for this project.

This project is designed to provide the environment for the development of LHCb applications and it is also a container for the general purpose LHCb scripts.

Bugs for this project can be reported at its savannah page in its bug tracker.

Usage

The settings and tools provided by LbScripts is the default environment for LHCb in all situations. It can also be enabled at will for its usage on a LHCb AFS account. For a more sophisticated installation (for a site or on a server with multiple users for example), please have a look at this page instead.

On AFS

The LHCb environment is enabled by default. In order to switch from the new LHCb environment to the old one, only one file has to be created in the home directory of the account.

$HOME/.oldLHCBLoginscript
This will disable the usage of the new scripts at login time and restore the old environment usual. This manipulation is needed only in case of failure of the setup provided by LbLogin and LbScripts.

It is possible to avoid invoking the LHCb scripts altogether by creating the following file:

$HOME/.noLHCBLoginscript

To use the current development version of LbScripts create the following file:

$HOME/.devLHCBLoginscript

And finally to use the scripts from CVMFS instead of AFS create the following file:

$HOME/.devLHCBuseCVMFS

For the windows platform. Assuming that the Z: drive is the AFS one, one just have to create a shortcut to cmd.exe with:

cmd.exe /k Z:\cern.ch\lhcb\software\releases\LBSCRIPTS\prod\InstallArea\scripts\LbLogin.bat

With a local installation

For a local installation, the install script will take care of downloading and installing the LbScripts project. It will also create the LbLogin wrappers (LbLogin.{sh,csh,bat}) and links to them in the main $MYSITEROOT directory.

On Linux

In order to get the LHCb environment in a local installation on Linux, one has just to call the following script:

source $MYSITEROOT/LbLogin.csh

in tcsh and

. $MYSITEROOT/LbLogin.sh

in bash. It has to be noted that the MYSITEROOT environment variable is not needed by the LbLogin script itself. It is mandatory to have it in order to be able to run install_project.py but it is only quoted in the previous example as a convenient way to locate LbLogin.

On Windows

On that platform, it is simpler. One only needs to create a shortcut to the cmd.exe executable:
cmd.exe /k %MYSITEROOT%\LbLogin.bat

As previously explained, the MYSITEROOT variable is only here for the example, one should rather replace it with the real location

The result will be the same if the command:

call %MYSITEROOT%\LbLogin.bat

is issued directly on the command prompt.

Project organisation

Here are the main packages sofar contained in the LbScripts project with a short description:

LbUtils
Package for generic utilities not related to LHCb specifics.
LbScriptsPolicy
Package containing all the internal mechanics for the build and setup of the LbScripts project
LbConfiguration
Package containing the LHCb specific configuration settings and some core tools like SetupProject
LbRelease
Contains all the user and management tools
LbLegacy
Contains old scripts for backward compatibility. They will eventually be replaced
LbScriptsSys
Steering package which contains the versions of the packages used in the project release. Its release tag has to be the same as the project version. It also contains the configuration file for the Doxygen generation.

Conventions for the script writing and location

There are two types of scripts which can be called from the command lines: