An incentive circuit for memory dynamics in the mushroom body of <i>Drosophila melanogaster</i>.
This page is built on request from the registry's record of the paper. The 6,000 most recent papers have a fuller page, built ahead of time, with the Code ↔ Paper reader, the tracing map and its validation, the record's versions, how to cite it and similar papers. This paper is older: its record, its code, its data and the requests about it are below.
Code
33 files of its code read; 15 matches between paragraphs and code. The Code ↔ Paper reader is built for the 6,000 most recent papers only: this paper's code is read at its source.
InsectRobotics/IncentiveCircuit
Code blocks with an identifier
Each block below is lines of the authors' code linked to a paragraph of this paper, with an identifier given for good: it is never reused nor deleted, and its page says what it names and how to cite it. What a block identifier is.
oscr:b:0BN4N2AVJNPNN-V: src/incentive/ , lines 130 to 198 (paragraphs 56, 13)circuit.py oscr:b:10JHP5EW5QPCT-K: src/incentive/ , lines 103 to 232 (paragraph 156)arena.py oscr:b:NNKF9QGEPH2H5-V: src/incentive/ , lines 88 to 128 (paragraphs 33, 18)circuit.py oscr:b:F0QFBKTCXKW8X-M: src/incentive/ , lines 23 to 139 (paragraphs 118, 119)models_base.py oscr:b:Z1SY1YMAQ5RFQ-N: src/incentive/ , lines 127 to 180 (paragraphs 13, 56)wheel.py oscr:b:3NNHTBENAA6DQ-V: src/incentive/ , lines 36 to 91 (paragraph 84)tmaze.py oscr:b:W979WRP350K9P-0: src/incentive/ , lines 36 to 92 (paragraph 118)bennett.py
Overview
Data
No dataset cited, and no data link found.
Contribute
The authors of this paper can claim it and correct its record, and the maintainers of its code (its owner, or a public member of its organization) correct what it says of their repository; anyone signed in can ask for its removal. Every request goes to the registry's own machine, which answers it; your account page follows them.
Sign in with ORCID to claim this paper as one of its authors or correct its record: when the paper's metadata lists your ORCID iD, you are recognized at once. Maintainers of its code: sign in with GitHub, then claim the repository on your account page.
Claim this paper
Correct its record
Say what each link of this record is, remove the ones that are not the paper's, add the ones that are missing. The correction becomes a new version of the record.
Add the badge to the code's README
Authors and maintainers of this paper's code: the badge says what OSCR knows of the paper and links the code to this page. Paste one of these under the README's title. Keep the two marks around it: they let the badge be replaced in place, never added twice. Nothing is changed for you.
Markdown
<!-- oscr-badge:start -->
[](https://openscicode.org/badge/doi/10.7554/elife.75611)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.7554/elife.75611.svg
:target: https://openscicode.org/badge/doi/10.7554/elife.75611
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.7554/elife.75611"><img src="https://openscicode.org/badge/doi/10.7554/elife.75611.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->On GitHub, open the README, choose Edit (the pencil), paste the snippet under the title, then "Commit changes".
Or let it be kept for you, once you choose it: oscr badge --write from the command line, or the GitHub Action in your repository's workflows. Every other form is on the badge page.
Request its removal
To ask for this record, the copies of its authors' scripts or its tracing map to be removed, use the removal request page: signed in, you say who you are, what to remove and why, then review and confirm the request. Published rules decide every request (how).
