[g13] bad tagger counters in database

[Paul Mattione]

I've loaded my study of the bad tagger counters for g13a into the  
caldb database (TAG_CALIB -> status -> tage and -> tagt_left and  
tagt_right).  I only looked from 53164 - 53862 (I ignored LH2 and  
53998 - 54035 data).

However, I didn't feel like poring over all of the anahist files to  
figure out exactly which run each counter died at.  Instead I  
determined the vast majority of the range over which each counter was  
definitely bad, and set it for those.  That way the database does not  
cut out the tagger counters for too large of a range.  It is not  
necessary to have the exact run number that each counter died because  
you don't want to recalculate the acceptance correction for every  
single run range where something new dies anyway.  As long as you set  
the run number for gpp within the run range, it'll be rejected (i.e.  
53333, 53460, 53800, etc).

However, when you calculate cross-sections you'll want to extend the  
cut range PAST the runs where it was bad.  You can see the details in  
the "Actual Run Ranges" section at:

http://clasweb.jlab.org/rungroups/g13/wiki_secure/index.php/TaggerEfficiencyStudy#Run_Dependence

This is probably more info than most people wanted, but if you have  
specific questions please email me and let me know.

  - Paul