Difference: LArSoftAtNevis (1 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

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.

Revision 162015-02-04 - WilliamSeligman

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

LArSoft at Nevis

Line: 17 to 17
  After you've run this command, you can follow the instruction in the MicroBooNE guide (without running any of the FNAL system-specific scripts, of course).
Changed:
<
<

DIstribution

>
>

Distribution

  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.
Line: 124 to 124
 

Setting up ROOT and Geant4

Changed:
<
<
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, check that there are no setup commands in any of your shell initialization files like ~/.bashrc, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
>
>
The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to use environment modules (the module command) to set up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, check that there are no setup or module commands in any of your shell initialization files like ~/.bashrc, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
  The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above. \ No newline at end of file

Revision 152014-12-11 - WilliamSeligman

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

LArSoft at Nevis

Line: 21 to 21
  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.
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, $UBFCL_DIR), you can write scripts that will work at both Nevis and FNAL without any changes. (Condor jobs must be different, 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/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.)
 

Limitations

Line: 65 to 65
 /a/share/westside/seligman/microboone/develop_uboone.sh
Changed:
<
<
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 v02_00_01. Then a typical use of this script would be:
>
>
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 v02_00_01 e5 debug
>
>
source /a/share/westside/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 v02_00_01 e5 debug"
>
>
alias MBD="source /a/share/westside/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: 96 to 96
 

Finding packages

Changed:
<
<
One potentially confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.
>
>
One potentially confusing aspect of LArSoft is that it has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.
  For a guide as to which package is in which group, see LArSoft dependencies. Don't forget that there's also a "uboonecode" package group; code in that group supersedes the more general non-experiment-specific LArSoft code.

Revision 142014-07-02 - WilliamSeligman

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

LArSoft at Nevis

Line: 31 to 31
 

Bash shell

Changed:
<
<
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. 24-Jun-2014: Right now, the MicroBooNE setup scripts will also work in zsh, but you'll see some annoying error messages.
>
>
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.
  You can temporarily go into the bash shell simply by typing bash. If you want to permanently change your login shell to bash, you can do it via the ypchsh command.
Changed:
<
<
Other shells (tcsh and zsh) will be fully supported (someday), according to the LArSoft maintenance team.
>
>
Other shells (tcsh and zsh) may be fully supported (someday), according to the LArSoft maintenance team.
 

Builds and releases

Revision 132014-06-26 - WilliamSeligman

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

LArSoft at Nevis

Line: 31 to 31
 

Bash shell

Changed:
<
<
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. 18-Jun-2014: Right now, the mrb+git setup will work only for larsoft in zsh; they will not work for uboonecode. I've issued a ticket to try to get them to fix this.
>
>
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. 24-Jun-2014: Right now, the MicroBooNE setup scripts will also work in zsh, but you'll see some annoying error messages.
  You can temporarily go into the bash shell simply by typing bash. If you want to permanently change your login shell to bash, you can do it via the ypchsh command.
Changed:
<
<
Other shells (tcsh and zsh) will be supported (someday), but the LArSoft maintenance team is not yet ready.
>
>
Other shells (tcsh and zsh) will be fully supported (someday), according to the LArSoft maintenance team.
 

Builds and releases

Revision 122014-06-18 - WilliamSeligman

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

LArSoft at Nevis

Line: 31 to 31
 

Bash shell

Changed:
<
<
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.
>
>
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. 18-Jun-2014: Right now, the mrb+git setup will work only for larsoft in zsh; they will not work for uboonecode. I've issued a ticket to try to get them to fix this.
  You can temporarily go into the bash shell simply by typing bash. If you want to permanently change your login shell to bash, you can do it via the ypchsh command.
Line: 65 to 65
 /a/share/westside/seligman/microboone/develop_uboone.sh
Changed:
<
<
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 v02_01_00. Then a typical use of this script would be:
>
>
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 v02_00_01. Then a typical use of this script would be:
 
