Just to make this clearer
_ I agree with Adrian that we should stop dropping db so the first
thing is to make sure we have a smarter way to change HV tables
- Adrian will start updating the db with pedestal values. At some point
peter will do the same with tdc offsets. For the pedestals, adrian will
tell us how bad/frequent/significant the shifts are, and how often they
should be checked. Note, this can also be done at any later stage.
_ We do not plan to change the way this info is read in our macros until
after the run. Therefore, we still use blast.sc_cal. However we will
load the db so that the information will be there for a later analysis
_ Chris, you are involved as I believe that runinfo was doing something
similar (??). If you can help, talk to the relevant guys
- There may be other run to run info that needs to be in the db. Note that
a lot is already in the epics screen. However, the trigger file, a data
quality flag may be handy. But they may go in elogbook
-
________________________________________________________________________________
Tancredi Botto, phone: +1-617-253-9204 mobile: +1-978-490-4124
research scientist MIT/Bates, 21 Manning Av Middleton MA, 01949
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
On Wed, 20 Nov 2002, Adrian T Sindile wrote:
> Hi!
> At today's analysis meeting, it was decided to move towards writing TDC
> offsets and ADC pedestals to the MySQL database from now on, instead of
> using files... Also, it would be nice to make CODA record info in the
> database for every run.
> Our MySQL database was already designed for this purpose, we have been
> only waiting for this moment.
> This will require writing programs for that (I will have to speak with
> Chris to come up with a common idea, as he already used similar stuff for
> the ELogbook). It will also require to add stuff to the reconstruction
> classes that need this info (Chi). Maybe Chris, Chi and I could get
> together and discuss this (is tomorrow (Thursday) OK?)...
>
> Anyway, once we start using the database for things required in the
> analysis (offsets, pedestals etc.) we will have to drop the habit of
> dropping the database whenever we change HV settings (it was just faster
> to do it that way, to avoid manual interaction with the HV daemon).
>
> Soon, I will modify permissions for the database users, so that we do not
> lose information by mistake (once you drop it, that info is forever lost).
> I will send an email when permissions are changed.
>
> Adrian
>
> -------------------------------
> Adrian Sindile
> Research Assistant
> Nuclear Physics Group
> University of New Hampshire
> phone: (603)862-1691
> FAX: (603)862-2998
> email: asindile@alberti.unh.edu
> http://einstein.unh.edu/~adrian/
>
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:28 EST