Gene expression dynamics of human and mouse craniofacial development at the single-cell level.
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
82 files of its code read; 38 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.
cotneylab/craniofacial_snrna
Zenodo 18246448
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:Q1RZRJNMKCMXS-B: old/main_figures.R , lines 171 to 230 (paragraph 55)oscr:b:TQAQ7CCY253VR-J: clustering/human/ , lines 1777 to 1783 (paragraph 11)Craniofacial-scRNAseq-ma nuscript-Rmarkdown.Rmd oscr:b:3CG01GK2DN2ZK-T: clustering/mouse/ , lines 395 to 469 (paragraph 55)mouse_ect_mes_subcluster ing.R oscr:b:F86NV5D11301G-M: clustering/mouse/ , lines 344 to 393 (paragraphs 24, 26)mouse_ect_mes_subcluster ing.R oscr:b:9P150HMPT0KPK-Y: old/02_annotate_mes_ect_subt , lines 190 to 240 (paragraphs 24, 26)ypes.R oscr:b:PXJNFBYGDCXS6-C: main figures/spatial_expression.R , lines 416 to 463 (paragraphs 20, 13)oscr:b:1K9CYV7Y041ZF-F: magma_celltyping/ewce_analysis.R , lines 292 to 339 (paragraph 69)oscr:b:R6H3X4EXBKNB8-H: clustering/mouse/ , lines 50 to 124 (paragraph 66)mouse_ect_mes_subcluster ing.R oscr:b:76HNG12D79JQY-X: main figures/spatial_expression.R , lines 65 to 152 (paragraph 65)oscr:b:CWM4JQK1W5MX8-9: old/mouse_figures.R , lines 672 to 736 (paragraph 20)oscr:b:8SMR193ZX83MZ-9: clustering/mouse/ , lines 1 to 48 (paragraph 58)mouse_ect_mes_subcluster ing.R oscr:b:NQFBHPGW0TSNV-1: clustering/human/ , lines 337 to 355 (paragraph 61)Ectoderm_subclustering_a nd_annotation.Rmd oscr:b:MZ5JGFEVBYDZ7-7: clustering/human/ , lines 477 to 496 (paragraph 61)Mesenchyme_subclustering _and_annotation.Rmd oscr:b:H3DXVTYRDCTMK-9: main figures/Species_Comparison.Rmd , lines 914 to 942 (paragraph 58)oscr:b:8QT640V44NTX2-8: clustering/mouse/ , lines 766 to 797 (paragraph 28)Mouse_Spatial_Expression .Rmd oscr:b:5PYKVDWWBTJ5E-S: old/magma_celltyping_finngen , lines 542 to 590 (paragraphs 36, 35).R oscr:b:6APK99P4KYB1A-G: clustering/mouse/ , lines 681 to 733 (paragraphs 62, 15)Mouse_Spatial_Expression .Rmd oscr:b:ZAAHXXAY85E82-Q: magma_celltyping/Magma_Celltyping.R , lines 581 to 649 (paragraph 33)oscr:b:RPPTZP87FEY77-X: old/magma_celltyping_finngen , lines 592 to 641 (paragraph 33).R oscr:b:S2PCHE90YPTTC-J: main figures/Spatial_Expression.Rmd , lines 159 to 180 (paragraph 36)oscr:b:HF31Y0G647W46-0: clustering/human/ , lines 45 to 68 (paragraph 53)Craniofacial-scRNAseq-ma nuscript-Rmarkdown.Rmd oscr:b:BKP9EYZCZ1X8X-S: clustering/mouse/ , lines 473 to 494 (paragraph 60)mouse_ect_mes_subcluster ing.R oscr:b:GN6M2J042SHJR-Z: main figures/phenomix_analysis.R , lines 28 to 86 (paragraphs 70, 34)oscr:b:YMSJHKSFRX9GY-T: clustering/mouse/ , lines 21 to 78 (paragraph 57)Mouse_clustering_and_ann otation.Rmd oscr:b:3TQSBC2Z4MXFC-2: clustering/mouse/ , lines 442 to 496 (paragraph 13)Mouse_SOX2-_SOX10+_subcl ustering_and_annotation. Rmd oscr:b:PEZ99V851W1YJ-E: old/02_subclustering_and_ann , lines 84 to 125 (paragraph 29)otation.R oscr:b:EZMDQXP0X3GSH-0: magma_celltyping/Magma_Celltyping.R , lines 1747 to 1807 (paragraph 67)oscr:b:GHZCN9JA2DZ4W-2: clustering/human/ , lines 1057 to 1085 (paragraph 10)Craniofacial-scRNAseq-ma nuscript-Rmarkdown.Rmd oscr:b:Q1YBMNK8XNHVD-I: main figures/Spatial_Expression.Rmd , lines 99 to 122 (paragraphs 34, 68)oscr:b:XESYF8Y9VE7W4-R: magma_celltyping/FinnGen/ , lines 1 to 60 (paragraph 35)retrieve_studies.sh oscr:b:CXXZFSPC0CTVP-U: old/mouse_spatial_plots.R , lines 95 to 164 (paragraph 16)
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-70232-6)
<!-- oscr-badge:end -->reStructuredText
.. oscr-badge:start
.. image:: https://openscicode.org/badge/doi/10.1038/s41467-026-70232-6.svg
:target: https://openscicode.org/badge/doi/10.1038/s41467-026-70232-6
:alt: OSCR
.. oscr-badge:endHTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1038/s41467-026-70232-6"><img src="https://openscicode.org/badge/doi/10.1038/s41467-026-70232-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).
