diff --git a/01-introduction.html b/01-introduction.html index e2e9537..9ae2c2c 100644 --- a/01-introduction.html +++ b/01-introduction.html @@ -392,7 +392,7 @@
Find the NanoAOD variable listing for example for the SingleElectron collision dataset from 2016 RunG. Scroll down to “Dataset semantics” and open @@ -423,7 +423,7 @@
Use the search facets of the search page.
diff --git a/02-nanoaod-miniaod.html b/02-nanoaod-miniaod.html index 3a2329c..7c5e316 100644 --- a/02-nanoaod-miniaod.html +++ b/02-nanoaod-miniaod.html @@ -118,11 +118,11 @@ Exploring CMS nanoAODTO-DO we can “borrow” information from below:
+In the previous episode, we found the description of the NanoAOD +variables.
+Let us now compare it to the MiniAOD format. Note that the variable +descriptions are not available attached to the datasets, but we can have +a look at the MiniAOD +description in the CMS WorkBook.
+You will see a table starting with:
+The objects in the MiniAOD format are C++ classes in CMSSW, the CMS +Software package, and the table gives the class name. We can find the +exact class description in the CMSSW reference manual. See, for +example
+pat::Muon
pat::Electron
.These are C++ classes that can inherit information from +parent classes or contain objects, of some complex types. Therefore, +some of the variables are not explicitly listed as they are available +through other objects.
+For example, for MiniAOD, we will not find eta
or
+pt
explicitly in the class description as they can be
+obtained through the LorentzVector
object. This is
+transparent in the code when accessing those values, but much less so in
+the documentation!
Let us now compare it to NanoAOD. The major difference is that +MiniAOD contains most of the constituents of a physics object (such as +tracks and/or calorimeter clusters) whereas NanoAOD only contains some +information about them.
+Many CMS open data users have relied on the Particle +flow information, available in the MiniAOD format but not in the +NanoAOD format. See the class description: `pat::Packe.
+TO-DO find them and compare variable lists
+Demo only,
+show container
+show edmDumpEventContent
miniAOD links for use: Getting -started with miniAOD, miniAOD -in Workbook
-nanoAOD links for use: Getting -started with nanoAOD
+started with miniAOD.md
files for episodes when you want static
-content.Rmd
files for episodes when you need to generate
-outputsandpaper::check_lesson()
to identify any issues
-with your lessonsandpaper::build_lesson()
to preview your lesson
-locallySearch for the ZprimeToTT samples in the CERN Open Data Portal. The resulting query is here.
@@ -444,7 +444,7 @@Find the NanoAOD variable listing for example for the SingleElectron collision dataset from 2016 RunG. Scroll down to “Dataset semantics” and open @@ -460,7 +460,7 @@
Use the search facets of the search page.
@@ -510,10 +510,10 @@TO-DO we can “borrow” information from below:
+In the previous episode, we found the description of the NanoAOD +variables.
+Let us now compare it to the MiniAOD format. Note that the variable +descriptions are not available attached to the datasets, but we can have +a look at the MiniAOD +description in the CMS WorkBook.
+You will see a table starting with:
+The objects in the MiniAOD format are C++ classes in CMSSW, the CMS +Software package, and the table gives the class name. We can find the +exact class description in the CMSSW reference manual. See, for +example
+pat::Muon
pat::Electron
.These are C++ classes that can inherit information from +parent classes or contain objects, of some complex types. Therefore, +some of the variables are not explicitly listed as they are available +through other objects.
+For example, for MiniAOD, we will not find eta
or
+pt
explicitly in the class description as they can be
+obtained through the LorentzVector
object. This is
+transparent in the code when accessing those values, but much less so in
+the documentation!
Let us now compare it to NanoAOD. The major difference is that +MiniAOD contains most of the constituents of a physics object (such as +tracks and/or calorimeter clusters) whereas NanoAOD only contains some +information about them.
+Many CMS open data users have relied on the Particle +flow information, available in the MiniAOD format but not in the +NanoAOD format. See the class description: `pat::Packe.
+TO-DO find them and compare variable lists
+Demo only,
+show container
+show edmDumpEventContent
miniAOD links for use: Getting -started with miniAOD, miniAOD -in Workbook
-nanoAOD links for use: Getting -started with nanoAOD
+started with miniAOD -Content from NanoAOD datasets
+Content from NanoAOD datasets
Last updated on 2024-07-23 | @@ -731,7 +779,7 @@
Search for the ZprimeToTT samples in the CERN Open Data Portal. The resulting query is here.
@@ -809,7 +857,7 @@Find the NanoAOD variable listing for example for the SingleElectron collision dataset from 2016 RunG. Scroll down to “Dataset semantics” and open @@ -425,7 +425,7 @@
Use the search facets of the search page.
diff --git a/instructor/02-nanoaod-miniaod.html b/instructor/02-nanoaod-miniaod.html index b3c7f8e..ba0cde6 100644 --- a/instructor/02-nanoaod-miniaod.html +++ b/instructor/02-nanoaod-miniaod.html @@ -118,11 +118,11 @@ Exploring CMS nanoAODEstimated time: 10 minutes
+Estimated time: 15 minutes
TO-DO we can “borrow” information from below:
+In the previous episode, we found the description of the NanoAOD +variables.
+Let us now compare it to the MiniAOD format. Note that the variable +descriptions are not available attached to the datasets, but we can have +a look at the MiniAOD +description in the CMS WorkBook.
+You will see a table starting with:
+The objects in the MiniAOD format are C++ classes in CMSSW, the CMS +Software package, and the table gives the class name. We can find the +exact class description in the CMSSW reference manual. See, for +example
+pat::Muon
pat::Electron
.These are C++ classes that can inherit information from +parent classes or contain objects, of some complex types. Therefore, +some of the variables are not explicitly listed as they are available +through other objects.
+For example, for MiniAOD, we will not find eta
or
+pt
explicitly in the class description as they can be
+obtained through the LorentzVector
object. This is
+transparent in the code when accessing those values, but much less so in
+the documentation!
Let us now compare it to NanoAOD. The major difference is that +MiniAOD contains most of the constituents of a physics object (such as +tracks and/or calorimeter clusters) whereas NanoAOD only contains some +information about them.
+Many CMS open data users have relied on the Particle +flow information, available in the MiniAOD format but not in the +NanoAOD format. See the class description: `pat::Packe.
+TO-DO find them and compare variable lists
+Demo only,
+show container
+show edmDumpEventContent
miniAOD links for use: Getting -started with miniAOD, miniAOD -in Workbook
-nanoAOD links for use: Getting -started with nanoAOD
+started with miniAOD.md
files for episodes when you want static
-content.Rmd
files for episodes when you need to generate
-outputsandpaper::check_lesson()
to identify any issues
-with your lessonsandpaper::build_lesson()
to preview your lesson
-locallySearch for the ZprimeToTT samples in the CERN Open Data Portal. The resulting query is here.
@@ -446,7 +446,7 @@Find the NanoAOD variable listing for example for the SingleElectron collision dataset from 2016 RunG. Scroll down to “Dataset semantics” and open @@ -463,7 +463,7 @@
Use the search facets of the search page.
@@ -502,7 +502,7 @@Estimated time: 10 minutes
+Estimated time: 15 minutes
TO-DO we can “borrow” information from below:
+In the previous episode, we found the description of the NanoAOD +variables.
+Let us now compare it to the MiniAOD format. Note that the variable +descriptions are not available attached to the datasets, but we can have +a look at the MiniAOD +description in the CMS WorkBook.
+You will see a table starting with:
+The objects in the MiniAOD format are C++ classes in CMSSW, the CMS +Software package, and the table gives the class name. We can find the +exact class description in the CMSSW reference manual. See, for +example
+pat::Muon
pat::Electron
.These are C++ classes that can inherit information from +parent classes or contain objects, of some complex types. Therefore, +some of the variables are not explicitly listed as they are available +through other objects.
+For example, for MiniAOD, we will not find eta
or
+pt
explicitly in the class description as they can be
+obtained through the LorentzVector
object. This is
+transparent in the code when accessing those values, but much less so in
+the documentation!
Let us now compare it to NanoAOD. The major difference is that +MiniAOD contains most of the constituents of a physics object (such as +tracks and/or calorimeter clusters) whereas NanoAOD only contains some +information about them.
+Many CMS open data users have relied on the Particle +flow information, available in the MiniAOD format but not in the +NanoAOD format. See the class description: `pat::Packe.
+TO-DO find them and compare variable lists
+Demo only,
+show container
+show edmDumpEventContent
miniAOD links for use: Getting -started with miniAOD, miniAOD -in Workbook
-nanoAOD links for use: Getting -started with nanoAOD
+started with miniAOD -Content from NanoAOD datasets
+Content from NanoAOD datasets
Last updated on 2024-07-23 | @@ -750,7 +798,7 @@
Search for the ZprimeToTT samples in the CERN Open Data Portal. The resulting query is here.
@@ -828,7 +876,7 @@.md
files for episodes when you want static
-content.Rmd
files for episodes when you need to generate
-outputsandpaper::check_lesson()
to identify any issues
-with your lessonsandpaper::build_lesson()
to preview your lesson
-locally.md
files for episodes when you want static
-content.Rmd
files for episodes when you need to generate
-outputsandpaper::check_lesson()
to identify any issues
-with your lessonsandpaper::build_lesson()
to preview your lesson
-locally