cicada

Library for common processed-data file formats

Description

This repository contains the libraries describing the objects generated by the Katydid processing. These objects should be contained in ROOT files: as such they inherit from the TObject class (the "mother of all ROOT objects"). Their nature should be very close to TTree objects.

Documentation

Additional documentation can be found here.

Repository content

• documentation: contains the repository documentation that gets built on RTD.
• Library: contains the headers and ccp files of the repository.
• Scarab: Scarab submodule.

Operating System Support

• Mac OS X (usually tested on OS X 10.12 and 10.13)
• Linux (usually tested on Debian Jessie and Scientific Linux 6)

Requirements

External

• CMake (3.1 or better)
• ROOT (6.0 or better)

Python dependencies

• colorlog (3.1.2 or better)

Submodules (included with Cicada; must be fetched via Git)

• Scarab

Installation

The following steps will build Cicada from scratch. Starting with a terminal window . . .

1. Clone the repository and make a build directory as recommended above. You will also have to initialize the submodules.

$ git clone "https://github.com/project8/cicada"
$ cd cicada
$ git submodule update --init --recursive
$ mkdir build

2. To configure the installation you can use cmake, ccmake, or cmake-gui.

For a first configuration, using either ccmake or cmake-gui is highly recommended. The following instructions are for ccmake, but the steps with cmake-gui would be approximately the same.

$ cd build
$ ccmake ..

You will be prompted to press [c] to configure, and the window will fill up with several options.

You should set the CMake variable CMAKE_BUILD_TYPE to either RELEASE, STANDARD, or DEBUG (default), in order of how much text output you would like (from least to most) and how much compiler optimization should be performed (from most to least).

The install prefix is specified by the CMake variable CMAKE_INSTALL_PREFIX. The library, binaries, and header files will be installed in the lib, bin, and include subdirectories. The default install prefix is the build directory.

After you've finished, if you've changed anything press [c] again to configure. Then [g] to generate and exit.

3. Build and install.

$ make install

Or if you want to take advantage of parallel building to get things done faster:

$ make -j install

If the compiler runs into errors during the build, first check that you've updated the submodules and that you have all of the required dependencies installed (many are called "optional" on this page, but if you want to build without them you must also specify this in the cmake window). If you made a change to the dependencies or submodules, you may have to wipe the build directory and start again from step 1; simply writing make install again will not always work.

4. Developpers: Add the installation folder (where the bin and lib have been installed) path to your paths.

• export PATH=/path/to/install/folder/bin:$PATH
• export LD_LIBRARY_PATH=/path/to/install/folder/lib:$LD_LIBRARY_PATH

5. Python and ROOT interfaces: To set necessary paths correctly, source the this_cicada.sh script:

• source /path/to/install/folder/bin/this_cicada.sh

Docker

Docker can be used as a test-bed for bugs or users that don't want to mess with their computer environment. You can pull the latest version from DockerHub:

$ docker pull project8/cicada:latest

Then start a container:

$ docker start -it project8/cicada:latest bash

Finally before using python or Cicada or ROOT in this container, use the environment setup script and the this_cicada.sh script

root@sdfafd8shusd$ source $CICADA_BUILD_PREFIX/setup.sh
root@sdfafd8shusd$ source $CICADA_BUILD_PREFIX/bin/this_cicada.sh

You should now be able to use Cicada:

root@sdfafd8shusd$ python
> import CicadaPy
> CicadaPy.loadLibraries()

Usage

As a dependency

Cicada does not have a use case by itself: it can be a dependencies to be added to your c++ package or uses via its Python interface to extract/read the Katydid output objects from your ROOT file. You can find a example on how to use it in the mermithid Python package (TODO_DOC).

Via its example

An example about how to read Katydid output file can be found under Library/python/ReadKTOutputFile.py. You can it there or it should exist in your installation folder if you have used make install.

You can use the python script with something like python ReadKTOutputFile -i namefile.root -b theBranchYouWant [-k]. The -k defines if the Katydid namespace should be used instead of the Cicada one (a.k.a. if this root file was generated by a version of Katydid earlier than 2.10). You can also import this module via python and use it:

python
from ReadKTOutputFile import ReadKTOutputFile
a = ReadKTOutputFile('namefile.root','theBranchYouWant')
print(a)

Then the namespace to use can be selected with a third argument given to ReadKTOutputFile (True: Katydid; False: Cicada).

The list of branches can be found using the Cicada documentation.