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

Diff of /gpamela/history/v_100.txt

Parent Directory | Revision Log | View Patch Patch

-revision 3.1 by cafagna,
Thu Jul 11 16:01:59 2002 UTC
+revision 3.5 by pamela,
Tue Apr  6 10:33:46 2004 UTC
 Line 1
  #
- # $Id$
+ # $Id: v_100.txt,v 3.4 2003/12/17 11:32:50 pamela Exp $
+ #
+ # $Log: v_100.txt,v $
+ # Revision 3.4  2003/12/17 11:32:50  pamela
+ # CALO SIMULATION COMPLETED: geometry and special tracking parameters updated and simulation checked by a comparison with the Trieste's standalone Monte Carlo simulation
+ #
+ # Revision 3.3  2002/12/05 17:27:59  pamela
+ # New GARFIELD.GAR file added and GPAMELA.FFR cleaned and updated
+ #
+ # Revision 3.2  2002/12/05 10:17:42  pamela
+ # Update CAS and CALO geometries and positions. Makefile updated as well
+ #
+ # Revision 3.1.1.1  2002/07/11 16:01:59  cafagna
+ # First GPAMELA release on CVS
  #
- # $Log$
  #
  #CMZ :  3.00/00 11/02/2002  20.05.23  by  Unknown
  #CMZ :  2.03/00 06/11/2000  02.14.56  by  Francesco Cafagna
-Line 14
+Line 26
  #CMZ :  1.00/03 30/04/96  12.23.59  by  Francesco Cafagna
  #CMZ :  1.00/02 05/04/96  15.31.25  by  Francesco Cafagna
  #CMZ :  1.00/01 28/11/95  18.51.23  by  Francesco Cafagna
  #-- Author :    Francesco Cafagna   28/11/95
