Draft: Resolve "Revise part5 with new data model (eic:: to eicd:: etc)"
Compare changes
- Wouter Deconinck authored
+ 70
− 102
@@ -37,17 +37,21 @@ For the purpose of this tutorial we will use the S3 interface since it does not
@@ -37,17 +37,21 @@ For the purpose of this tutorial we will use the S3 interface since it does not
Each reconstruction output file has essentially the same structure, defined by the EIC Data Model. This structure can be retrieved with `rootls`, e.g.
root -l s3https://dtn01.sdcc.bnl.gov:9000/eictest/ATHENA/RECO/master/SINGLE/pi+/1GeV/45to135deg/pi+_1GeV_45to135deg.0001.root
You may encounter some (or many) warnings when you run this on a regular ROOT installation, but the ROOT files are built in such a way that they only use basic ("plain old data") types that ROOT can interpret without any helper classes. There are helper classes available inside the ATHENA container.
You may encounter some (or many) warnings when you run this on a regular ROOT installation, but the ROOT files are built in such a way that they only use basic ("plain old data") types that ROOT can interpret without any helper classes. There are helper classes available inside the `eic-shell` container.
The `events` tree is of course what we are interested in. We can explore its top-level structure as follows. We first start a ROOT session:
root -l s3https://dtn01.sdcc.bnl.gov:9000/eictest/ATHENA/RECO/master/SINGLE/pi+/1GeV/45to135deg/pi+_1GeV_45to135deg.0001.root
@@ -59,83 +63,33 @@ This will display a large number of branches (and their size):
@@ -59,83 +63,33 @@ This will display a large number of branches (and their size):
During the development of the reconstruction, there are more branches enabled here than are strictly necessary (e.g. simulated and digitized hits, intermediate reconstruction parameters). These are all available for analysis (with fixed interfaces). In this tutorial we will focus on a few branches in particular:
During the development of the reconstruction, there are often more branches enabled here than are strictly necessary (e.g. simulated and digitized hits, intermediate reconstruction parameters). These are all available for analysis (with fixed interfaces). In this tutorial we will focus on a few branches in particular:
@@ -145,38 +99,50 @@ We can inspect each of these three branches in more detail (some information rem
@@ -145,38 +99,50 @@ We can inspect each of these three branches in more detail (some information rem
@@ -209,13 +175,15 @@ root [6] events->Print("EcalBarrelScFiClusters*")
@@ -209,13 +175,15 @@ root [6] events->Print("EcalBarrelScFiClusters*")
@@ -244,7 +212,7 @@ These types of plots will likely be limited to simple data inspection.
@@ -244,7 +212,7 @@ These types of plots will likely be limited to simple data inspection.
For a more advanced analysis, you can take advantage of the RDataFrame features, such as in this (shortened) DIS example. The [original](https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/blob/master/benchmarks/dis/analysis/dis_electrons.cxx) is used in our CI system and determines DIS parameters for every change to the detector geometry, simulation, digitization, or reconstruction.
For a more advanced analysis, you can take advantage of the RDataFrame features, such as in this (shortened) DIS example. The [original](https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/blob/master/benchmarks/dis/analysis/dis_electrons.cxx) is used in our CI system and determines DIS parameters for every change to the detector geometry, simulation, digitization, or reconstruction.