Hi,
a few weeks ago, I patched the digitization file in blastmc v2 and
migrated them into v3. However, I was not able to finish them because I
did not have enough time and enough detailed knowledge on each detector
system. So I did not spend as much time on digitization as I did on
geom/sets/hits files.
I agree with Tancredi that an expert from the group working on each
detector should check and finish the digitization and probably event the
geom/set/hits part of the v3 blastmc.
One reminder. The current digitization also lacks the full degrees of
freedom implemented in other parts of monte carlo. For instance, the time
for light to travel from the hit to the PMT's on TOF paddles are
calculated by the vertical distance between the hit and the ends of the
paddle, not the distance along the paddle itself. So the misalignment of
the TOF paddles from the vertical line is not reflected.
Chi
On Tue, 8 Apr 2003, Tancredi Botto wrote:
>
> I've submitted a few changes to blastmc v3 (after fresh update).
> Here is a (slightly re-edited) cvs log
>
>
>
> _ Added some comments in fort99 - gives pointer to dgen/epel info
>
> _ blast.geom: added realistic scattering chamber geometries (cell walls,
> exit foil). Having all 8 cerenkovs is now default.
>
> - removed old geom files, blast.geom is the only geom file in v3
>
> _ Added a "forward" cerenkov set with n=1.02 (all else have 1.03)
>
> _ Cerenkov digitization buggy: forced ADC = Nphotoelectrons. However this
> number is way too high (30 PE!!) I think. Note: all detector digitization seem
> only tentative
>
> _ If energy loss = 0 then tdc=-1 (tof/sb/nc). This fixes a problem with
> geant (the tdc is always computed, also for neutrals, since it depends
> only the tracking time of flight) and the data analysis (the tdc is used
> to select events)
>
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST