One of the important measurements of BRAHMS is single
particle yields and cross-section. Two major ingredients
for
the calculations are Data from the
experiment and the
Weighting Factors come from
acceptance, physics processes
(decay, multiple scattering...), and hardware and software
inefficiencies associated with the observables. In addition,
information on the beam luminosities, trigger normalizations
are required to calulate cross-section. Current status
of
preparations for BRAHMS data analysis is described.
The status of data reconstruction software (tracking, pid...)
is
not discussed here.
Data
Event (Track) Weight
1. The p-theta boundary and phi (azimuthal)
acceptance both can be either
analytically
approximated (E802 and E866 HH) or numerically
estimated using MC
(E866 FS).
Since the geometry
of BRAHMS FS is rather non-trivial to be
approximated analytically,
I propose to use Monte-Carlo to calculate
boundaries.
2. Since the vertex position is not
fixed (expected interaction sigma =
15 - 25 cm?), the
p-theta boundary should be calculated as a function
of z. (See figures
of "acceptance vs z" for MRS
90 degree for pi+ ,
pi-
, MRS
35 degree for pi+ , pi-
, FS
2.3 degree pi+ , and pi-
.)
3. Since the vertex position varies
in z, the boundaries
for p-theta-z
has to be estimated for the each experimental settings.
Assuming +-15
to 20 cm is the interaction region we are interested
in, the
variation of the acceptance on z can be 10-20% depending
on the angle.
The acceptance is calculated using root histogram
operations for
each bins. Since we have all "final" detector
dimensions including
TOFW, I'll soon start production of the acceptance
maps.
Initially the map will have a information of (output/input) in
small bin sizes
(y: 0.005 - 0.01, p: 50 - 100 MeV).
4. Reconstructing pt spectra has
been exercised using central
Fritiof/GEANT
data. Since the pid is not fully functional yet,
the spectra
reconstructed was for h+. The difference between
the acceptance
corrected reconstructed spectra and the initial
input is
0-30%.
5. Communication between acceptance
maps and the database has to be
done.
2. Hardware ineffciency
TPC and DC inefficiencies
has to be calculated , but they are expected to be small.