Changed:
<
<
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v02_01_00 e5 debug
>
>
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v02_00_01 e5 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 v02_01_00 e5 debug"
>
>
alias MBD="source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v02_00_01 e5 debug"
 

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

Revision 112014-06-17 - 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 /cvmfs/oasis.opensciencegrid.org/microboone/products/setup_uboone.sh
>
>
source /a/share/westside/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: 65 to 65
 /a/share/westside/seligman/microboone/develop_uboone.sh
Changed:
<
<
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 v1_00_08. Then a typical use of this script would be:
>
>
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 v02_01_00. Then a typical use of this script would be:
 
Changed:
<
<
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_08 e4 debug
>
>
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v02_01_00 e5 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 v1_00_08 e4 debug"
>
>
alias MBD="source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v02_01_00 e5 debug"
 

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

Line: 88 to 88
 
# If you haven't done this already; replace <vers> with
# your desired version number.
Changed:
<
<
setup uboonecode -q e4:debug
>
>
setup uboonecode -q e5:debug
 ls $UBOONECODE_DIR/job

Revision 102014-04-29 - WilliamSeligman

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

LArSoft at Nevis

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 that has 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/oasis.opensciencegrid.org/microboone on any of the Nevis Neutrino systems; they all have CVMFS installed. We automatically mirror Fermilab's releases.
  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, $UBFCL_DIR), you can write scripts that will work at both Nevis and FNAL without any changes. (Condor jobs must be different, since our batch cluster is organized differently.)
Line: 65 to 65
 /a/share/westside/seligman/microboone/develop_uboone.sh
Changed:
<
<
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 v1_00_04. Then a typical use of this script would be:
>
>
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 v1_00_08. Then a typical use of this script would be:
 
Changed:
<
<
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_04 e4 debug
>
>
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_08 e4 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 v1_00_04 e4 debug"
>
>
alias MBD="source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_08 e4 debug"
 

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

Look at ~seligman/.bashrc for more ideas.

Changed:
<
<

Production scripts

>
>

Finding scripts

 
Changed:
<
<
An easy way to access the production MicroBooNE .fcl files is to set up the uboone product. The uboone setup includes both ubooncode and larsoft:
setup uboone v2_4 -qe4:debug
>
>
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:
 
Deleted:
<
<
You will then be able to view the latest .fcl files:
 
Changed:
<
<
ls $UBFCL_DIR
>
>
# If you haven't done this already; replace with # your desired version number. setup uboonecode -q e4:debug ls $UBOONECODE_DIR/job
 
Changed:
<
<
The only difficulty is that the numbering scheme for uboone does not agree with of LArSoft, since the scripts are updated on a different schedule. To see a list of available versions:
ups list -aK+ uboone
>
>
Similarly, you'll find the .xml files in $UBOONECODE_DIR/job and python scripts in $UBOONECODE_DIR/python; note that these files only work at Fermilab, since Nevis uses condor differently (we don't have BlueArc, for example).
 

Finding packages

Line: 124 to 120
 

Where can one run LArSoft

Changed:
<
<
You can run jobs on any of the Neutrino systems with CVMFS installed. (06-Mar-2014: I plan to install this on Neutrino systems as I upgrade them to SL6)
>
>
You can run jobs on any of the Neutrino systems, since they all have CVMFS installed.
 

Setting up ROOT and Geant4

Changed:
<
<
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.bashrc, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
>
>
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, check that there are no setup commands in any of your shell initialization files like ~/.bashrc, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
  The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above.

Revision 92014-03-07 - WilliamSeligman

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

LArSoft at Nevis

Line: 13 to 13
 source /cvmfs/oasis.opensciencegrid.org/microboone/products/setup_uboone.sh
Changed:
<
<
You only have to run this once per login session.
>
>
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!
  After you've run this command, you can follow the instruction in the MicroBooNE guide (without running any of the FNAL system-specific scripts, of course).

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 that has 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/oasis.opensciencegrid.org/microboone on any of the Nevis Neutrino systems that has CVMFS installed. We automatically mirror Fermilab's releases.
  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, $UBFCL_DIR), you can write scripts that will work at both Nevis and FNAL without any changes. (Condor jobs must be different, since our batch cluster is organized differently.)

