Search results

Jump to navigation Jump to search
  • 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
    28 KB (4,772 words) - 14:30, 20 November 2024
  • 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
    9 KB (647 words) - 03:43, 9 March 2025
  • computing resources Docker software containers for submitting to special farms analysis workflow - how to read existing datasets production simulation workflow
    3 KB (300 words) - 19:28, 20 November 2024
  • 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
    26 KB (3,975 words) - 16:57, 9 November 2024
  • Here is a summary of recommended use patterns Personal utility scripts, analysis scripts, histograms and documents should go on the home area. Builds of
    20 KB (2,905 words) - 16:56, 27 February 2025
  • 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
    25 KB (3,882 words) - 23:47, 4 November 2024
  • 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
    32 KB (4,953 words) - 00:57, 31 January 2025
  • 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
    20 KB (3,038 words) - 21:29, 4 December 2024
  • temp this area is intended to be used to keep some data files around to do analysis, for example FileTransferService redmine web page
    2 KB (385 words) - 21:47, 3 March 2025
  • 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
    15 KB (1,978 words) - 21:40, 10 February 2025
  • 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
    3 KB (440 words) - 14:26, 24 June 2019
  • 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
    25 KB (4,119 words) - 17:25, 23 January 2025
  • 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
    46 KB (7,810 words) - 18:34, 23 October 2024
  • for diagnostic histograms and TTrees, and analysis output like TrkAna that can be used in a normal root analysis. The .art files contain the actual c++ objects
    32 KB (5,201 words) - 18:06, 20 July 2024
  • protected) Physics studies Infrastructure work Other links: 2023 HSF/IRIS-HEP Analysis Preservation training SCD journal club FCRSG (former SCPMT) 2020 Mu2e 2021
    4 KB (174 words) - 16:13, 8 December 2024
  • as your VO (Virtual Organization, i.e. your experiment) and your role ("Analysis" or "Production"). In our current procedures, you should never need to
    36 KB (5,675 words) - 20:42, 4 October 2024
  • 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
    2 KB (59 words) - 13:47, 19 February 2025
  • hit making - you will not get TDR era hits. You can also do some limited analysis with the calorimeter information from TDR era files; when you make hits
    27 KB (3,708 words) - 07:50, 14 February 2025
  • Lunch 13:30 - 14:30 Using STNtuple for analysis Giani Pezzullo, Pasha Murat 14:30 - 15:30 Using TrkAna for analysis Andy Edmonds, Dave Brown 15:30 - 16:00
    12 KB (1,604 words) - 15:57, 25 June 2019
  • 0 bytes (0 words) - 16:13, 2 May 2024
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)