On 02/05/2015 05:44 PM, Bartosz Golaszewski wrote:
> when working with sigrok today I figured out that the best way to
> include the averaging mode in sigrok seems to be implementing a new
> output module which would take only analog packets into account and do
> the averaging without the need for the driver to care about it.
That's not a great fit either -- the output modules take packets and output
something that fits the module -- VCD text, WAV format, etc -- but not
packets. Frontends thus take the output of these modules and write them to
files or display them.
Putting an averaging function in there would mean you'd need an averaging
function in EVERY output modules, to massage their analog input before
processing as usual. Clearly, this is the wrong place.
The truth is there isn't a great place in sigrok for this sort of thing.
What's needed is a new subsystem that gets to have a go at packets leaving
the driver, before they hit the frontend. There are lots of uses for such a
subsystem -- not least analog to digital conversion. We thought of it some
time ago, but unfortunately nobody's taken it on. Some ideas were written up
here:
http://sigrok.org/wiki/Domain-specific_measurements_and_analysis
It's quite a big job, which is why nobody ever got started on it I guess.
--
Bert Vermeulen [email protected] email/xmpp
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
