/[PAMELA software]/gpamela/history/v_100.txt
ViewVC logotype

Diff of /gpamela/history/v_100.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 3.3 by pamela, Thu Dec 5 17:27:59 2002 UTC revision 3.4 by pamela, Wed Dec 17 11:32:50 2003 UTC
# Line 1  Line 1 
1  #  #
2  # $Id: v_100.txt,v 3.2 2002/12/05 10:17:42 pamela Exp $  # $Id: v_100.txt,v 3.3 2002/12/05 17:27:59 pamela Exp $
3  #  #
4  # $Log: v_100.txt,v $  # $Log: v_100.txt,v $
5    # Revision 3.3  2002/12/05 17:27:59  pamela
6    # New GARFIELD.GAR file added and GPAMELA.FFR cleaned and updated
7    #
8  # Revision 3.2  2002/12/05 10:17:42  pamela  # Revision 3.2  2002/12/05 10:17:42  pamela
9  # Update CAS and CALO geometries and positions. Makefile updated as well  # Update CAS and CALO geometries and positions. Makefile updated as well
10  #  #
# Line 22  Line 25 
25  #CMZ :  1.00/01 28/11/95  18.51.23  by  Francesco Cafagna  #CMZ :  1.00/01 28/11/95  18.51.23  by  Francesco Cafagna
26  #-- Author :    Francesco Cafagna   28/11/95  #-- Author :    Francesco Cafagna   28/11/95
27    
28    9 December 2003, Bari
29    
30    CALORIMETER SIMULATION completed! The update of the geometry and of the
31    special tracking parameters and the tuning of the calorimeter have been
32    successfully done. A great quantity of simulated data have been produced
33    in the calorimeter for different particles (muons, electrons and pions)
34    and momenta (5 and 40 GeV/c) and the output data have been analyzed. The
35    distributions of the total energy deposited in the calorimeter and the
36    total number of strips hit have been compared with the respective
37    distributions produced by the Trieste's tuned standalone Monte Carlo
38    simulation program of the PAMELA calorimeter. The accord between the
39    two simulations is excellent. Many thanks to Mirko for his collaboration.
40    
41    Working in progress on TRD. The GARFIELD interface to the HEED program is not
42    optimized to track particle with a charge greater than one and photons. The
43    program print a warning message to advise the user when it is the case.
44    
45    18 April 2003, Bari
46    
47    The buffer size of each column of the GPAMELA Ntuple has been increased to
48    4096 and set equal to the record length, defined by a call to the HROPEN
49    routine.
50    Also the length of the common /PAWC/ (parameter NWPAW) has been increased
51    to 1.34E8, according to the rule that it has to be larger than the number
52    of columns times the buffer size.
53    
54    10 April 2003, Bari
55    
56    The variables in the HIT STRUCTURE of the CALORIMETER and their way to be
57    filled have been changed according to the electronics system of the real
58    detector. In fact, because each silicon detector (module) consists of
59    32 strips and each strip is connected to those belonging to the two detectors
60    of the same row (or column) for forming 24 cm long strips, the sum of the
61    deposited energies in the strips forming a `long strip' is now calculated for
62    each event (gpucal.F subroutine) and it is stored in a hit only at the
63    end of the event (gutrev.F subroutine).
64    The output variables of the GPAMELA en-tuple are then filled in the vectors
65    ICAPLANE(NTHCAL), ICASTRIP(NTHCAL), ENESTRIP(NTHCAL) and ICAMOD(NTHCAL),
66    by a call to the GPDCAL subroutine:
67    -ICAPLANE(i) contains the number of hit plane;
68    -ICASTRIP(i) contains the number of hit strip;
69    -ICAMOD(i) can assume different values based on the number of times and
70               positions in which a `long strip' has been hit.
71    -ENESTRIP(i) contains the deposited energy in the hit strip;
72    where i is the number of hit (1<i<4224).
73    Note that in the calorimeter each hit is filled at the end of the event and
74    that there is a hit for each `long strip' hit from
75    the particle. This use of the hit structure is different for the other
76    detectors and it has been considered to avoid a too big number of hit in the
77    calorimeter due to the showers. Follows that NTHCAL, which is the
78    max number of hit in the calorimeter, is equal to 4224, the total
79    number of `long strips'. So, for each event, the real number of hit will
80    be less or equal to 4224.
81    ICAMOD(i) is an additional information that does not exist in the real
82    detector: if the strip i (i=1,32) of the module 1 or 2 or 3
83    is hit, the value of ICAMOD(i) is respectively incremented of 1, 100, 10000.
84    Analogously it is done, if it is the strip j (j=33,64) of the modules 4, 5
85    and 6 or if it is the strip k (k=65,96) of the modules 7, 8 and 9.
86    For example if we consider the hit 1 of an event, we could read:
87    ICASTRIP(1)=30, ICAPLANE(1)=21, ENESTRIP(1)=0.5E-03 and ICAMOD(1)=10001.
88    It means that the hit 1 contains the information that in the strip 30 of the
89    plane 21 has been deposited a total energy of 0.5E-03 GeV. In addition the
90    `long strip 30' has been hit two times, one in the first module and the
91    other in the third one.
92    
93    The energy deposited in the calorimeter is calculated in GeV.
94    
95    To store the hits in the calorimeter the subroutine GSAHIT is used instead of
96    GSCHIT.
97    
98    To retrieve the hit structure the call to the routine GPRHIT is done instead
99    of a call to the GFHITS subroutine.
100    
101    25 February 2003, Bari
102    
103    BUG found:
104    DCUTEAER, DCUTEAL, DCUTECE, DCUTECP, DCUTEFE, DCUTEG10C, DCUTEG10, DCUTEKAP,
105    DCUTEN2G, DCUTEROA, DCUTESCIN, DCUTESICA, DCUTETRAD, DCUTEW2,
106    DCUTEW, DCUTEXE variables missed in the commons: gpaer.inc, gpal.inc, gpce.inc,
107    gpcp.inc, gpfe.inc, gpg10c.inc, gpg10.inc, gpkap.inc, gpn2g.inc, gproa.inc,
108    gpscin.inc (obsolete), gpscint.inc, gpsica.inc, gptrad.inc, gpw2.inc, gpw.inc,
109    gpxe.inc, gpdaer.inc, gpdal.inc, gpdce.inc, gpdcp.inc, gpdfe.inc, gpdg10c.inc,
110    gpdg10.inc, gpdkap.inc, gpdn2g.inc, gpdroa.inc, gpdscin.inc, gpdsica.inc,
111    gpdtrad.inc, gpdw2.inc, gpdw.inc, gpdxe.inc.
112    They have been added in these commons and they have been initialized in the
113    GPSTM subroutine.
114    
115    Updated the special tracking parameters SICALO, TUNGA, KAOLINITE and G10C
116    in the subroutines gpsica.F, gpw2.F, gpw.F, gpce.F and gpg10c.F. They were
117    suggested by Mirko Boezio.
118    
119    Updated the value of the absorption length for silicon in the calorimeter
120    and tracker although this parameter is ignored by GEANT. For this reason
121    it was equal to the radiation length.
122    
123    Updated the relative positions of the calorimeter planes. The corrected
124    shifting are:
125    
126    first view: (Dxo,Dyo)=(0.10,0.05) cm
127    second view: (Dxo,Dyo)=(-0.05,0.10) cm
128    third view: (Dxo,Dyo)=(-0.10,-0.05) cm
129    fourth view: (Dxo,Dyo)=(0.05,-0.10) cm
130    
131  4 November 2002, Bari  4 November 2002, Bari
132    
133  CAS detectors distances modified  CAS detectors distances modified
# Line 161  TRACK COMMAND CALLED BY GPGARIN Line 267  TRACK COMMAND CALLED BY GPGARIN
267    
268  TRD IONIZATION ENERGY LOSS GENERATED NOW BY GARFIELD  TRD IONIZATION ENERGY LOSS GENERATED NOW BY GARFIELD
269     To generate the ionization in the TRD straw tubes the HEED program     To generate the ionization in the TRD straw tubes the HEED program
270     interfaced by GARFIELD is used (GEANT does not simulate the ionization     interfaced by GARFIELD is used (GEANT does not correctly simulate
271     in thin layer and in the gas, correctly). The idea is that GEANT tracks     the ionization in thin layer and in the gas). The idea is that GEANT
272     the particle in the gas and then passes the coordinates, translated in     tracks the particle in the gas and then passes the coordinates,
273     the DRS, to GARFIELD. The GARFIELD subroutines are called by GPUTRD.     translated in the DRS, to GARFIELD. The GARFIELD subroutines are
274     The energy loss and the number of clusters in TRD are stored in the     called by GPUTRD. The energy loss and the number of clusters in TRD
275     variables EGARTRD and NGARTRD of the CWN-tplu.     are stored in the variables EGARTRD and NGARTRD of the CWN-tplu.
276    
277   1 May 2001, Bari   1 May 2001, Bari
278    
# Line 245  NEW SEQUENCES ADDED: $XPRINTPLOT,$PRINTP Line 351  NEW SEQUENCES ADDED: $XPRINTPLOT,$PRINTP
351     The definition of the ITRSO detector has been changed in the GPSED routine:     The definition of the ITRSO detector has been changed in the GPSED routine:
352     NVTRD has been forced to 2 for compatibility with GPDTRD.     NVTRD has been forced to 2 for compatibility with GPDTRD.
353    
 3 april 2001, Bari  
   
   
354  28 march 2001, Bari  28 march 2001, Bari
355    
356     ITRSO has been defined as a sensitive detector in GSTMED routine and it has     ITRSO has been defined as a sensitive detector in GSTMED routine and it has
Legend:
Removed from v.3.3  
changed lines
  Added in v.3.4
  ViewVC Help
Powered by ViewVC 1.1.23