https://github.com/osh/gr-eventstream

gr-eventstream is a set of GNU Radio blocks for creating precisely timed events and either inserting them into, or extracting them from normal data-streams precisely. It allows for the definition of high speed time-synchronous c++ burst event handlers, as well as bridging to standard GNU Radio Async PDU messages with precise timing easily.
https://github.com/osh/gr-eventstream

burst c-plus-plus event-handling extract-data extractor gnu-radio injection message-passing python radio signal-processing signaling-pathways synchronization synchronization-service synchronous timing-simulator

Last synced: 6 months ago
JSON representation

gr-eventstream is a set of GNU Radio blocks for creating precisely timed events and either inserting them into, or extracting them from normal data-streams precisely. It allows for the definition of high speed time-synchronous c++ burst event handlers, as well as bridging to standard GNU Radio Async PDU messages with precise timing easily.

• Host: GitHub
• URL: https://github.com/osh/gr-eventstream
• Owner: osh
• Created: 2011-09-15T05:49:14.000Z (about 14 years ago)
• Default Branch: master
• Last Pushed: 2017-09-20T14:56:52.000Z (about 8 years ago)
• Last Synced: 2025-03-26T04:21:38.489Z (7 months ago)
• Topics: burst, c-plus-plus, event-handling, extract-data, extractor, gnu-radio, injection, message-passing, python, radio, signal-processing, signaling-pathways, synchronization, synchronization-service, synchronous, timing-simulator
• Language: C++
• Homepage: http://deepsig.nl
• Size: 842 KB
• Stars: 44
• Watchers: 10
• Forks: 28
• Open Issues: 6
• Metadata Files:
  • Readme: README
  • Changelog: CHANGES

Awesome Lists containing this project

README

          
#

# Copyright 2017 Tim O'Shea

# 

This directory contains the GNU Radio Eventstream Out-of-Tree Synchronous Stream-Event Scheduler 

These blocks are intended to help improve the translation of 

streams of data items into scheduled-finite length events 

occurring in the data streams in both directions.

* es.sink provides the translation from stream to events

* es.source provides the translation from events to streams

* triggers cause events to be scheduled in es.source 

 and es.sink block event queues.

Some examples of specific triggers included are,

    - es_trigger_edge_f: cause an event when float stream rises

                         above a fixed threshold value

    - es_trigger_sample_timer: cause an event to occur on 

                    a periodic sample increment in the stream

* handlers consume events and do some ammount of signal

  processing on them

Some example of specific handlers included are,

    - es_handler_print: print the event to STDOUT

    - es_handler_pdu: convert the event to a PDU and send

                        it out a message port

    - es_handler_insert_vector: a source handler which

                populates an event window from a PMT vector

    - es_handler_file: a sink handler which writes event

                contents out to a file