Changes between Version 42 and Version 43 of HowToAddSample

Timestamp:

Jan 6, 2017, 2:30:21 PM (8 years ago)

Author:

Clarence Wret

Comment:

--

HowToAddSample

@@ -3 +3 @@
 = How to add a sample in NUISANCE =
 
-This is an informal step-by-step guide on how to add samples into the NUISANCE framework. Most of this can be derived by looking at the already implemented measurements, and I'd advise potential readers to have a look around in the `src` directory in addition to reading this guide.
+This is an informal step-by-step guide on how to add samples into the NUISANCE framework. Most of this can be derived by looking at the recently [https://nuisance.hepforge.org/trac/browser/src?order=date&desc=1 implemented measurements] for up-to-date references.
 
 For this tutorial I'll be adding the T2K CC1pi+ H,,2,,O data. The data comes from the [http://t2k-experiment.org/results/nd280data-numu-cc1pi-xs-on-h2o-2015/ T2K site] and [https://arxiv.org/abs/1605.07964 arxiv]. The data is supplied both in a ROOT file and a number of .csv files: I'll be using the ROOT file here.
@@ -111 +111 @@
 Now that we have the rough structure set-up, we can finally start writing some code.
 
-
+[=#point_header]
 == Writing the header ==
 
@@ -152 +152 @@
 
 [=#point_const]
-== Making the constructor ==
+== Writing the constructor ==
 
 NUISANCE loads samples through `FCN/SampleList.cxx` in the function `SampleUtils::LoadSample`, which makes a `std::list` of `MeasurementBase` pointers which it later loops over from the executables.
@@ -249 +249 @@
 == Specifying the event-level dependent variable(s) ==
 
+We are now at the point where we can write the `FillEventVariables(FitEvent *event)` implementation mentioned [=#point_header above]. This function defines the dependent variable(s) and how to get them from each `FitEvent` object that gets passed.
+
+This is where the p,,mu,, and E^rec^,,nu,, implementations differ.
+
+The `FitEvent` class provides numerous getter functions to make `FillEventVariables` as simple as possible.
+
+=== For the p,,mu,, ===
+
+To get the muon momentum, we first need a muon in the event. The function `FitEvent::NumFSParticle(int pdg)` counts the number of final-state particles with pdg-code `pdg` and returns that number. So our first check is 
+
+{{{
+  // Need to make sure there's a muon
+  if (event->NumFSParticle(13) == 0) return;
+}}}
+
+To then get the muon kinematics in the `FitEvent` we use `FitEvent::GetHMFSParticle(int pdg)` to get the '''H'''ighest'''M'''omentum'''F'''inal'''S'''tate'''Particle''', which return a `FitParticle` object. The implementation for the `FitParticle` is in `FitBase/FitParticle.cxx`. We can now access the ROOT object `TLorentzVector` which stores the kinematics for the muon. So to get the muon we do:
+
+{{{
+  // Get the muon
+  TLorentzVector Pmu  = event->GetHMFSParticle(13)->fP;
+}}}
+=== For the E^rec^,,nu,, ===
+
+
+
 [=#point_signaldef]
 == Specifying a signal definition ==
@@ -333 +358 @@
 }}}
 
-=== Make NUISANCE aware of the sample ===
+= Make NUISANCE aware of the sample =
 FCN/SampleList
 
-=== Add the sample to the makefile ===
+= Add the sample to the makefile =
 CMake
+
+= Possible extensions =
+2D is similar