OSCR

The genetic architecture of cortical similarity networks.

Code ↔ Paper

5 matches between paragraphs of the paper and lines of its authors' code, computed by the harvester (lexical-v1). Click a colored paragraph or line to see its counterpart.

3 blocks of code here have a permanent identifier (oscr:b:…), listed with the matches below: citable for good, with a page of its own. Select a match and press Cite to copy it. What a block identifier is.

The 5 matches
  1. [1] § Methods › Magnetic resonance imaging (MRI) data › Structural MRI feature selection ↔ get_vertex_df.py, lines 11 to 57 · score 0.67 · fractional anisotropy, FA, SA, volume, MC, thickness · block oscr:b:H30T19HTCAHP4-U · Report a mismatch
  2. [2] § Methods › Magnetic resonance imaging (MRI) data › Structural MRI feature selection ↔ MIND.py, lines 8 to 49 · score 0.65 · surface area, cortical thickness, Vol, MIND network, biological, SA · block oscr:b:2N70MCVWWBKTM-G · Report a mismatch
  3. [3] § Methods › Magnetic resonance imaging (MRI) data › Structural MRI feature selection ↔ MIND.py, lines 8 to 49 · score 0.56 · surface area, Cortical thickness, summing, volume, vertex · block oscr:b:2N70MCVWWBKTM-G · Report a mismatch
  4. [4] § Methods › Magnetic resonance imaging (MRI) data › Structural MRI feature selection ↔ MIND.py, lines 8 to 49 · score 0.56 · surface area, Cortical thickness, summing, volume, vertex · block oscr:b:2AAN0938ZR5FZ-N · Report a mismatch
  5. [5] § Methods › Magnetic resonance imaging (MRI) data › Structural MRI feature selection ↔ get_vertex_df.py, lines 11 to 57 · score 0.53 · FreeSurfer, vertex, MC, CT, thickness, surface · block oscr:b:H30T19HTCAHP4-U · Report a mismatch

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 · 203 lines · 9.4 KB · no license · 2 matches

  1. import sys
  2. import numpy as np
  3. import os
  4. import pandas as pd
  5. from os.path import exists
  6. from nibabel.freesurfer.io import read_morph_data, read_annot
  7. from nibabel.freesurfer.mghformat import load
  8. from collections import defaultdict
  9. from MIND_helpers import calculate_mind_network, is_outlier
  10. def get_vertex_df(surf_dir, features, parcellation):
  11. '''
  12. INPUT SPECIFICATIONS:
  13. • surf_dir (str) : This is a string the location containing all relevant directories output by FreeSurfer (i.e. label, mri, surf).
  14. • features (list):
  15. This function accepts the "features" argument as a list containing items in the following forms:
  16. str:
  17. • One of ['CT','Vol','SA','MC','SD']. In this form, the function will automatically assume that the requested features are found in the surf_dir/surf directory and correspond to the following files:
  18. CT: ?h.thickness
  19. Vol: ?h.volume
  20. SA: ?h.area
  21. MC: ?h.curv
  22. SD: ?h.sulc
  23. • You may also pass a string in the form 'thickness', 'volume', 'sulc', etc, which refer directly to default files already found in the surf_dir/surf directory for both rh and lh.
  24. For example, the function will interpret the entry 'thickness' to refer to the files surf_dir/surf/lh.thickness and surf_dir/surf/rh.thickness
  25. • Finally, you may pass a string in the form of a FULL path as follows: with a question mark '?' indicating the position specifying the hemisphere such as "full/path/to/?h.feature".
  26. Using this formulation will cause the command to look for files that exactly match both "full/path/to/lh.feature" and "full/path/to/rh.feature". If the left and right version of the files aren't exactly the same otherwise, this won't work.
  27. tuple: (path/to/lh_surface_feature, path/to/rh_surface_feature)
  28. • If you would rather pass other features directly into the function, you must specify the locations (using paths) of both the left and right versions of each desired feature as a tuple.
  29. **The files must be readable by nibabel's read_morph_data function, i.e. in FreeSurfer's surface format!***
  30. So for example, if you have used the provided register_and_vol2surf function to generate surface maps of fractional anisotropy in a separate folder, you could pass them as an element in the list like:
  31. (path/to/lh.FA.mgh, path/to/rh.FA.mgh)
  32. A valid list of feature values combining these different input types would therefore be: ['CT','SD',(path/to/lh_feature1, path/to/rh_feature1), (path/to/lh_feature2, path/to/rh_feature2)]
  33. • parcellation (str): This is a string the location containing parcellation scheme to be used. The files 'lh.' + parcellation + '.annot' and 'rh.' + parcellation + '.annot' must exist inside the surf_dir/label directory.
  34. '''
  35. #specify data locations
  36. surfer_location = surf_dir + '/'
  37. #Check inputs!
  38. if (exists(surfer_location + '/label/lh.' + parcellation + '.annot') == False) or (exists(surfer_location + '/label/rh.' + parcellation + '.annot') == False):
  39. raise Exception('Parcellation files not found.')
  40. all_shorthand_features = ['CT','Vol','SA','MC','SD']
  41. all_shorthand_features_dict = dict(zip(all_shorthand_features, ['thickness','volume','area','curv','sulc']))
  42. lh_feature_locs = []
  43. rh_feature_locs = []
  44. #Check feature inputs, store location of files
  45. for feature in features:
  46. if feature in all_shorthand_features:
  47. lh_loc = surfer_location + 'surf/lh.' + all_shorthand_features_dict[feature]
  48. rh_loc = surfer_location + 'surf/rh.' + all_shorthand_features_dict[feature]
  49. if (exists(lh_loc) == False) or (exists(rh_loc) == False):
  50. raise Exception('Feature for input "' + feature +'" not found.')
  51. else:
  52. lh_feature_locs.append(lh_loc)
  53. rh_feature_locs.append(rh_loc)
  54. elif type(feature) is str:
  55. if len(feature.split('/')) == 1:
  56. lh_loc = surfer_location + 'surf/lh.' + feature
  57. rh_loc = surfer_location + 'surf/rh.' + feature
  58. if (exists(lh_loc) == False) or (exists(rh_loc) == False):
  59. raise Exception('Feature for input "' + feature +'" not found.')
  60. else:
  61. lh_feature_locs.append(lh_loc)
  62. rh_feature_locs.append(rh_loc)
  63. else:
  64. lh_loc = feature.split('/')
  65. lh_loc[-1] = 'l' + lh_loc[-1][1:]
  66. lh_loc = '/'.join(lh_loc)
  67. rh_loc = feature.split('/')
  68. rh_loc[-1] = 'r' + rh_loc[-1][1:]
  69. rh_loc = '/'.join(rh_loc)
  70. if (exists(lh_loc) == False) or (exists(rh_loc) == False):
  71. raise Exception('Feature for input "' + feature +'" not found.')
  72. else:
  73. lh_feature_locs.append(lh_loc)
  74. rh_feature_locs.append(rh_loc)
  75. elif type(feature) is tuple:
  76. lh_loc = feature[0]
  77. rh_loc = feature[1]
  78. if (exists(lh_loc) == False) or (exists(rh_loc) == False):
  79. raise Exception('Feature for input "' + feature[0] +'" or "' + feature[1] +'" not found.')
  80. else:
  81. lh_feature_locs.append(lh_loc)
  82. rh_feature_locs.append(rh_loc)
  83. else:
  84. raise Exception('Unrecognized format for feature input: ', feature)
  85. #Get annotation files
  86. lh_annot = read_annot(surfer_location + '/label/lh.' + parcellation + '.annot', orig_ids = True)
  87. rh_annot = read_annot(surfer_location + '/label/rh.' + parcellation + '.annot', orig_ids = True)
  88. annot_dict = {'lh':lh_annot, 'rh':rh_annot}
  89. '''
  90. The regions in the lh and rh need to be renamed and distinct.
  91. So, here we append lh_ or rh_ to the front of each region name and make a conversion dict.
  92. This will likely need to change for different processing pipelines (FS versions) and datasets etc.
  93. so make sure this dict is correct and looks good.
  94. '''
  95. lh_region_names = ['lh_' + str(x).split("'")[1] for x in lh_annot[2]]
  96. rh_region_names = ['rh_' + str(x).split("'")[1] for x in rh_annot[2]]
  97. lh_convert_dict = dict(zip(lh_annot[1][:,-1], lh_region_names))
  98. rh_convert_dict = dict(zip(rh_annot[1][:,-1], rh_region_names))
  99. convert_dicts = {'lh': lh_convert_dict,\
  100. 'rh': rh_convert_dict}
  101. used_labels_l = np.intersect1d(np.unique(lh_annot[0]), list(lh_convert_dict.keys()))
  102. used_labels_r = np.intersect1d(np.unique(rh_annot[0]), list(rh_convert_dict.keys()))
  103. used_labels = {'lh': used_labels_l,\
  104. 'rh': used_labels_r}
  105. used_regions_l = np.array([value for key, value in lh_convert_dict.items() if key in used_labels_l])
  106. used_regions_r = np.array([value for key, value in rh_convert_dict.items() if key in used_labels_r])
  107. combined_regions = np.hstack((used_regions_l, used_regions_r))
  108. unknown_regions = [x for x in combined_regions if (('?' in x) | ('unknown' in x) | ('Unknown' in x) | ('Medial_Wall' in x) | (len(x) == 3))]
  109. combined_regions = np.array([x for x in combined_regions if x not in unknown_regions])
  110. vertex_data_dict = defaultdict()
  111. #Now load up all the vertex-level data!
  112. for hemi in ['lh','rh']:
  113. print(hemi)
  114. hemi_data_dict = defaultdict()
  115. if hemi == 'lh':
  116. print('Loading left hemisphere data:')
  117. for i, lh_feature_loc in enumerate(lh_feature_locs):
  118. print(lh_feature_loc)
  119. #check for mgh/mgz format vs regular curv files
  120. if lh_feature_loc.endswith('mgh') or lh_feature_loc.endswith('mgz'):
  121. hemi_data_dict['Feature_' + str(i)] = load(lh_feature_loc).get_fdata().flatten()
  122. else:
  123. hemi_data_dict['Feature_' + str(i)] = read_morph_data(lh_feature_loc)
  124. elif hemi == 'rh':
  125. print('Loading right hemisphere data:')
  126. for i, rh_feature_loc in enumerate(rh_feature_locs):
  127. if rh_feature_loc.endswith('mgh') or rh_feature_loc.endswith('mgz'):
  128. hemi_data_dict['Feature_' + str(i)] = load(rh_feature_loc).get_fdata().flatten()
  129. else:
  130. hemi_data_dict['Feature_' + str(i)] = read_morph_data(rh_feature_loc)
  131. used_features = list(hemi_data_dict.keys())
  132. print(used_features)
  133. hemi_data = np.zeros((len(used_features) + 1, len(annot_dict[hemi][0])))
  134. hemi_data[0] = annot_dict[hemi][0]
  135. for i, feature in enumerate(used_features):
  136. print(i, feature)
  137. hemi_data[i + 1] = hemi_data_dict[feature]
  138. col_names = ['Label'] + used_features
  139. hemi_data = pd.DataFrame(hemi_data.T, columns = col_names)
  140. #Select only the vertices that map to regions.
  141. hemi_data = hemi_data.loc[hemi_data['Label'].isin(used_labels[hemi])]
  142. hemi_data["Label"] = hemi_data["Label"].map(convert_dicts[hemi])
  143. vertex_data_dict[hemi] = hemi_data
  144. vertex_data = pd.concat([vertex_data_dict['lh'], vertex_data_dict['rh']], ignore_index = True)
  145. #Output data
  146. print("features used: ")
  147. print(used_features)
  148. return vertex_data, combined_regions, used_features

