OSCR

Robust and replicable effects of ageing on resting-state brain electrophysiology measured with MEG

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 · 212 lines · 7 KB · BSD-3-Clause

  1. # -*- coding: utf-8 -*-
  2. #
  3. # This file is execfile()d with the current directory set to its containing dir.
  4. #
  5. # Note that not all possible configuration values are present in this
  6. # autogenerated file.
  7. #
  8. # All configuration values have a default; values that are commented out
  9. # serve to show the default.
  10. import inspect
  11. import os
  12. import shutil
  13. import sys
  14. __location__ = os.path.join(
  15. os.getcwd(), os.path.dirname(inspect.getfile(inspect.currentframe()))
  16. )
  17. # If extensions (or modules to document with autodoc) are in another directory,
  18. # add these directories to sys.path here. If the directory is relative to the
  19. # documentation root, use os.path.abspath to make it absolute, like shown here.
  20. sys.path.insert(0, os.path.join(__location__, "../.."))
  21. # -- General configuration -----------------------------------------------------
  22. # If your documentation needs a minimal Sphinx version, state it here.
  23. # needs_sphinx = '1.0'
  24. # Add any Sphinx extension module names here, as strings. They can be extensions
  25. # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
  26. extensions = [
  27. #"sphinx.ext.autosummary",
  28. #"sphinx.ext.autodoc",
  29. "sphinx.ext.intersphinx",
  30. "sphinx.ext.todo",
  31. "sphinx.ext.viewcode",
  32. "sphinx.ext.coverage",
  33. "sphinx.ext.doctest",
  34. "sphinx.ext.ifconfig",
  35. "sphinx.ext.mathjax",
  36. "sphinx.ext.napoleon",
  37. "sphinx_gallery.gen_gallery",
  38. "autoapi.extension",
  39. ]
  40. autoapi_type = "python"
  41. autoapi_keep_files = True
  42. autoapi_add_toctree_entry = False
  43. autoapi_dirs = ["../../osl_ephys"]
  44. sphinx_gallery_conf = {
  45. "examples_dirs": "tutorials", # path to your example (tutorial) scripts
  46. "gallery_dirs": "tutorials_build", # path to where to save gallery generated output
  47. }
  48. # Add any paths that contain templates here, relative to this directory.
  49. # templates_path = ["_templates"]
  50. # The suffix of source filenames.
  51. source_suffix = ".rst"
  52. # The encoding of source files.
  53. # source_encoding = 'utf-8-sig'
  54. # The master toctree document.
  55. master_doc = "index"
  56. # General information about the project.
  57. project = "osl-ephys"
  58. copyright = "2022, OHBA Methods Group, University of Oxford"
  59. author = "OHBA Methods Group, University of Oxford"
  60. # The version info for the project you're documenting, acts as replacement for
  61. # |version| and |release|, also used in various other places throughout the
  62. # built documents.
  63. #
  64. # The short X.Y version.
  65. version = "2.0.0" # Is set by calling `setup.py docs`
  66. # The full version, including alpha/beta/rc tags.
  67. release = "" # Is set by calling `setup.py docs`
  68. # The language for content autogenerated by Sphinx. Refer to documentation
  69. # for a list of supported languages.
  70. # language = None
  71. # There are two options for replacing |today|: either, you set today to some
  72. # non-false value, then it is used:
  73. # today = ''
  74. # Else, today_fmt is used as the format for a strftime call.
  75. # today_fmt = '%B %d, %Y'
  76. # List of patterns, relative to source directory, that match files and
  77. # directories to ignore when looking for source files.
  78. # exclude_patterns = ["_build"]
  79. # The reST default role (used for this markup: `text`) to use for all documents.
  80. # default_role = None
  81. # If true, '()' will be appended to :func: etc. cross-reference text.
  82. # add_function_parentheses = True
  83. # If true, the current module name will be prepended to all description
  84. # unit titles (such as .. function::).
  85. # add_module_names = True
  86. # If true, sectionauthor and moduleauthor directives will be shown in the
  87. # output. They are ignored by default.
  88. # show_authors = False
  89. # The name of the Pygments (syntax highlighting) style to use.
  90. pygments_style = "sphinx"
  91. # A list of ignored prefixes for module index sorting.
  92. # modindex_common_prefix = []
  93. # If true, keep warnings as "system message" paragraphs in the built documents.
  94. # keep_warnings = False
  95. # -- Options for HTML output ---------------------------------------------------
  96. # The theme to use for HTML and HTML Help pages. See the documentation for
  97. # a list of builtin themes.
  98. html_theme = "pydata_sphinx_theme"
  99. # Theme options are theme-specific and customize the look and feel of a theme
  100. # further. For a list of options available for each theme, see the
  101. # documentation.
  102. html_theme_options = {
  103. "gitlab_url": "https://github.com/OHBA-analysis/osl-ephys",
  104. }
  105. # Add any paths that contain custom themes here, relative to this directory.
  106. # html_theme_path = []
  107. # The name for this set of Sphinx documents. If None, it defaults to
  108. # "<project> v<release> documentation".
  109. # try:
  110. # from osl_dynamics import __version__ as version
  111. # except ImportError:
  112. # pass
  113. # else:
  114. # release = version
  115. html_title = "osl-ephys"
  116. # A shorter title for the navigation bar. Default is the same as html_title.
  117. html_short_title = "osl-ephys"
  118. # The name of an image file (relative to this directory) to place at the top
  119. # of the sidebar.
  120. html_logo = "https://avatars.githubusercontent.com/u/15248840?s=200&v=4"
  121. # The name of an image file (within the static path) to use as favicon of the
  122. # docs. This file should be a Windows icon file (.ico) being 16x16 or 32x32
  123. # pixels large.
  124. # html_favicon = None
  125. # Add any paths that contain custom static files (such as style sheets) here,
  126. # relative to this directory. They are copied after the builtin static files,
  127. # so a file named "default.css" will overwrite the builtin "default.css".
  128. # html_static_path = ["_static"]
  129. # If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
  130. # using the given strftime format.
  131. # html_last_updated_fmt = '%b %d, %Y'
  132. # If true, SmartyPants will be used to convert quotes and dashes to
  133. # typographically correct entities.
  134. # html_use_smartypants = True
  135. # Custom sidebar templates, maps document names to template names.
  136. # html_sidebars = {}
  137. # Additional templates that should be rendered to pages, maps page names to
  138. # template names.
  139. # html_additional_pages = {}
  140. # If false, no module index is generated.
  141. # html_domain_indices = True
  142. # If false, no index is generated.
  143. # html_use_index = True
  144. # If true, the index is split into individual pages for each letter.
  145. # html_split_index = False
  146. # If true, links to the reST sources are added to the pages.
  147. # html_show_sourcelink = True
  148. # If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
  149. # html_show_sphinx = False
  150. # If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
  151. # html_show_copyright = False
  152. # If true, an OpenSearch description file will be output, and all pages will
  153. # contain a <link> tag referring to it. The value of this option must be the
  154. # base URL from which the finished HTML is served.
  155. # html_use_opensearch = ''
  156. # This is the file name suffix for HTML files (e.g. ".xhtml").
  157. # html_file_suffix = None
  158. # Output file base name for HTML help builder.
  159. htmlhelp_basename = "osl-doc"
  160. intersphinx_mapping = {
  161. 'mne': ('https://mne.tools/stable/', None),
  162. 'osl-ephys': ('https://osl-ephys.readthedocs.io/en/stable/', None),
  163. 'dask': ('https://distributed.dask.org/en/stable/', None),
  164. 'sails': ('https://sails.readthedocs.io/en/stable/', None),
  165. 'matplotlib': ('https://matplotlib.org/stable/', None),
  166. }

conf.py, under BSD-3-Clause · at the source

Overview

Journal: eLife
Dates: published 16 October 2026
Identifiers: DOI · PMCID PMC13657627
Methods: Spectral & time-frequency, Connectivity, Statistics, Smoothing, state filtering, decompositions, Preprocessing, fMRI & imaging

Abstract

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

Repositories

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

Zenodo 10401792

License: CC-BY-4.0
State: the link answers
Evidence: found in the paper
Software Heritage: not checked
Found in: the references
At the source:

Zenodo 6875059

License: BSD-3-Clause
State: the link answers
Evidence: found in the paper
Software Heritage: not checked
Found in: the references
116 files
At the source:

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/zenodo:10401792.svg)](https://openscicode.org/badge/repo/zenodo:10401792)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/repo/zenodo:10401792.svg
   :target: https://openscicode.org/badge/repo/zenodo:10401792
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/repo/zenodo:10401792"><img src="https://openscicode.org/badge/repo/zenodo:10401792.svg" alt="OSCR"></a>
<!-- oscr-badge:end -->

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)

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