Skip to content
Snippets Groups Projects
README.org 2.74 KiB
Newer Older
Christian Bourjau's avatar
Christian Bourjau committed
* Introduction
This repository contains the analysis on multiplicity estimators done in the HMTF for the ALICE experiment. The choice of the multiplicity estimator has significant impact on observables later retrieved based on multiplicity selections. In order to better to better understand these biases, various observables are extracted from MC truth data using various estimators.

* Estimators 

* Running the analysis 
The analysis is structured in two parts. The first one uses the AliRoot framework to loop over the given events and creates basic histograms. The second part of the analysis (post-analysis) is implemented in pyroot. It extracts the desired observables from the previously created histograms and creates the appropriate plots to display them.
** Dependencies
As mentioned, the first part of the analysis is implemented in the standard AliRoot framework and has no further dependencies. The post-analysis is implemented in pyroot (included in the standard ROOT distribution) but also uses rootpy ([[http://www.rootpy.org/][link]]) for convenience sake. This dependency can removed if necessary. For the time being, the following is a short instruction on how to set up rootpy:
Python development should best be done in virtual environments. Thus, virtualenv and virtualenvwrapper should be installed from the distributions repositories. Then, something like:
#+begin_src sh
  $ mkvirtualenv hmtf
  $ workon hmtf
  $ mkdir hmtf
  $ cd hmtf
  $ git clone https://github.com/rootpy/rootpy
  $ cd rootpy
  $ pip install ./
#+end_src
should set up rootpy.
** Really running the analysis
Christian Bourjau's avatar
Christian Bourjau committed
The entry point to running the analysis is always `run.sh', together with the platform it should b deployed at and the type of data it should use. Take a look at `run.sh` to see what is happening. For running the analysis locally, you need to first download the needed files, and then change the `run.sh` file to point to a `input_files.dat` file with the paths to the galice.root files. This sounds more complicated than it is. Again, see `run.sh`
Christian Bourjau's avatar
Christian Bourjau committed

Christian Bourjau's avatar
Christian Bourjau committed
Examples:
Christian Bourjau's avatar
Christian Bourjau committed
#+begin_src sh
Christian Bourjau's avatar
Christian Bourjau committed
  $ ./run.sh local pythia
  $ ./run.sh lite pythia
  $ ./run.sh pod pythia
#+end_src
Christian Bourjau's avatar
Christian Bourjau committed
So, deploying the analysis on vaf should be as easy as:
Christian Bourjau's avatar
Christian Bourjau committed

Christian Bourjau's avatar
Christian Bourjau committed
#+begin_src sh
    $ git clone https://github.com/cbourjau/hmtfmc
    $ cd hmtfmc
    $ sh run.sh pod pythia
#+end_src
Christian Bourjau's avatar
Christian Bourjau committed
(To be executed on vaf after requesting your workers and such)
Christian Bourjau's avatar
Christian Bourjau committed
However, for some reason the analysis does run very slow on vaf. I would appreciate feedback on why this might be the case very much!
Christian Bourjau's avatar
Christian Bourjau committed
** Running the post analysis
If rootpy is installed running the postanalysis should be as easy as:
#+begin_src sh
Christian Bourjau's avatar
Christian Bourjau committed
  $ python post.py hmtf_mc_mult_pythia.root
Christian Bourjau's avatar
Christian Bourjau committed
#+end_src
Christian Bourjau's avatar
Christian Bourjau committed

Christian Bourjau's avatar
Christian Bourjau committed
The results of the post analysis are saved in the same file but in the "folder" `results_post`