OSCR

Individual dopaminergic neurons induce unique, yet overlapping combinations of behavioural modulations, including safety learning, memory retrieval, and acute locomotion

Code ↔ Paper

The paper beside its authors' code: matches between them have not been computed for this paper yet.

Paper

Loaded from Europe PMC by your browser; OSCR does not store it: doi.org · Europe PMC

The paper is loaded when this pane is shown.

The authors' code

Python · 96 lines · 3.8 KB · no license

  1. # The default ``config.py``
  2. def set_prefs(prefs):
  3. """This function is called before opening the project"""
  4. # Specify which files and folders to ignore in the project.
  5. # Changes to ignored resources are not added to the history and
  6. # VCSs. Also they are not returned in `Project.get_files()`.
  7. # Note that ``?`` and ``*`` match all characters but slashes.
  8. # '*.pyc': matches 'test.pyc' and 'pkg/test.pyc'
  9. # 'mod*.pyc': matches 'test/mod1.pyc' but not 'mod/1.pyc'
  10. # '.svn': matches 'pkg/.svn' and all of its children
  11. # 'build/*.o': matches 'build/lib.o' but not 'build/sub/lib.o'
  12. # 'build//*.o': matches 'build/lib.o' and 'build/sub/lib.o'
  13. prefs['ignored_resources'] = [
  14. '*.pyc', '*~', '.ropeproject', '.hg', '.svn', '_svn', '.git',
  15. '.tox', '.env', 'node_modules', 'bower_components']
  16. # Specifies which files should be considered python files. It is
  17. # useful when you have scripts inside your project. Only files
  18. # ending with ``.py`` are considered to be python files by
  19. # default.
  20. #prefs['python_files'] = ['*.py']
  21. # Custom source folders: By default rope searches the project
  22. # for finding source folders (folders that should be searched
  23. # for finding modules). You can add paths to that list. Note
  24. # that rope guesses project source folders correctly most of the
  25. # time; use this if you have any problems.
  26. # The folders should be relative to project root and use '/' for
  27. # separating folders regardless of the platform rope is running on.
  28. # 'src/my_source_folder' for instance.
  29. #prefs.add('source_folders', 'src')
  30. # You can extend python path for looking up modules
  31. #prefs.add('python_path', '~/python/')
  32. # Should rope save object information or not.
  33. prefs['save_objectdb'] = True
  34. prefs['compress_objectdb'] = False
  35. # If `True`, rope analyzes each module when it is being saved.
  36. prefs['automatic_soa'] = True
  37. # The depth of calls to follow in static object analysis
  38. prefs['soa_followed_calls'] = 0
  39. # If `False` when running modules or unit tests "dynamic object
  40. # analysis" is turned off. This makes them much faster.
  41. prefs['perform_doa'] = True
  42. # Rope can check the validity of its object DB when running.
  43. prefs['validate_objectdb'] = True
  44. # How many undos to hold?
  45. prefs['max_history_items'] = 32
  46. # Shows whether to save history across sessions.
  47. prefs['save_history'] = True
  48. prefs['compress_history'] = False
  49. # Set the number spaces used for indenting. According to
  50. # :PEP:`8`, it is best to use 4 spaces. Since most of rope's
  51. # unit-tests use 4 spaces it is more reliable, too.
  52. prefs['indent_size'] = 4
  53. # Builtin and c-extension modules that are allowed to be imported
  54. # and inspected by rope.
  55. prefs['extension_modules'] = []
  56. # Add all standard c-extensions to extension_modules list.
  57. prefs['import_dynload_stdmods'] = True
  58. # If `True` modules with syntax errors are considered to be empty.
  59. # The default value is `False`; When `False` syntax errors raise
  60. # `rope.base.exceptions.ModuleSyntaxError` exception.
  61. prefs['ignore_syntax_errors'] = False
  62. # If `True`, rope ignores unresolvable imports. Otherwise, they
  63. # appear in the importing namespace.
  64. prefs['ignore_bad_imports'] = False
  65. # If `True`, rope will transform a comma list of imports into
  66. # multiple separate import statements when organizing
  67. # imports.
  68. prefs['split_imports'] = False
  69. # If `True`, rope will sort imports alphabetically by module name
  70. # instead of alphabetically by import statement, with from imports
  71. # after normal imports.
  72. prefs['sort_imports_alphabetically'] = False
  73. def project_opened(project):
  74. """This function is called after opening the project"""
  75. # Do whatever you like here!

