- Mixins defined in Logger.h
- Mixin used in base classes (THcDC is currently a good example)

Added a few more spdlog loggers

Added logging to many.

- Added logging to hodoscope, aerogel hitlist and detectormap
- Working on scandalizer features.

Added logging.

Added more logging.

added more logging.

More logging.

Don't confuse index of scalers with slot number

See https://github.com/JeffersonLab/analyzer/commit/cd7c26b5b1161115a0e35a4824148b78a189e986

NOTE:
This changes the format of the "variable" lines in the db map file that
defines the scaler layout.

The number after the variable directive is now the slot number instead of
the index of which scaler module (starting from zero) is being used.
Updated DBASE/db_PScalevt.dat and DBASE/db_HScalevt.dat files which have
been generated by an updated MAPS/SCALERS/make_scaler_db.py.  This change is
made so that the "variable" line format is the same as used in
THaScalerEvtHandler.cxx.

Change fBCM_Name to vector of strings .
Fixed memory leak when it was array of char.

1) add error message if Time between sucessive reads is zero.
    This should never happen.

2) Add the event number of that scaler read to the Scaler root tree
   The tree variable is evNumber

  All Int_t variables that hold scaler values are now UInt_t
  Some variables that were Double_t are UInt_t
  Keep track of overflows so that tree variables holding scaler counts
     are correct for high rate scalers
  Catch overflows when computing differences from last scaler reading.

  1.  If there are multiple ROCs with scalers (hardware, TI, FADC), then
there will be multiple event 129s.  In the case where analysis of these
events is defered to the end of the analysis, all the event 129s will
be analyzed as if a single event, resulting in one entry in the tree.
  2.  Scalers are read either when a given time interval has passed since
the last scaler read (usually 2 seconds), or every time an event is tagged
as a sync event.  In the case of the "timed" reading of events, different ROCs
with scalers are not guaranteed to read their scalers at the same event.  But
or sync event scaler reads, all ROCs read their scalers.  This commit adds an
option SetOnlyUseSyncEvents(Bool_t).  If set, only scaler events triggered
by the sync event will be analyzed.

  Add #include <set>
  Don't use new method of looping over vector

  When the db file is read, a list of crate #s and a list of
  module types is made.  The tag of each bank searched for scalers
  must have a tag that is in one of these lists.
  If all scalers are in banks tagged with the module type, then,
  SetOnlyBanks(kTRUE) should be called in which case bank tags will
  be compared only against this list of module types.

  In the end method of the Hall C rocs, the scalers are read for a final
  time and a user event 129 is created with the scaler counts.
  These events do not always appear at the end of the coda file, leading to
  the risk that triggered scaler reads will appear after the event 129s.

  If the event type of these final scaler reads is passed to the scaler
  object with the SetDelayedType(int evtype) method, then the scaler analyis
  will cache these events and analyze them at the end of the analysis.

  Use pointer to event from evdata->GetRawDataBuffer() instead
  of making a local copy of the event before scanning it for
  scaler data

  There was already an AddEvtType in the base class.
  Should use SetEvtType to set the event type.  If the handler is to
  look for more than one event type, use AddEvtType for the extra
  event types.

  Process slot with clock first so that time is available to other slots
  Add option to use data in first scaler event
     (handler->SetUseFirstEvent(Bool_t)) instead of subtracting first event
     from subsequent events

  THcScalerEvtHandler will work for rocs with scaler data with or
  without the data being wrapped in a bank.

  Rename ScalerLoc so it doesn't conflict with class of same name in podd
  Ignore .pcm files
  Makefile does version check for root 6
  Address warnings in hodtest.C