title | layout | related | redirect_from | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
CMS Offline Software |
default |
|
|
This tutorial will guide you through the creation of a topic branch for your analysis, and how to share it with your coworkers.
The instructions contained in this tutorial will allow you to create a fake analysis. For your real work, please use the branches suggested by your analysis coordinator.
Please make sure you registered to GitHub and that you have provided them a ssh public key to access your private repository. For more information see the FAQ.
The analysis workflow usually depends on changes not released in an official CMSSW builds. The old recipes where of the kind:
- Get a given release.
- Checkout a few, non released, packages as suggested by the Analysis convenors.
- (Optionally) checkout a few packages from your user area.
The equivalent which are going to use for git is:
- Get a given release.
- Merge in your area a few, non released, topic branches, as suggested by the analysis convenors.
- (Optionally) merge your private code:
- From a your private fork of CMSSW.
- From from your usercode directory.
This is done with the usual:
scram project CMSSW_7_0_0_pre0
cd CMSSW_7_0_0_pre0/src
eval `scram run -sh`