Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Update nest-variables-used-in-simulation.md
  • Loading branch information
saq10002 committed Jan 23, 2015
1 parent 0dd2ded commit 8a8d0f8
Showing 1 changed file with 21 additions and 8 deletions.
29 changes: 21 additions & 8 deletions nest-variables-used-in-simulation.md
Expand Up @@ -6,11 +6,24 @@ 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_()```
- 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

0 comments on commit 8a8d0f8

Please sign in to comment.