+March 2004, Bari
+ NON-REPRODUCIBILITY PROBLEM OF A GPAMELA RUN FIXED.
+ The non-reproducibility of a GPAMELA run was due to the random number
+ initialization in the GARFIELD code. In GARFIELD by default, the initial
+ seeds of the random number generators are always the same while the random
+ number generators are called a given number of times (determined by the
+ hour of the day) during the initialization phase (see init.f subroutine in
+ the GARFIELD code for details). Follows that different runs produce
+ different results without changing the initial seeds. To have identical
+ results in different runs, the GARFIELD program has to start typing the
+ noRNDM_initialisation switch. To avoid of specifying this switch by the user,
+ the GARFIELD package has been upgraded with a patch. In this way the problem
+ is partially solved because, now, the initial seeds of the random generators
+ in GARFIELD will be always the same even if the RNDM GEANT data card is
+ activated by the user for changing the initial seeds in the GPAMELA program.
+ Work is in progress for a more general correction of this problem.
+ Please, use the updated GARFIELD code released with the CVS version v4r1
+ to fix this problem.
+ RNDM ROUTINE REPLACED BY THE GRNDM ROUTINE IN GPXTR AND NPOISS.
+ The obsolete RNDM random number generator has been replaced by the GEANT
+ GRNDN routine in the gpxtr.F subroutine and in the npoiss.F function.
+ BUG FOUND AND FIXED: the set and detector calorimeter addresses (ISCAL
+ and IDCASI variables) used in GUTREV were respectively set to a fixed
+ values of 12 and 1. The correct values of these variables are stored in
+ the GPSED common when the set and the detector ZEBRA banks are filled
+ during a run. In general the values of the set and detector addresses
+ depend on the number of active detectors in a given run. ISCAL=12 and
+ IDCASI=1 are only right when all the detectors of GPAMELA are active.
+December 2003, Bari
+ CALORIMETER SIMULATION completed! The update of the geometry and of the
+ special tracking parameters and the tuning of the calorimeter have been
+ successfully done. A great quantity of simulated data have been produced
+ in the calorimeter for different particles (muons, electrons and pions)
+ and momenta (5 and 40 GeV/c) and the output data have been analyzed. The
+ distributions of the total energy deposited in the calorimeter and the
+ total number of strips hit have been compared with the respective
+ distributions produced by the Trieste's tuned standalone Monte Carlo
+ simulation program of the PAMELA calorimeter. The accord between the
+ two simulations is excellent. Many thanks to Mirko for his collaboration.
+ Working in progress on TRD. The GARFIELD interface to the HEED program is not
+ optimized to track particle with a charge greater than one and photons. The
+ program print a warning message to advise the user when it is the case.
+April 2003, Bari
+ The buffer size of each column of the GPAMELA Ntuple has been increased to
+and set equal to the record length, defined by a call to the HROPEN
+ routine.
+ Also the length of the common /PAWC/ (parameter NWPAW) has been increased
+ to 1.34E8, according to the rule that it has to be larger than the number
+ of columns times the buffer size.
+April 2003, Bari
+ The variables in the HIT STRUCTURE of the CALORIMETER and their way to be
+ filled have been changed according to the electronics system of the real
+ detector. In fact, because each silicon detector (module) consists of
+strips and each strip is connected to those belonging to the two detectors
+ of the same row (or column) for forming 24 cm long strips, the sum of the
+ deposited energies in the strips forming a `long strip' is now calculated for
+ each event (gpucal.F subroutine) and it is stored in a hit only at the
+ end of the event (gutrev.F subroutine).
+ The output variables of the GPAMELA en-tuple are then filled in the vectors
+ ICAPLANE(NTHCAL), ICASTRIP(NTHCAL), ENESTRIP(NTHCAL) and ICAMOD(NTHCAL),
+ by a call to the GPDCAL subroutine:
+ -ICAPLANE(i) contains the number of hit plane;
+ -ICASTRIP(i) contains the number of hit strip;
+ -ICAMOD(i) can assume different values based on the number of times and
+            positions in which a `long strip' has been hit.
+ -ENESTRIP(i) contains the deposited energy in the hit strip;
+ where i is the number of hit (1<i<4224).
+ Note that in the calorimeter each hit is filled at the end of the event and
+ that there is a hit for each `long strip' hit from
+ the particle. This use of the hit structure is different for the other
+ detectors and it has been considered to avoid a too big number of hit in the
+ calorimeter due to the showers. Follows that NTHCAL, which is the
+ max number of hit in the calorimeter, is equal to 4224, the total
+ number of `long strips'. So, for each event, the real number of hit will
+ be less or equal to 4224.
+ ICAMOD(i) is an additional information that does not exist in the real
+ detector: if the strip i (i=1,32) of the module 1 or 2 or 3
+ is hit, the value of ICAMOD(i) is respectively incremented of 1, 100, 10000.
+ Analogously it is done, if it is the strip j (j=33,64) of the modules 4, 5
+ and 6 or if it is the strip k (k=65,96) of the modules 7, 8 and 9.
+ For example if we consider the hit 1 of an event, we could read:
+ ICASTRIP(1)=30, ICAPLANE(1)=21, ENESTRIP(1)=0.5E-03 and ICAMOD(1)=10001.
+ It means that the hit 1 contains the information that in the strip 30 of the
+ plane 21 has been deposited a total energy of 0.5E-03 GeV. In addition the
+ `long strip 30' has been hit two times, one in the first module and the
+ other in the third one.
+ The energy deposited in the calorimeter is calculated in GeV.
+ To store the hits in the calorimeter the subroutine GSAHIT is used instead of
+ GSCHIT.
+ To retrieve the hit structure the call to the routine GPRHIT is done instead
+ of a call to the GFHITS subroutine.
+February 2003, Bari
+ BUG found:
+ DCUTEAER, DCUTEAL, DCUTECE, DCUTECP, DCUTEFE, DCUTEG10C, DCUTEG10, DCUTEKAP,
+ DCUTEN2G, DCUTEROA, DCUTESCIN, DCUTESICA, DCUTETRAD, DCUTEW2,
+ DCUTEW, DCUTEXE variables missed in the commons: gpaer.inc, gpal.inc, gpce.inc,
+ gpcp.inc, gpfe.inc, gpg10c.inc, gpg10.inc, gpkap.inc, gpn2g.inc, gproa.inc,
+ gpscin.inc (obsolete), gpscint.inc, gpsica.inc, gptrad.inc, gpw2.inc, gpw.inc,
+ gpxe.inc, gpdaer.inc, gpdal.inc, gpdce.inc, gpdcp.inc, gpdfe.inc, gpdg10c.inc,
+ gpdg10.inc, gpdkap.inc, gpdn2g.inc, gpdroa.inc, gpdscin.inc, gpdsica.inc,
+ gpdtrad.inc, gpdw2.inc, gpdw.inc, gpdxe.inc.
+ They have been added in these commons and they have been initialized in the
+ GPSTM subroutine.
+ Updated the special tracking parameters SICALO, TUNGA, KAOLINITE and G10C
+ in the subroutines gpsica.F, gpw2.F, gpw.F, gpce.F and gpg10c.F. They were
+ suggested by Mirko Boezio.
+ Updated the value of the absorption length for silicon in the calorimeter
+ and tracker although this parameter is ignored by GEANT. For this reason
+ it was equal to the radiation length.
+ Updated the relative positions of the calorimeter planes. The corrected
+ shifting are:
+ first view: (Dxo,Dyo)=(0.10,0.05) cm
+ second view: (Dxo,Dyo)=(-0.05,0.10) cm
+ third view: (Dxo,Dyo)=(-0.10,-0.05) cm
+ fourth view: (Dxo,Dyo)=(0.05,-0.10) cm
+November 2002, Bari
+ CAS detectors distances modified
+ The distances between the CAS detectors have been modified based on the
+ latest CAD drawings.
+November 2002, Bari
+ CALORIMETER geometry upgrade
+ The volumes CAPD and CAAD have been taken off from the calorimeter.
+ In addition the logical tree has been slightly changed to make the shifts of
+ the silicon planes into the calorimeter box easier, i.e. the CAPL volume,
+ which was made of the CASI, CAKP, CAGL, C10C and CAKA volumes, has
+ been split up in the volumes CANS and CAPL. Now CANS is made of the CAKP,
+ CAGL, C10C and CAKA volumes while CAPL contains the CASI volume, that has to
+ be shifted as a function of the vertical position in the calorimeter. Also the
+ dimensions of some volumes have been upgraded, including the external ones:
+ CALB and CALS. CALS is an aluminum box of dimensions: 48.4*48.4*21.278 cm^3,
+ having side-walls 1 cm thick and a bottom of 1 mm. The real box is more
+ complicated and the configuration of the bottom should be upgraded if we want
+ a reliable description of the event in the S4 scintillator.
+October 2002, Stockholm
+ ANTICOINC. GEOMETRY UPGRADE
+    The AC geometry has been updated. The top AC scintillator (CAT) now
+    consists of 1 single sheet of scintillator with a hole in the middle
+    and the correct geometry(*). The side AC scintillators (CAS) also
+    have the correct shape. The AC scintillators are placed in aluminum
+    boxes with plastic rims inside. For these rims a 'new' material, PLAS,
+    was defined. PLAS has all the characteristics of SCIN but is
+    non-sensitive. No PMTs or PMT holders have been modelled.
+    (*)-The interfaces on CAT where the PMTs should be located are
+        slightly different from the real case.
 February 2002, Bari
  MACRO CLEAN-UP
-Line 116 
 TRACK COMMAND CALLED BY GPGARIN
+Line 303 
 TRACK COMMAND CALLED BY GPGARIN
  TRD IONIZATION ENERGY LOSS GENERATED NOW BY GARFIELD
     To generate the ionization in the TRD straw tubes the HEED program
-    interfaced by GARFIELD is used (GEANT does not simulate the ionization
+    interfaced by GARFIELD is used (GEANT does not correctly simulate
-    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
-    the particle in the gas and then passes the coordinates, translated in
+    tracks the particle in the gas and then passes the coordinates,
-    the DRS, to GARFIELD. The GARFIELD subroutines are called by GPUTRD.
+    translated in the DRS, to GARFIELD. The GARFIELD subroutines are
-    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
-    variables EGARTRD and NGARTRD of the CWN-tplu.
+    are stored in the variables EGARTRD and NGARTRD of the CWN-tplu.
 May 2001, Bari
-Line 200 
 NEW SEQUENCES ADDED: $XPRINTPLOT,$PRINTP
+Line 387 
 NEW SEQUENCES ADDED: $XPRINTPLOT,$PRINTP
     The definition of the ITRSO detector has been changed in the GPSED routine:
     NVTRD has been forced to 2 for compatibility with GPDTRD.
-april 2001, Bari
 march 2001, Bari
     ITRSO has been defined as a sensitive detector in GSTMED routine and it has

 Legend:



Removed from v.3.1
 


changed lines


 
Added in v.3.5
 Legend:



Removed from v.3.1
 


changed lines


 
Added in v.3.5
-Removed from v.3.1
+Added in v.3.5

	ViewVC Help
Powered by ViewVC 1.1.23