Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
exascale-brainsim/nest-variables-used-in-simulation.md
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
29 lines (24 sloc)
1.65 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This document contains a detailed description of which variables are accessed by the OpenMP threads in NEST-2.6.0 simulation. | |
Scheduler::update() | |
------------------- | |
The main simulation runs through the function ```nest::Scheduler::update()```. The simulation progresses in discrete time windows. A certain number of timesteps sum up to the minimum synaptic delay, ```min_delay_```, also called a timeslice. During this interval of length ```min_delay_```, individual threads can work separately. Thus all spike events are delivered (by each thread) at the beginning of each timeslice, and spike events are gathered (from all threads) at the end of each timeslice. | |
Roughly, the call hierarchy inside ```Scheduler::update()``` looks like the following: | |
- for each thread in parallel do until simulation is over | |
- Only at the beginning of a timeslice, call ```Scheduler::deliver_events_()``` | |
- for each node (neuron/device) assigned to this thread do | |
- call ```Node::update()``` | |
- Synchronize threads | |
- Using a single thread, do the following | |
- After each ```min_delay_``` interval, call ```Scheduler::gather_events_()``` | |
- ```Scheduler::advance_time_()``` | |
Variables used by ```Scheduler::update()``` | |
------------------------------------------- | |
Each OpenMP thread ```t``` accessess the following variables/functions: | |
* ```Scheduler::nodes_vec_[t]``` | |
* ```Node::update(clock_, from_step_, to_step_)``` | |
* | |
Important Variables for GPU Computation | |
======================================= | |
* ```Scheduler::net_```, the network object | |
* ```Scheduler::nodes_vec_```, vector containing neurons/devices assigned to each thread | |
* Number of OpenMP threads |