OSCR

Blocking RAN translation without altering repeat RNAs rescues <i>C9ORF72</i>-related ALS and FTD phenotypes.

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

23 files of its code read. The Code ↔ Paper reader is built for the 6,000 most recent papers only: this paper's code is read at its source.

wainger-lab/STING

License: none: the authors keep all their rights
State: the link is dead

waingerlab/Jiang_etal

License: none: the authors keep all their rights
State: the link answers
Copies: kept by the registry: this license allows it
Tools found in the code: Image Processing Toolbox

Overview

Authors: Xin Jiang, Laure Schaeffer, Divya Patni, Tommaso Russo, Chao-Zong Lee, Corey Aguilar, Christine Marques, Karen Jansen-West, Marian Hruska-Plochan, Ananya Ray-Soni, Su Min Lim, Aaron Held, Mei Yue, Paula Castellanos Otero, Sandeep Aryal, Hortense D A M Beaussant, Himanish Basu, Hiro Takakuwa, Lillian M Daughrity, Nandini Ramesh
and 26 other authorsPaulo Da Costa, Ana Rita A A Quadros, Matthew Nolan, Charles Jourdan F Reyes, Hayden Wheeler, Laura C Moran, Grant Griesman, Benjamin Wymann, Bianca A Trombetta, Emma Sofia Lopez-De-Silanes, Michael Canori, Gopinath Krishnan, Yasmim Vieira Souza Da Silva, Gilbert Eriani, Mark W Albers, Steven E Arnold, Yuyu Song, Ankur Jain, Isaac M Chiu, Yong-Jie Zhang, Fen-Biao Gao, Brian J Wainger, Magdalini Polymenidou, Leonard Petrucelli, Franck Martin, Clotilde Lagier-Tourenne
Published: 5 February 2026
Type: Research article
Status: code verified (how the code is found and verified)
License: CC BY

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.

Add the badge to the code's README

OSCR: the badge of this paper

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 -->
[![OSCR](https://openscicode.org/badge/doi/10.1126/science.adv2600.svg)](https://openscicode.org/badge/doi/10.1126/science.adv2600)
<!-- oscr-badge:end -->
reStructuredText
.. oscr-badge:start

.. image:: https://openscicode.org/badge/doi/10.1126/science.adv2600.svg
   :target: https://openscicode.org/badge/doi/10.1126/science.adv2600
   :alt: OSCR

.. oscr-badge:end
HTML
<!-- oscr-badge:start -->
<a href="https://openscicode.org/badge/doi/10.1126/science.adv2600"><img src="https://openscicode.org/badge/doi/10.1126/science.adv2600.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).