public interface Ensemble extends Node
A group of Nodes with largely overlapping inputs and outputs.
There are no strict rules for how to group Nodes into Ensembles, but here are some things to consider:
The membership of an Ensemble is fixed once the Ensemble is created. This means that the Ensemble model doesn't deal explicitly with growth and death of components during simulation (although you can set input/output weights to zero to mimic this). It also means that an Ensemble isn't a good model of a functional "assembly".
VisiblyMutable.Event, VisiblyMutable.Listener, VisiblyMutable.NameChangeEvent, VisiblyMutable.NodeRemovedEvent
Modifier and Type | Method and Description |
---|---|
void |
collectSpikes(boolean collect) |
Node[] |
getNodes() |
SpikePattern |
getSpikePattern()
This method provides a means of efficiently storing the output of an
Ensemble if the component Nodes have Origins that produce SpikeOutput.
|
boolean |
isCollectingSpikes() |
void |
redefineNodes(Node[] nodes)
Replaces the set of nodes inside the Ensemble
|
void |
stopProbing(java.lang.String stateName) |
clone, getChildren, getDocumentation, getName, getOrigin, getOrigins, getTermination, getTerminations, notifyAboutDeletion, run, setDocumentation, setName, toScript
reset
getMode, setMode
addChangeListener, removeChangeListener
Node[] getNodes()
SpikePattern getSpikePattern()
void collectSpikes(boolean collect)
collect
- If true, the spike pattern is recorded in subsequent runs and
is available through getSpikePattern() (defaults to false)boolean isCollectingSpikes()
void redefineNodes(Node[] nodes)
nodes
- New nodes to usevoid stopProbing(java.lang.String stateName)