--- PamCut/doc/PamCutDevGuide.tex 2009/05/27 13:30:01 1.1 +++ PamCut/doc/PamCutDevGuide.tex 2009/06/15 14:44:01 1.3 @@ -86,10 +86,42 @@ calling {\bf Setup} at the beginning of the analysis, {\bf OnGood} and {\bf OnBad} for every event (depending on the selection result), and {\bf Finalize} at the end of the analysis. In all other aspects, it behaves exactly as {\bf -PamCutCollection}.\\ +PamCutCollection}. The handling of the actions depend on their position with +respect to cuts. In the main analysis code, cuts can be added to the +collection; then, an action or more can be added. This sequence of cuts and the +actions added after the cuts will be called a bunch. The last bunch may have no +actions at its end. +\begin{verbatim} + . + . + . +Cut1 cut1(``cut1''); +Cut2 cut2(``cut2''); +Action1 action1(``action1''); + +Cut1 cut3(``cut3''); +Cut2 cut4(``cut4''); +Cut1 cut5(``cut5''); +Cut2 cut6(``cut6''); +Action1 action2(``action2''); +Action1 action3(``action3''); + . + . + . +\end{verbatim} +In the example above, {\bf cut1}, {\bf cut2} and {\bf action1} are the first +bunch, {\bf cut3}, {\bf cut4}, {\bf cut5}, {\bf cut6}, {\bf action2} and {\bf +action3} are the second bunch and so on. If all the cuts in the bunch are +successful, the {\bf SmartCollection} will call {\bf OnGood} for every action +in that bunch, and then the analysis will go on with the next bunch for the same +event. If a certain cut in a bunch fails, then {\bf OnBad} is called for the +actions of the bunch, but successive bunches are ignored; the current event is +discarded and the focus switches on the next one (the {\bf +SmartBlindCollection} behaves a little different; see the Doxygen +documentation for more details.) +\\ Loosely speaking, after defining an action one simply has to instantiate it, -add it to a {\bf SmartCollection} and launch the analysis (fire and -forget\ldots). +add it to a {\bf SmartCollection} and launch the analysis. \section{The software organization} The software is organized in a tree of directories. The idea is that each node @@ -502,18 +534,35 @@ implementations of actions if you need some example to setup your build. \section{How to build and use the library} +\subsection{Standard Pamela environment} If the makefiles are correctly set up, the only remaining thing is to type \verb1make all1. Remember to set the PAMELA environment with the set\_pam\_env script BEFORE invoking \verb1make1. This will generate a {\it libPamCut.so} file which will contain all the cuts. To clean the project and build from scratch -type \verb1make clean all1. To use the library in an analysis code the +type \verb1make clean all1. The software can then be installed in the usual +Pamela environment calling \verb1make install1: this will place all the +headers in the folder \verb1$PAM_INC/PamCut1 and the {\it libPamCut.so} file in +\verb1$PAM_LIB1. To eliminate the installed files call \verb1make distclean1; +note that this will NOT do the work of \verb1make clean1, eg., clean the +project, but simply remove the files copied in the Pamela directories. Remember +to type \verb1make install1 each time you modify and recompile the software, to +upgrade the installed version to the new one. + +To use the library in an analysis code the environment header must be included in the code: \verb1#include "/PamCutEnv.h"1. With this, all the classes and common definitions will be accessible. A typical usage of {\bf PamCut} inside the analysis code would look like: \begin{verbatim} - + + #include + + int main(){ + . + . + . + PamCutCollection collection; DummyCut1 dummy1; @@ -523,23 +572,48 @@ collection.Process(event, 0, event->GetEntries()-1); + . + . + . + } + \end{verbatim} In the simple example above a \verb1DummyCut11 and a \verb1DummyCut21 object (which requires some sort of parameter) are instantiated. They are added to \verb1collection1 which takes care of applying them to all the events. -When the analysis code is compiled the linker must be aware that it -needs a library called {\it libPamCut.so} and where to find it. In the {\it -makefile} which builds the analysis program the following option must be added -to the linker invocation: +\subsection{Custom environment} +If you don't have access to the Pamela software directories (eg., you don't +have write permission on them) you cannot install the software; but you can +still use PamCut directly from the source folder. + +First of all, you have to tell the compiler where to find the {\bf PamCut}'s +headers. They are in the main {\bf PamCut} directory, so you may add this +option: \newline -\verb1-L -lPamCut1. - -One could also wish to move {\it libPamCut.so} to another directory: this path -must then replace what is indicated as \verb11 above. +\verb1 -I1 +\newline +to the compiler invocation in the {\it makefile} of your main analysis program. +This tells the compiler to search for headers in the folder specified after +\verb1-I1. So, if {\it } is the folder which contains the {\bf +PamCut}'s main folder, you don't have to change anything in your main analysis +file (with respect to what described in the previous subsection), since: +\newline +\verb1 #include 1 +\newline +includes the file {\it PamCutEnv.h} which is in the folder {\it PamCut} in the +standard inclusion directories, one of which is the one specified with the +\verb1-I1 compiler directive. Obviously, one can play with directories, having +care to indicate the right paths to the compiler -Finally, when the analysis code is compiled and linked against libPamCut.so, to +The following option must be added to the linker invocation: +\newline +\verb1 -L -lPamCut1. +\newline +to tell the linker where the dynamic library is. + +Then, when the analysis code is compiled and linked against libPamCut.so, to launch it it's necessary to tell the environment where the library is, so that the program can dynamically access it at runtime. This information is encoded in the environment variable LD\_LIBRARY\_PATH, which contains the paths of the