-
Notifications
You must be signed in to change notification settings - Fork 0
Muon Analysis
The DQ Framework provides a useful family of tools for acquiring derived data. These are all called table-makers, which are extremely configurable and are meant to allow you to skim the large datasets down to only the useful components for your analysis - which are referred to as reduced tables. When doing a muon analysis in Run 3, using the table-maker tools has become essential!
This does not mean that it is simple to use, unfortunately...
Here are some links to documentation to get started:
- Documentation for forward track analysis
- Latest O2 analysis tutorial
- PWG-DQ documentation, for up to date information.
- For fancy configuration see here.
- O2Physics code for PWG-DQ, for code-specific details.
The typical things that are configured in the table-maker:
- Event and Moun Cuts (NB).
- Derived tables to be outputted.
- QC Histograms
- MC Signal definitions (only for MC datasets).
This is not at all an extensive list. The configuration will highly depend on the analysis and is non-trivial.
The DQ Framework does also provide table-reader tasks to run on the derived data outputted by the table-maker. These also need to be configured properly depending on the requirement of the analysis - refer to the above links for further details.
When you want more freedom to develop your own analysis workflow, you can manually write your own O2Physics analysis task to process the derived data from the table-maker. For this, you can find a bare-bones template analysis task here: O2 Muon Task Template. When developing your own task, it is highly recommended to refer to the O2Physics code for PWG-DQ for implementation specifics.
-
Table-maker and table-reader: Can be configured and run either locally or on Hyperloop. Note: Since the table-maker is so widely used for analysis, there are official productions where it is already run on large datasets - use this to your advantage!
-
Custom O2Physics analysis task: When developing your own task, this will need to be done locally only. Once the task has been tested, presented on, and accepted by the experiment to be added to the O2Physics repository; then it will only be accessible to run on Hyperloop.