Skip to content

Commit

Permalink
Change to FAQ, suggested by issue #22.
Browse files Browse the repository at this point in the history
  • Loading branch information
PTRRupprecht committed Oct 24, 2021
1 parent 6792647 commit 418af7f
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions Demo scripts/Calibrated_spike_inference_with_Cascade.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -675,6 +675,17 @@
">The output **spike_prob** is the _expected number of spikes_ in this time bin, at the same resolution as the original calcium recording. This metric is also called _spike probability_ for brevity in the paper and elsewhere. If you sum over the trace in time, you will get the estimated **number of spikes**. If you multiply the trace with the frame rate, you will get an estimate of the instantaneous **spike rate**. Spike probability and spike rates can therefore be converted by multiplication with the frame rate."
]
},
{
"cell_type": "markdown",
"metadata": {
"id": "2tXN9GYU7Kc9"
},
"source": [
"#### Can **spike_prob** be larger than 1?\n",
"\n",
">Yes. As described above (\"What does the output of the algorithm mean?\"), the output of the algorithm is strictly speakint not a probability and therefore not restricted to values between 0 and 1. A value >1 would simply indicate that the estimated number of spikes in the time bin is larger than 1. "
]
},
{
"cell_type": "markdown",
"metadata": {
Expand Down

0 comments on commit 418af7f

Please sign in to comment.