get_vertex_df.py at commit 0d33445, no license · at the source

Overview

Authors: Isaac Sebenius1,2,3, Varun Warrier1,4, Richard A. I. Bethlehem4, Richard Dear1, Eva-Maria Stauffer1, Yuanjun Gu1,5, Rafael Romero-Garcia1,6, Jakob Seidlitz7,8,9, Edward Bullmore1,10, Sarah Morgan2,11
  1. Department of Psychiatry, University of Cambridge,Cambridge, United Kingdom
  2. Department of Computer Science and Technology, University of Cambridge,Cambridge, United Kingdom
  3. Harvard Medical School,Boston, MA US
  4. Department of Psychology, University of Cambridge,Cambridge, United Kingdom
  5. Autism Research Centre, University of Cambridge,Cambridge, United Kingdom
  6. Instituto de Biomedicina de Sevilla (IBiS) HUVR/CSIC/Universidad de Sevilla/CIBERSAM, ISCIII, Departamento de Fisiología Médica y Biofísica,Seville, Spain
  7. Department of Psychiatry, University of Pennsylvania,Philadelphia, PA USA
  8. Department of Child and Adolescent Psychiatry and Behavioral Science, The Children’s Hospital of Philadelphia,Philadelphia, PA USA
  9. Lifespan Brain Institute, The Children’s Hospital of Philadelphia,Philadelphia, PA USA
  10. School of Academic Psychiatry, Institute of Psychiatry, Psychology & Neuroscience, King’s College London,London, United Kingdom
  11. School of Biomedical Engineering & Imaging Sciences, King’s College London,London, United Kingdom