Revision 82014-03-07 - WilliamSeligman

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

LArSoft at Nevis

Line: 6 to 6
  This documents how to use the LArSoft and MicroBooNE software as managed by mrb+git. If you are looking for older LArSoft versions managed by SRT, see the LArSoft at Nevis SRT page.
Changed:
<
<

DIstribution

>
>

Setting up the Environment

 
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 systems that has CVMFS installed (06-Mar-2014: I plan to install this on Neutrino systems as I upgrade them to SL6). We automatically mirror Fermilab's releases.
>
>
The simplest way to initialize the mrb+git environment at Nevis is to execute the following command:
source /cvmfs/oasis.opensciencegrid.org/microboone/products/setup_uboone.sh
 
Changed:
<
<

Limitations

>
>
You only have to run this once per login session.
 
Changed:
<
<

Mirror delay

>
>
After you've run this command, you can follow the instruction in the MicroBooNE guide (without running any of the FNAL system-specific scripts, of course).
 
Changed:
<
<
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.
>
>

DIstribution

 
Changed:
<
<

Nightly builds

>
>
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 that has CVMFS installed. We automatically mirror Fermilab's releases.
 
Changed:
<
<
Nightly builds are not yet available. If you're doing cutting-edge LArSoft development, you can work around this limitation by checking out the development version of the entire LArSoft and/or uboonecode package; e.g.,
>
>
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, $UBFCL_DIR), you can write scripts that will work at both Nevis and FNAL without any changes. (Condor jobs must be different, since our batch cluster is organized differently.)
 
Changed:
<
<
mrb g larsoft_suite
mrb g uboonecode
>
>

Limitations

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

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

Line: 35 to 37
  Other shells (tcsh and zsh) will be supported (someday), but the LArSoft maintenance team is not yet ready.
Changed:
<
<

Setting up the Environment

>
>

Builds and releases

 
Changed:
<
<
The simplest way to initialize the mrb+git environment at Nevis is to execute the following command:
>
>
Nightly builds are no longer available. LArSoft and MicroBooNE have new releases on the order of once per week, so they're not needed anymore. For a list of available versions, set up the mrb+git environment and use:
 
Changed:
<
<
source /cvmfs/oasis.opensciencegrid.org/microboone/products/setup_uboone.sh
>
>
ups list -aK+ uboonecode
 
Changed:
<
<
You only have to run this once per login session.
>
>
See the release page for a description of the different releases.
 
Changed:
<
<
After you've run this command, you can follow the instruction in the MicroBooNE guide (without running any of the FNAL system-specific setup scripts, of course).
>
>
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.

 

Notes

Line: 74 to 83
 

Production scripts

Changed:
<
<
An easy way to access the production MicroBooNE is to set up the uboone product; e.g.:
>
>
An easy way to access the production MicroBooNE .fcl files is to set up the uboone product. The uboone setup includes both ubooncode and larsoft:
 
setup uboone v2_4 -qe4:debug
Changed:
<
<
The uboone setup includes both ubooncode and larsoft. The only difficulty is that the numbering scheme for uboone does not agree with of LArSoft, since the scripts are updated more frequently. To see a list of available versions:
>
>
You will then be able to view the latest .fcl files:
ls $UBFCL_DIR

The only difficulty is that the numbering scheme for uboone does not agree with of LArSoft, since the scripts are updated on a different schedule. To see a list of available versions:

 
ups list -aK+ uboone

Revision 72014-03-07 - WilliamSeligman

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

LArSoft at Nevis

Line: 6 to 6
  This documents how to use the LArSoft and MicroBooNE software as managed by mrb+git. If you are looking for older LArSoft versions managed by SRT, see the LArSoft at Nevis SRT page.
Changed:
<
<

Locations

>
>

