On Wed, 28 Apr 2004, Djamel Ouerdane wrote: > Hi, > > I could trace back the run period for which vdrift is bad: > > TPM1: 8672 - 9354 > TPM2: 8670 - 9354, > > namely all calibrations committed on the 24th of July 2003. > > That's quite a number of runs... Now this is _really_ odd. With a dv that's this off I wouldn't expect to see tracks at all, let alone good matching and PID, but looking at my plots for this run range they don't seem different from the ones outside... This begs the question: Do we really USE the calibrated drift velocities? Or are we still just picking up the default value from BrDetectorParameters.txt? Trying to trace this in the code, I'm actually not quite sure... I'll try looking a bit more into this later today - unless someone has a ready answer, of course :-) -- Bjorn H. Samset Phone: 22856465/92051998 PhD student, heavy ion physics Adr: Schouterrassen 6 Inst. of Physics, University of Oslo 0573 Oslo \|/ ----------------------------> -*- <----------------------------- /|\ _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Wed Apr 28 04:51:51 2004
This archive was generated by hypermail 2.1.8 : Wed Apr 28 2004 - 04:52:12 EDT