Institutions: University of Cambridge (United Kingdom); Harvard University (United States); Universidad de Sevilla (Spain); University of Pennsylvania (United States); Children's Hospital of Philadelphia (United States); King's College London (United Kingdom)
Journal: Nature communications, volume 17, issue 1, article 7801
Dates: received 3 March 2025; accepted 29 April 2026; published online 20 June 2026
Type: Research article · Language: English
License: CC BY
Identifiers: DOI 10.1038/s41467-026-73714-9 · PMID 42323287 · PMCID PMC13438111 · OpenAlex W4405711577
Open access: gold, a free copy (OpenAlex)
Status: code verified (how the code is found and verified)
Categories: genetics / omics (modality), structural MRI / diffusion (modality), human (organism)
Methods: Spectral & time-frequency, Statistics, Smoothing, state filtering, decompositions, Machine learning, fMRI & imaging, Preprocessing
Keywords: Genetics of the nervous system, Neuroscience
MeSH: Cerebral Cortex*, Nerve Net*, Brain Mapping, Female, Humans, Magnetic Resonance Imaging, Male (* major topic)
Topic: Bioinformatics and Genomic Networks (Molecular Biology, Biochemistry, Genetics and Molecular Biology), according to OpenAlex
Funding: Wellcome Trust (214322, 226392/Z/22/Z); National Institute for Health Research (NIHR) (NIHR203312)
Citations: cited by 1 paper (Europe PMC); 111 references in the paper

