Wiki source code of Co-simulation TVB and Nest multiscale

Version 25.1 by kuschlionel on 2021/04/16 21:42

version	line-number	content
1.1	1	(% class="jumbotron" %)
	2	(((
	3	(% class="container" %)
	4	(((
18.1	5	= Co-simulation TVB and Nest multiscale =
1.1	6
18.1	7	demonstration of the implementation with an example : Mouse Brain from neurons to brain regions
	8
18.2	9	Authors: L. Kusch, S. Diaz, W. Klijn, V. Jirsa
18.1	10
	11	[[image:co_simulation_no_title.png]]
1.1	12	)))
	13	)))
	14
	15	(% class="row" %)
	16	(((
	17	(% class="col-xs-12 col-sm-8" %)
	18	(((
18.1	19	= Co-simulation =
1.1	20
18.1	21	This project is a proof of concept for co-simulation of network models with regions represented at different scales (spiking neurons and mean-fields) integrating the activity from the corresponding simulators (NEST and TVB).(OP1.11).
1.1	22
23.1	23	This prototype is based on future co-simulation between TVB and Nest with other simulators (Arbor, Neurons, Gazebo,... ) .
18.1	24
	25	= Demonstration : Mouse Brain from neurons to brain regions =
	26
22.1	27	You can find the demonstration of this proof of concept in the lab: [[https:~~/~~/lab.ebrains.eu/user/user-redirect/lab/tree/drive/Shared%20with%20all/Co-simulation%20TVB%20and%20Nest%20multiscale/demonstration_mouse_brain.ipynb>>https://lab.ebrains.eu/user/user-redirect/lab/tree/drive/Shared%20with%20all/Co-simulation%20TVB%20and%20Nest%20multiscale/demonstration_mouse_brain.ipynb]]
18.1	28
23.1	29	This proof of concepts prove that the co-simulation can be done, but it misses the theoretical validation of the coupling simulation. The coupling between Neural Mass model and Spiking Neural Network is complex and need some theoretical reflection for getting meaningful simulation.
21.1	30
18.1	31	= The implementation : easy to reconfigure =
	32
24.1	33	The code of the proof of concept is available in this repository: [[https:~~/~~/github.com/multiscale-cosim/TVB-NEST>>url:https://github.com/multiscale-cosim/TVB-NEST]]
18.1	34
22.1	35	All the instruction of the installation and the usage of it are in the Readme.
	36	\\This project is designed to be reusable and configurable for the researchers who want to do co-simulation across scales using supercomputer.
	37	The main idea is that all simulators and translator are independent, but they share parameters for configuration and communication.
	38	The following figure will give an idea of the interconnection between the simulators and translator for the demonstration case :
18.1	39
	40
	41	[[image:co-simulation-page.png]]
	42
	43	The demonstration should be used as an example of how to use the proof of concept for your own application.
22.1	44	All the simulators haves their own folder which contains the configuration for your application. A script in the folder allows the orchestrator to launch the simulator with the good configuration. The second role of the orchestrator is to create the environment for the simulation which guarantees that all components are properly connected with each others.
18.1	45
1.1	46	= Who has access? =
	47
18.1	48	Everyone can have access and use it in the limit of the licence.
1.1	49	)))
	50
	51
	52	(% class="col-xs-12 col-sm-4" %)
	53	(((
	54	{{box title="Contents"}}
	55	{{toc/}}
	56	{{/box}}
	57
	58
	59	)))
	60	)))