News

2020-05-12 Change of default behaviour when connecting to lxplus

As from this morning, the default environment when logging to lxplus is LbEnv (stable flavour).

2020-04-27 Change of default behaviour when connecting to lxplus

Dear all,

Until now, when logging on to lxplus (and other clusters) the LHCb software environment has been configured for users by a set of scripts called LbScripts. They provide the tools needed to run and develop LHCb Software such as lb-run or lb-dev.

As mentioned during LHCb weeks last year, we have had to rewrite those scripts in order to follow the evolution of the python language. We took this opportunity to improve the design, add functionality and to make them easier to deploy. This replacement is called LbEnv.

One major change is that there is no default platform (a.k.a CMTCONFIG or BINARY_TAG) at log-in time, as it is difficult to find a default that makes sense for all uses of the software (Simulation, Run1/Run2 analysis, Upgrade development). The lb-run and lb-dev tools have however been upgraded to choose the most appropriate platform when invoked. This means that it is not necessary to set those environment variables any more before using lb-run.

LbEnv has been available for test for some time, and all issues encountered by the testers have been fixed. We would be however very grateful if you could start testing your workflows with it as per: http://lhcb-core-doc.web.cern.ch/lhcb-core-doc/LHCbEnvironment.html#user-configuration-of-group-login.

If no major issues are encountered, we would like to make it the default in the coming weeks, ideally on the 11th of May.

Best regards,

Ben & Marco, for the Core Software Team

P.S. More info can be found at: http://lhcb-core-doc.web.cern.ch/lhcb-core-doc/LHCbEnvironment.html

The release notes for the python LbEnv package providing lb-run, and LbDevTools providing lb-dev can be found here: https://gitlab.cern.ch/lhcb-core/LbEnv/-/releases https://gitlab.cern.ch/lhcb-core/LbDevTools/-/releases