A multimodal cell census and atlas of the mammalian primary 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
143 files of its code read; 10 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.
Zenodo 4726182
data.nemoarchive.org/publication_release/lein_2020_m1_study_analysis
AllenInstitute/BICCN_M1_Evo
ZhuangLab/MERlin
BICCN/CellCensusMotorCortex
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:0AC96TE4VH8TZ-6: IntegratedTree/integratedTree.code.R , lines 97 to 174 (paragraph 94)oscr:b:VR2Q38BP0H1VQ-8: cross_species_integration/ , lines 45 to 98 (paragraphs 22, 23)ED_Figure_2_c.R oscr:b:N1WAEEY4M2AY3-D: cross_species_integration/ , lines 1 to 62 (paragraph 32)Figure_6_b_c.R oscr:b:ECGCFEAMY5AM3-1: SNARE-Seq2 Scripts/Human SNARE-Seq2 Data Processing.R , lines 750 to 792 (paragraph 101)oscr:b:T4CDGN37MZ144-1: cross_species_integration/ , lines 104 to 192 (paragraph 93)integrate_human_marmoset _mouse.R oscr:b:AZ47GRGTFHM69-G: cross_species_integration/ , lines 168 to 222 (paragraph 93)integrate_human_macaque_ marmoset_mouse.R oscr:b:TQY0BKGMQMF4A-9: IntegratedTree/pairwisePrunning.R , lines 90 to 176 (paragraphs 90, 86)oscr:b:6C2KW029TA76T-N: SNARE-Seq2 Scripts/Human Marmoset SNARE-Seq2 Subclass TFBS Conservation.R , lines 1 to 46 (paragraph 21)
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.1038/s41586-021-03950-0)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1038/s41586-021-03950-0.svg
:target: https://openscicode.org/badge/doi/10.1038/s41586-021-03950-0
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41586-021-03950-0"><img src="https://openscicode.org/badge/doi/10.1038/s41586-021-03950-0.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".
- AllenInstitute/
BICCN_M1_Evo on GitHub - ZhuangLab/
MERlin on GitHub - BICCN/
CellCensusMotorCortex on GitHub
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).