DIstribution

 
Changed:
<
<
  • The Nevis copy of the LArSoft installation is currently in /a/data/westside/seligman/larsoft.
  • The Nevis copy of the uboonecode installation is currently in /a/data/westside/seligman/products.
>
>
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 systems that has CVMFS installed (06-Mar-2014: I plan to install this on Neutrino systems as I upgrade them to SL6). We automatically mirror Fermilab's releases.
 
Changed:
<
<

Releases

>
>

Limitations

 
Changed:
<
<
As of 07-Feb-2014, the following Fermilab LArSoft releases are maintained at Nevis:
v1_00_04 - Incorporating some additional fixes before the "real" code freeze for the MCC4 challenge.
v1_00_03 - Code freeze before MCC4 challenge.
v1_00_02 - Minor compilation fixes; use updated cetbuildtools.  
v1_00_01 - Freeze after switch to mrb+git   
>
>

Mirror delay

 
Changed:
<
<

Limitations of the Nevis LArSoft installation

>
>
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.
 

Nightly builds

Changed:
<
<
Nightly builds are not yet available at Nevis (nor anywhere else outside of uboonevm.fnal.gov). If you're doing cutting-edge LArSoft development, you can work around this limitation by checking out the development version of the entire LArSoft and/or uboonecode package; e.g.,
>
>
Nightly builds are not yet available. If you're doing cutting-edge LArSoft development, you can work around this limitation by checking out the development version of the entire LArSoft and/or uboonecode package; e.g.,
 
mrb g larsoft_suite

Line: 46 to 39
  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 /cvmfs/oasis.opensciencegrid.org/microboone/products/setup_uboone.sh
 

You only have to run this once per login session.

Line: 57 to 50
 

Regular development work

Changed:
<
<
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:
>
>
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:
 
/a/share/westside/seligman/microboone/develop_uboone.sh
Line: 79 to 72
  Look at ~seligman/.bashrc for more ideas.
Added:
>
>

Production scripts

An easy way to access the production MicroBooNE is to set up the uboone product; e.g.:

setup uboone v2_4 -qe4:debug

The uboone setup includes both ubooncode and larsoft. The only difficulty is that the numbering scheme for uboone does not agree with of LArSoft, since the scripts are updated more frequently. To see a list of available versions:

ups list -aK+ uboone
 

Finding packages

One potentially confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.

Line: 105 to 110
 

Where can one run LArSoft

Changed:
<
<
Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.
>
>
You can run jobs on any of the Neutrino systems with CVMFS installed. (06-Mar-2014: I plan to install this on Neutrino systems as I upgrade them to SL6)
 

Setting up ROOT and Geant4

Revision 62014-03-05 - WilliamSeligman

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

LArSoft at Nevis

Line: 15 to 15
  As of 07-Feb-2014, the following Fermilab LArSoft releases are maintained at Nevis:
Added:
>
>
v1_00_04 - Incorporating some additional fixes before the "real" code freeze for the MCC4 challenge. v1_00_03 - Code freeze before MCC4 challenge.
 v1_00_02 - Minor compilation fixes; use updated cetbuildtools. v1_00_01 - Freeze after switch to mrb+git
Line: 61 to 63
 /a/share/westside/seligman/microboone/develop_uboone.sh
Changed:
<
<
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 v1_00_02. Then a typical use of this script would be:
>
>
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 v1_00_04. Then a typical use of this script would be:
 
Changed:
<
<
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_02 e4 debug
>
>
source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_04 e4 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 v1_00_02 e4 debug"
>
>
alias MBD="source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_04 e4 debug"
 

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

Revision 52014-02-22 - WilliamSeligman

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

LArSoft at Nevis

Line: 23 to 23
 

Nightly builds

Changed:
<
<
Nightly builds are not yet available at Nevis (nor anywhere else outside of uboonevm.fnal.gov).
>
>
Nightly builds are not yet available at Nevis (nor anywhere else outside of uboonevm.fnal.gov). If you're doing cutting-edge LArSoft development, you can work around this limitation by checking out 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.

 

