Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RLM Development #13

Open
jkbchouinard opened this issue Jan 15, 2025 · 0 comments
Open

RLM Development #13

jkbchouinard opened this issue Jan 15, 2025 · 0 comments

Comments

@jkbchouinard
Copy link
Collaborator

Using the principles we explored in our meeting (Jan. 20), we can add some form of memory into the model using recurrence. This can be easily integrated into our existing MELM as follows:

with nengo.Network() as model:

    # Existing MELM ensemble and connection construction

    rep_recur_con = nengo.Connection(rep_ens, rep_ens, "transform", "synapse")

    # Existing MELM probing

We can also consider a separately integrating and block that contributes to the output just like the representation ensemble:
image
(I apologize, I drew this with my computer mouse and it is... not incredible)

Just like with the MELM, we're interested in seeing how this model performs when trained and tested on our spiking dataset. Since we're concerned with performance over time, plotting the error (absolute and squared) over time could be a useful exercise in visualizing where the model struggles.

Similarly, it would be useful to generate visualizations of the RLM model using nengo-gui for a more visual and intuitive way to interpret the underlying architecture (my drawing is not adequate).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant