Search results

used in this example to set up our Mu2e environment, and can be used to create and manage custom user environments. Upon initialising, Mamba will write some

use highest number from $MUSE_ENVSET_DIR There is a way to make your own custom local envset, see that section. When running setup on a linux OS (such as

mu2einit that create one experiment-specific environment. If you mix experiment-specific or project-specific environments, you will often get an inconsistent software

some OSG sites (SU-ITS and FNAL as of 10/2019) can run custom singularity containers. A custom container can be built on our Mu2e image node (see above)

user. The user may simply check a box for what VM to use, or may build a custom VM for the experiment, or even specific to the workflow. An light-weight

way the code would be accessed on a standard disk. The disk is actually a custom nfs server with a small ( ~8 GB) local cache on the node and a backend that

format event-data files. As of March 2022, Mu2e has two data analysis environments based on ROOT, TrkAna and Stntuple. See also: the ROOT Class Index. RPC

for a few very specific purposes. FermiCloud OpenStack Service Request a custom configured VM; best suited for temporary use. You can only log in to the

on each machine is externally managed. You will also want to port any customizations from your .login and .cshrc files to .my_bash_profile and .my_bashrc

interactive command lines and ROOT macros were parsed and executed by a custom written interpreter named CINT . CINT was advertised as an interpreter for

written source modules found in Mu2e Offline in Sources/src/*_source.cc . A custom source module that is used in the trigger; it copies events from the live

execute either of these workflows make sure you have defined the Mu2e environment by executing mu2einit in your shell. This ensures that you have known

TrkHitReco/src/SConscript these files, mostly in src subdirectories, can customize the scons behavior for operating on the code in the directory where it