This repository was archived by the owner on May 13, 2026. It is now read-only.
Excitatory/Inhibitory LIF neuron model - #888
Open
monkin77 wants to merge 4 commits into
Open
Conversation
monkin77
marked this pull request as ready for review
August 24, 2024 13:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue Number: #887
Objective of pull request: Model E/I LIF neurons to represent more complex behaviors containing positive and negative inputs, each with their own decay time constants (
du_excanddu_inh). It also allows varying the voltage and current time constants of neurons belonging to the same layer.Pull request checklist
Your PR fulfills the following requirements:
flakeheaven lint src/lava tests/) and (bandit -r src/lava/.) pass locallypytest) passes locallyPull request type
What is the new behavior?
du_excanddu_inh) to represent more complex scenariosDoes this introduce a breaking change?
Supplemental information
This only contains the floating-point precision version of the model. I believe it is possible to implement a fixed-precision version of it, although it requires further investigation.
I would appreciate your opinion on this as I've not delved deep into the microcode documentation.