Open mfahdaz opened 3 years ago
Aspect | Detail |
---|---|
Summary | MVP Design of the Communication Protocol |
Task Area | Design |
Assignee | |
Information | |
Prerequisites | |
Dependencies |
Design of the communication protocol for Co-Simulation, this includes the specification of the protocol stack for: Steering channel Data channel
A large set of requirements are found in the discussion section of this card, to be copied here
Copy past of the data collected by Fahad
Plugin
Services
API
A unified interface to transport the diverse nature of data.
Communication types:
Command & Control
HPC communication
Known variations of data to be transported:
Simulation data
Visualization
Steering
Monitoring information
Provenance data
Requirements
The system must be able to receive spikes from a simulator running on multiple nodes.
The system must be able to sort the incoming spikes into spikes per neuron, transpose the data.
The system must be able to format the outgoing spikes into data objects that can be injected directly into the translation software.
The system must be able to collect the output of the translation software and forward this to a second simulator.
The components in the system must be able to run concurrently.
The data from simulation should be transferred as fast as possible
The amount of data sent per time step to analysis could be flexible
The user could be able to request data flexible, at different rates and times
The system must be able to exchange of parameters and settings before the simulation, and data transfer starts
Simulation Information about the start and the end of the simulation must be exchanged between simulation and analysis.
The received data should be stored in a buffer. This is necessary to allow intermediate processing and transfer in chunks of data rather than a 1:1 mapping from incoming to outgoing package sizes.
The framework should enable data access at arbitrary rates and asynchronous.
Another requirement is to facilitate the secure/encrypted communication (e.g. using PKI).
The secure /encrypted is to keep in mind. We should not design for
Update on the tasks, requirements and acceptance criteria. Split into MVP and general/overall parts. Detailed diagrams and images will be created for internal discussion and a first verion.
Next steps:
Summary
Design of the communication protocol for Co-Simulation, this includes the specification of the protocol stack for:
Tasks
Requirements
MVP - with TVB-NEST science usecase/showcase:
Overall:
Acceptance criteria
MVP: Communication protocol for the science showcase for:
Overall: Communication protocol for: