Hm, yes, for things that move really slowly this of course works – I
can't argue with that (nor can I argue with Marcus the First); I'd just
argue that the algorithm Sean describes sounds so complicated that
intuitively, it sounds like what he'd *like* to have is some DSP on a
downsampled version o
Meh, I use function probes to capture 'stuff' that changes
slowly--timescales of seconds or tens-of-seconds.
I wouldn't do this for faster stuff, but doing that allows you to use
"ordinary" python in a python module, with the probe value as calling
parameter.
On 2016-12-21 11:47, Marcus Müller
Hi Sean,
you really shouldn't be doing that at all.
If you want to do signal processing, write a simple python block that
operates on a sample stream.
The signal probe is really just that, for sporadic "debug" and "display"
operation, not for any "useful" application.ö
Best regards,
Marcus
I have a function probe to get an int from one block's output, and been
using a function probe to get the value of the probe signal. I now want to
have the block output a vector of ints, and use a probe signal vector to
capture them, and nave a few function probes to get index 0, 1, and so
forth. H
