Hi Selemon, There are actully plenty of options for RICH, and H2 implicitly. The option -rich : will require a check on the RICH using the parameters RICH-fidHighX ..etc will defualt value of +-20 as we have talked about. I also realized over the vacation at some point that the cuts in T5 is not really +-14 SINCE there is a Yoffset on T5 in the order +0.32. therefore the proper limits should be -14.32 --> 13.68 if I interptet this corrctly. I do not think you need to have the runnumber in the name. The runperiod+nominal angle really sets the geometry for FFS and FS completely in the run5 . On the other hand we do need to indicate if the fiducial is set by H2 or by rich. On MRS one has to be carefull one the positon of TFW2 which is an issue Flemming -------------------------------------------- Flemming Videbaek Physics Department Bldg 510-D Brookhaven National Laboratory Upton, NY11973 phone: 631-344-4106 fax: 631-344-1334 e-mail: videbaek @ bnl.gov ----- Original Message ----- From: "Bekele, Selemon" <bekeleku@ku.edu> To: <brahms-dev-l@lists.bnl.gov> Sent: Thursday, January 05, 2006 1:06 PM Subject: [Brahms-dev-l] Acceptance Maps > > Hi, > > I have a small script that enables one to generate maps > by submitting condor jobs. I would like people to give me > suggestions on what options to use and with what values. > It would be good to fill in what I have for the FS: > > generateMaps -e 1 -r 13196 -s FS > --T5-fidfhiY=14 --T5-fidflowY=-14 > -d 5 //vertex bin width > -Z 40 -z -40 //vertex range > -o FS_CuCuAccMapFromRun13196at4A3450.root > what else? > > I do not see any options for H1,H2, RICH in the acceptance code. > which seems that I do not need to worry about them for the acceptance > maps. Correct me if that is wrong and let me know how to include them. > > > I have set the output file in such a way that it tells one > > the detector system (FS) > the particle species (CuCu) > the run number for the geometry (13196) > the setting (4A3450) > > any other suggestions are welcome. If there has been an existing format hardwired > in codes, I can easily make the nameing follow that format. > > Thanks, > > Selemon, > > _______________________________________________ > Brahms-dev-l mailing list > Brahms-dev-l@lists.bnl.gov > http://lists.bnl.gov/mailman/listinfo/brahms-dev-l > _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Thu Jan 5 13:29:10 2006
This archive was generated by hypermail 2.1.8 : Thu Jan 05 2006 - 13:29:17 EST