Abstract

The genetic architecture of human brain networks is central to understanding cortical organisation and evolution, the causal links between brain structure and function, and the pathogenesis of neuropsychiatric disorders. Using N > 48,000 subjects, we investigated common genetic effects on Morphometric INverse Divergence (MIND), a heritable, multi-modal structural MRI metric of inter-areal similarity and connectivity. Genetic correlations between MIND network edges were largely reducible to two gradients, each aligned with distance from one of the two phylogenetically primitive areas (paleocortex and archicortex) predicted by the dual origin theory of cortical evolution. MIND was more heritable than comparable measures of functional (f)MRI connectivity, and the paleocortically-aligned MIND gradient was genetically correlated with, and causally predictive of, fMRI connectivity. Finally, we identified genetic overlaps between MIND gradients and neuropsychiatric and biomedical traits. These results provide fresh insight into the dual origins of the cortex and their implications for brain function and health.

Reproduced under the paper's license (CC BY), from the paper cited above.

Repositories

Its files are read in the Code ↔ Paper reader above, with 5 matches between paragraphs and lines of code.

jrs95/geni.plots

License: GPL-3.0
State: the link answers, verified on 27 September 2026
Evidence: files inventoried
Commit: aa25803629235b681ada96741a1b0c07dc059870, 14 October 2024
Languages: R (7)
Size: 42 files, 7 scripts
Software Heritage: not archived
Found in: “Code availability”
Holds: README, license file, environment (DESCRIPTION), continuous integration, documentation, 1 notebook
Not found: CITATION.cff, tests
Tools: tidyverse (5 files), ggplot2 (4 files), patchwork (1 file)
Availability: 1 check, the latest on 27 September 2026: the link answers
  • 27 September 2026: the link answers
