Difference: LArSoftAtNevis (16 vs. 17)

Revision 172015-10-05 - 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/westside/seligman/microboone/setup_uboone.sh
>
>
source /a/share/amsterdam/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: 19 to 19
 

Distribution

Changed:
<
<
The MicroBooNE software directories are imported to Nevis via CVMFS. You can browse the files at /cvmfs/oasis.opensciencegrid.org/microboone on any of the Nevis Neutrino systems; they all have CVMFS installed. We automatically mirror Fermilab's releases.
>
>
The MicroBooNE software directories are imported to Nevis via CVMFS. You can browse the files at /cvmfs/fermilab.opensciencegrid.org/ and /cvmfs/uboone.opensciencegrid.org/ on any of the Nevis Neutrino systems; they all have CVMFS installed. We automatically mirror Fermilab's releases.
 
Changed:
<
<
A strong advantage of this set-up is that if you use the CVMFS paths (those that begin with /cvmfs/oasis.opensciencegrid.org/) and abstract path variables (e.g., $MRB_INSTALL), you can write scripts that will work at both Nevis and FNAL without any changes. (Nevis Condor jobs must be different from those at FNAL, since our batch cluster is organized differently.)
>
>
A strong advantage of this set-up is that if you use the CVMFS paths (those that begin with /cvmfs/fermilab.opensciencegrid.org/) and abstract path variables (e.g., $MRB_INSTALL), you can write scripts that will work at both Nevis and FNAL without any changes. (Nevis Condor jobs must be different from those at FNAL, since our batch cluster is organized differently.)
 

Limitations

Deleted:
<
<

Mirror delay

We're using an alternate CVMFS server oasis.opensciencegrid.org. It may take a day or so for a release at FNAL to be available at Nevis.

 

Bash shell

The mrb+git scripts will only run in the bash shell. In other shells, you'll see error messages about missing libraries or being unable to set up products. 31-Jun-2014: Although for a time it seemed like some of the setup scripts would run in zsh, those same scripts would not run in a condor environment. LArSoft and uboonecode are still bash-only.

Line: 62 to 58
 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/westside/seligman/microboone/develop_uboone.sh
>
>
/a/share/amsterdam/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/westside/seligman/microboone/develop_uboone.sh ~/mydev v03_04_05 e6 debug
>
>
source /a/share/amsterdam/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/westside/seligman/microboone/develop_uboone.sh ~/mydev v03_04_05 e6 debug"
>
>
alias MBD="source /a/share/amsterdam/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.

 
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