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.

Sign up for GitHub

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

Jump to bottom

Unexpected behaviour with connectivity in PyGeNN #620

Open
neworderofjamie opened this issue Apr 16, 2024 · 0 comments
Open

Unexpected behaviour with connectivity in PyGeNN #620

neworderofjamie opened this issue Apr 16, 2024 · 0 comments
Labels
bug PyGeNN
Milestone
GeNN 5.X

Comments

@neworderofjamie
Copy link
Contributor

If you do the following:

  1. Define sparse connectivity with SynapseGroup.set_sparse_connections
  2. Modify it with a custom connectivity update
  3. Pull connectivity with SynapseGroup.pull_connectivity_from_device
  4. Access the connectivity with SynapseGroup.get_sparse_pre_inds and SynapseGroup.get_sparse_post_inds

You don't see the updated connectivity because the original is cached. Quite what should happen with this caching needs more thought.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug PyGeNN
Projects
None yet
Milestone
GeNN 5.X
Development

No branches or pull requests
1 participant
@neworderofjamie