RE: [Brahms-dev-l] Acceptance Maps

From: Bekele, Selemon <bekeleku@ku.edu>
Date: Fri Jan 06 2006 - 10:55:00 EST
Hi Flemming,

     I got a reply from Truls about the location of the recent
version of the Acceptance codes. Below is shown what I plan to use
to make the acceptance maps. I would appreciate any final comments
or changes before I begin submitting jobs.

#########################################################

1) fiducial is set by RICH

 generateMaps -e 1 -r 13196 -s FS
            --T5-fidfhiY=13.68
            --T5-fidflowY=-14.32
            --rich=kTRUE                            //default false
            --xfptmap=kTRUE                         //default false
            -d 5                                    //vertex bin width
            -Z 40 -z -40                            //vertex range
            -o FS_CuCuRun05AccMapAt4A3450_FidSetByRICH.root

2) fiducial is set by H2

 generateMaps -e 1 -r 13196 -s FS
            --T5-fidfhiY=13.68
            --T5-fidflowY=-14.32 
            --rich=kFALSE                            //default false
            --xfptmap=kTRUE                          //default false
            -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
            --xfptmap=kTRUE                          //default false     
            -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: Fri 1/6/2006 7:45 AM
To: Bekele, Selemon
Cc: brahms-dev-l@lists.bnl.gov
Subject: Re: [Brahms-dev-l] Acceptance Maps
 
Hi selemon,

The current code is in banapp/anatools not in the old tml_apps. I trust truls informaed everyone on this.


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: "Flemming Videbaek" <videbaek@rcf.rhic.bnl.gov>
Cc: <brahms-dev-l@lists.bnl.gov>
Sent: Thursday, January 05, 2006 5:00 PM
Subject: RE: [Brahms-dev-l] Acceptance Maps



Hi Flemming,

  I do not see any options for the RICH. May be there is a private version
of the code out there which have yet to be committed to CVS. Anyway, here are 
the default options:

#############################################################################

anatools> generateMaps --help
Usage: generateMaps [options]
 
