Hi, The situation in the DC performance for the selected runs looks bad. pp: In significant number of pp runs I can't calculate the efficiency because lack of tracks. (it was quite reasonable for Ramiro's 4 deg runs but for 12deg is very bad). This means that when version 01 (or 02) was created many pp runs were no supported due to the lack of fine calibration. Because the calibration for pp has been done the solution is simple: redo tracking starting from local tracks. Once again - the pp spectra based on v01/v02 should not be reasonable. dAu: For dau it is very bad with T3, e.g. in run set for 12A843 we have T3 track only in run 8375. The problem is that T3 is used to make a reference tracks for T5, T2 and T1. I will try to find out what can be done about T3. From the e-log I learnt that after 8375 there was a problem with T3 and probably starting since 8392, 2 modules of T3 were off. So, for dAu runs>8375 the efficiency calculation is very difficult to support. I will try to modify the code in the way to not require T3. I have also comment to the run list selected for 12A843(dAu): runs 8382, 8384, 8560, 8569 are low statistics runs ~50k event (note that 8560 is a 0 field run!!!), whereas good runs with numbers between 8547 and 8558 have been ignored. Second comment: Combination T3-T4 provides the best momentum determination - this means that using T2-T4 rather that T3-T4 for d+Au makes worst momentum resolution for Fs tracks as compare to p+p. I dont know how large is the effect but we have to keep in mind. I guess that the correction for momentum resolution should be included in the acceptance maps. Regards Pawel. yin.zhongbao@fi.uib.no wrote: >Dear Pawel, > > > >>1. The exact lists of runs used to make the dsts for the mentioned >>settings - and because >>my program works on local tracking files I need info. which local >>tracking files where used and >>where they are on the disk. (Bjorn,Kris??) >> >> > >pp runs: >12A427: 8834, 8838, 8839, 8840 >12A843: 8855, 8862, 8863, 8867, 8868, 8869, 8871, 8874, 8875, 8877 >12A1692: 8881, 8885, 8886, 8889-8894, 8896, 8897, 8900, 8901, 8902, >8905, 8906, 8907, 8909, 8910, 8913 > >local tracking files: >/brahms/data07/data/run03/pp/200/rXXXX/ltr/ > >dAu runs: >12A843: 8375, 8382, 8383, 8384, 8558, 8560, 8569, 8570, 8571, 8572, 8573, >8601, 8602, 8603 > >12A1692: >8388, 8389, 8610, 8611, 8615, 8622, 8623, 8631, 8632 > >local tracking files: >/brahms/data07/data/run03/dau/200/rXXXX/ltr/ > > > > >>2. For global tracking we need files with tracks matching parameters. >>Which files >>were used for d+Au (Bjorn?) and which were used for p+p (Kris). >> >> > >/brahms/u/bramreco/bhs/calib/run03/dau/200/matching/asciifiles >/brahms/u/bramreco/bhs/calib/run03/pp/200/matching/asciifiles > > > >>And question: >> >>3. Does any one know how Td1 performance or calibration may affect the >>Fs efficiency? >>Do we consider only Fs tracks with a valid Td1 hit? Note, that my >>calculations do not >>include correction for eventual mismatch between Fs and Td1. >> >> > >I don't know. But I assume it is fine not including correction for >mismatch between Fs and Td1 at the moment. > >Thank you very much for your kind help. > >Best regards... >Zhongbao >----------------------------------------------------- >Zhongbao YIN Phone: +47-55-582792 (O) >Address: +47-55-276803 (H) > Fantoftveien 14G 466 E-mail: > 5075 Bergen Yin.Zhongbao@fi.uib.no >------------------------------------------------------ > > > > _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Wed Dec 17 06:52:12 2003
This archive was generated by hypermail 2.1.8 : Wed Dec 17 2003 - 06:52:31 EST