Page 18 - manuscript_ijb05583
P. 18
intensity.
Upon upwards crossings of the debris threshold, the time difference to the previous event’s (e1)
downwards crossing time-point was measured (Δt). If the new event e2 was too close to e1, e2
got flagged as non-sortable (red). As e2 would further impact the sorting process of the
previously approved event e1, its sorting process had to be aborted retroactively. For this, an
additional event parameter was created that got checked by the sorting algorithm just before
secluding the BB into the ejection channel.
If there was enough distance between events, e2 was pre-flagged as sortable (orange) and e1
received its final sorting flag (green) allowing it to be sorted.
Upon downwards crossing of the threshold, the algorithm checked whether the current event
(e2) was flagged as sortable or not (orange or red respectively). If not, the event was further
ignored. In case it was pre-flagged as sortable (orange), its peak fluorescent value was checked.
If the value surpassed the fluorescent threshold of 0.7 V, e2 was categorized as intact BB and
ultimately flagged as sortable (green). Otherwise, e2 was categorized as debris and ultimately
flagged as non-sortable (red). Lastly, a new timestamp was set to calculate timing offsets to
future events (e3).
17
