Search results

examples follow. A user has an analysis repo they want to build against the current Offline build. The user would clone the analysis repo in their workDir then

as your VO (Virtual Organization, i.e. your experiment) and your role ("Analysis" or "Production"). In our current procedures, you should never need to

wrap compiled c++ code so it can be used in python art error codes Elastic Analysis Facility (EAF) Spack - setup and build tool to replace UPS and MRB SpackMaintenance

computing resources Docker software containers for submitting to special farms analysis workflow - how to read existing datasets production simulation workflow

written to tape. But simulation run by individuals in pursuit of their analysis is not usually written to tape. Most analyzers find it is sufficient to

interactively for code building or analysis, for example, is not efficient and not recommended, please see disk page for build and analysis areas. You cannot overwrite

This page is intended as a guide to the Fermilab Elastic Analysis Facility (EAF) for Mu2e collaborators. The official EAF documentation from SCD can be

Here is a summary of recommended use patterns Personal utility scripts, analysis scripts, histograms and documents should go on the home area. Builds of

123456_12345678.art ntd.mu2e.streamA.triggerTable123.0001.root A backup of an analysis project might look like: bck.batman.node123.2014-06-04.aa.tgz The Rucio

general purpose VO. VO's can also have roles. Most users will use the default Analysis role, but production uses the Production role. In order to use any Fermilab

on the build results. It explicitly is not for running production jobs, analysis, or anything at all that takes more than a few minutes. As soon as anyone

kx509 -n --minhours 168 -o /tmp/x509up_voms_mu2e_Analysis_${USER} upload_file /tmp/x509up_voms_mu2e_Analysis_${USER} A POMS campaign requires two files: a

temp this area is intended to be used to keep some data files around to do analysis, for example FileTransferService redmine web page

collection of code and scripts used for simulation, reconstruction and analysis of Mu2e data. Offline is kept in a git repository. It depends on external

caches. Examples of this sort of file are the Genie flux files or a large analysis fit template library. The lab has developed a stashCache feature for CVMFS

The Mu2e EventNtuple is a data format that analyzers can use for their analysis. The advantages of using these over the art files are that: file sizes

periods per year. (We also expect "run periods" defined by production and analysis operational needs, and may or may not be similar to the simulation periods)

run has excessive noise in the tracker, it might not be good for physics analysis, but would be fine for calorimeter cosmics calibration. This system has

order to do final analysis of the data we will produce datasets in a format that is more user friendly for fast turn around analysis. To date, this has

Mock data samples can be helpful in two ways: to help prepare physics analysis efforts; to help us understand the size of our data .art files and ntuples