/[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.2 by pamela, Thu Dec 5 10:17:42 2002 UTC revision 3.11 by cafagna, Thu May 11 23:53:15 2006 UTC
# Line 1  Line 1 
1    
2  #  #
3  # $Id: v_100.txt,v 3.1.1.1 2002/07/11 16:01:59 cafagna Exp $  # $Id: v_100.txt,v 3.10 2006/04/10 11:07:43 cafagna Exp $
4  #  #
5  # $Log: v_100.txt,v $  # $Log: v_100.txt,v $
6    # Revision 3.10  2006/04/10 11:07:43  cafagna
7    # GEN data card updated, ZDGEN added
8    #
9    # Revision 3.9  2005/12/14 03:34:40  cafagna
10    # An update of the history and inform readme files.
11    #
12    # Revision 3.8  2005/12/14 03:16:08  cafagna
13    # Neutron detector added. Geometry and GPCALOR package
14    #
15    # Revision 3.7  2005/10/18 08:24:35  cafagna
16    # History updated
17    #
18    # Revision 3.6  2005/07/25 11:53:21  cafagna
19    # Several updates. See history for details
20    #
21    # Revision 3.5  2004/04/06 10:33:46  pamela
22    # NON-REPRODUCIBILITY problem of a GPAMELA RUN fixed; bug found and fixed filling in the hit structure of the calorimeter
23    #
24    # Revision 3.4  2003/12/17 11:32:50  pamela
25    # CALO SIMULATION COMPLETED: geometry and special tracking parameters updated and simulation checked by a comparison with the Trieste's standalone Monte Carlo simulation
26    #
27    # Revision 3.3  2002/12/05 17:27:59  pamela
28    # New GARFIELD.GAR file added and GPAMELA.FFR cleaned and updated
29    #
30    # Revision 3.2  2002/12/05 10:17:42  pamela
31    # Update CAS and CALO geometries and positions. Makefile updated as well
32    #
33  # Revision 3.1.1.1  2002/07/11 16:01:59  cafagna  # Revision 3.1.1.1  2002/07/11 16:01:59  cafagna
34  # First GPAMELA release on CVS  # First GPAMELA release on CVS
35  #  #
# Line 17  Line 45 
45  #CMZ :  1.00/03 30/04/96  12.23.59  by  Francesco Cafagna  #CMZ :  1.00/03 30/04/96  12.23.59  by  Francesco Cafagna
46  #CMZ :  1.00/02 05/04/96  15.31.25  by  Francesco Cafagna  #CMZ :  1.00/02 05/04/96  15.31.25  by  Francesco Cafagna
47  #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
48  #-- Author :    Francesco Cafagna   28/11/95  #-- Author :    Francesco Cafagna   28/11/95
49    
50    May 2006, Bari & Florence
51    
52    CAL HIT STRUCTURE BUGS FIXED
53    
54       The maximum number of hit is now different for the two hit
55       structures: CALST and CALI. Vectors inizialization and HBOOK
56       ntple booking have been updated. The GPDCAL routine has been fixed
57       so to handle the case in wich hits stored are more than the maximum
58       number of hit.
59       In this case in the ntple up to the maximum number of hits will be stored.
60    
61    Mar 2006, Bari
62    
63    GEN DATA CARD UPDATED
64    
65       To enable generation on a surface perpendicular to the XY plane,
66       GEN gata card has been updated addingh a new parameter: ZDGEN. This is
67       the dimension, along Z axis , of the generation surface. The Z
68       position will be randomply chosen according to: Z= ZDGEN*RNDM_NUMBER +
69       ZGEN, i.e. Z= GEN(6)*RNDM_NOMBER + GEN(3).
70    
71    Nov 2005, Bari
72    
73    GUHADR AND GUPHAD UPDATED
74    
75       To use GCALOR package the hadronic routines have been updated. The
76       inizialization routine call CALSIG, while the other calls GCALOR.
77    
78    NEW GPKEY ADDED: GPCALOR
79    
80       This logical has been added to enable the GCALOR package. This flag
81       is set to true in GPDAT if the data card: HPAK, is set to
82       'GCAL'. The gpkey.inc has been update accordingly.
83    
84      
85    NEUTRON DETECTOR ADDED. NEW DIR: GPND
86    
87       The neutron detector has been added. At the moment it is just the
88       geometry. The directory structure of the repository has been
89       updated as well. Dimensions has been taken from picture and
90       literature. A full upgrade to the drawing is needed.
91    
92    GCALOR PACKAGE ADDED. NEW DIRs: GPCALOR, GPCALORDES
93    
94       GCALOR package contins the CALOR simulation code and an interface
95       to use it in GEANT. The important feature for us is the usage of
96       the MICAP code. This is facused on the low energy neutron
97       simulation. for details see:
98       http://www.staff.uni-mainz.de/zeitnitz/Gcalor/gcalor.html
99       This package should be distributed with the GEANT library but is
100       not up to date. I did download the latest release and stored into
101       gpcalor directory of the gpamela tree.
102       Then I did clean up the code substituting the explicit inclusion of
103       the commons with a #include cpp directive. In parallel I did
104       extract the commons to include files having the same common name. I
105       did store the include files into a newly created directory:
106       gpcalordes.
107       The Makefile has been updated accordingly.
108       Please note that to avoid conflict with CRENLIB distribution the gcalor source file has been named gpcalor.F
109       NOTE: There are still problem due to different common sizes. In
110       particular the common MICFIL is maller in the geant library
111       libgeant.a . There the subroutines: gmorin, gmxsec, gmplxs, are
112       present and linked using a wrong version of the common. This still needs to be debuged.
113       NOTE2: The auxiliary files with the cross sections: chetc.dat.gz
114       and xsneut.dat.gz, have been added to the aux directory and moved
115       to the working directory, i.e. GPAMELA_BIN. The GCALOR routine will
116       look for CERN_ROOT environment variable. If found files are
117       searched there at first, then in the working directory. A fool
118       proof policy has to be implemented to avoid problem with
119       synchronization fo these files.
120      
121    
122    The GCALOR package
123    May 2005, Bari
124    
125    Some updates on the latest modification done in the past year.
126    
127    NEW DATA CARD ADDED: HFSF
128    
129       To define a policy for the random number initial seeds
130       definition. Using this card is possible to override GEANT seeds
131       defined via NRDM card. The policy is selected according to the
132       values:
133    
134       - 1: The seeds are initialized to the initial values found in a user
135            defined file or the default file: INPUTSEED.DAT
136      
137       - 2: The seeds are initialized to the final values found in a user defined
138            file or the default file: INPUTSEED.DAT
139    
140       The case 1 must be used in case the user needs to reproduce the
141       random chain of a previous run. In this case the user can save the
142       initial seeds, used in the run he would like to reproduce, in a
143       binary file and pass the filename to the program using the *FLSF
144       data card. In case the user file is not specified the default
145       INPUTSEED.DAT will be used.
146      
147       The case 2 must be used in case the user needs to chain several
148       GPAMELA run and likes to be sure he is starting the random
149       generator using the right sequence. In this case the user must
150       specify an input binary file using the *FLSF data card, otherwise
151       the INPUTSEED.DAT file will be used.
152    
153    NEW DATA CARD ADDED: *FSFI
154    
155       Using this card the user can specify the logical unit and name of
156       the file storing the initial seeds to be used to initialize the
157       random number generator. This file must be a FORTRAN binary one
158       storing four integer numbers. The first two are the number to be
159       used in the case: HFSF=1, the other two will be used in the case:
160       HFSF=2. This file can be one created by GPAMELA or by the user
161       filled with his own seeds. For this purpose an utility program:
162       writeseeds.f, has been added in the aux directory.  In case the
163       *FSFI card is not specified the default values: 24 and INPUTSEEDS.DAT, will
164       be used as LUN and file name respectively.
165      
166    NEW DATA CARD ADDED: *LSFI
167    
168       Using this card the user can specify the logical unit and name of
169       the file storing the first and last seeds used in the GPAMELA
170       run. This file is a FORTRAN binary one. This file can be used as
171       input one specifying it in the *FSFI data card of the next GPAMELA
172       run.  In case the *LSFI card is not specified the default values: 26
173       and HBOOKFILENAME.DAT (as sepified in *HFI), will be used as LUN
174       and file name respectively.
175      
176    NEW UTILITY PROGRAMS ADDED: writeseeds.f, readseeds.f
177    
178       These new programs have been added in the aux directory. Using these a
179       user defined seed file can be created and re-read.
180    
181    NEW VOLUMES ADDED: MSHE, BSPH; PRESSURIZED CONTAINER ADDED
182    
183       Alexey Bakaldin, in MEPHI, did add the PAMELA pressurized container to
184       the simulation. He did defined new volumes filled with aluminum and
185       placed inside the mother volume. Positions have been fine tuned by
186       Marialuigia Ambriola and compared to the CAD drawings.
187       Two new volumes have been added to simulate the container:
188       - MSHE, a tube simulating the middle part of the container
189       - BSPH, the spherical bottom part of the container
190    
191       To better simulate the upper part the SHEL volume has been modified
192       into a cone. Dimentions of the top cover: TSPH, have been modified
193       accordingly.
194    
195    DETECTOR POSITIONS REVIEWED
196    
197       All detector Z positions have been reviewd to fit into the
198       simulated pressurized container.
199    
200    TRD GEOMETRY AND CALIBRATION REVIEWD
201    
202       The TRD geometry has been deeply reviewed. Using the CAD drawings
203       the carbon fiber frames have been simulated and radiator dimentions
204       corrected. For this reason the calibration done on the beam tests
205       has been revied and new sets of calibration constants calculated
206       comparing the beam test data with the GPAMELA results. The new
207       constants are about 3% larger than the previous ones.
208      
209    TRACKER GEOMETRY REVIEWED. NEW VOLUME DEFINED: THBP, TPAS, TPAI
210      
211       Thanks to Lorenzo Bonechi for the drawings and explanations. Now the
212       hybrd cards have been put into the simulation and the geometry updated
213       considering the dead zones in the silicon detectors. The hybrid zone
214       has been simulated as well. At the moment the hybrid is simulated as
215       a G10 plates. The full height of the tracker magnet has been
216       reviewed as well.
217    
218       The tracker ladder is now simulated inside a nitrogen box: TPAS,
219       placed inside an aluminum frame: TRPB. Each silicon ladder has been
220       simulated using two silicon blocks: TRSL, into each of this block a
221       smaller silicon detector: TPAI, has been placed inside the larger
222       silicon block TRSL. In this way the subdivided silicon ladder can
223       be upgraded with an indipendend roto-translation for each sensor.
224      
225       The TRPB aluminum frame has been enlarged to fit the external
226       magnet canister frame.
227      
228       The last plane has been flipped with a 180 degree rotation around
229       the X axis.
230      
231    TRACKER HIT STRUCTURE REVIEWED
232    
233       Taking into account the new version of the tracker geometry, the hit
234       structure for this detector has been revied.
235    
236    CALORIMETER GEOMETRY REVIEWED
237    
238       Marco Albi reviewed the calorimeter dimentions and positioning.
239    
240    
241    29 March 2004, Bari
242    
243    NON-REPRODUCIBILITY PROBLEM OF A GPAMELA RUN FIXED.
244       The non-reproducibility of a GPAMELA run was due to the random number
245       initialization in the GARFIELD code. In GARFIELD by default, the initial
246       seeds of the random number generators are always the same while the random
247       number generators are called a given number of times (determined by the
248       hour of the day) during the initialization phase (see init.f subroutine in
249       the GARFIELD code for details). Follows that different runs produce
250       different results without changing the initial seeds. To have identical
251       results in different runs, the GARFIELD program has to start typing the
252       noRNDM_initialisation switch. To avoid of specifying this switch
253       by the user,
254       the GARFIELD package has been upgraded with a patch. In this way the problem
255       is partially solved because, now, the initial seeds of the random generators
256       in GARFIELD will be always the same even if the RNDM GEANT data card is
257       activated by the user for changing the initial seeds in the GPAMELA program.
258       Work is in progress for a more general correction of this problem.
259       Please, use the updated GARFIELD code released with the CVS version v4r1
260       to fix this problem.  
261    
262    
263    RNDM ROUTINE REPLACED BY THE GRNDM ROUTINE IN GPXTR AND NPOISS.
264       The obsolete RNDM random number generator has been replaced by the GEANT
265       GRNDN routine in the gpxtr.F subroutine and in the npoiss.F function.
266    
267    BUG FOUND AND FIXED: the set and detector calorimeter addresses (ISCAL
268       and IDCASI variables) used in GUTREV were respectively set to a fixed
269       values of 12 and 1. The correct values of these variables are stored in
270       the GPSED common when the set and the detector ZEBRA banks are filled
271       during a run. In general the values of the set and detector addresses
272       depend on the number of active detectors in a given run. ISCAL=12 and
273       IDCASI=1 are only right when all the detectors of GPAMELA are active.
274    
275    9 December 2003, Bari
276    
277       CALORIMETER SIMULATION completed! The update of the geometry and of the
278       special tracking parameters and the tuning of the calorimeter have been
279       successfully done. A great quantity of simulated data have been produced
280       in the calorimeter for different particles (muons, electrons and pions)
281       and momenta (5 and 40 GeV/c) and the output data have been analyzed. The
282       distributions of the total energy deposited in the calorimeter and the
283       total number of strips hit have been compared with the respective
284       distributions produced by the Trieste's tuned standalone Monte Carlo
285       simulation program of the PAMELA calorimeter. The accord between the
286       two simulations is excellent. Many thanks to Mirko for his collaboration.
287    
288       Working in progress on TRD. The GARFIELD interface to the HEED program is not
289       optimized to track particle with a charge greater than one and photons. The
290       program print a warning message to advise the user when it is the case.
291    
292    18 April 2003, Bari
293    
294       The buffer size of each column of the GPAMELA Ntuple has been increased to
295       4096 and set equal to the record length, defined by a call to the HROPEN
296       routine.
297       Also the length of the common /PAWC/ (parameter NWPAW) has been increased
298       to 1.34E8, according to the rule that it has to be larger than the number
299       of columns times the buffer size.
300    
301    10 April 2003, Bari
302    
303       The variables in the HIT STRUCTURE of the CALORIMETER and their way to be
304       filled have been changed according to the electronics system of the real
305       detector. In fact, because each silicon detector (module) consists of
306       32 strips and each strip is connected to those belonging to the two detectors
307       of the same row (or column) for forming 24 cm long strips, the sum of the
308       deposited energies in the strips forming a `long strip' is now calculated for
309       each event (gpucal.F subroutine) and it is stored in a hit only at the
310       end of the event (gutrev.F subroutine).
311       The output variables of the GPAMELA en-tuple are then filled in the vectors
312       ICAPLANE(NTHCAL), ICASTRIP(NTHCAL), ENESTRIP(NTHCAL) and ICAMOD(NTHCAL),
313       by a call to the GPDCAL subroutine:
314       -ICAPLANE(i) contains the number of hit plane;
315       -ICASTRIP(i) contains the number of hit strip;
316       -ICAMOD(i) can assume different values based on the number of times and
317                  positions in which a `long strip' has been hit.
318       -ENESTRIP(i) contains the deposited energy in the hit strip;
319       where i is the number of hit (1<i<4224).
320       Note that in the calorimeter each hit is filled at the end of the event and
321       that there is a hit for each `long strip' hit from
322       the particle. This use of the hit structure is different for the other
323       detectors and it has been considered to avoid a too big number of hit in the
324       calorimeter due to the showers. Follows that NTHCAL, which is the
325       max number of hit in the calorimeter, is equal to 4224, the total
326       number of `long strips'. So, for each event, the real number of hit will
327       be less or equal to 4224.
328       ICAMOD(i) is an additional information that does not exist in the real
329       detector: if the strip i (i=1,32) of the module 1 or 2 or 3
330       is hit, the value of ICAMOD(i) is respectively incremented of 1, 100, 10000.
331       Analogously it is done, if it is the strip j (j=33,64) of the modules 4, 5
332       and 6 or if it is the strip k (k=65,96) of the modules 7, 8 and 9.
333       For example if we consider the hit 1 of an event, we could read:
334       ICASTRIP(1)=30, ICAPLANE(1)=21, ENESTRIP(1)=0.5E-03 and ICAMOD(1)=10001.
335       It means that the hit 1 contains the information that in the strip 30 of the
336       plane 21 has been deposited a total energy of 0.5E-03 GeV. In addition the
337       `long strip 30' has been hit two times, one in the first module and the
338       other in the third one.
339    
340       The energy deposited in the calorimeter is calculated in GeV.
341    
342       To store the hits in the calorimeter the subroutine GSAHIT is used instead of
343       GSCHIT.
344    
345       To retrieve the hit structure the call to the routine GPRHIT is done instead
346       of a call to the GFHITS subroutine.
347    
348    25 February 2003, Bari
349    
350    BUG found:
351       DCUTEAER, DCUTEAL, DCUTECE, DCUTECP, DCUTEFE, DCUTEG10C, DCUTEG10, DCUTEKAP,
352       DCUTEN2G, DCUTEROA, DCUTESCIN, DCUTESICA, DCUTETRAD, DCUTEW2,
353       DCUTEW, DCUTEXE variables missed in the commons: gpaer.inc, gpal.inc, gpce.inc,
354       gpcp.inc, gpfe.inc, gpg10c.inc, gpg10.inc, gpkap.inc, gpn2g.inc, gproa.inc,
355       gpscin.inc (obsolete), gpscint.inc, gpsica.inc, gptrad.inc, gpw2.inc, gpw.inc,
356       gpxe.inc, gpdaer.inc, gpdal.inc, gpdce.inc, gpdcp.inc, gpdfe.inc, gpdg10c.inc,
357       gpdg10.inc, gpdkap.inc, gpdn2g.inc, gpdroa.inc, gpdscin.inc, gpdsica.inc,
358       gpdtrad.inc, gpdw2.inc, gpdw.inc, gpdxe.inc.
359       They have been added in these commons and they have been initialized in the
360       GPSTM subroutine.
361    
362       Updated the special tracking parameters SICALO, TUNGA, KAOLINITE and G10C
363       in the subroutines gpsica.F, gpw2.F, gpw.F, gpce.F and gpg10c.F. They were
364       suggested by Mirko Boezio.
365    
366       Updated the value of the absorption length for silicon in the calorimeter
367       and tracker although this parameter is ignored by GEANT. For this reason
368       it was equal to the radiation length.
369    
370       Updated the relative positions of the calorimeter planes. The corrected
371       shifting are:
372    
373       first view: (Dxo,Dyo)=(0.10,0.05) cm
374       second view: (Dxo,Dyo)=(-0.05,0.10) cm
375       third view: (Dxo,Dyo)=(-0.10,-0.05) cm
376       fourth view: (Dxo,Dyo)=(0.05,-0.10) cm
377    
378  4 November 2002, Bari  4 November 2002, Bari
379    
380  CAS detectors distances modified  CAS detectors distances modified
381    
382  The distances between the CAS detectors has been modified based on the     The distances between the CAS detectors have been modified based on the
383  latest CAD drawings.     latest CAD drawings.
384    
385  2 November 2002, Bari  2 November 2002, Bari
386    
387  CALORIMETER geometry upgrade  CALORIMETER geometry upgrade
388    
389  The volumes CAPD and CAAD have been taken off from the calorimeter.     The volumes CAPD and CAAD have been taken off from the calorimeter.
390  In addition the logical tree has been slightly changed to make the shifts of     In addition the logical tree has been slightly changed to make the shifts of
391  the silicon planes into the calorimeter box easier, i.e. the CAPL volume,     the silicon planes into the calorimeter box easier, i.e. the CAPL volume,
392  which was made of the CASI, CAKP, CAGL, C10C and CAKA volumes, has     which was made of the CASI, CAKP, CAGL, C10C and CAKA volumes, has
393  been split up in the volumes CANS and CAPL. Now CANS is made of the CAKP,     been split up in the volumes CANS and CAPL. Now CANS is made of the CAKP,
394  CAGL, C10C and CAKA volumes while CAPL contains the CASI volume, that has to     CAGL, C10C and CAKA volumes while CAPL contains the CASI volume, that has to
395  be shifted as a function of the vertical position in the calorimeter. Also the     be shifted as a function of the vertical position in the calorimeter. Also the
396  dimensions of some volumes have been upgraded, including the external ones:     dimensions of some volumes have been upgraded, including the external ones:
397  CALB and CALS. CALS is an aluminum box of dimensions: 48.4*48.4*21.278 cm^3,     CALB and CALS. CALS is an aluminum box of dimensions: 48.4*48.4*21.278 cm^3,
398  having side-walls 1 cm thick and a bottom of 1 mm. The real box is more     having side-walls 1 cm thick and a bottom of 1 mm. The real box is more
399  complicated and the configuration of the bottom should be upgraded if we want     complicated and the configuration of the bottom should be upgraded if we want
400  a reliable description of the event in the S4 scintillator.     a reliable description of the event in the S4 scintillator.
401    
402  22 October 2002, Stockholm  22 October 2002, Stockholm
403    
# Line 158  TRACK COMMAND CALLED BY GPGARIN Line 514  TRACK COMMAND CALLED BY GPGARIN
514    
515  TRD IONIZATION ENERGY LOSS GENERATED NOW BY GARFIELD  TRD IONIZATION ENERGY LOSS GENERATED NOW BY GARFIELD
516     To generate the ionization in the TRD straw tubes the HEED program     To generate the ionization in the TRD straw tubes the HEED program
517     interfaced by GARFIELD is used (GEANT does not simulate the ionization     interfaced by GARFIELD is used (GEANT does not correctly simulate
518     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
519     the particle in the gas and then passes the coordinates, translated in     tracks the particle in the gas and then passes the coordinates,
520     the DRS, to GARFIELD. The GARFIELD subroutines are called by GPUTRD.     translated in the DRS, to GARFIELD. The GARFIELD subroutines are
521     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
522     variables EGARTRD and NGARTRD of the CWN-tplu.     are stored in the variables EGARTRD and NGARTRD of the CWN-tplu.
523    
524   1 May 2001, Bari   1 May 2001, Bari
525    
# Line 242  NEW SEQUENCES ADDED: $XPRINTPLOT,$PRINTP Line 598  NEW SEQUENCES ADDED: $XPRINTPLOT,$PRINTP
598     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:
599     NVTRD has been forced to 2 for compatibility with GPDTRD.     NVTRD has been forced to 2 for compatibility with GPDTRD.
600    
 3 april 2001, Bari  
   
   
601  28 march 2001, Bari  28 march 2001, Bari
602    
603     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.2  
changed lines
  Added in v.3.11
  ViewVC Help
Powered by ViewVC 1.1.23