Skip to content

Commit c06cfdc

Browse files
authored
fix links in the QC analysis doc (#567)
1 parent e019b41 commit c06cfdc

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

doc/Advanced.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -354,7 +354,7 @@ In this piece of documentation it is assumed that the users already have some id
354354
### Getting AODs directly
355355
356356
First, let's see how to get data directly from an AOD file. To read the table, we will use TableConsumer from DPL, as in [the example of a QC analysis
357-
task](Modules/Example/src/AnalysisTask.cxx):
357+
task](../Modules/Example/src/AnalysisTask.cxx):
358358
```
359359
void AnalysisTask::monitorData(o2::framework::ProcessingContext& ctx)
360360
{
@@ -363,7 +363,7 @@ void AnalysisTask::monitorData(o2::framework::ProcessingContext& ctx)
363363
...
364364
}
365365
```
366-
In [our QC configuration file](Modules/Example/etc/analysisDirect.json) we will request AOD data as a direct source
366+
In [our QC configuration file](../Modules/Example/etc/analysisDirect.json) we will request AOD data as a direct source
367367
, just as normal Analysis Tasks do:
368368
```
369369
"tasks": {
@@ -397,7 +397,7 @@ which produces a new table with hash numbers generated out of tracks in AODs:
397397
DECLARE_SOA_TABLE(Hashes, "AOD", "HASH", hash::Bin);
398398
...
399399
```
400-
Thus, in [our QC config file](Modules/Example/etc/analysisDerived.json) we should query data described as `AOD/HASH/0`:
400+
Thus, in [our QC config file](../Modules/Example/etc/analysisDerived.json) we should query data described as `AOD/HASH/0`:
401401
```
402402
"tasks": {
403403
"AnalysisQcTask": {

0 commit comments

Comments
 (0)