9 files

Zenodo 7974716

License: other-open
State: the link answers, verified on 2 November 2026
Evidence: files inventoried
Size: 1 file
Software Heritage: not checked
Found in: “Code availability”
Not found: README, license file, CITATION.cff, environment file, tests, continuous integration, documentation
Tools: NumPy (5 files), pandas (5 files), NiBabel (3 files), SciPy (3 files), Matplotlib (2 files), AFNI (1 file), FreeSurfer (1 file), Nipype (1 file)
Availability: 2 checks, the latest on 2 November 2026: the link answers (HTTP 200)
  • 2 November 2026: the link answers (HTTP 200)
  • 27 September 2026: the link answers (HTTP 200)
7 files
At the source:

isebenius/mind

License: none: the authors keep all their rights
State: the link answers, verified on 2 November 2026
Evidence: files inventoried
Commit: 0d334454eaac62e49a197801446ce7750256c882, 12 March 2024
Languages: Python (4), Jupyter (2)
Size: 15 files, 6 scripts
Software Heritage: not archived
Found in: the Zenodo archive record
Holds: README, environment (requirements.txt)
Not found: license file, CITATION.cff, tests, continuous integration, documentation
Tools: NumPy (5 files), pandas (5 files), NiBabel (3 files), SciPy (3 files), Matplotlib (2 files), AFNI (1 file), FreeSurfer (1 file), Nipype (1 file)
Availability: 2 checks, the latest on 2 November 2026: the link answers
  • 2 November 2026: the link answers
  • 27 September 2026: the link answers
7 files

Code availability

Code to calculate MIND networks can be accessed at 10.5281/zenodo.7974716. FastGWA was conducted with GCTA software v.1.94.1107. Colocalisation was performed using coloc v5.2.3 and R v4.3.1. Genal was used for for MR sensitivity analysis108. Both plink v1.9 and 2.0 were used in this study109. Gradient decomposition was performed using the BrainSpace Python package v0.1.1048. Data analysis and visualisation was conducted using Python 3.6, 3.9, and 3.11. Locus plots were created using https://github.com/jrs95/geni.plots. Brain network plots were created using NetPlotBrain v0.3.0110. UpSet plots were created using the code from ref. 111. Phenogram chromosome maps were created using the software at https://visualization.ritchielab.org/phenograms/plot.

Reproduced under the paper's license (CC BY), from the paper cited above.

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.

What the map holds:

  • 3 repositories of the authors' code, each at its verified commit, with its license and how the link was found in the paper;
  • 19 scripts, each with its path and the digest of its content;
  • 5 matches between paragraphs of the paper and lines of the code (method lexical-v1);
  • neither the text of the paper nor the code itself.

Its JSON (tracing-map.json) is deposited on Zenodo with its DOI once the map is validated.

Data

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

Data availability

