Graded

[epaxon]

Issue Number:

Objective of pull request: Add graded spike processes

Pull request checklist

Your PR fulfills the following requirements:

• [ ] Issue created that explains the change and why it's needed
• [ ] Tests are part of the PR (for bug fixes / features)
• [ ] Docs reviewed and added / updated if needed (for bug fixes / features)
• [ ] PR conforms to Coding Conventions
• [ ] PR applys BSD 3-clause or LGPL2.1+ Licenses to all code files
• [ ] Lint (flakeheaven lint src/lava tests/) and (bandit -r src/lava/.) pass locally
• [ ] Build tests (pytest) passes locally

Pull request type

Please check your PR type:

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Documentation changes
• [ ] Other (please describe):

What is the current behavior?

-

What is the new behavior?

• graded spike processes: GradedVec, InvSqrt, NormVecDelay

Does this introduce a breaking change?

• [ ] Yes
• [x] No

Supplemental information

[epaxon]

Does the pull request automatically update when i push the branch?

[PhilippPlank]

Does the pull request automatically update when i push the branch?

Yes, everything you or someone else pushes to the underlying branch will update the PR. Changes from the main branch will not be automatically integrated though.

[epaxon]

is merging seriously blocked by this "Codacy Static Code Analysis" because i have, "for i in range(niters)" and I don't use the counter variable "i"? In my opinion this is better code style than to replace "i" with "".

[tim-shea]

is merging seriously blocked by this "Codacy Static Code Analysis" because i have, "for i in range(niters)" and I don't use the counter variable "i"? In my opinion this is better code style than to replace "i" with "".

No, Codacy doesn't block merging. @PhilippPlank requested changes.

EDIT: Wait, I see now what you're referring to. That's really weird.