Curious event.. - Githubissues

153957 commented 9 years ago

Why did station 202 trigger for event 1432514377592294598 (2015/5/25 0:39:37)

trace_202_ 1432514377592294598

Channel 2 only reached 212 ADC counts (pulseheight: 8).

153957 commented 9 years ago

Found the event with:

data = tables.open_file('2015_5_25.h5', 'r')
ams = data.root.hisparc.cluster_amsterdam
min(sort(ams.station_202.events.col('pulseheights') + ams.station_202.events.col('baseline'))[:, 2])

pulseheight + baseline gives highest ADC value reached by channel.
sort() sorts the channels for each event, from low to high.
then filter to get the 3rd value (column) from each event (e.g. 260 from: [-1, -1, 260, 300])
then get the min value from this list.

With the 2 low trigger each channel should be above the low threshold (253), so the lowest of the lower of the two should at least be 254. Possibly a bit less due to filtering of the traces (which PySPARC does not do)..

davidfokkema commented 9 years ago

Interesting. I'll take a look, hopefully Monday.

davidfokkema commented 8 years ago

I checked for other stations, most notably a LabVIEW station (College Hageveld, 203). Event 1451956613516963433 is also very curious. A pulseheight of only 2 ADC counts. I'm closing this for now. It seems that the hardware sporadically triggers on noise.

HiSPARC / pysparc

Curious event.. #20