Difference: LHCbRichMirrorAlignGitInfo (33 vs. 34)

Revision 342018-05-23 - ParasNaik

Line: 1 to 1
 
META TOPICPARENT name="LHCbRichMirrorAlign"
Line: 118 to 118
 
  • LbLogin (for some reason you have to run this after setting the user release area)
  • cd $User_release_area
Changed:
<
<
Then this you do only once, when you start from scratch (though peform it separately when starting from each new Panoptes release, here we assume the newest is v7r3, you should check in gitlab):
  • lb-dev --nightly lhcb-head Panoptes/v7r3
    • This creates a local git repository in PanoptesDev_v7r3. This is called a "satellite project".
    • (NOTE we do need to use the nightlies, unless we know that other people are working on code that may affect us... simply use lb-dev Panoptes/v7r3 instead if this is not the immediate case)
>
>
Then this you do only once, when you start from scratch (though peform it separately when starting from each new Panoptes release, here we assume the newest is v8r1, you should check in gitlab):
  • lb-dev --nightly lhcb-head Panoptes/v8r1
    • This creates a local git repository in PanoptesDev_v8r1. This is called a "satellite project".
    • (NOTE we do need to use the nightlies, unless we know that other people are working on code that may affect us... simply use lb-dev Panoptes/v8r1 instead if this is not the immediate case)
  These you do as long as you are working with the project and version in the previous line (NOTE the "Dev"):
Changed:
<
<
  • cd $User_release_area/PanoptesDev_v7r3
>
>
  • cd $User_release_area/PanoptesDev_v8r1
 
  • git lb-use Panoptes
    • This adds the gitlab remote to the local repository of the satellite project, and fetches that remote (makes a local copy of the remote repository, although you still don't see it in your working tree).
Line: 134 to 134
  * [new branch] 2018-patches -> Panoptes/2018-patches
* [new tag] v1r0 -> Panoptes/v1r0
[...]
Changed:
<
<
* [new tag] v7r1 -> Panoptes/v7r1
* [new tag] v7r3 -> Panoptes/v7r3
>
>
* [new tag] v8r1 -> Panoptes/v8r1
 

You will see that there are several references that you can use.

Line: 222 to 221
 
  • git lb-checkout Panoptes/asolomin-MirrAlign-20170123 Rich/RichMirrorAlignmentOnline

After the merge requests are applied and only after, when you are ready to start work again you will want to update your local packages from the 2018-patches, in case there were any changes in the 2018-patches in the meantime:

Changed:
<
<
  • cd $User_release_area/PanoptesDev_v7r3
>
>
  • cd $User_release_area/PanoptesDev_v8r1
 
  • git fetch --all # (Remember, you must do this in order to get access to remote changes in Panoptes/2018-patches or any other branch)
  • git lb-checkout Panoptes/2018-patches Rich/RichMirrorAlignmentOnline (and the same for ALL other packages you checked out from 2018-patches, unless you are still working on a branch of a different package)
Line: 250 to 249
 new shell ( e.g. ssh -Y asolomin@lxplusNOSPAMPLEASE.cern.ch )
  • setenv User_release_area /afs/cern.ch/user/a/asolomin/gituser
  • LbLogin
Changed:
<
<
  • cd $User_release_area/PanoptesDev_v7r3
>
>
  • cd $User_release_area/PanoptesDev_v8r1
 
  • make install
  • cd /afs/cern.ch/user/a/asolomin/public/rich_align_test (or wherever your test is)
Changed:
<
<
>
>
 

Slight differences to the above for the Hlt project

 
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