Burst Firing in a Motion-Sensitive Neural Pathway Correlates with Expansion Properties of Looming Objects that Evoke Avoidance Behaviors
Bibliographic record
Abstract
The locust visual system contains a well-defined motion-sensitive pathway that transfers visual input to motor centers involved in predator evasion and collision avoidance. One interneuron in this pathway, the descending contralateral movement detector (DCMD), is typically described as using rate coding; edge expansion of approaching objects causes an increased rate of neuronal firing that peaks after a certain retinal threshold angle is exceeded. However, evidence of intrinsic DCMD bursting properties combined with observable oscillations in mean firing rates and tight clustering of spikes in raw traces, suggest that bursting may be important for motion detection. Sensory neuron bursting provides important timing information about dynamic stimuli in many model systems, yet no studies have rigorously investigated if bursting occurs in the locust DCMD during object approach. We presented repetitions of 30 looming stimuli known to generate behavioral responses to each of 20 locusts in order to identify and quantify putative bursting activity in the DCMD. Overall, we found a bimodal distribution of inter-spike intervals (ISI) with peaks of more frequent and shorter ISIs occurring from 1-8 ms and longer less frequent ISIs occurring from 40-50 ms. Subsequent analysis identified bursts and isolated single spikes from the responses. Bursting frequency increased in the latter phase of an approach and peaked at the time of collision, while isolated spiking was predominant during the beginning of stimulus approach. We also found that the majority of inter-burst intervals (IBIs) occurred at 40-50 ms (or 20-25 bursts/s). Bursting also occurred across varied stimulus parameters and suggests that burst timing may be a key component of looming detection. Our findings suggest that the DCMD uses two modes of coding to transmit information about looming stimuli and that these modes change dynamically with a changing stimulus at a behaviorally-relevant time.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".