Added more information about spike generation and precision #364

Merged
merged 2 commits into from May 24, 2016

Conversation

Projects
None yet
3 participants
@jougs
Contributor

jougs commented May 24, 2016

This fixes trac.783

I propose @steffengraber and @heplesser as reviewers.

+## Spike generation and precision
+
+A neuron fires a spike when the membrane potential at the end of an update interval of
+the simulation resolution is above threshold. For most models, the membrane potential

This comment has been minimized.

@heplesser

heplesser May 24, 2016

Contributor

I'd reorder the sentence a little: "A neuron fires a spike when the membrane potential is above threshold at the end of an update interval (i.e., a multiple of the simulation resolution)."

@heplesser

heplesser May 24, 2016

Contributor

I'd reorder the sentence a little: "A neuron fires a spike when the membrane potential is above threshold at the end of an update interval (i.e., a multiple of the simulation resolution)."

+This means that the last membrane potential value at the last time step before the spike
+can vary, while the potential right after the step will usually be the reset potential
+(some models may deviate from this). The time of the spike is always the time at the end
+of the interval during which the threshold was crossed.

This comment has been minimized.

@heplesser

heplesser May 24, 2016

Contributor

I would highlight the end of the interval.

@heplesser

heplesser May 24, 2016

Contributor

I would highlight the end of the interval.

+is then reset to some fixed value and clamped to that value during the refractory time.
+This means that the last membrane potential value at the last time step before the spike
+can vary, while the potential right after the step will usually be the reset potential
+(some models may deviate from this). The time of the spike is always the time at the end

This comment has been minimized.

@heplesser

heplesser May 24, 2016

Contributor

Add: "This also means that the membrane potential recording will never show values above the threshold."

@heplesser

heplesser May 24, 2016

Contributor

Add: "This also means that the membrane potential recording will never show values above the threshold."

This comment has been minimized.

@steffengraber

steffengraber May 24, 2016

Contributor

Standard markdown definition says:

A First Level Header
====================

A Second Level Header
---------------------

### Header 3

You did it the github way.
So, what is our standard?

@steffengraber

steffengraber May 24, 2016

Contributor

Standard markdown definition says:

A First Level Header
====================

A Second Level Header
---------------------

### Header 3

You did it the github way.
So, what is our standard?

-Please see the [FAQ on precise spike time neurons](../qa-precise-spike-times/index.html)
-for details about neuron update in continuous time and the [documentation on connection management](../connection_management/index.html)
+NEST also has a small number of models that determine the precise time of the threshold

This comment has been minimized.

@heplesser

heplesser May 24, 2016

Contributor

Replace "a small number of" with "some".

@heplesser

heplesser May 24, 2016

Contributor

Replace "a small number of" with "some".

@heplesser

This comment has been minimized.

Show comment
Hide comment
@heplesser

heplesser May 24, 2016

Contributor

@jougs Thanks! I suggested some small changes, with those 👍.

Contributor

heplesser commented May 24, 2016

@jougs Thanks! I suggested some small changes, with those 👍.

@steffengraber

This comment has been minimized.

Show comment
Hide comment
@steffengraber

steffengraber May 24, 2016

Contributor

@jougs @heplesser
We have to decide what we use, standard markdown or the github flavored.
I used standard markdown.

Contributor

steffengraber commented May 24, 2016

@jougs @heplesser
We have to decide what we use, standard markdown or the github flavored.
I used standard markdown.

@steffengraber

This comment has been minimized.

Show comment
Hide comment
@steffengraber

steffengraber May 24, 2016

Contributor

@jougs @heplesser
For me standard means the setext-style.
Github used the atx-style.

Kramdown understand Github-flavored markdown. See #365.
So, you are right to change the headlines. 👍

Contributor

steffengraber commented May 24, 2016

@jougs @heplesser
For me standard means the setext-style.
Github used the atx-style.

Kramdown understand Github-flavored markdown. See #365.
So, you are right to change the headlines. 👍

@jougs

This comment has been minimized.

Show comment
Hide comment
@jougs

jougs May 24, 2016

Contributor

@heplesser, @steffengraber: thanks for the review. I hope to have addressed your comments.

Contributor

jougs commented May 24, 2016

@heplesser, @steffengraber: thanks for the review. I hope to have addressed your comments.

@heplesser

This comment has been minimized.

Show comment
Hide comment
@heplesser

heplesser May 24, 2016

Contributor

ATX-style also seems common in iPython notebooks, so I think it is smart to move all to atx. Thus merging.

Contributor

heplesser commented May 24, 2016

ATX-style also seems common in iPython notebooks, so I think it is smart to move all to atx. Thus merging.

@heplesser heplesser merged commit ec44c45 into nest:master May 24, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment