The task of the CST Constants Updating Routine is twofold:
For the CST, a Pedestal is introduced as:
The reason for scaling the pedestal is the need for a higher precision than the ``natural'' 12-bit delivered by the FADCs. Otherwise, the dynamic updating algorithm would not be sensitive to even - fluctuations (s. Eq. 6).For the initialization of the Pedestals, the first 64 events (for every Pipeline Counter) are used, for which the mean value for the above defined Pedestals is calculated. After events (on average) one has obtained valid pedestals.
The next 1024 events are then used for initializing the Sigma quadruples (s. Sec. 2.1.2). For this purpose, one accumulates the :
as well as its square:After 1024 events the can be calculated from the mean values of the two sums:
The is to be used within the Hit Strip - and the Cluster Criterion (s. Sec. 2.3). The and the square sum are stored for being used during the dynamic updating. Internal counters guarantee that the real HitFinding starts only after valid constants have been established.
The Dynamic Updating of the Pedestals calculates a Pseudo-Pedestal from the data of the current event and adds it to the old Pedestal with a certain weight:
Currently, a weight of is being used.For the sigmas, a likewise slow update of and has proven to be inefficient for two reasons:
After 1024 Updates fresh variances are calculated if the number of valid updates is greater than (1024/4), otherwise the old variance is kept. This could possibly lead to strips never getting new (i.e. better) variances: the hot strips. The average occupancy of the CST has been estimated to be below the percent level. Therefore, if the number of valid updates for a strip is below (1024 - 64) which corresponds to an occupancy above 6%, the strip is marked as hot by setting bit 30 of the Counts variable. In this case, the sums will be accumulated even if the strip has a hit. This leads to some cooling.