FBW-P04

Visual Motion and Target Tracking

Connect visual motion processing to neural control for direction detection and continuous target following.

Training preparationApplications open

Apply to join training

Statistics temporarily unavailable

Project background

Establish motion-direction recognition before connecting the readout to steering and continuous tracking. Evaluation will vary target speed, contrast, background interference and occlusion. Input mapping and circuit structure must be justified rather than replaced with hidden access to target coordinates.

This project connects a defined neural-computation question to a reproducible evaluation protocol and a community participation pathway. Results will be interpreted only within their recorded model, task and evidence scope.

Training goals

  • Improve stable direction recognition.
  • Reduce tracking angle error and target loss.
  • Reduce reacquisition time after an occlusion.

Current foundation and milestones

The connectome and general simulation form a foundation. Visual encoding and tracking-specific readouts still need development and evidence.

Next milestone: Establish a motion-direction recognition benchmark

  1. PlannedEstablish a motion-direction recognition benchmark
  2. PlannedImplement the versioned task and measurement interface
  3. PlannedEvaluate frozen conditions and independent reproduction

Content updated:

Technical approach

Build simplified visual stimuli and spatiotemporal encoding, verify the relation between visual cell types and input positions, and read downstream responses. Evaluate the visual readout and behavioral controller separately before assessing them together. Ground-truth screen coordinates are evaluator inputs, not a substitute for neural visual recognition.

Method schematic

Visualmotion encodingMappedvisual pathwaysDirection andaction readoutTarget andobserver stateAction changes the next sensory observation
A proposed project interface. Arrows describe information flow, not measured neural connections or a running training batch.

Task and evaluation design

Evaluation design

Changing speedCondition 1Background interferenceCondition 2Brief occlusionCondition 3
Planned conditions for the project benchmark. These illustrations are protocol designs, not recorded performance.
IndicatorDefinitionDirectionUnitsObservation
Direction accuracyFraction of held-out stimuli with the correct direction readout.Higher is better%Awaiting evaluation
Tracking angle errorAngular difference between desired and realized tracking direction.Lower is betterdegreesAwaiting evaluation
Target lossFraction of the evaluation interval outside the tracking criterion.Lower is better%Awaiting evaluation
Reacquisition timeModel time needed to recover tracking after occlusion.Lower is bettermodel timeAwaiting evaluation

No measured values have been published. Acceptance thresholds will be frozen in each task protocol before evaluation.

Expected deliverables

  • Motion-direction readout configurations.
  • Versioned tracking-control configurations.
  • Speed and occlusion evaluation sets with reproduction reports.

Ways to participate

  • Visual stimulus construction
  • Parameter optimization
  • Batch evaluation
  • Control-interface development

Device requirements and task schedules will be matched by the community after runnable profiles have been evaluated. Unknown specifications are welcome in the application.

Apply to join training

Applications are received for community review and matching. Selection does not mean training has started.

Participation roles

Select at least one role.

Optional device information

Unknown specifications are welcome. These are self-reported intentions, not measured performance.

Signing in associates this application with your account. Applying does not start training or authorize payments.

View my applications ↗

References and related work

External sources provide technical background. They do not establish equivalent FBW capabilities.

View published research records ↗