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