goodEventTagger are now implemented into anaGm2 as a class called goodEventTagger.cxx. It has only one function goodEventTagger(), which will be called at the end of each sub-run, filling the bigtreesub.root with isGoodEvent= 1 or 0 inside offline branch, according to the badEventList.txt and badEventListManual.txt.
We will be able to start "proc3" (marking all bad runs and events) after this merge request been accpted.
What will be in next merge request
Macros for Drift Chamber planes mis-alignment checking. (proc4)