config.py at commit 9cb9fca, no license · at the source

Overview

Journal: eLife
Dates: published 19 October 2026
Identifiers: DOI · PMCID PMC13675010
Methods: Statistics, Machine learning

Abstract

No abstract was found for this paper: the paper, at the publisher.

Repository

Its files are read in the Code ↔ Paper reader above.

mthane/IMBA

License: none: the authors keep all their rights
State: the link answers
Evidence: found in the paper
Commit: 9cb9fcaf79f412166d2e571398898b416b6660eb
Languages: R (97), C++ (8), Python (5), Shell (5)
Size: 115 scripts
Software Heritage: not archived
Found in: “Data availability”
116 files
At the source: github.com/mthane/IMBA

Tracing map

Proposed by the machine: these links were found in the paper and verified at the source, without human review. The map will receive a Zenodo DOI once one of the paper's authors has validated it with their ORCID.

Data

No dataset and no data link were found in the paper.

Versions

The history of this record: each version stored by the harvester or made by a correction of its authors or of the maintainers of its code, and what changed in its facts. The texts of the paper (its abstract, its availability statements) are not part of it; versions that changed only those are not listed.

No version of this record has been stored yet.

Cite

Cite the paper by its DOI: .

The tracing map gets a citation of its own once an author has validated it and it has a DOI.

Similar papers

No other paper with a page shares enough with this one yet: tools, categories, datasets, references or authors.

Contribute

The authors of this paper can claim it, correct its record and validate its tracing map, 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 OSCR's own machine, which answers it; your account page follows them.

Sign in with ORCID to claim this paper as one of its authors, correct its record or validate its tracing map: 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.

Add the badge to the code's README

OSCR: the badge of this paper

If you are an author or a maintainer of this paper's code, you can add this badge. It says what OSCR knows of the paper (its code, its validated tracing map) and links the code to this page. Paste one of these snippets under the README's title. Keep the two marks around it, so that the badge can be replaced in place and is never added twice. OSCR changes nothing in your repository.

Markdown
<!-- oscr-badge:start -->
[![OSCR](https://openscicode.org/badge/repo/github.com/mthane/imba.svg)](https://openscicode.org/badge/repo/github.com/mthane/imba)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/repo/github.com/mthane/imba.svg
   :target: https://openscicode.org/badge/repo/github.com/mthane/imba
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/repo/github.com/mthane/imba"><img src="https://openscicode.org/badge/repo/github.com/mthane/imba.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".

If you choose to, you can have the badge kept up to date for you, with oscr badge --write from the command line or with the GitHub Action in your repository's workflows. Every other form and option (a card, AsciiDoc, LaTeX, shields.io) is on the badge page.

Request its removal

To ask OSCR to remove this record, the copies of its authors' scripts or its tracing map, 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).

Discussion, reproductions, activity

Discussion: code errors and mismatches between the code and the paper about this paper and its code, from readers and its authors, beside the paper and its tracing map.

Report a mismatch between the code and the paper · Report a code error (signed in)

Reproductions: reports from readers who ran the authors' code and did not get the paper's result, what they ran, with which environment, commit and data.

Report a reproduction failure (signed in)

Versions of its code: the releases of its code tied to a version of this paper (the preprint, the accepted manuscript, the version of record…), each with the tracing map versioned with it.

Activity: what happens around this paper: new versions of its record, its map's validation, discussions and reproductions. It opens with sign-in.