Dear Pawel, comments in-lined. flemming ---------------------------------------------------------------- Flemming Videbaek Physics Department Brookhaven National Laboratory > Hi, > I committed DC calibration for runs 9813 to 9991. > Note, that the calibration has been done with TRFS time reference > enabled, because the found that > for some runs it improves the resolution a lot. > ONE HAS TO ADD: > if(runNo>=9813 && runNo<=9991)localdctrack->UseTrFsRef(kTRUE); > otherwise the quality of tracks will be very bad. > We decided to keep this option for all AuAu data in run04. > (it is also used for p+p). > > If we agree I can keep the local tracking scripts up to date according > to what is > in the db. Are the official scripts on ~bramreco/run04/auau/200/ltr > and ~bramreco/run04/auau/63/ltr ? ### Yes the official scripts are here. They should be kept up to date. Also please commit to CVS when making a change so we can follow the hsitory. > > I also updated TrackOffset.C and GlobalTracking.C on ~/run04/auau/63/gtr > (only), so the > T2_T3 matching params are supported in the same way as other > BrModuteMatchTrack related parameters > (FFS, T3_T4, T4_T5, T2_T4). > ### Thank you. --I have a question, namely when running the global tracking there is 'information' printed out about the DCEnhancement matching (or cut) parameters. By inspecting the code these seem to hardwored in the code for auau (run2) and [presumably] pp run 2. Is it expetced thse should be the same for the all later runs? _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Mon Jun 28 12:07:31 2004
This archive was generated by hypermail 2.1.8 : Mon Jun 28 2004 - 12:07:53 EDT