Bash shell

Revision 42014-02-19 - WilliamSeligman

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

LArSoft at Nevis

Line: 19 to 19
 v1_00_01 - Freeze after switch to mrb+git
Added:
>
>

Limitations of the Nevis LArSoft installation

Nightly builds

Nightly builds are not yet available at Nevis (nor anywhere else outside of uboonevm.fnal.gov).

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.

You can temporarily go into the bash shell simply by typing bash. If you want to permanently change your login shell to bash, you can do it via the ypchsh command.

Other shells (tcsh and zsh) will be supported (someday), but the LArSoft maintenance team is not yet ready.

 

Setting up the Environment

The simplest way to initialize the mrb+git environment at Nevis is to execute the following command:

Line: 60 to 74
  One potentially confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.
Changed:
<
<
For a guide as to which package is in which group, see LArSoft dependencies.
>
>
For a guide as to which package is in which group, see LArSoft dependencies. Don't forget that there's also a "uboonecode" package group; code in that group supersedes the more general non-experiment-specific LArSoft code.
 
Changed:
<
<

Where can one run LArSoft

>
>
Browsing code on the web
 
Changed:
<
<
Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.
>
>
If you want to browse the code in one of the package groups (e.g., larsim, larreco, ubooncode), you can use the Redmine repository listings at FNAL. The "magic formula" is:
 
Changed:
<
<

Limitations of Nevis LArSoft installation

>
>
https://cdcvs.fnal.gov/redmine/projects/<package-name>/repository
 
Changed:
<
<
  • Nightly builds are not yet available at Nevis (nor anywhere else outside of uboonevm.fnal.gov).
  • The mrb+git scripts will only run in the bash shell. Other shells (tcsh and zsh) will be supported (someday), but the LArSoft maintenance team is not yet ready.
>
>
So if you want to look at the package group larreco, you'd visit the URL https://cdcvs.fnal.gov/redmine/projects/larreco/repository

Browsing code in UNIX

My preferred way is to look at the code as it's stored on the local computer cluster. After you've set up LArSoft, you can find the code for a given package group in the directory:

$<PACKAGE-NAME>_DIR/source

If you wanted to look at the packages in group larsim, you can do:

ls $LARSIM_DIR/source

Where can one run LArSoft

Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.

 

Setting up ROOT and Geant4

Changed:
<
<
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
>
>
When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.bashrc, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.
  The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above.

Revision 32014-02-10 - WilliamSeligman

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

LArSoft at Nevis

Line: 21 to 21
 

Setting up the Environment

Changed:
<
<
The simplest way to initialize the variables to run LArSoft at Nevis is to execute the following command:
>
>
The simplest way to initialize the mrb+git environment at Nevis is to execute the following command:
 
source /a/share/westside/seligman/microboone/setup_uboone.sh

You only have to run this once per login session.

Changed:
<
<
After you've run this command, you can follow the instruction in the MicroBooNE guide.
>
>
After you've run this command, you can follow the instruction in the MicroBooNE guide (without running any of the FNAL system-specific setup scripts, of course).
 

Notes

Line: 58 to 58
 

Finding packages

Changed:
<
<
One potentially-confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.
>
>
One potentially confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.
  For a guide as to which package is in which group, see LArSoft dependencies.

Revision 22014-02-10 - WilliamSeligman

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

LArSoft at Nevis

Added:
>
>
This documents how to use the LArSoft and MicroBooNE software as managed by mrb+git. If you are looking for older LArSoft versions managed by SRT, see the LArSoft at Nevis SRT page.

Locations

 
  • The Nevis copy of the LArSoft installation is currently in /a/data/westside/seligman/larsoft.
  • The Nevis copy of the uboonecode installation is currently in /a/data/westside/seligman/products.
Changed:
<
<
This documents how to use the LArSoft and MicroBooNE software as managed by mrb+git. If you are looking for older LArSoft versions managed by SRT, see the LArSoft at Nevis SRT page.
>
>

