On Fri, 19 Dec 2003, Pawel Staszel wrote: > Hi Bjorn and Zhongbao, > If I have a new local tracks files today, there will be a good chance > that I manage > calculate the efficiencies before I do disappear for the Christmas > holiday. You can at least have the pp files - they are here: /brahms/data09/data/run03/pp/200 and are labeled v04. I'm currently doing matching on them - so far they look OK, but I haven't really checked in detail. Note that to save space I will DELETE version 03, since that one seems to have had a number of problems and should NOT be used! As for changing the setup in global tracking, I think your suggestion is reasonable. If I don't hear anything else very soon I will run the global tracking with bfs->SetCleanUp(BrBfsTrackingModule::kCUT2, kFALSE); bfs->SetCleanUp(BrBfsTrackingModule::kCUT3, kTRUE); (That is, I will start the reco anyway, but I can kill it again if this is not what we want...) I would also like to let this step finish before starting on the dAu local tracking, since I really would like to check that everything looks OK before leaving this afternoon. Is there a subset of dAu runs that I can try to run through quickly so you can have them after lunch for efficiency calculations, or do you need all of them? Ping :-) -Bjorn > > My plane is to provide T1,T2,T3,T4 and T5 efficiencies for pp runs and > T4, T5 for dAu. > > I modified the efficiency code so we can support T5, even T3 tracks are > not present. > We will have T1 and T2 only for 8375 , and I would suggest to assume that > T1 and T2 have the same efficiencies as for p+p (we know that these > detectors > are quite stable). > > Because, for d+Au we may have only Fs tracks with flag T2Used=kTRUE, > I would suggest to utilize only Fs tracks with flag T2Used=kTRUE, both > for p+p and d+Au. > I think that I will reduce the systematic error on R_dA, specially if > you use the same acceptance maps. > Note, that if you decide to do this Bjorn has to modified Fs tracking setup: > by default we clean up T2-T4 tracks that have the same T4 track as any > of T3-T4 , for > the mentioned purpose we have to revers the situation. > To let all the T2-T4 tracks survive the clean up just do: > bfs->SetCleanUp(BrBfsTrackingModule::kCUT2, kFALSE); > bfs->SetCleanUp(BrBfsTrackingModule::kCUT3, kTRUE); > > Cheers > Pawel. -- 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 Fri Dec 19 05:33:05 2003
This archive was generated by hypermail 2.1.8 : Fri Dec 19 2003 - 05:33:22 EST