You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The input and output idea in #51 immediately shows that more is needed for the kinds of graphs we want to process.
We want to be able to have multiple outputs per node
they should be able to have independent sets of nodes attached to them (rather than always passing a header and a frame together)
they might have different types - the header of a frame vs the array of a frame
they might have different emission frequencies - emitting buffer headers 5 times per frame
We want to have multiple inputs per node
after a split with 5x headers per frame, we might want to have a merge node that then combines the header metadata and the frame after it's assembled from buffers
We want to add metadata to the type of output/input
e.g. push vs pull nodes
"gather inputs from slot A, and then emit all gathered items from slot A whenever an item is received in slot B"
"await until we receive a value in slot A and B"
We want to keep the means of communication between nodes abstract
direct synchronous argument passing
multiprocess queues
socket-based queues
So I am thinking of borrowing some of the UX from Qt without all the overhead, something like this
then we get into something like a petri net with a bipartite graph structure that goes Node -> Scheduler -> Node -> ... where the Scheduler can be one of several methods for distributing events from a signal to a slot.
This is sort of an open ended implementation without a firm target that i'll be exploring around with between the conversion of SDCard (async) and streaming (sync) pipelines.
The text was updated successfully, but these errors were encountered:
The
input
andoutput
idea in #51 immediately shows that more is needed for the kinds of graphs we want to process.split
with 5x headers per frame, we might want to have amerge
node that then combines the header metadata and the frame after it's assembled from bufferspush
vspull
nodesSo I am thinking of borrowing some of the UX from Qt without all the overhead, something like this
then we get into something like a petri net with a bipartite graph structure that goes
Node -> Scheduler -> Node -> ...
where theScheduler
can be one of several methods for distributing events from a signal to a slot.This is sort of an open ended implementation without a firm target that i'll be exploring around with between the conversion of SDCard (async) and streaming (sync) pipelines.
The text was updated successfully, but these errors were encountered: