[BLAST_SHIFTS] elogbook and checklist

From: Tancredi Botto (tancredi@mitlns.mit.edu)
Date: Thu Jul 03 2003 - 17:18:42 EDT


Dear collaborators,
although for many it seemed a natural transition I recommend (read *request*)
that all entries pertinent to the logbook (wire chamber trips, changed cabling,
e-maps, including abs..) be submitted to the Electronic Logbook

Also, it is very important that the checklist is filled out correctly. You
have to do this for every run, whether garbage or not.

If we don't stick to these simple rules the price to pay will be
horrendous and your analysis a pain. The time this will become mission
critical is very close, and elog is simple enough you don't need extensive
education on it. I went through great lenghts to "fix" the run database
for the recent D2 runs (pol and unpol). If you don't know what I am
talking about do ~elog/bin/view.tcl on a spud and search for runs.

no logbook, no data to analyse, no thesis.

P.S.
the elog essentials do work, although refinements are of course possible.
but to make it 100% backward compatible would be very difficult. That is
another reason why it is important to be consistent starting now.

-- 
________________________________________________________________________________
Tancredi Botto,  		phone: +1-617-253-9204  mobile: +1-978-490-4124
research scientist		MIT/Bates, 21 Manning Av    Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^



This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST