Multi-modal dissection of cell-type specific TDP-43 pathology in the motor cortex.
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
216 files of its code read; 20 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.
timoast/sinto
DanzerLab/Ruf_et_al_2026
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:TDYRDWCMZ545K-P: Source/Z_Visualization/ , lines 151 to 204 (paragraph 9)Z103_Fig3_MS.R oscr:b:PDNVH9CYD4EAH-1: Source/Z_Visualization/ , lines 89 to 157 (paragraph 9)Z206_SupplFig_CellType_M oduleScore_NegControl.R oscr:b:WDSZ3C6DZQ1WZ-T: Source/Z_Visualization/ , lines 262 to 324 (paragraphs 46, 4)Z204_SupplFig_Hierarchic al_CellType_Clustering.R oscr:b:ZARTREQ8F6GSS-R: Source/Z_Visualization/ , lines 358 to 439 (paragraph 5)Z101_Fig1_MS.R oscr:b:K9PQPNXXDPZ69-G: Source/D_Functional_Analysis/ , lines 57 to 133 (paragraph 55)D2_Chromatin_Regions_Ann otation_ChipSeekR.R oscr:b:DRD0CXTY13Y92-N: Source/D_Functional_Analysis/ , lines 66 to 143 (paragraph 51)D22_Add_ALS_ALSFTD_Signa tures_Module_Scores.R oscr:b:Z5ZDG2B7BFVGJ-L: Source/F_FANS/ , lines 1 to 54 (paragraph 42)A6_ScDblFinder_Detect_Do ublets.R oscr:b:KKX092XDWF1B8-0: Source/Z_Visualization/ , lines 135 to 192 (paragraphs 7, 8)Z203_SupplFig_Hierarchic al_CellType_Tree.R oscr:b:GN8CWNANYJVM2-5: Source/A_Data_Wrangling/ , lines 49 to 106 (paragraph 14)A3_Hierarchical_Cell_Typ e_Annotation.R oscr:b:11E5MK819TKP8-C: Source/A_Data_Wrangling/ , lines 183 to 233 (paragraph 7)A3_Hierarchical_Cell_Typ e_Annotation.R oscr:b:XNHXM82KAN4WF-6: Source/F_FANS/ , lines 1 to 73 (paragraph 46)A15_Multiome_Label_Trans fer.R oscr:b:9TXRN8SSVEJZH-P: Source/F_FANS/ , lines 1 to 54 (paragraph 42)A3_Souporcell_Doublet_De tection.sh oscr:b:Y078YYFYWDADP-W: Source/N_APA_Analysis/ , lines 1 to 64 (paragraph 52)N1_APA_FANS_DaPars.sh oscr:b:AWTCZ0Z271MFS-B: Source/N_APA_Analysis/ , lines 1 to 56 (paragraph 52)N4_APA_M0_Case_WNN_L25_D aPars.sh oscr:b:D96WHXC3CDY9A-H: Source/A_Data_Wrangling/ , lines 179 to 238 (paragraph 44)A1_Prepare_SeuratObject. R oscr:b:HKVK201NTY4B3-R: Source/I_Spatial_Analysis/ , lines 151 to 199 (paragraph 51)I3_LIBD_Spatial_GeneModu leScores_CellTypes.R oscr:b:HRDE8TYNH6TY9-I: Source/Z_Visualization/ , lines 316 to 394 (paragraph 10)Z103_Fig3_MS.R oscr:b:SY7375RQ15Q2M-O: Source/Z_Visualization/ , lines 2669 to 2743 (paragraph 8)Z209_SupplFig_C9orf72.R
Overview
Data
Datasets cited
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.1038/s41467-026-69944-6)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1038/s41467-026-69944-6.svg
:target: https://openscicode.org/badge/doi/10.1038/s41467-026-69944-6
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41467-026-69944-6"><img src="https://openscicode.org/badge/doi/10.1038/s41467-026-69944-6.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).
