Note the picPET outputs a h/w event counter along with the timestamp. This
can be ignored but the counter helps identify noisy inputs, allows one to
distinguish between fast and too-fast inputs, and was very useful during
development to validate the accuracy of the device.
The event counter also lets you catch lost events in the downstream gear that
is capturing/logging data from the picPET.
--
These are my opinions. I hate spam.
tvb@LeapSecond.com said:
> Note the picPET outputs a h/w event counter along with the timestamp. This
> can be ignored but the counter helps identify noisy inputs, allows one to
> distinguish between fast and too-fast inputs, and was very useful during
> development to validate the accuracy of the device.
The event counter also lets you catch lost events in the downstream gear that
is capturing/logging data from the picPET.
--
These are my opinions. I hate spam.