> For the complete documentation index, see [llms.txt](https://docs.axobug.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axobug.com/model.md). # Model & credits The brain behind AXOBUG, the model we run and how to interpret what you see. ## A mapped fruit fly brain The atlas uses FlyWire v783 neuron positions and annotations. The hosted simulation is a leaky integrate-and-fire model over 138,639 neurons and 2,700,513 retained connections, adapted from Fly Brain Bench. | Component | What AXOBUG uses | | ---------- | -------------------------------------------------------------- | | Anatomy | FlyWire v783 connectome and cell annotations | | Simulation | Pruned leaky integrate-and-fire network | | Model ID | flywire-v783-pruned-lif-v1 | | Movement | An engineered decoder maps neural channel rates to body drives | ## What a response means A preset injects a signal into an annotated population and the simulation tracks its propagation. Connections with fewer than five synapses between a neuron pair were removed; neuron physiology is uniform. This is an accessible computational model of mapped wiring. The model does not learn across requests, understand natural language or interpret raw video. Games and visuals add their own mapping from response to action. A fly dodging in a game demonstrates that integration, not a model trained to play the game. ## What you see on the site The playground displays actual model responses: recorded results at standard settings, API results for custom settings. Its body movement uses the decoder. The homepage ambient atlas uses continuous decorative highlights; its sugar action also requests an actual model response. ## Built on shared knowledge Connectome and annotations: FlyWire Consortium, Dorkenwald et al. and Schlegel et al. Brain model: Shiu et al. Engine and visualizations adapted from Raphael Rocha’s Fly Brain Bench. Preserve the upstream MIT and CC BY 4.0 notices when reusing their code or data.
Research & sourcesVisit the upstream research and project links.https://axobug.com/research
Data attributionOriginal data credits and a record of the adaptations.https://axobug.com/neuro/ATTRIBUTION.md
Upstream code licenseThe original MIT license notice.https://axobug.com/neuro/LICENSE.txt
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.axobug.com/model.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.