CodeEnvironment: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Creating an environment in which you can build and run Mu2e code is a three step process that stars with a clean shell: | Creating an environment in which you can build and run Mu2e code is a three step process that stars with a clean shell: | ||
# Create the recommended login scripts; see[[Shells#Setup_scripts]] | # Create the recommended login scripts; see [[Shells#Setup_scripts]] | ||
# Issue the command <code> setup mu2e </code>; see[[LoginTutorial#Check_setup_mu2e]] | # Issue the command <code> setup mu2e </code>; see [[LoginTutorial#Check_setup_mu2e]] | ||
# One or more of: | # One or more of: | ||
#* muse setup | #* muse setup | ||
Revision as of 04:08, 4 October 2023
This page reviews the management of the Mu2e bash shell environment for building code, running executables, or submitting jobs.
Creating an environment in which you can build and run Mu2e code is a three step process that stars with a clean shell:
- Create the recommended login scripts; see Shells#Setup_scripts
- Issue the command
setup mu2e; see LoginTutorial#Check_setup_mu2e - One or more of:
- muse setup
- setup mu2egrid
- setup sam_web_client
- and many more
You will encounter several different versions of the items in 3 as you work through the tutorials.
If you are an expert who has chosen to not setup UPS in their login scripts, steps 1 and two are merged together as described in Shells#Expert_Only.