Releases

  As of 07-Feb-2014, the following Fermilab LArSoft releases are maintained at Nevis:
Line: 15 to 19
 v1_00_01 - Freeze after switch to mrb+git
Deleted:
<
<

Limitations of Nevis LArSoft installation

  • Nightly builds are not yet available at Nevis (nor anywhere else outside of FNAL systems).
  • The mrb+git scripts will only run in the bash shell. Other shells (tcsh and zsh) will be supported (someday), but FNAL CD is not yet ready.

Where can one run LArSoft

Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.

 

Setting up the Environment

The simplest way to initialize the variables to run LArSoft at Nevis is to execute the following command:

Line: 33 to 28
  You only have to run this once per login session.
Changed:
<
<
After you've run this command, you can follow the instruction in the !MicroBooNE guide.
>
>
After you've run this command, you can follow the instruction in the MicroBooNE guide.

Notes

Regular development work

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:

/a/share/westside/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 v1_00_02. Then a typical use of this script would be:

source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_02 e4 debug

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

alias MBD="source /a/share/westside/seligman/microboone/develop_uboone.sh ~/mydev v1_00_02 e4 debug"

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

Look at ~seligman/.bashrc for more ideas.

Finding packages

One potentially-confusing aspect of the new arrangement is that LArSoft has been sub-divided into package groups. In order to check out a package, you have to know which group it's in. For example, you can't check out LArG4; you have to check out "larsim" which is a group of packages, one of which is LArG4.

For a guide as to which package is in which group, see LArSoft dependencies.

Where can one run LArSoft

Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.

Limitations of Nevis LArSoft installation

  • Nightly builds are not yet available at Nevis (nor anywhere else outside of uboonevm.fnal.gov).
  • The mrb+git scripts will only run in the bash shell. Other shells (tcsh and zsh) will be supported (someday), but the LArSoft maintenance team is not yet ready.
 
Changed:
<
<

Nevis notes

>
>

Setting up ROOT and Geant4

  When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

Revision 12014-02-07 - WilliamSeligman

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

LArSoft at Nevis

  • The Nevis copy of the LArSoft installation is currently in /a/data/westside/seligman/larsoft.
  • The Nevis copy of the uboonecode installation is currently in /a/data/westside/seligman/products.

This documents how to use the LArSoft and MicroBooNE software as managed by mrb+git. If you are looking for older LArSoft versions managed by SRT, see the LArSoft at Nevis SRT page.

As of 07-Feb-2014, the following Fermilab LArSoft releases are maintained at Nevis:

v1_00_02 - Minor compilation fixes; use updated cetbuildtools.  
v1_00_01 - Freeze after switch to mrb+git   

Limitations of Nevis LArSoft installation

  • Nightly builds are not yet available at Nevis (nor anywhere else outside of FNAL systems).
  • The mrb+git scripts will only run in the bash shell. Other shells (tcsh and zsh) will be supported (someday), but FNAL CD is not yet ready.

Where can one run LArSoft

Since all the machines on the Nevis Linux Cluster are linked together via automount, the software should run on any machine on the cluster, whether or not that particular machine is owned by the Neutrino group. You do not have to login to westside.

Setting up the Environment

The simplest way to initialize the variables to run LArSoft at Nevis is to execute the following command:

source /a/share/westside/seligman/microboone/setup_uboone.sh

You only have to run this once per login session.

After you've run this command, you can follow the instruction in the !MicroBooNE guide.

Nevis notes

When you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT and Geant4, so there's no need to set-up the Nevis versions. In fact, to make sure the Nevis versions don't conflict with the LArSoft versions, make sure there are no setup commands in any of your shell initialization files like ~/.myprofile, especially if you're switching to LArSoft from some other project or from working on the ROOT tutorial.

The LArSoft environment also affects some standard Linux features, such as the default rules for make and the yum command. If you are doing any work that does not involve LArSoft directly, you're advised not to set up the LArSoft environment as described above.

 
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