Hello @xchoo, NP and thanks for getting back.
With respect to the following:
you previously in another post (I don’t remember which) noted that filtering is done while inputing to the Ensembles (and not at the output of the Ensemble), however, I guess, this statement is equivalent to
i.e. output of a connection is exactly what’s input to the Ensemble/Node (with no other in-between processing of values).
With respect to the following,
I haven’t tested it yet, but just confirming with you… it still won’t work for the TensorNode
in question right? as you realize it as a bug in current Nengo-DL version… isn’t it?
However, with respect to the bug you raised, if one still wishes to work on the spike amplitude output (and not the filtered one), then I guess he/she has to explicitly set the synapse of Connection
to the respective Node/Ensemble/TensorNode
as None
. Isn’t it?
With respect to the following,
it means that ndl_model.layers
and ndl_model.net.ensembles
are essentially representing the same thing… right?
Yeh , thanks for mentioning the following… I should try it as well.
With respect to the following,
just explicitly confirming, the filtered “spike train” is considered as x
at all the layers and current J
is calculated for each of them. Isn’t it?