Getting set up for high-level analysis

These are instructions for setting up to run a macro to do higher level analysis on processed data produced by DarkArt. You will do an 'anonymous checkout' of only the relevant pieces of code to run the macro. Many people will be doing many different analyses, and the macro provided here is just a basic starting point.

These steps need to be done only once.

  1. Be on a machine with ROOT and git installed. This could be your personal computer or a machine at your institution or one of the ds50 machines at FNAL ( or If you want to work on one of the ds50 machines at FNAL, it highly recommended that you work on, which has 32 cores and 70TB of space in /scratch. Note you do NOT need to be on a machine with the full art/darkart suite installed. If you need to install git, it is very easy to do; see, for example, On, you can get access to ROOT and git by
    source /ds50/app/ds50/setup_highlevel
  2. Create and/or navigate into a directory where you want to work. For example, I did:
    mkdir ds50analysis
    cd ds50analysis

    If you are working on a machine with the full DarkArt suite installed (e.g. on, blackhole, or andromeda), please make your directory OUTSIDE of your darkart working space, if you have one. That is, do NOT work in /ds50/app/${USER}/work/ for this high level analysis. This is to help prevent you from inadvertently changing things in the repository.
  3. Do:
    git clone
    cd darkart

    The clone step could take a while. What's actually happening is that you are downloading the entire DarkArt code repository. High level analysis is contained as a subdirectory in the full repository.

That's it for setup! You should now see two directories: analysis/ and darkart/. The first contains the analysis macros; the second contains, among other things, the class files that are necessary to read the processed ROOT file from DarkArt. You shouldn't need to modify anything in the darkart/ directory.

These steps put you in the 'master' branch of the darkart repository. This branch will be maintained with tagged versions only and should contain vetted analyses. The default analysis.C macro contains the standard analysis and builds histograms of things like F90, S1 and S2. It is almost certainly the case that you will need a tailored version of this macro for your analyses. It is highly recommended that you make changes in a separate version of the file from analysis.C so that if/when you use git to stay up to date with the repository, you don't hit code confilcts. You are also welcome to create your own local git branch to keep your code organized. See, for example, for instructions on using git.

To move to a newer version of the high-level analysis, you may checkout that version via its git tag. For example:

git checkout v1_00_00