forked from reanahub/reana-demo-root6-roofit
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor(docs): move from reST to Markdown (reanahub#68)
Convert docs from reStructuredText to Markdown so that the changelog file is compatible with Release Please.
- Loading branch information
Showing
4 changed files
with
227 additions
and
252 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
# Authors | ||
|
||
The list of contributors in alphabetical order: | ||
|
||
- [Ana Trisovic](https://orcid.org/0000-0003-1991-0533) | ||
- [Anton Khodak](https://orcid.org/0000-0003-3263-4553) | ||
- [Audrius Mecionis](https://orcid.org/0000-0002-3759-1663) | ||
- [Daniel Prelipcean](https://orcid.org/0000-0002-4855-194X) | ||
- [Diego Rodriguez](https://orcid.org/0000-0003-0649-2002) | ||
- [Dinos Kousidis](https://orcid.org/0000-0002-4914-4289) | ||
- [Giuseppe Steduto](https://orcid.org/0009-0002-1258-8553) | ||
- [Jan Okraska](https://orcid.org/0000-0002-1416-3244) | ||
- [Lukas Heinrich](https://orcid.org/0000-0002-4048-7584) | ||
- [Marco Donadoni](https://orcid.org/0000-0003-2922-5505) | ||
- [Marco Vidal](https://orcid.org/0000-0002-9363-4971) | ||
- [Maria Fernando](https://github.com/MMFernando) | ||
- [Rokas Maciulaitis](https://orcid.org/0000-0003-1064-6967) | ||
- [Tibor Simko](https://orcid.org/0000-0001-7202-5803) | ||
- [Vladyslav Moisieienkov](https://orcid.org/0000-0001-9717-0775) |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,208 @@ | ||
# REANA example - ROOT6 and RooFit | ||
|
||
[![image](https://github.com/reanahub/reana-demo-root6-roofit/workflows/CI/badge.svg)](https://github.com/reanahub/reana-demo-root6-roofit/actions) | ||
[![image](https://img.shields.io/badge/discourse-forum-blue.svg)](https://forum.reana.io) | ||
[![image](https://img.shields.io/github/license/reanahub/reana-demo-root6-roofit.svg)](https://github.com/reanahub/reana-demo-root6-roofit/blob/master/LICENSE) | ||
[![image](https://www.reana.io/static/img/badges/launch-on-reana-at-cern.svg)](https://reana.cern.ch/launch?url=https%3A%2F%2Fgithub.com%2Freanahub%2Freana-demo-root6-roofit&specification=reana.yaml&name=reana-demo-root6-roofit) | ||
|
||
## About | ||
|
||
This [REANA](http://www.reana.io/) reproducible analysis example emulates a typical | ||
particle physics analysis where the signal and background data is processed and fitted | ||
against a model. The example will use the [RooFit](https://root.cern.ch/roofit) package | ||
of the [ROOT](https://root.cern.ch/) framework. | ||
|
||
## Analysis structure | ||
|
||
Making a research data analysis reproducible basically means to provide "runnable | ||
recipes" addressing (1) where is the input data, (2) what software was used to analyse | ||
the data, (3) which computing environments were used to run the software and (4) which | ||
computational workflow steps were taken to run the analysis. This will permit to | ||
instantiate the analysis on the computational cloud and run the analysis to obtain (5) | ||
output results. | ||
|
||
### 1. Input data | ||
|
||
In this example, the signal and background data will be generated; see below. Therefore | ||
there is no explicit input file to be taken care of. | ||
|
||
### 2. Analysis code | ||
|
||
The analysis will consist of two stages. In the first stage, signal and background are | ||
generated. In the second stage, a fit will be made for the signal and background. | ||
|
||
For the first generation stage, [gendata.C](code/gendata.C) is a ROOT macro that | ||
generates signal and background data. | ||
|
||
For the second fitting stage, [fitdata.C](code/fitdata.C) is a ROOT macro that makes a | ||
fit for the signal and the background data. | ||
|
||
The code was taken from the RooFit tutorial | ||
[rf502_wspacewrite.C](https://root.cern/doc/master/rf502__wspacewrite_8C.html) and was | ||
slightly modified. | ||
|
||
### 3. Compute environment | ||
|
||
In order to be able to rerun the analysis even several years in the future, we need to | ||
"encapsulate the current compute environment", for example to freeze the ROOT version our | ||
analysis is using. We shall achieve this by preparing a [Docker](https://www.docker.com/) | ||
container image for our analysis steps. | ||
|
||
This analysis example is runs within the [ROOT6](https://root.cern.ch/) analysis | ||
framework. The computing environment can be therefore easily encapsulated by using the | ||
upstream [reana-env-root6](https://github.com/reanahub/reana-env-root6) base image. (See | ||
there how it was created.) | ||
|
||
We shall use the ROOT version 6.18.04. Note that we can actually use this container image | ||
"as is", because our two macros `gendata.C` and `fitdata.C` can be "uploaded" and | ||
"mounted" into the running container at runtime. There is no need to compile any of the | ||
analysis source code beforehand. We can therefore use the ROOT 6.18.04 base image | ||
directly, without building a new container image specially dedicated to our analysis. The | ||
ROOT 6.18.04 base image fully specifies the complete analysis environment that we need | ||
for our analysis. | ||
|
||
### 4. Analysis workflow | ||
|
||
The analysis workflow is simple and consists of two above-mentioned stages: | ||
|
||
```console | ||
START | ||
| | ||
| | ||
V | ||
+-------------------------+ | ||
| (1) generate data | | ||
| | | ||
| $ root gendata.C ... | | ||
+-------------------------+ | ||
| | ||
| data.root | ||
V | ||
+-------------------------+ | ||
| (2) fit data | | ||
| | | ||
| $ root fitdata.C ... | | ||
+-------------------------+ | ||
| | ||
| plot.png | ||
V | ||
STOP | ||
``` | ||
|
||
For example: | ||
|
||
```console | ||
$ root -b -q 'gendata.C(20000,"data.root")' | ||
$ root -b -q 'fitdata.C("data.root","plot.png")' | ||
$ ls -l plot.png | ||
``` | ||
|
||
Note that you can also use [CWL](http://www.commonwl.org/v1.0/), | ||
[Yadage](https://github.com/diana-hep/yadage) or [Snakemake](https://snakemake.github.io) | ||
workflow specifications: | ||
|
||
- [workflow definition using CWL](workflow/cwl/workflow.cwl) | ||
- [workflow definition using Yadage](workflow/yadage/workflow.yaml) | ||
- [workflow definition using Snakemake](workflow/snakemake/Snakefile) | ||
|
||
### 5. Output results | ||
|
||
The example produces a plot where the signal and background data is fitted against the | ||
model: | ||
|
||
![](https://raw.githubusercontent.com/reanahub/reana-demo-root6-roofit/master/docs/plot.png) | ||
|
||
## Running the example on REANA cloud | ||
|
||
There are two ways to execute this analysis example on REANA. | ||
|
||
If you would like to simply launch this analysis example on the REANA instance at CERN | ||
and inspect its results using the web interface, please click on one of the following | ||
badges, depending on which workflow system (CWL, Serial, Snakemake, Yadage) you would | ||
like to use: | ||
|
||
<a href="https://reana.cern.ch/launch?url=https%3A%2F%2Fgithub.com%2Freanahub%2Freana-demo-root6-roofit&specification=reana-cwl.yaml&name=reana-demo-root6-roofit-cwl"> | ||
<img src="https://www.reana.io/static/img/badges/launch-with-cwl-on-reana-at-cern.svg" alt="Launch with CWL on REANA@CERN badge" /> | ||
</a> | ||
<br /> | ||
<a href="https://reana.cern.ch/launch?url=https%3A%2F%2Fgithub.com%2Freanahub%2Freana-demo-root6-roofit&specification=reana.yaml&name=reana-demo-root6-roofit-serial"> | ||
<img src="https://www.reana.io/static/img/badges/launch-with-serial-on-reana-at-cern.svg" alt="Launch with Serial on REANA@CERN badge" /> | ||
</a> | ||
<br /> | ||
<a href="https://reana.cern.ch/launch?url=https%3A%2F%2Fgithub.com%2Freanahub%2Freana-demo-root6-roofit&specification=reana-snakemake.yaml&name=reana-demo-root6-roofit-snakemake"> | ||
<img src="https://www.reana.io/static/img/badges/launch-with-snakemake-on-reana-at-cern.svg" alt="Launch with Snakemake on REANA@CERN badge"/> | ||
</a> | ||
<br /> | ||
<a href="https://reana.cern.ch/launch?url=https%3A%2F%2Fgithub.com%2Freanahub%2Freana-demo-root6-roofit&specification=reana-yadage.yaml&name=reana-demo-root6-roofit-yadage"> | ||
<img src="https://www.reana.io/static/img/badges/launch-with-yadage-on-reana-at-cern.svg" alt="Launch with Yadage on REANA@CERN badge"/> | ||
</a> | ||
|
||
If you would like a step-by-step guide on how to use the REANA command-line client to | ||
launch this analysis example, please read on. | ||
|
||
We start by creating a [reana.yaml](reana.yaml) file describing the above analysis | ||
structure with its inputs, code, runtime environment, computational workflow steps and | ||
expected outputs: | ||
|
||
```yaml | ||
version: 0.6.0 | ||
inputs: | ||
files: | ||
- code/gendata.C | ||
- code/fitdata.C | ||
parameters: | ||
events: 20000 | ||
data: results/data.root | ||
plot: results/plot.png | ||
workflow: | ||
type: serial | ||
specification: | ||
steps: | ||
- name: gendata | ||
environment: 'docker.io/reanahub/reana-env-root6:6.18.04' | ||
commands: | ||
- mkdir -p results && root -b -q 'code/gendata.C(${events},"${data}")' | ||
- name: fitdata | ||
environment: 'docker.io/reanahub/reana-env-root6:6.18.04' | ||
commands: | ||
- root -b -q 'code/fitdata.C("${data}","${plot}")' | ||
outputs: | ||
files: | ||
- results/plot.png | ||
``` | ||
In this example we are using a simple Serial workflow engine to represent our sequential | ||
computational workflow steps. Note that we can also use the CWL workflow specification | ||
(see [reana-cwl.yaml](reana-cwl.yaml)), the Yadage workflow specification (see | ||
[reana-yadage.yaml](reana-yadage.yaml)) or the Snakemake workflow specification (see | ||
[reana-snakemake.yaml](reana-snakemake.yaml)). | ||
We can now install the REANA command-line client, run the analysis and download the | ||
resulting plots: | ||
```console | ||
$ # create new virtual environment | ||
$ virtualenv ~/.virtualenvs/reana | ||
$ source ~/.virtualenvs/reana/bin/activate | ||
$ # install REANA client | ||
$ pip install reana-client | ||
$ # connect to some REANA cloud instance | ||
$ export REANA_SERVER_URL=https://reana.cern.ch/ | ||
$ export REANA_ACCESS_TOKEN=XXXXXXX | ||
$ # create new workflow | ||
$ reana-client create -n myanalysis | ||
$ export REANA_WORKON=myanalysis | ||
$ # upload input code, data and workflow to the workspace | ||
$ reana-client upload | ||
$ # start computational workflow | ||
$ reana-client start | ||
$ # ... should be finished in about a minute | ||
$ reana-client status | ||
$ # list workspace files | ||
$ reana-client ls | ||
$ # download output results | ||
$ reana-client download | ||
``` | ||
|
||
Please see the [REANA-Client](https://reana-client.readthedocs.io/) documentation for | ||
more detailed explanation of typical `reana-client` usage scenarios. |
Oops, something went wrong.