CodeEnvironment: Difference between revisions
Jump to navigation
Jump to search
(Created page with " ==Introduction== This page explains the initial steps to preparing the linux shell environment for building code, running executable, or submitting jobs. ==Mu2e environment...") |
|||
| Line 24: | Line 24: | ||
<li>does a UPS setup of a version of [[Muse]]</li> | <li>does a UPS setup of a version of [[Muse]]</li> | ||
</ol> | </ol> | ||
At this point, you are ready start selecting which Mu2e code to build or run. | |||
[[Category:Computing]] | [[Category:Computing]] | ||
[[Category:Code]] | [[Category:Code]] | ||
[[Category:Tutorial]] | [[Category:Tutorial]] | ||
Revision as of 21:29, 20 September 2021
Introduction
This page explains the initial steps to preparing the linux shell environment for building code, running executable, or submitting jobs.
Mu2e environment
Please refer to the Shells pages to setup your bash login scripts. This page assumes you have followed the recommendations there, in particular, you have placed
source /cvmfs/fermilab.opensciencegrid.org/products/common/etc/setups.sh
in your .bash_profile
After logging in you should be able to
setup mu2e
If you see any errors, you probably do not have the above condition met.
The setup mu2e command executes a UPS procedure to alter your environment. In particular this command:
- sets variable environmental variables such as MU2E_DATA_PATH
- sets your product path (where UPS can find more UPS products) to /cvmfs/mu2e.opensciencegrid.org/artexternals /cvmfs/fermilab.opensciencegrid.org/products/common/db
- does a UPS setups of a version of git
- does a UPS setup of a version of Muse
At this point, you are ready start selecting which Mu2e code to build or run.