[nengo-user] Adaptive LIF nodes/NodeFactory

[Daniel Rasmussen]

Hi Peter,

A NodeFactory is the thing that actually generates the neuron objects that
make up an ensemble.  By default the `make` function uses a
LIFNeuronFactory, which means that the ensemble will be made up of LIF
neurons.  If you want to use a different type of neuron, then you need to
pass the corresponding NodeFactory to the `node_factory` parameter of the
`make` function.  For example, to make an ensemble with ALIF neurons you
could do
```
import nef
from ca.nengo.model.neuron.impl import ALIFNeuronFactory
net = nef.Network("alif_network")
net.make("alif_ensemble", 100, 1, node_factory=ALIFNeuronFactory())
```
You can change the parameters of the ALIF neurons by passing different
arguments to the ALIFNeuronFactory constructor (see ALIFNeuronFactory.java
for what's available).  Sorry that isn't better documented, we almost
always use LIF neurons in our work
so I don't think this is in any of our examples.

I would actually recommend using the development release of Nengo 1.4.
It's quite stable, as most of the active development work has moved on to
Nengo 2.0, and it includes some useful improvements and bug fixes since the
stable release.

Daniel


On 18 July 2014 16:08, Johnson, Peter S <peter.s.johnson at lmco.com> wrote:

>  Hi,
>
>
>
> How would one create a node with ALIF neurons (or any non LIF neuron)?
> Relatedly, what is a NodeFactory and how is it used in the context of the
> make function?
>
> Sorry if this is in the docs; I was unable to find it.
>
>
>
> NB: I am using the last stable release of nengo. Is there any particular
> reason to prefer one over the other?
>
>
>
> Thanks,
>
> -Peter Johnson
>
> _______________________________________________
> nengo-user mailing list
> nengo-user at ctnsrv.uwaterloo.ca
> http://ctnsrv.uwaterloo.ca/mailman/listinfo/nengo-user
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://artsservices.uwaterloo.ca/pipermail/nengo-user/attachments/20140721/6fae3e30/attachment-0002.html>