Revise input and output ports in NESTML - #1299
Draft
clinssen wants to merge 229 commits into
Draft
Conversation
added 30 commits
October 17, 2024 11:08
tomtetzlaff
reviewed
May 29, 2026
|
|
||
| The statements in the event handler will be executed when the event occurs and integrate the state of the system from "just before" the event (at :math:`t-\epsilon`, for :math:`\epsilon\rightarrow 0`) to "just after" the event (at :math:`t=t+\epsilon`). Analogous to the ``update`` block, the predefined variable ``t`` indicates the time :math:`t` at the start of the interval (the function ``timestep()`` may not be used inside an ``onReceive`` block to prevent confusion). | ||
|
|
||
| Typically, the statements in the ``onReceive`` block integrate the delta function across time, yielding the surface area under the curve, the value of which corresponds to the weight of the spike. To perform this integration in a concise way, we use the sifting proprty of the delta function. The sifting property states that for any continuous function :math:`f(t)`: |
Collaborator
There was a problem hiding this comment.
Suggested change
| Typically, the statements in the ``onReceive`` block integrate the delta function across time, yielding the surface area under the curve, the value of which corresponds to the weight of the spike. To perform this integration in a concise way, we use the sifting proprty of the delta function. The sifting property states that for any continuous function :math:`f(t)`: | |
| Typically, the statements in the ``onReceive`` block integrate the delta function across time, yielding the surface area under the curve, the value of which corresponds to the weight of the spike. To perform this integration in a concise way, we use the sifting property of the delta function. The sifting property states that for any continuous function :math:`f(t)`: |
tomtetzlaff
approved these changes
May 29, 2026
tomtetzlaff
left a comment
Collaborator
There was a problem hiding this comment.
Very nice. Apart from the small typo, this looks very good to me. Thanks a lot for this nice solution.
Contributor
Author
|
Thank you very much for the review and the kind thumbs up! |
clinssen
marked this pull request as ready for review
May 31, 2026 14:31
clinssen
marked this pull request as draft
June 1, 2026 15:19
added 20 commits
June 3, 2026 09:20
…is not released yet
…is not released yet
…is not released yet
…is not released yet
…roneously make the second kernel inhibitory
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduces the NESTML predefined
sift()function to process spike events in event handlers. See here for documentation onsift(): https://github.com/nest/nestml/pull/1299/files#diff-22c1d3766680291b0aed3cd548fc0980ecc6511ebb5532a8ed2607105e1775e3R1198Remove the
excitatoryandinhibitoryspiking input port qualifiers. Instead, spikes should be routed (a) on the basis of having multiple spiking input ports (like one for excitatory and one for inhibitory input); or (b) on the basis of a condition likeA consequence of this is that spike ports can no longer be assumed to be linear and time-invariant in the general case (as in this case, a spike from the buffer will be processed differently depending on the sign of its weight). On the C++ side, this means that each spiking input port now uses the
VectorRingBufferclass (https://github.com/nest/nestml/pull/1299/files#diff-ee49404cf3290ce0e9ee40e25068b6d123da357aee83794ab89745a7e2aaf988R1) rather than theRingBuffer. The performance penalty of this is approximately 12.5% in a small balanced network example. An extra code generation option,linear_time_invariant_spiking_input_ports, is provided to instruct the NEST code generator that a set of given ports can be considered LTI. With this option enabled, performance is indistinguishable from the current main branch performance.Should be merged after #1288.Done.Should be merged after #1349.Done.Should be merged after #1358.Done.Should be merged after #1291.
Replaces #1137.
Fixes #944.