Hi Flemming, >>The params are there (module some l.c. u.c ) which module is this? >>--Rich-fidlowX ..." for the RICH. low or Low in fidlowX? >>The default parameters are OK so all needed is to turn rich on. How do you turn the rich on? It is not obvious but I tried using "-rich" as one of the options to generatMaps, it did not work since "-r" needs an argument. Below is what I tried (failing in each case) 1) anatools> generateMaps --rich=1 -e 1 -r 12376 -s FS --T5-fidfhiY=14 --T5-fidflowY=-14 -d 5 -Z 20 -z -20 -o FS_CuCuRun05AccMapat4A861_FidSetByRICH.root Error in <BrAppOptionManager::ProcessLongOption>: Unknown option --rich=1. Try generateMaps --help 2) anatools> generateMaps -rich -e 1 -r 12376 -s FS --T5-fidfhiY=14 --T5-fidflowY=-14 -d 5 -Z 20 -z -20 -o FS_CuCuRun05AccMapat4A861_FidSetByRICH.root Error in <BrAppOptionManager::ProcessCommandLine>: short options can not follow option -r that need an argument 3) With High and Low for RICH-fid...X anatools> generateMaps -e 1 -r 12376 -s FS --T5-fidfhiY=14 --T5-fidflowY=-14 --RICH-fidHighX=20 --RICH-fidLowX=-20 -d 5 -Z 20 -z -20 -o FS_CuCuRun05AccMapat4A861_FidSetByRICH.root Error in <BrAppOptionManager::ProcessLongOption>: Unknown option --RICH-fidHighX=20. Try generateMaps --help 4) With high and low for RICH-fid...X anatools> generateMaps -e 1 -r 12376 -s FS --T5-fidfhiY=14 --T5-fidflowY=-14 --RICH-fidhighX=20 --RICH-fidlowX=-20 -d 5 -Z 20 -z -20 -o FS_CuCuRun05AccMapat4A861_FidSetByRICH.root Error in <BrAppOptionManager::ProcessLongOption>: Unknown option --RICH-fidhighX=20. Try generateMaps --help Selemon, -----Original Message----- From: Flemming Videbaek [mailto:videbaek@rcf.rhic.bnl.gov] Sent: Thu 1/5/2006 2:31 PM To: Bekele, Selemon Cc: brahms-dev-l@lists.bnl.gov Subject: Re: [Brahms-dev-l] Acceptance Maps The params are there (module some l.c. u.c ) --Rich-fidlowX ..." for the RICH. The default parameters are OK so all needed is to turn rich on. On H1 and H2 your are right but the code DOES require that the plane within slat 1-40 (1-32) are in fact hit the x fiducial is set properly Should we have the Y-cutoffs too ? This is a general question /fv -------------------------------------------- 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: "Flemming Videbaek" <videbaek@rcf.rhic.bnl.gov> Cc: <brahms-dev-l@lists.bnl.gov> Sent: Thursday, January 05, 2006 3:18 PM Subject: RE: [Brahms-dev-l] Acceptance Maps Hi Flemming, thanks for the reply. Looking at the code generateMaps.cxx in CVS, I do not see the parameters RICH-fidHighX etc anywhere. Similarly for H2. Anyway assuming that the following parameters, or something similar, exist RICH-fidHighX, RICH-fidLowX RICH-fidHighY, RICH-fidLowY H2-fidHighX, H2-fidLowX H1-fidHighY, H1-fidLowY it would be great if people can edit the following, filling in the corresponding "max" and "min" values 1) fiducial is set by RICH, please comment on the line marked by ?? generateMaps -e 1 -r 13196 -s FS --T5-fidfhiY=13.68 --T5-fidflowY=-14.32 ?? --RICH-fidHighX=max --RICH-fidLowX=-min ?? --RICH-fidHighY=max --RICH-fidLowY=-min -d 5 //vertex bin width -Z 40 -z -40 //vertex range -o FS_CuCuRun05AccMapat4A3450_FidSetByRICH.root 2) fiducial is set by H2, please comment on the line marked by ?? generateMaps -e 1 -r 13196 -s FS --T5-fidfhiY=13.68 --T5-fidflowY=-14.32 --H2-fidHighX=1 --H2-fidLowX=32 ?? --H2-fidHighY=max --H2-fidLowY=min -d 5 //vertex bin width -Z 40 -z -40 //vertex range -o FS_CuCuRun05AccMapat4A3450_FidSetByH2.root 3) fiducial is set by H1, please comment on the line marked by ?? generateMaps -e 1 -r 13196 -s FFS --H1-fidHighX=1 --H1-fidLowX=40 ?? --H1-fidHighY=max --H1-fidLowY=min -d 5 //vertex bin width -Z 40 -z -40 //vertex range -o FFS_CuCuRun05AccMapat4A3450_FidSetByH1.root Is there anything else for the FFS? Thanks, Selemon, -----Original Message----- From: Flemming Videbaek [mailto:videbaek@rcf.rhic.bnl.gov] Sent: Thu 1/5/2006 12:28 PM To: Bekele, Selemon; brahms-dev-l@lists.bnl.gov Subject: Re: [Brahms-dev-l] Acceptance Maps 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 16:29:03 2006
This archive was generated by hypermail 2.1.8 : Thu Jan 05 2006 - 16:29:10 EST