1 / 12

Hybrid/OCP Workgroup

Hybrid/OCP Workgroup. Issues. Heterogeneous model semantics (common principles, differences) Ptolemy II FRP CHIRP Simulink/Stateflow/Matlab Giotto/Masaccio OCP. Software Synergies. Relationship between: OCP Controls API Ptolemy II CHIRP tool FRP tools Where are the synergies?

rbivens
Download Presentation

Hybrid/OCP Workgroup

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hybrid/OCP Workgroup

  2. Issues • Heterogeneous model semantics(common principles, differences) • Ptolemy II • FRP • CHIRP • Simulink/Stateflow/Matlab • Giotto/Masaccio • OCP

  3. Software Synergies • Relationship between: • OCP • Controls API • Ptolemy II • CHIRP tool • FRP tools • Where are the synergies? • How can we leverage the synergies?

  4. Hierarchical View leader follower sensors actuators controller Br Acc Ba S PID bang-bang

  5. What is a Domain? MoC + Realization The definition of the interaction of components (the model of computation) and the software that supports this interaction. Multi-domain modeling means: • Hierarchical composition • heterogeneous models allowed • Domains can be specialized • avoid creeping featurism • enable verification/validation

  6. Features of a MoC • Time • Information sharing • Control flow • Determinism • Dynamic reconfiguration • E.g. higher-order abstractions

  7. Time • How is time represented/manipulated in each MoC? • Coordination of time across MoCs • Coordination of real-time needs across MoCs(and conveyance of these needs to the OCP) • Models of time • Priority based (fixed or dynamic, as in RT-ARM) • Time triggered protocols • Global chronology • Global synchrony

  8. Taxonomy of MoCs • Continuous time • Continuous space • Discrete events (placed in time) • Finite state machines • Stream-based (functional/dataflow) • Rendezvous-based (CSP, CCS, Pi) • Discrete time • Publish and subscribe

  9. Milestones • Figure out how timed MoCs interact with OCP publish/subscribe • E.g. time triggered, continuous-time, discrete events • Figure out how dynamic reconfiguration/higher order abstractions interact with publish/subscribe • Expand controls abstraction to cover dynamic scheduling & reconfiguration. • Determine how MoCs support verification/ certification (correct by construction). • Define abstraction of real-time QoS for application builder.

  10. Implications for OCP • Domain plug-in interface for OCP • OCP as interoperability fabric • Divide API so technology can be reused • Resolve semantics questions • time strategy? • stream-based model strategy? • reconfiguration strategy?

  11. leader follower sensors actuators controller Br Acc Ba S PID bang-bang What technology can be shared when building Domains? • Abstract syntax • Type systems • Components • Interfaces • …

  12. Meetings (Small groups preferred) • Multi vehicle • Northrop, Stanford, GaTech, Boeing?? • DSL’s, FRP, streams, HoFs, continuous-time • Yale, OGI, ?? • RTOS support in OCP - QNX • Boeing, Stanford, Berkeley, ?? • Midsummer SEC WG meeting (OCP, MoC) • all

More Related