24.1 Project Overview

Goals of the Final Project

The final project is your chance to put together everything you have learned into one coherent analysis. You will work through a full mini analysis, starting from raw data and ending with physics results and plots that you could, in principle, show in a presentation or report.

You will take a real or realistic dataset, convert or load it into ROOT, explore the variables, select interesting events, build histograms and graphs, fit relevant distributions, extract physical quantities with uncertainties, and present your results in clear and reproducible form.

The aim is not to produce a perfect professional analysis, but to practice the complete workflow so that, after this course, you know how to approach real problems with ROOT.

Structure of the Project

The project is divided into logical steps, each corresponding to a later section of this Final Project chapter:

1. Import the data into ROOT.
2. Explore the dataset to understand its variables and basic distributions.
3. Apply data selection to define signal and background regions.
4. Create histograms and other ROOT objects that summarize the data.
5. Fit the relevant distributions to extract model parameters.
6. Calculate physics or application specific quantities from fit results or event variables.
7. Estimate statistical uncertainties on the main results.
8. Produce publication quality figures that communicate the results clearly.
9. Save the analysis results for later reuse.
10. Write a short report that explains what you did and what you found.

Each of these steps will have its own section with practical guidance. You are encouraged to structure your code and directories so that each step is a separate macro or script, or at least a clearly separated function, which makes the workflow easier to understand and modify.

Example Datasets and Context

You can choose from several types of datasets, depending on your interests and what is provided with the course materials. Typical examples include:

A simple particle or nuclear physics dataset. For instance, events from a detector where each event contains measured energies, times, and possibly reconstructed momenta of particles. You might study an energy spectrum, a time distribution, or an invariant mass distribution to identify a peak corresponding to a known particle or transition.

A detector calibration or laboratory experiment dataset. For example, measurements from a scintillator, a Geiger counter, a semiconductor detector, or a spectroscopy setup. The analysis might focus on calibrating energy, resolving multiple peaks, or estimating detector resolution.

A general statistical dataset provided in text or CSV form. Even if the context is not strictly particle or nuclear physics, you can still use ROOT to perform histograms, fits, and uncertainty estimates exactly as you would in a physics analysis.

The project is designed so that the exact physics context is less important than practicing ROOT skills. However, you should still describe in your report what the quantities represent and what physical or experimental question you are answering.

Required ROOT Skills and Concepts

The project assumes that you have basic familiarity with the topics covered earlier in the course, especially:

Reading and writing ROOT files with TFile, and handling TTrees for event based data.
Creating and using histograms and graphs, including drawing and basic styling.
Performing fits with TF1 and understanding parameters and uncertainties.
Running ROOT macros and organizing analysis code into functions or separate files.

You do not need to use every advanced feature from the course, but you should demonstrate that you can combine several core elements in a consistent way.

Typical Workflow for the Project

You should think of the project as a small version of a real analysis workflow. A typical sequence looks like this:

First, you obtain the raw data. This might be a text or CSV file, or an existing ROOT file with a TTree. If needed, you convert the data into a ROOT file with a structured TTree so that later steps are efficient and clean.

Next, you open the dataset in ROOT, list its contents, and inspect the tree structure and branches. You make a first round of simple plots, often one dimensional histograms of key variables, to see basic shapes, ranges, and any obvious problems in the data.

Then you define selection criteria, usually simple cuts on variables, to isolate the region of interest. You check how many events pass the cuts and whether the resulting distributions look reasonable compared to the full dataset.

After the selections are fixed, you construct the main histograms or graphs that will be used in your final physics results. You choose binning, ranges, and labels carefully so that the distributions are informative and suitable for fitting.

You then perform fits to key distributions with appropriate functions. You check the goodness of fit and extract parameter values such as means, widths, or slopes. From these, you compute the physical quantities you care about, for example a particle mass, an energy calibration factor, or a decay constant.

Finally, you estimate statistical uncertainties, improve the visual appearance of the plots, save all relevant objects and outputs, and write a short report explaining what you did.

Throughout, you should keep your code organized so that you can easily re run the entire chain if the input data or your selection criteria change.

Assessment Criteria

The project will be evaluated on the clarity and completeness of your analysis workflow, not only on the final numerical values. The main aspects are:

Correct use of ROOT tools. Scripts or macros should run, use ROOT objects appropriately, and avoid common pitfalls such as lost object ownership or inconsistent histogram binning.

Logical and transparent workflow. Each step from data import to final results should be understandable, with clear rationale for choices like binning, cuts, and fit ranges.

Quality of plots and outputs. Figures should have readable axes labels, units where appropriate, sensible ranges, and minimal unnecessary clutter. They should be saved in a format suitable for inclusion in a report or presentation.

Documentation and reproducibility. Your analysis should be reproducible from the stored files and code, with comments and a written report that explain what each major piece does.

Physical interpretation. You should briefly interpret the main result in the context of the dataset. This includes explaining what a peak or parameter represents, and how the uncertainty affects your conclusion, even at a basic level.

Planning Your Own Analysis

Before you start coding, it is helpful to sketch your analysis plan. Identify the main question you want to answer with the dataset, such as determining a peak position, measuring a rate, or comparing two distributions. Then outline which variables in the dataset are relevant and what kind of histograms or fits will be needed.

You can then map each part of your plan to one section of the project:

Which files to import, and whether a ROOT conversion step is needed.
Which quick plots to make first to understand the data.
Which cuts to try and how to define signal and background.
Which final histograms and graphs will appear in your figures.
Which function models to use for fits.
Which numerical results you will quote and how to compute uncertainties.
Which plots and tables you will include in the report.

If you treat the project like a small real analysis, you will gain much more from the experience and be better prepared for future work with ROOT and experimental data.

How This Chapter Guides You

The remaining sections of the Final Project chapter follow the same order as the project workflow. Each section gives practical advice, typical ROOT commands, and example structures, but it does not prescribe a single exact solution. You will make choices that fit your particular dataset and analysis goal.

As you read and work through these sections, you can develop your own macros, modify them to match your data, and gradually build a complete and coherent ROOT analysis from input to final report.

Views: 16