All summary statistics generated in this study are publicly available at 10.17863/CAM.128272. These include summary statistics for the 276 network edges and 2 genetic gradients for both MIND and FC phenotypes. Summary statistics for schizophrenia (SCZ), major depressive disorder (MDD), attention-deficit hyperactivity disorder (ADHD), autism spectrum disorder (ASD), bipolar disorder (BPD), and Alzheimer’s disease (ALZ) can be downloaded from https://pgc.unc.edu/for-researchers/download-results/95–100. Summary statistics for C-reactive protein concentration (CRP), Body Mass Index (BMI) and gestational duration (GEST) can be downloaded, respectively, from https://ftp.ebi.ac.uk/pub/databases/gwas/summary_statistics/GCST90029001-GCST90030000/GCST90029070/, https://portals.broadinstitute.org/collaboration/giant/index.php/GIANT_consortium_data_files#2018_GIANT_and_UK_BioBank_Meta-analysis, and https://egg-consortium.org/gestational-duration-2019.html101–104. Further information for each of the summary statistics is provided in Supplementary Table 2. Paleocortical and archicortical distance maps were downloaded from ref. 56. The maps of the first genetic principal components of surface area, cortical thickness, mean diffusivity, mean curvature, and intracellular volume fraction were accessed from ref. 20. The first principal component of the T1w/T2w microstructural profile covariance matrix was downloaded from ref. 105. Brain maps of allometric scaling, evolutionary expansion, and externopyramidisation were downloaded from ref. 106. Source data are provided in this paper.

Reproduced under the paper's license (CC BY), from the paper cited above.

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.

Version 1, 27 September 2026: the first record

Recorded: type, language, journal, volume, issue, pages, dates, 10 authors, 2 keywords, 7 MeSH terms, 2 funders, 108 references.

Cite

This paper

Sebenius, I., Warrier, V., Bethlehem, R. A. I., Dear, R., Stauffer, E.-M., Gu, Y., Romero-Garcia, R., Seidlitz, J., Bullmore, E., & Morgan, S. (2026). The genetic architecture of cortical similarity networks. Nature communications, 17(1), 7801. https://doi.org/10.1038/s41467-026-73714-9

BibTeX

