Tuda logbooks General E1104 ISACII E1195 E1103 E1147 S1287 S1203 S1233 S1284 S1447 23Na(a,p) S1540 S1381  S1847 Catania
  S1287  ELOG logo
Entry  Fri Jan 11 06:56:01 2013, Jessica Tomlinson, Other, General, multiplicities, hit patterns and good hits in an event 411mev-multiplicities-and-hitpat.pdf
    Reply  Fri Jan 11 09:48:58 2013, Tom Davinson, Other, General, Re: multiplicities, hit patterns and good hits in an event 
Message ID: 61     Entry time: Fri Jan 11 09:48:58 2013     In reply to: 60
Author: Tom Davinson 
Type: Other 
Category: General 
Subject: Re: multiplicities, hit patterns and good hits in an event 

Jessica Tomlinson wrote:

I have attached a pdf of a series of slides with some multiplicity and hit pattern plots on, also a list of cuts. As well as this I looked at how many 'good hits' (explained in pdf) I am getting per event.

Before Christmas I found that the code was not clearing the raw arrays read in by MIDAS and so unless a new piece of data filled the array channel number the data from the last event was being read into the next event too. It was only clearing the 'data(i) arrays which is what the data is unpacked as. I have now got it clearing both so data is not read in for multiple events.

As far as I am aware it has never been necessary to explicitly zero the 'raw' (or packed) data arrays containing the

ADC/TDC data and active channels in each event. Usually it is only necessary to zero those elements of the 'unpacked'

arrays which contain event data.

ELOG V2.9.2-2455