Dear Rolandas,
I am still not quite sure that I fully understood your question. But it
seems to relate to the mapping, i.e. to how abstract pyNN-quantities
allocate real physical resources on the chip.
Sometimes a picture says more than a thousand words. Therefore I am
attaching for illustration:
(1) a minimal pyNN script which generates some populations of external
inputs and neurons, and then makes some connections between these
populations of varying strength (it does not do anything meaningful),
(2) a visualization of the chip configuration when executing this pyNN
script. From the color-coded synaptic strength, you can see where the
external inputs feed their spikes into the system (line drivers) and
also how recurrent connections are formed.
To comment on the questions from your email:
> In the table that you referred, for every line driver was given a
neuron id.
Yes and no: only _some_ line drivers are driven by a neuron. The others
are driven by external inputs. (Please, reexamine the table.)
> Does that mean, that every line driver refer to only 1 neuron?
Every line driver will transmit spikes from one pre-synaptic spike
source to many post-synaptic neurons. A spike source can be either an
on-chip neuron (class IF_facets_hardware1) or an external spikes source
(class SpikeSourcePoisson or SpikeSourceArray).
> If so, inputs for multiple neurons should be generated using "for"
loop and SpikeSourceArray with times of spikes for each neuron?
Maybe the example script sheds some light on this: It connects many
inputs to many neurons with just one line, using the pynn.Projection
function.
Does this clarify your questions?
Otherwise, I can only repeat my offer from November to send me a sketch
of your network architecture, or a minimal pyNN script to illustrate
your question.
Best regards from Heidelberg,
Johannes
On 01/11/2017 07:40 PM, SUBSCRIBE KIP-SPIKEY-USERS Anonymous wrote:
> Hello Johannes,
>
> thank you for your reply.
>
> I will try to clarify the structure of the network:
>
> Network consists of 100 fully interconnected neurons.
> All neurons receive low frequency Poisson noise inputs
>
> In addition, 3-5 populations of 10 predefined neurons out of the population of 100 neurons receive sequences of spike patterns:
> 10 neurons, belonging to the same population, are activated simultaneously, then a period of only noise inputs follows, and the correlated activation continues; etc;
> a second, third etc population of 10 neurons is activated in the same way.
>
> I want to better understand what you meant by "The first SpikeSourceArray generated in the pynn script will send its spikes through driver no. 255 (resp 511), the second SpikeSourceArray will use driver 254 (resp 510)". In the table that you referred, for every line driver was given a neuron id. Does that mean, that every line driver refer to only 1 neuron? If so, inputs for multiple neurons should be generated using "for" loop and SpikeSourceArray with times of spikes for each neuron?
>
> Best regards,
> Rolandas
>
> ########################################################################
>
> To unsubscribe from the KIP-SPIKEY-USERS list, click the following link:
> http://listserv.uni-heidelberg.de/cgi-bin/wa?TICKET=NzM2MzcwIGJpbGxAS0lQLlVOSS1IRUlERUxCRVJHLkRFIEtJUC1TUElLRVktVVNFUlMgIBNCT7uJwhRr&c=SIGNOFF
>
########################################################################
To unsubscribe from the KIP-SPIKEY-USERS list, click the following link:
https://listserv.uni-heidelberg.de/cgi-bin/wa?SUBED1=KIP-SPIKEY-USERS
|
