Ciao Eun-Joo, No, there's nothing wrong with the calibration you committed, I was not clear enough. The problem is related to the DB revision structure. If you look at the values from the web interface, they look fine because in my cgi script, I ignored the _stop_ time of a revision when I display things (this needs a fix by the way). If you try the TofDbBrowser, they are all -1111 (ADC gaps TFW2, run e.g. 10361). In principle, this should not happen, but then I had the idea that the calibration you have committed was only valid until a certain point in time (if you had specified -f <final run>). It would mean that the runs following that stop point would pick an older revision which is not bound by the validity stop. And I remember that at some point, the ADC gaps were all -1111 (before you committed your new cal). It would be nice if we could remove a revision that we know is definitely bad ... This is my understanding of the problem, and is what Hiro was pointing at in some message (maybe it was not posted on the list). Djam -- Djamel Ouerdane ------------------------------------------o | Niels Bohr Institute | Home: | | Blegdamsvej 17, DK-2100 Ø | Jagtvej 141 2D, | | Fax: +45 35 32 50 16 | DK-2200 Copenhagen N | | Tel: +45 35 32 52 69 | +45 35 86 19 74 | | http://www.nbi.dk/~ouerdane | | ouerdane@nbi.dk | o---------------------------------------------------------o _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Tue Nov 23 10:53:28 2004
This archive was generated by hypermail 2.1.8 : Tue Nov 23 2004 - 10:53:48 EST