@article{sebenius2026genetic,
author = {Sebenius, Isaac and Warrier, Varun and Bethlehem, Richard A. I. and Dear, Richard and Stauffer, Eva-Maria and Gu, Yuanjun and Romero-Garcia, Rafael and Seidlitz, Jakob and Bullmore, Edward and Morgan, Sarah},
title = {{The genetic architecture of cortical similarity networks}},
journal = {Nature communications},
year = {2026},
month = jun,
volume = {17},
number = {1},
pages = {7801},
publisher = {Nature Portfolio},
issn = {2041-1723},
doi = {10.1038/s41467-026-73714-9},
url = {https://doi.org/10.1038/s41467-026-73714-9},
pmid = {42323287},
pmcid = {PMC13438111}
}

RIS

TY - JOUR
AU - Sebenius, Isaac
AU - Warrier, Varun
AU - Bethlehem, Richard A. I.
AU - Dear, Richard
AU - Stauffer, Eva-Maria
AU - Gu, Yuanjun
AU - Romero-Garcia, Rafael
AU - Seidlitz, Jakob
AU - Bullmore, Edward
AU - Morgan, Sarah
TI - The genetic architecture of cortical similarity networks
T2 - Nature communications
J2 - Nat Commun
PY - 2026
DA - 2026/06/20
VL - 17
IS - 1
SP - 7801
SN - 2041-1723
PB - Nature Portfolio
DO - 10.1038/s41467-026-73714-9
UR - https://doi.org/10.1038/s41467-026-73714-9
LA - en
ER -

CSL-JSON

{
"id": "10.1038/s41467-026-73714-9",
"type": "article-journal",
"title": "The genetic architecture of cortical similarity networks",
"container-title": "Nature communications",
"author": [
{
"family": "Sebenius",
"given": "Isaac"
},
{
"family": "Warrier",
"given": "Varun"
},
{
"family": "Bethlehem",
"given": "Richard A. I."
},
{
"family": "Dear",
"given": "Richard"
},
{
"family": "Stauffer",
"given": "Eva-Maria"
},
{
"family": "Gu",
"given": "Yuanjun"
},
{
"family": "Romero-Garcia",
"given": "Rafael"
},
{
"family": "Seidlitz",
"given": "Jakob"
},
{
"family": "Bullmore",
"given": "Edward"
},
{
"family": "Morgan",
"given": "Sarah"
}
],
"container-title-short": "Nat Commun",
"volume": "17",
"issue": "1",
"page": "7801",
"DOI": "10.1038/s41467-026-73714-9",
"PMID": "42323287",
"PMCID": "PMC13438111",
"ISSN": "2041-1723",
"publisher": "Nature Portfolio",
"URL": "https://doi.org/10.1038/s41467-026-73714-9",
"language": "en",
"issued": {
"date-parts": [
[
2026,
6,
20
]
]
}
}

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

Similar papers

The papers with a page that share the most with this one: the tools found in their code, their categories, datasets, cited references and authors, the rarest counting most.

[1] doi:10.1038/s41593-023-01376-7 [code]
Robust estimation of cortical similarity networks from brain MRI.
Journal: Nature neuroscience
In common: Nipype, AFNI, FreeSurfer, 5 other tools, structural MRI / diffusion, 5 references, 7 authors
[2] doi:10.1038/s41588-023-01475-y [code]
Genetic insights into human cortical organization and development through genome-wide analyses of 2,347 neuroimaging phenotypes.
Journal: Nature genetics
In common: AFNI, FreeSurfer, NiBabel, 3 other tools, structural MRI / diffusion, genetics / omics, 12 references, 5 authors
[3] doi:10.1038/s41467-025-63792-6 [code]
Reduced brain structural similarity is associated with maturation, neurobiological features, and clinical status in schizophrenia.
Journal: Nature communications
In common: Nipype, AFNI, FreeSurfer, 7 other tools, structural MRI / diffusion, 5 references, 5 authors
[4] doi:10.1038/s41380-025-02927-z [code]
Polygenic scores for autism are associated with reduced neurite density in adults and children from the general population.
Journal: Molecular psychiatry
In common: AFNI, FreeSurfer, patchwork, 7 other tools, structural MRI / diffusion, genetics / omics, 7 references, 3 authors
[5] doi:10.1038/s42003-026-10276-y [code]
The cellular correlates and adolescent reorganisation of cortical myelination networks in the common marmoset.
Journal: Communications biology
In common: Nipype, AFNI, FreeSurfer, 7 other tools, structural MRI / diffusion, 10 references, 2 authors
[6] doi:10.1002/alz.70973
Structural similarity networks reveal brain vulnerability in dementia.
Journal: Alzheimer's & dementia : the journal of the Alzheimer's Association
In common: structural MRI / diffusion, 10 references, 4 authors
[7] doi:10.1038/s41380-024-02724-0 [code]
Molecular and micro-architectural mapping of gray matter alterations in psychosis.
Journal: Molecular psychiatry
In common: NiBabel, ggplot2, tidyverse, 4 other tools, structural MRI / diffusion, 1 reference, 5 authors
[8] doi:10.1038/s41467-024-46023-2 [code]
Genetic architecture of the structural connectome.
Journal: Nature communications
In common: Nipype, AFNI, FreeSurfer, 5 other tools, structural MRI / diffusion, genetics / omics, 17 references
[9] doi:10.1038/s41562-025-02145-1 [code]
Genome-wide association meta-analysis of age at onset of walking in over 70,000 infants of European ancestry.
Journal: Nature human behaviour
In common: ggplot2, tidyverse, pandas, 3 other tools, genetics / omics, 17 references, author Varun Warrier
[10] doi:10.1038/s41593-024-01624-4 [code]
Cortical gene expression architecture links healthy neurodevelopment to the imaging, transcriptomics and genetics of autism and schizophrenia.
Journal: Nature neuroscience
In common: patchwork, NiBabel, ggplot2, 4 other tools, genetics / omics, 8 references, 3 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/doi/10.1038/s41467-026-73714-9.svg)](https://openscicode.org/badge/doi/10.1038/s41467-026-73714-9)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1038/s41467-026-73714-9.svg
   :target: https://openscicode.org/badge/doi/10.1038/s41467-026-73714-9
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41467-026-73714-9"><img src="https://openscicode.org/badge/doi/10.1038/s41467-026-73714-9.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.