/[PAMELA software]/yoda/techmodel/forroutines/tracker/common/commontracker.f
ViewVC logotype

Contents of /yoda/techmodel/forroutines/tracker/common/commontracker.f

Parent Directory Parent Directory | Revision Log Revision Log

Revision 6.0 - (show annotations) (download)
Tue Feb 7 17:11:10 2006 UTC (18 years, 11 months ago) by kusanagi
Branch: MAIN
CVS Tags: yodaPreTermistors2_1/00, YODA6_2/01, YODA6_2/00, YODA6_3/19, YODA6_3/18, YODA6_3/13, YODA6_3/12, YODA6_3/11, YODA6_3/10, YODA6_3/17, YODA6_3/16, YODA6_3/15, YODA6_3/14, YODA6_3/06, YODA6_1/00, YODA6_0/00, YODA6_3/04, YODA6_3/05, YODA6_3/20, YODA6_3/07, YODA6_3/00, YODA6_3/01, YODA6_3/02, YODA6_3/03, YODA6_3/08, YODA6_3/09, yodaPreTermistores2_0/00, HEAD
Changes since 1.1: +0 -0 lines 
Several new features in this revision:
a) all the packets are conform to the Mass Memory Format specifications (http://people.roma2.infn.it/~cpu/Mass_Memory_Format.html)
b) unpacking either using the old files structure OR the new one file unpacking.
c) parametrized root files compression factor
d) deleting of the following packet: TofTest, TrkTest, TrkEvent.
e) the Tracker routines now work without the use of temp files.

The point a) allow Yoda to unpack in the root file all the packets generated by the CPU. According to the MassMemoryFormat; that is three possible data are available:

1) almost explicit structure of the packet (like for Log, Tracker, Mcmd, etc....);
2) dummy data collection structure (InitHeader, InitTrailer, CalibHeader, CalibTrailer);
3) just the data of the packet (almost all Alarm and Init procedures). The class regarding this packets have only one parameters, a TArrayC class, which contain the data-block included in the packet (tat is the data below the packet Header).

The point b) has been implemented as a consequence of an agreement about a more compact structure of the unpacked data. Up to now the structure of each unpacked data consisted of a folder, named after the packet type, and three files: xxx.Header.root, xxx.NamePacket.root, xxx.Registry.root.
Starting from this release YODA, by default will unpack the data in a unique root file. The structure of this file will consist of:
- several TTree(s) named after the packet type;
- into each TTree are foreseen three TBranche(s):
    - 'Header'  (the old xxx.Header.root file)
    - 'NameOfThePacket' (the old xxx.Event.root file or the xxx.Event.DETECTOR.root)
    - 'Registry' (the old xxx.Registry.root file)

Anyway is still possible, but deprecated, to unpack using the old structure, passing to the "yoda" command the optional parameter "-multifile"

The point c) has been implemented because is well know that writing time in a TTree is as much fast as much lower is the compression factor for the root file; anyway for a PAMELA dat file, a compression equal to 0 will generate a root file which will be more than two times the original size. To modify the compression parameter just add the optional parameter "-c [0-9]" to the yoda command line.
1 ************************************************************************
2 *
3 * Common commontracker.f
4 *
5 * contains tracker general variables definitions
6 *
7 * to be included in:
8 * - ../readraw/readraw.F
9 * - ../reduction/reduction.f
10 * - ../reduction/fillpedsig.f
11 * - ../reduction/filladc.f
12 * - ../reduction/cncomp.f
13 * - ../reduction/cnoise.f
14 * - ../reduction/cutcn.f
15 * - ../analysis/preanalysis.f
16 * - ../analysis/analysis.f
17 * - ../align/align.f
18 * - ../magnet/read_B.f
19 * - !???
20 *
21 * parameters:
22 * - !???
23 *
24 *************************************************************************
25
26
27 c------------------------------------------------------------------------
28 c
29 c HBOOK initialization variable
30 c
31 c------------------------------------------------------------------------
32 c$$$
33 c$$$c parameter (NWPAWC=6500000)
34 c$$$ INTEGER HMEM
35 c$$$ parameter (NWPAWC=8500000)
36 c$$$ common/PAWC/HMEM(NWPAWC)
37 c$$$
38
39 c------------------------------------------------------------------------
40 c
41 c ntuples id numbers and parameters
42 c
43 c------------------------------------------------------------------------
44 c$$$
45 c$$$ parameter (ntp_level0=20) !LEVEL0
46 c$$$ parameter (ntp_level1=21) !LEVEL1
47 c$$$ parameter (ntp_level2=22) !LEVEL2
48
49
50 c parameter (nclstrmax=1000) !maximum number of clusters per event
51 parameter (nclstrmax=500)
52 parameter (nclstrp=17) !maximum number of strips to be checked for
53 ! inclusion in the cluster
54 parameter (maxlength=nclstrmax*nclstrp) !maximum number of strip belonging
55 ! to clusters for the whole event
56
57
58 c------------------------------------------------------------------------
59 c
60 c spectrometer parameters
61 c
62 c------------------------------------------------------------------------
63
64 parameter (nviews=12) !number of views
65 parameter (nplanes=nviews/2) !number of planes
66 parameter (nladders_view=3) !number of ladders per view
67 parameter (nva1_ladder=8) !number of VA1s per ladder (per side)
68 parameter (nstrips_va1=128) !number of strips per VA1
69
70 parameter (nstrips_ladder=nstrips_va1*nva1_ladder) !number of strips per ladder
71 parameter (nva1_view=nva1_ladder*nladders_view) !number of VA1s per view
72 parameter (nstrips_view=nstrips_va1*nva1_view) !number of strips per view
73 parameter (nva1=nva1_view*nviews) !number of VA1s
74 parameter (nstrips=nstrips_va1*nva1) !number of strips
75
76 parameter (pitchX=51.) !strip pitch in um
77 parameter (pitchY=66.5)
78
79 parameter (SiDimX=53330.) !Si sensor dimensions in um
80 parameter (SiDimY=70000.)
81
82 * edges of the sensitive areas, in X and Y
83 parameter (edgeX_l=731.5) ! X side
84 parameter (edgeX_r=731.5) !
85 parameter (edgeX_u=900.) !
86 parameter (edgeX_d=1117.) !
87 parameter (edgeY_l=985.) ! Y side
88 parameter (edgeY_r=985.5) !
89 parameter (edgeY_u=1221.) !
90 parameter (edgeY_d=894.) !
91
92
93 parameter (edgeX=edgeX_l) !distance of the first strip from the Si sensor
94 parameter (edgeY=edgeY_l) ! edge in um. NB while X strips a simmetrically
95 ! arranged respect to the Si sensor centre
96 ! (731.5 um on both sides), Y strips are not
97 ! centered: 985.5 um is the distance of the first
98 ! strip on the hybrid side, 985 um is the one on
99 ! the other side
100 parameter (glue=30.) !distance between the two sensors in a ladder in um
101
102
103
  ViewVC Help
Powered by ViewVC 1.1.23