Hi Bjørn, Trine and Truls First of all, a very nice and detailed note. Great to read. I have a few questions : * What kind of cuts were apllied on the tracks except the acceptance cuts. X and Y vertex cuts, chi**2, etc. * What tracking parameters were used. * How long time does it take to change something and redo the analysis (just curious) I think the 2 first should be written somewhere in the appendix. Sorry if I missed them. And some comments : It would be great if you instead of plotting number of crashes vs number of clusters plotted vs centrality class just to make sure. It seems that this is something that needs to be fixed. It is good that the trackstringfinder does not crash. I have some ideas for improvements but also other problems that I would like to solve, so it depends on what priority people thinks this should have. It would be great if the efficiency tester would be made public in brahms_app, I would like to test it on T1. The problem with a dip in number of tracks vs pads is related to hot/cold pads. Plot number of clusters vs pads and rows (2d) and you will see hot regions and cold regions (gStyle->SetPalette(1) ;). If you remove those from the detectorparams file and you obtain the correction vs pads AND number of clusters you are safe, but maybe you can just extrapolatem, if you just have a dip - someone stronger in the force can probably guide you better. Cheers Peter :-) --------------------------------- )-: |Peter H L Christiansen aka PAN @ NBI | |EMAIL : pchristi@nbi.dk | |OFFICE : Tb1 @ NBI | |PHONE : 353 25269 | |SNAIL : Hans Tavsensgade 35, 4th | |PHONE : 35 349336 | :-D --------------------------------- \-:
This archive was generated by hypermail 2b29 : Wed Feb 21 2001 - 10:36:45 EST