microsoft / accessorframework Goto Github PK

test cases should include:

• accessor instantiation
• send/receive messages of different data types
• simultaneous messages
• immediate reactions
• delayed reactions
• nested actors

Integrate with the CI/CD pipeline and link build statuses

A refinement of accessors is Lingua Franca (see https://github.com/icyphy/lingua-franca ) that you may want to check out. There is a C target and an Accessors target, with the C target being better developed and more mature. Creating a C++ target would be relatively easy, I think.

Integrate with googletest and add a basic test suite

Change AtomicAccessor::Impl::ProcessInputs() to process multiple inputs on a single port during each round of execution (but NOT inputs the accessor sends to itself to be processed during the next round, i.e. feedback input). This will unlock support for input ports with multiple sources.

Currently, callback scheduling and delays are represented as fundamental integer types. Represent them as std::chrono::durations instead to make the callback system more robust.

Currently, accessor models are static; at runtime, ports cannot be added to or removed from accessors, and children cannot be added or removed from parents. Add dynamic modeling so that accessor models can adapt to changing environments such as devices coming online and going offline at runtime.