CodeEnvironment: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
No edit summary
Line 26: Line 26:


At this point, you are ready start selecting which Mu2e code to build or run.
At this point, you are ready start selecting which Mu2e code to build or run.
==Another way==
From time to time, you might see the instruction
source /cvmfs/mu2e.opensciencegrid.org/setupmu2e-art
this a equivalent to
setup mu2e
but we recommend the latter.





Revision as of 22:30, 20 September 2021

Introduction

This page explains the initial steps to preparing the linux shell environment for building code, running executables, 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:

  1. sets variable environmental variables such as
  2. MU2E_DATA_PATH
  3. sets your product path (where UPS can find more UPS products) to
  4. /cvmfs/mu2e.opensciencegrid.org/artexternals /cvmfs/fermilab.opensciencegrid.org/products/common/db
  5. does a UPS setups of a version of git
  6. does a UPS setup of a version of Muse

At this point, you are ready start selecting which Mu2e code to build or run.


Another way

From time to time, you might see the instruction

source /cvmfs/mu2e.opensciencegrid.org/setupmu2e-art

this a equivalent to

setup mu2e

but we recommend the latter.