Options:
     --D1-fidX          Closest acceptable distance to D1 magnet walls in X, default is 0
     --D1-fidY          Closest acceptable distance to D1 magnet walls in Y, default is 0
     --D2-fidX          Closest acceptable distance to D2 magnet walls in X, default is 0
     --D2-fidX          Closest acceptable distance to D2 magnet walls in X, default is 0
     --D2-fidY          Closest acceptable distance to D2 magnet walls in Y, default is 0
     --D2-fidY          Closest acceptable distance to D2 magnet walls in Y, default is 0
     --D3-fidX          Closest acceptable distance to D3 magnet walls in X, default is 0
     --D3-fidY          Closest acceptable distance to D3 magnet walls in Y, default is 0
     --D4-fidX          Closest acceptable distance to D4 magnet walls in X, default is 0
     --D4-fidY          Closest acceptable distance to D4 magnet walls in Y, default is 0
     --D5-fidX          Closest acceptable distance to D5 magnet walls in X, default is 1
     --D5-fidY          Closest acceptable distance to D5 magnet walls in Y, default is 0
    --T1-drbhighX      Set T1 back dead region high X, default is -1111
     --T1-drblowX       Set T1 back dead region low X, default is -1111
     --T1-drfhighX      Set T1 front dead region high X, default is -1111
     --T1-drflowX       Set T1 front dead region low X, default is -1111
     --T1-fidbhiX       Highest acceptable X on back of T1, default is 99
     --T1-fidbhiY       Highest acceptable Y on back of T1, default is 99
     --T1-fidblowX      Lowest acceptable X on back of T1, default is -99
     --T1-fidblowY      Lowest acceptable Y on back of T1, default is -99
     --T1-fidfhiX       Highest acceptable X on front of T1, default is 99
     --T1-fidfhiY       Highest acceptable Y on front of T1, default is 99
     --T1-fidflowX      Lowest acceptable X on front of T1, default is -99
     --T1-fidflowY      Lowest acceptable Y on front of T1, default is -99
     --T2-drbhighX      Set T2 back dead region high X, default is -1111
     --T2-drblowX       Set T2 back dead region low X, default is -1111
     --T2-drfhighX      Set T2 front dead region high X, default is -1111
     --T2-drflowX       Set T2 front dead region low X, default is -1111
     --T2-fidbhiX       Highest acceptable X on back of T2, default is 99
     --T2-fidbhiY       Highest acceptable Y on back of T2, default is 99
     --T2-fidblowX      Lowest acceptable X on back of T2, default is -99
     --T2-fidblowY      Lowest acceptable Y on back of T2, default is -99
     --T2-fidfhiX       Highest acceptable X on front of T2, default is 99
     --T2-fidfhiY       Highest acceptable Y on front of T2, default is 99
     --T2-fidflowX      Lowest acceptable X on front of T2, default is -99
     --T2-fidflowY      Lowest acceptable Y on front of T2, default is -99
     --T3-drbhighX      Set T3 back dead region high X, default is -1111
     --T3-drblowX       Set T3 back dead region low X, default is -1111
     --T3-drfhighX      Set T3 front dead region high X, default is -1111
     --T3-drflowX       Set T3 front dead region low X, default is -1111
     --T3-fidbhiX       Highest acceptable X on back of T3, default is 99
     --T3-fidbhiY       Highest acceptable Y on back of T3, default is 99
     --T3-fidblowX      Lowest acceptable X on back of T3, default is -99
     --T3-fidblowY      Lowest acceptable Y on back of T3, default is -99
     --T3-fidfhiX       Highest acceptable X on front of T3, default is 99
     --T3-fidfhiY       Highest acceptable Y on front of T3, default is 99
     --T3-fidflowX      Lowest acceptable X on front of T3, default is -99
     --T3-fidflowY      Lowest acceptable Y on front of T3, default is -99
     --T4-drbhighX      Set T4 back dead region high X, default is -1111
     --T4-drblowX       Set T4 back dead region low X, default is -1111
     --T4-drfhighX      Set T4 front dead region high X, default is -1111
     --T4-drflowX       Set T4 front dead region low X, default is -1111
     --T4-fidbhiX       Highest acceptable X on back of T4, default is 99
     --T4-fidbhiY       Highest acceptable Y on back of T4, default is 99
     --T4-fidblowX      Lowest acceptable X on back of T4, default is -99
     --T4-fidblowY      Lowest acceptable Y on back of T4, default is -99
     --T4-fidfhiX       Highest acceptable X on front of T4, default is 99
     --T4-fidfhiY       Highest acceptable Y on front of T4, default is 99
     --T4-fidflowX      Lowest acceptable X on front of T4, default is -99
     --T4-fidflowY      Lowest acceptable Y on front of T4, default is -99
     --T5-drbhighX      Set T5 back dead region high X, default is -1111
     --T5-drblowX       Set T5 back dead region low X, default is -1111
     --T5-drfhighX      Set T5 front dead region high X, default is -1111
     --T5-drflowX       Set T5 front dead region low X, default is -1111
     --T5-fidbhiX       Highest acceptable X on back of T5, default is 24.5
     --T5-fidbhiY       Highest acceptable Y on back of T5, default is 99
     --T5-fidblowX      Lowest acceptable X on back of T5, default is -24.5
     --T5-fidblowY      Lowest acceptable Y on back of T5, default is -99
     --T5-fidfhiX       Highest acceptable X on front of T5, default is 24.5
     --T5-fidfhiY       Highest acceptable Y on front of T5, default is 99
     --T5-fidflowX      Lowest acceptable X on front of T5, default is -24.5
     --T5-fidflowY      Lowest acceptable Y on front of T5, default is -99
     --TPM1-drbhighX    Set TPM1 back dead region high X, default is -1111
     --TPM1-drblowX     Set TPM1 back dead region low X, default is -1111
     --TPM1-drfhighX    Set TPM1 front dead region high X, default is -1111
     --TPM1-drflowX     Set TPM1 front dead region low X, default is -1111
     --TPM1-fidbhiX     Highest acceptable X on back of TPM1, default is 99
     --TPM1-fidbhiY     Highest acceptable Y on back of TPM1, default is 99
     --TPM1-fidblowX    Lowest acceptable X on back of TPM1, default is -99
     --TPM1-fidblowY    Lowest acceptable Y on back of TPM1, default is -99
     --TPM1-fidfhiX     Highest acceptable X on front of TPM1, default is 99
     --TPM1-fidfhiY     Highest acceptable Y on front of TPM1, default is 99
     --TPM1-fidflowX    Lowest acceptable X on front of TPM1, default is -99
     --TPM1-fidflowY    Lowest acceptable Y on front of TPM1, default is -99
     --TPM2-drbhighX    Set TPM2 back dead region high X, default is -1111
     --TPM2-drblowX     Set TPM2 back dead region low X, default is -1111
     --TPM2-drfhighX    Set TPM2 front dead region high X, default is -1111
     --TPM2-drflowX     Set TPM2 front dead region low X, default is -1111
     --TPM2-fidbhiX     Highest acceptable X on back of TPM2, default is 99
     --TPM2-fidbhiY     Highest acceptable Y on back of TPM2, default is 99
     --TPM2-fidblowX    Lowest acceptable X on back of TPM2, default is -99
     --TPM2-fidblowY    Lowest acceptable Y on back of TPM2, default is -99
     --TPM2-fidfhiX     Highest acceptable X on front of TPM2, default is 99
     --TPM2-fidfhiY     Highest acceptable Y on front of TPM2, default is 99
     --TPM2-fidflowX    Lowest acceptable X on front of TPM2, default is -99
     --TPM2-fidflowY    Lowest acceptable Y on front of TPM2, default is -99
 -h  --help             Show this help, default is true
 -e  --maxError         Maximum relative average error on pion map, default is 5
 -o  --outputfile       Output file name, default is
     --pbeam            pbeam for Xf calculation, default is 100
     --pidmap           generate Pid maps, default is true
     --pmax             Maximum P in calculation, default is 40
     --ptmax            Maximum Pt in calculation, default is 7
 -r  --run              Run number, default is -1
 -s  --spectrometer     Spectrometer (FFS,FS,MRS), default is
 -v  --verbose          Verbosity level, default is 0
 -V  --version          Version number, default is false
 -d  --vtxbinwidth      Width of vertex bins, default is 5
 -Z  --vtxzmax          Max. vertex z, default is 20
 -z  --vtxzmin          Min. vertex z, default is -20
     --xfptmap          generate xfPt map, default is false
################################################################

Selemon,

-----Original Message-----
From: Flemming Videbaek [mailto:videbaek@rcf.rhic.bnl.gov]
Sent: Thu 1/5/2006 3:36 PM
To: Bekele, Selemon
Cc: devlist
Subject: Re: [Brahms-dev-l] Acceptance Maps
 
Hi
my spelling my not be the best. try generateMaps --help it list all valid options including there default
values.
--------------------------------------------
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 4:28 PM
Subject: RE: [Brahms-dev-l] Acceptance Maps



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-l
Received on Fri Jan 6 10:55:54 2006

This archive was generated by hypermail 2.1.8 : Fri Jan 06 2006 - 10:56:06 EST