clever framework name that doesn’t violate copyright laws march 27, 2015
TRANSCRIPT
Clever Framework Name That Doesn’t Violate Copyright LawsMARCH 27, 2015
Meeting AgendaFramework OverviewPrototype 1 Design GoalsPrototype 1 DemoPrototype 2 Design GoalsTimeline Moving ForwardQuestions & Answers
Framework Overview
• Here, include the full burglar alarm graph• Talk about this representation of information flow• “And, when deploying this graph, we’ll actually deploy it as three
graphs across three different devices”• Show the boundaries
Shaping the NetworkGraph implementation should use the same concepts as graph designBusiness logic should be decoupled from connection logicThis computational graph abstraction applies to any level of the systemNew devices must be able to connect to the network at runtime
Quick Prototype 0 example: show the components in the Photo Collector device, the edge configuration for the application, and the resulting graph that the framework produces
Components
We support three types of components:◦ Processors: an atomic unit of C# code◦ Subgraphs: a fully encapsulated graph, embedded as a node in a larger graph◦ Pools: a collection of same-type components, whose members can change at runtime
Behavior Output channelsInput channels
Processors A processor is a C# class.
◦ For each input channel, it provides a callback function to the framework to receive incoming messages◦ For each output channel, it requests a callback function from the framework to send output messages◦ It provides start and stop methods, to manage any services it encapsulates
For example, consider the processor that encapsulates the connection with the Kinect.◦ On start, the processor uses the Kinect SDK to start a connection.◦ When it receives a photo request, the processor uses the Kinect’s Camera API to take a photo, and
outputs the resulting photo.◦ On stop, the processor uses the Kinect SDK to stop the connection.
Subgraphs So I’m still not entirely sure how to demonstrate this, but one option might be:
◦ Show the photo collector device in its entirety◦ Show that the Kinect-Wunderbar-BusinessLogic section can be encapsulated as a subgraph that acts as a
camera◦ Show the photo collector device with just this opaque camera component and its connection with the
monitor
Pools
Use the CM as a pool example here plz
Feature Priority1. Dynamic Network Topology
2. Framework Scalability
3. Large Scale Data Aggregation
4. Historical Data Storage
5. Robust Connections
6. System Diagnostics
7. UX/UI
Prototype 1DESIGN GOALS AND DEMO
GoalsFramework ScalabilityInteraction with Cloud Services to store and produce data
Large Scale Data Aggregation InfrastructureHeterogeneous data, multiple inputs and outputs
Dynamic Network TopologyIntroduce new components without reconfiguring
Prototype 1 Demo
INSERT DEMO GRAPHIC
INSERT SYSTEM BLOCK DIAGRAM
Prototype 2DESIGN GOALS
GoalsComplete Large Scale Data Aggregation
Synthesize different types of inputs into one or more different types of outputs Increase the amount of data flow
Robust Connections Demonstrate transmission failure recovery and unintentional disconnection recovery Network components directly related can tell when a device disconnects
System Diagnostics Expand status logging of components, demonstrate logging capabilities of Framework
UX/UI Ability to view actions while running the application
Updated Timeline