Post-Inhibitory Rebound Latency
Find the first spike after inhibition release within a finite observation window; zero latency with reboundObserved=false is an explicit nondetection, not an inferred event.
Description
Post-inhibitory rebound latency measures the first observed spike after inhibition ends within a stated observation window.
Post-inhibitory rebound latency measures the first observed spike after inhibition ends within a stated observation window. A missing event needs a separate presence flag.
The tool returns reboundObserved (rebound observed); latencyMs (latency ms). Input measurements and model parameters are supplied by the caller; the tool computes the stated summary rather than acquiring those measurements.
When to use Post-Inhibitory Rebound Latency
Use Post-Inhibitory Rebound Latency when you already have spikeTimesMs, inhibitionEndMs, observationEndMs and want reboundObserved, latencyMs. This is useful for checking a supplied calculation, documenting a measurement convention, or comparing observations prepared on the same basis.
How to use Post-Inhibitory Rebound Latency and understand its results
- Enter spikeTimesMs, inhibitionEndMs, observationEndMs using the field table below. Match the units, ordering and data boundaries described in the calculation.
- Run the tool after checking the stated bounds and matching paired observations or categories. A malformed request gives a tool error rather than a usable measurement.
- Read reboundObserved, latencyMs. Use the calculation and interpretation below to distinguish amounts, ratios, signs and decision flags where applicable.
- Review the supplied parameters and assumptions before using the result in a report or comparing it with another observation.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| spikeTimesMs | Spike times ms | list of number | Required |
| inhibitionEndMs | Inhibition end ms | number | Required |
| observationEndMs | Observation end ms | number | Required |
Use distinct increasing spike times and an observation end at or after release. Include both boundaries; absent rebound returns latency zero with reboundObserved=false.
latency = first qualifying spike−inhibitionEnd The symbols refer to the supplied quantities or generated values described above; unit conversions and comparison boundaries follow the stated implementation.
{
"input": {
"spikeTimesMs": [
5,
15,
25
],
"inhibitionEndMs": 10,
"observationEndMs": 30
},
"output": {
"reboundObserved": true,
"latencyMs": 5
}
}Limitations and assumptions
Read the boolean before interpreting zero, which can also be a real immediate spike. No causal rebound mechanism is established.
Numerical inputs must be finite. The tool checks its declared input shape and calculation constraints; those checks do not verify the quality, calibration or representativeness of the supplied observations.
Alternative or Complementary methods
Spike Reliability: Measure trial reliability as at least one spike in a supplied inclusive response window; empty trials count as nonresponsive, not missing observations. Spike Timing Precision: Derive per-trial stimulus-aligned first-spike latencies and inverse sample SD precision; identical latencies have undefined infinite precision and return an error.
Methodological background: Spike train variability.1
References
-
Spike train variability — Gerstner et al.; Neuronal Dynamics
Similar or alternative tools
- Spike Reliability
Measure trial reliability as at least one spike in a supplied inclusive response window; empty trials count as nonresponsive, not missing observations.
- Spike Timing Precision
Derive per-trial stimulus-aligned first-spike latencies and inverse sample SD precision; identical latencies have undefined infinite precision and return an error.