You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Tutorials/PWGHF/README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Welcome to the heavy-flavour analysis tutorial!
6
6
7
7
This directory contains the code and configuration for running a minimalistic version of the D<sup>0</sup> analysis on Run 3 data.
8
8
9
-
See the [official PWG-HF O<sup>2</sup> documentation](https://aliceo2group.github.io/analysis-framework/docs/advanced-specifics/pwghf.html) for the overview of the full heavy-flavour analysis framework.
9
+
See the [PWG-HF O<sup>2</sup> documentation](https://aliceo2group.github.io/analysis-framework/docs/advanced-specifics/pwghf.html) for the overview of the full heavy-flavour analysis framework.
10
10
11
11
## Setup
12
12
@@ -30,10 +30,10 @@ This table contains paired track indices which point to tracks in the track tabl
30
30
These derived skims are produced by executing the [`run_skim.sh`](run_skim.sh) bash script in the working directory:
It will use the configuration from [`dpl-config_skim.json`](dpl-config_skim.json) and produce the `AnalysisResults_trees.root` file with the derived table and the `AnalysisResults.root` file with control histograms in the working directory.
36
+
It processes files specified in `./input_skim.txt`, uses the configuration from [`dpl-config_skim.json`](dpl-config_skim.json), and produces the `./AnalysisResults_trees.root` file with the derived table and the `./AnalysisResults.root` file with control histograms.
37
37
38
38
## Mini task
39
39
@@ -52,19 +52,21 @@ The absolute path to the parent file is stored in the derived file but it can be
52
52
Run the mini task by executing the [`run_task.sh`](run_task.sh) bash script in the working directory:
It will use the configuration from [`dpl-config_task.json`](dpl-config_task.json) and produce the output file `AnalysisResults.root` with histograms in the working directory.
58
+
It processes files specified in `./input_task.txt`, uses the configuration from [`dpl-config_task.json`](dpl-config_task.json), and produces the `./AnalysisResults.root`file with histograms.
59
59
60
60
## Exercise tips
61
61
62
62
Organise your working environment so that you can easily switch between running the code in the working directory and modifying the code in the O2Physics repository.
63
63
64
-
When you execute the bash script, the terminal output is saved in the `stdout.log` log file in the working directory.
64
+
When you execute the bash script, the terminal output is saved in the `./stdout.log` log file.
65
65
If an error occurs, the script will report the non-zero exit code and ask you to check the log file to find the problem.
66
+
If you get errors that have to be tolerated, you need to remove the `--min-failure-level error` option from the command.
66
67
67
-
The full O<sup>2</sup> configuration is dumped at the end of processing into the `dpl-config.json` file in the working directory.
68
+
The full O<sup>2</sup> configuration is dumped at the end of processing into the `./dpl-config.json` file.
69
+
It is useful to compare it with the input configuration file to spot mismatches.
68
70
69
71
See the [rebuilding instructions](https://aliceo2group.github.io/analysis-framework/docs/gettingstarted/installing.html#building-partially-for-development-using-ninja) in the analysis framework documentation for advice on compiling your code changes.
0 commit comments