Changes between Version 13 and Version 14 of HowToAddSample

Timestamp:

Jan 5, 2017, 3:29:27 PM (8 years ago)

Author:

Clarence Wret

Comment:

--

HowToAddSample

@@ -29 +29 @@
 === Choosing a distribution ===
 
-The T2K CC1pi+ H2O data release contains various distributions in FIG 4. In this tutorial I'll look at adding one kinematic distribution and one derived distribution: p,,mu,, and E^rec^,,nu,, respectively.
+The T2K CC1pi+ H,,2,,O data release contains various distributions in FIG 4. In this tutorial I'll look at adding one kinematic distribution and one derived distribution: p,,mu,, and E^rec^,,nu,, shown below.
 
-[[Image(T2K_CC1pip_H2O_enurec.png​, 300px)]][[Image(T2K_CC1pip_H2O_enurec.png​, 300px)]]
+[[Image(T2K_CC1pip_H2O_pmu.png​, 300px)]][[Image(T2K_CC1pip_H2O_enurec.png​, 300px)]]
 
 In NUISANCE we try to add all available distributions from a publication. '''However''', some distributions will have detector effects "folded" into them (i.e. they will be raw detector-level data). We can only use these if there is some method which bring detector-level variables (e.g. p_mu seen in the detector) to truth-level variable (e.g. p_mu seen after correcting for the detector effects).
+
 
 == Implementing a sample ==
@@ -39 +40 @@
 NUISANCE is designed to easily allow adding new samples.
 
-Each experimental measurement (e.g. MiniBooNE CC1pi0 cos(theta(pi0, neutrino))) is its own class. To simplify including new samples we supply a base class for 1D (`Measurement1D`) and 2D (`Measurement2D`) measurements, which in turn inherits from the virtual base class (`MeasurementBase`). These `MeasurementBase` classes are then looped over in the executables and data/MC comparisons are the result.
+Each experimental measurement is its own class. To simplify including new samples we supply a base class for 1D (`Measurement1D`) and 2D (`Measurement2D`) measurements, which in turn inherits from the virtual base class (`MeasurementBase`). 
+
+These `MeasurementBase` classes are then looped over in the executables and data/MC comparisons are the result.
 
 The inheritance tree is simple and goes `Specific_Measurement -> MeasurementXD -> MeasurementBase`
 
+
 === Setting up the inheritance ===
+
 In the case of our T2K CC1pi+ H,,2,,O data, we're dealing with 1D distributions. They should therefore inherit from the `Measurement1D` class.
 
+{{{
+#ifndef T2K_CC1PIP_H2O_XSEC_1DPMU_NU_H_SEEN 
+#define T2K_CC1PIP_H2O_XSEC_1DPMU_NU_H_SEEN
+
+#include "Measurement1D.h"
+#include "T2K_SignalDef.h"
+
+class T2K_CC1pip_H2O_XSec_1Dpmu_nu : public Measurement1D {
+public:
+  T2K_CC1pip_H2O_XSec_1Dpmu_nu(std::string inputfile, FitWeight *rw, std::string  type, std::string fakeDataFile);
+  virtual ~T2K_CC1pip_H2O_XSec_1Dpmu_nu() {};
+  
+  void FillEventVariables(FitEvent *event);
+  bool isSignal(FitEvent *event);
+  
+  private:
+};
+  
+#endif
+}}}
+
 === Naming the sample ===
+
 Some automatic processing is done on loading up the sample. Most of these are simple string comparisons, but do place responsibility on the user.