Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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![]() | ||||||||
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 uboonecodeThis 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![]() | |||||||
Notes | ||||||||
Line: 58 to 51 | ||||||||
The MicroBooNE guide![]() | ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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![]() /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![]() /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 delayWe're using an alternate CVMFS serveroasis.opensciencegrid.org . It may take a day or so for a release at FNAL to be available at Nevis. | |||||||
Bash shellThe mrb+git scripts will only run in the bash![]() LArSoft and uboonecode are still bash-only. | ||||||||
Line: 62 to 58 | ||||||||
The MicroBooNE guide![]() | ||||||||
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. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 17 to 17 | ||||||||
After you've run this command, you can follow the instruction in the MicroBooNE guide![]() | ||||||||
Changed: | ||||||||
< < | DIstribution | |||||||
> > | Distribution | |||||||
The MicroBooNE software directories are imported to Nevis via CVMFS![]() /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![]() ![]() 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![]() ![]() 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![]() ![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 21 to 21 | ||||||||
The MicroBooNE software directories are imported to Nevis via CVMFS![]() /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![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 31 to 31 | ||||||||
Bash shell | ||||||||
Changed: | ||||||||
< < | The mrb+git scripts will only run in the bash![]() | |||||||
> > | The mrb+git scripts will only run in the bash![]() 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![]() | ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 31 to 31 | ||||||||
Bash shell | ||||||||
Changed: | ||||||||
< < | The mrb+git scripts will only run in the bash![]() 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![]() | |||||||
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![]() | ||||||||
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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 31 to 31 | ||||||||
Bash shell | ||||||||
Changed: | ||||||||
< < | The mrb+git scripts will only run in the bash![]() | |||||||
> > | The mrb+git scripts will only run in the bash![]() 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![]() | ||||||||
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. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 19 to 19 | ||||||||
DIstribution | ||||||||
Changed: | ||||||||
< < | The MicroBooNE software directories are imported to Nevis via CVMFS![]() /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![]() /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 | |||||||
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![]() ![]() 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![]() ![]() 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![]() ![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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![]() DIstribution | ||||||||
Changed: | ||||||||
< < | The MicroBooNE software directories are imported to Nevis via CVMFS![]() /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![]() /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.) |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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![]() /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![]() | |||||||
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![]() /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 delayWe're using an alternate CVMFS serveroasis.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![]() | |||||||
Changed: | ||||||||
< < | After you've run this command, you can follow the instruction in the MicroBooNE guide![]() | |||||||
> > | 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 uboonecodeThis 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_DIRThe 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 MicroBooNE software directories are imported to Nevis via CVMFS![]() /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![]() 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![]() | |||||||
> > | The MicroBooNE guide![]() | |||||||
/a/share/westside/seligman/microboone/develop_uboone.sh | ||||||||
Line: 79 to 72 | ||||||||
Look at ~seligman/.bashrc for more ideas. | ||||||||
Added: | ||||||||
> > | Production scriptsAn easy way to access the production MicroBooNE is to set up theuboone product; e.g.:
setup uboone v2_4 -qe4:debugThe 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 packagesOne 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 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 15 to 15 | ||||||||
As of 07-Feb-2014, the following Fermilab LArSoft releases![]() | ||||||||
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. |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 uboonecodeThis takes a while to compile the first time, and will take up about 1.5GB in your working directory. | |||||||
Bash shell |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
LArSoft at Nevis | ||||||||
Line: 19 to 19 | ||||||||
v1_00_01 - Freeze after switch to mrb+git | ||||||||
Added: | ||||||||
> > | Limitations of the Nevis LArSoft installationNightly buildsNightly builds are not yet available at Nevis (nor anywhere else outside ofuboonevm.fnal.gov ).
Bash shellThe mrb+git scripts will only run in the bash![]() bash . If you want to permanently change your login shell to bash, you can do it via the ypchsh![]() | |||||||
Setting up the EnvironmentThe 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![]() | |||||||
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: | ||||||||
< < |
| |||||||
> > | 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 UNIXMy 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 LArSoftSince 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 towestside . | |||||||
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![]() ![]() 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![]() ![]() 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![]() ![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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.shYou 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 | ||||||||
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![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
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 | |||||||
| ||||||||
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![]() | ||||||||
Line: 15 to 19 | ||||||||
v1_00_01 - Freeze after switch to mrb+git | ||||||||
Deleted: | ||||||||
< < | Limitations of Nevis LArSoft installation
Where can one run LArSoftSince 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 towestside . | |||||||
Setting up the EnvironmentThe 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![]() NotesRegular development workThe MicroBooNE guide![]() /a/share/westside/seligman/microboone/develop_uboone.shLet'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 debugThis 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 packagesOne 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 LArSoftSince 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 towestside .
Limitations of Nevis LArSoft installation
| |||||||
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![]() ![]() 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![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
LArSoft at NevisOn this page:
![]() v1_00_02 - Minor compilation fixes; use updated cetbuildtools. v1_00_01 - Freeze after switch to mrb+git Limitations of Nevis LArSoft installation
Where can one run LArSoftSince 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 towestside .
Setting up the EnvironmentThe 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.shYou 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 notesWhen you set up LArSoft, the Nevis-specific setup command is disabled. The LArSoft software distribution contains its own copies of ROOT![]() ![]() 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![]() ![]() ![]() |