Closed w-klijn closed 3 years ago
A first design document can be found here: https://docs.google.com/document/d/13hIfdwWZvI-7cOSrwVmDltSPP2-qtQ9mlU4uj9CcV5I/edit#heading=h.26in1rg
Nest-Elephant (in transit) coupling deployed and tested in alpha version on deepest (July 13th, 2020).
Continued in #48
Summary
NEST/Arbor and TVB speak different languages: NEST and Arbor typically exchange spikes where TVB is 'rate' based. The information stream needs to be translate at runtime. To allow reuse of the existing spiketrain analysis functionality Elephant should be used to do this translation.
Lionel has a working POC coupling TVB and NEST. And Kim has a POC allowing Many to one MPI distribution and deployment. The lessons learned from these two
Tasks
Requirements
Acceptance criteria