Documentation of SBS-offline¶

• Table of contents
• Documentation of SBS-offline
  • Overview
  • Purpose
  • Getting the code and building the program
    • Prerequisites
    • Instructions for analyzer cmake installation compatible
    • Downloading the repository
    • Building and installing the library
  • How to use SBS-offline

Overview¶

This page is maintained by the UConn group (Eric Fuchey + Andrew Puckett) and as of February 14, 2020 is specific to the '''''master''''' branch of SBS-offline on github.

Purpose¶

This page documents the SBS-offline program code, which purpose is to perform the data analysis for the upcoming SBS experiments.

Getting the code and building the program¶

Prerequisites¶

*Working [https://root.cern.ch/drupal/ ROOT] installation. '''libsbsdig is compatible with ROOT version 5 and ROOT version 6'''. '''''ROOT 6 is strongly recommended'''
*Working installation of cmake '''version 3.9 minimum'''
*Working analyzer '''built with cmake'''. for that purpose, refer to the instruction below.

Instructions for analyzer cmake installation compatible¶

clone the analyzer repository from: * git clone git@github.com:JeffersonLab/analyzer.git
build it with cmake following the instructions at: * https://github.com/JeffersonLab/analyzer#compiling-with-cmake
2 precisions:
*it seems that in these instructions the "build" directory ''has to be'' in the analyzer directory.
*for your environment settings, in addition to the two lines mentionned in the instructions, you still want to define ANALYZER as the path to your install directory e.g. * setenv ANALYZER $HOME/local/analyzer

Downloading the repository¶

The code is hosted on a github repository owned by JLab. To clone via ssh (preferred method on JLab batch farm), do:

git clone git@github.com:JeffersonLab/SBS-offline.git

For this method to work, the ssh public key on the machine where you want to get the code must be added to your github account (see [https://help.github.com/articles/generating-ssh-keys/ Guide] to generating ssh keys and adding to your github.com account.)

Cloning the repository defaults to the "master" branch.

Building and installing the library¶

Create a "build" directory that is parallel to the "SBS-offline" source directory (this is not strictly required, but the build directory must be separate from the "SBS-offline" directory in any case).
You also need to have setup an installation path e.g. /path/to/sbs-offline-install
NB: similarly to the build directory, the /path/to/gsbs-offline-install directory shall '''not''' be the same as the source directory!
The following instructions assume that "build" is parallel to "SBS-offline":
If successful, the libsbs library and several other files and folders will be created in the "build" and the "install" directory.

To build and install, the procedure needs to be completed. From scratch:

mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/path/to/sbs-offline-install ../SBS-offline
make install

Then, the following line should be added in the OS login configuration file to take advantage of this functionality:

• source /path/to/sbs-offline-install/bin/sbsenv.sh (or source /path/to/g4sbs_install/bin/sbsenv.csh on the batch farm)

How to use SBS-offline¶

A working example script using the SBS-offline library is available in the SBS-offline repository at the following path: * replay/replay_gmn.C
It is recommended prior to use it to source a short environment file to setup the database path correctly (and optionally the directory where to retrieve the data): * replay/setup_db.csh
It is preferable to not use them in this directory but copy them in another directory outside of your copy of the SBS-offline repository.

The script (and any other script using the SBS-offline library) uses the Hall A analyzer (Podd).
To execute this script:

> analyzer
analyzer [0] .L replay_gmn.C+
analyzer [1] replay_gmn_test("your_input_file_base", -1)

The first argument "your_input_file_base" is the base name of the input file minus the ".root" file suffix (i.e. the full file name would be "your_input_file_base.root").
The second argument is the number of arguments to process (-1 for all).
This will produce a file called "replayed_your_input_file_base.root" containing the information extracted from the analysis of the input file.