Finally lets look at the entire analysis routine to see what boilerplate code we need to make a complete analysis routine. To avoid having to always specify the entire long name each time we use it, we can use the import statement. The import statement is used to import a namespace into the current routine, so that the abbreviated name can be used. Next we declare the class itself, in this case called LCDResolution, which as we have explained before extends the framework routine EventAnalyzer. Finally we declare a public constructor for the LCDResolution class which takes no arguments, so that the class can be created by the framework.
Constructors always have the same name as the class itself, and have no declared return type.
If we needed to do some initialization we could do it in the body of the class constructor, but in this case there is no initialization needed, so the constructor body is empty. The remaining tutorials in this series contain several more examples of writing analysis routines. The API' s for the hep.analysis classes , which include Histogram and EventAnalyzer classes. The API's for the hep.physics classes , which include Particle and ParticleType classes. Please send us comments on this tutorial.