Space.f95
knows what points, lines, tracks, rectangles, etc.
are
Contains procedures to fill objects and get parameters
back. |
| Coordinate_type: |
X and Y coordinate. |
| Line_type: |
X0 and PHI, can be filled with
these parameters or any coordinate and PHI or two coordinates
(line connecting two points). Also tangent of a XYtrack
at given y. |
| XYTrack_type: |
a curved line, to be filled
with a line (tangent at Y=0) and the inverse radius. |
| Rectangle_type: |
X,Y coordinate for centre and
X,Y coordinate for pitch(=width) and length(=height). |
| Grid_type: |
a rectangle subdivided in nX times nY small
rectangles (recty), a bitmap specifies which recty
belongs to the pad. |
| getCentre: |
centre (coordinate) of a Pad_type. |
| Distance: |
calculate the distance between
2 objects. |
| FillLoc: |
fill the location of a Pad_type. |
| AllocBitMap: |
allocates the bit map for Grid_type. |
| FillBitMap: |
fills the bit map for Grid_type. |
| printGrid: |
prints the grid information
for Grid_type. |
| intTrackPad: |
integral of a track over a
pad. |
operators:
+
- * == =
|
partially defined for coordinates
and lines. |
Input files: |
| TPCfiles.txt: |
which MIDAS files will be processed.
F number: number of MIDAS files to be read,
must be given.
R nev1 nev2: range of events to be processed, running event number.
S nev1 nev2 nev3 ...: sample of events to be processed, MIDAS event
number.
If neither R nor S are given the full run is processed; range
and sample do not work if more than one file shall be processed.
*: comment, line ignored.
> MIDAS files: a list of MIDAS files should follow this line. |
| TPCinput.txt: |
steering cards, thresholds,
...
You should know how these parameters are used. There
are default values for all of them but they might be
useless. You might not use all parameters for your
analysis.
> keyword: the following line contains the value for keyword.
*: comment, line ignored. |
| TPClayout.txt: |
pad layout.
top: values for nPads,nGroups,nRows,nTbin,maxPinGroup,maxPinRow,maxGinRow
For rectangles: list of pad, group, row, centre position
along the row (along width), centre-position of the
row (along height), width and height for each pad.
For Grid_type in addition a grid number is given. The
grid information is given at the bottom: Grid number, number of columns and rows
in one line followed by the pattern. space and . mean empty,
every other sign means 'belongs to pad'. This is also an example for multiplexed
layout.
Apart from the pattern everything is read without format (i.e. spacing does not
matter). But there are no real comment lines, the number of lines skipped is
fixed. An example how to write the layout file. The pads,
groups and rows must be given from 1 to N, pads must be in order. If your input
data has groups (read-out channels) in the range from 0 to N-1, group 0 will
be called N when the data are read in. Please change your layout accordingly. |
| TPCpedestal.txt: |
pedestals for each group.
One comment line followed by a line for each group
which gives the value. |
| TPCftime.txt: |
fall times for each group;
format as for pedestals. |
| TPCrtime.txt: |
rise times for each group;
format as for pedestals. |
| TPCgain.txt: |
relative gain for each group;
format as for pedestals. |
| TPCbias.txt: |
bias for rows.
1st line: comment
2nd line: numbers of rows nR for which a bias
is given, number of x-values nX (should be
the same for all rows).
3rd line: list of nR row numbers, the first number is a dummy.
nX lines with values for: X (position within row), nR bias
values. |