Difference: LArSoftAtNevis (17 vs. 18)

Revision 182019-09-13 - WilliamSeligman

Line: 1 to 1
 
META TOPICPARENT name="WilliamSeligman"

LArSoft at Nevis

Line: 10 to 10
  The simplest way to initialize the mrb+git environment at Nevis is to execute the following command:
Changed:
<
<
source /a/share/amsterdam/seligman/microboone/setup_uboone.sh
>
>
source /nevis/amsterdam/share/seligman/microboone/setup_uboone.sh
 

You only have to run this once per login session. If this command hasn't been run in a while, there may be a delay as files are downloaded via CVMFS; give it time!

Line: 42 to 42
  See the release page for a description of the different releases.
Changed:
<
<
If you're doing cutting-edge LArSoft development, you can get the development version of the entire LArSoft and/or uboonecode package; e.g.,

mrb g larsoft_suite
mrb g uboonecode

This takes a while to compile the first time, and will take up about 1.5GB in your working directory.

>
>
If you're doing cutting-edge LArSoft development, you can get the development version of the entire LArSoft and/or uboonecode package. See https://cdcvs.fnal.gov/redmine/projects/uboonecode/wiki/Uboone_guide for more information.
 

Notes

Line: 58 to 51
 The MicroBooNE guide contains several procedures, but most of them are not commands that you'd type in every day. If your typical work flow is to login and start editing code in something you've already checked out, you may be interested in this script that WilliamSeligman wrote for himself:
Changed:
<
<
/a/share/amsterdam/seligman/microboone/develop_uboone.sh
>
>
/nevis/amsterdam/share/seligman/microboone/develop_uboone.sh
 

Let's assume that you've previously set up (via mrb newDev) and checked-out (via mrb gitCheckout) some code that you're working on into your directory ~/mydev, and that code is part of LArSoft release v03_04_05. Then a typical use of this script would be:

Changed:
<
<
source /a/share/amsterdam/seligman/microboone/develop_uboone.sh ~/mydev v03_04_05 e6 debug
>
>
source /nevis/amsterdam/share/seligman/microboone/develop_uboone.sh ~/mydev v03_04_05 e6 debug
 

This becomes handy if you set up an alias in ~/.bashrc, the script that gets automatically executed when you login to bash:

Changed:
<
<
alias MBD="source /a/share/amsterdam/seligman/microboone/develop_uboone.sh ~/mydev v03_04_05 e6 debug"
>
>
alias MBD="source /nevis/amsterdam/share/seligman/microboone/develop_uboone.sh ~/mydev v03_04_05 e6 debug"
 

Then you just have to type MBD after you login, and you're ready to work.

Line: 79 to 72
 

Finding scripts

Changed:
<
<
The production MicroBooNE .fcl files used to be in a product called "uboone", which no longer exists as an independent entity. All the files that used to be part of "uboone" are now in "uboonecode". The production .fcl scripts can be found by setting up uboonecode:
>
>
The production MicroBooNE .fcl scripts can be found by setting up uboonecode:
 
# If you haven't done this already; replace <vers> with
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback