Skip to content

Create an account and get up to 25% off.

Order

Pathway Mouse Mus musculus

Read this first

Every mouse pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

Intraflagellar transport

R-MMU-5620924 in Reactome release 97: under Assembly of the 9+0 primary cilium, with 57 genes placed in it by the mapping files and 0 child pathways in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-HSA-5620924 (human), R-RNO-5620924 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

Every mouse pathway in Reactome is inferred from the curated human one: We use the set of manually curated human reactions to electronically infer reactions in fourteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. [R11] Reactome's own sentence about what that produces is printed beside the record: The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments. [R11]

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R11] Reactome, reactome.org. Computationally inferred events. https://reactome.org/documentation/inferred-events, read 2026-09-09.
  5. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  6. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this mouse pathway

The mapping files place 57 genes in this mouse pathway; showing 1 to 57, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneDync2h1Authority110350Mapping file id110350 NCBI fileEvidenceIEA
GeneDync2i1Authority217935Mapping file id217935 NCBI fileEvidenceIEA
GeneDync2i2Authority71820Mapping file id71820 NCBI fileEvidenceIEA
GeneDync2li1Authority213575Mapping file id213575 NCBI fileEvidenceIEA
GeneDynll1Authority56455Mapping file id56455 NCBI fileEvidenceIEA
GeneDynll2Authority68097Mapping file id68097 NCBI fileEvidenceIEA
GeneDynlrb1Authority67068Mapping file id67068 NCBI fileEvidenceIEA
GeneDynlrb2Authority75465Mapping file id75465 NCBI fileEvidenceIEA
GeneDynlt2a1Authority21647Mapping file id21647 NCBI fileEvidenceIEA
GeneDynlt2a2Authority100041639Mapping file id100041639 NCBI fileEvidenceIEA
GeneDynlt2a3Authority100041586Mapping file id100041586 NCBI fileEvidenceIEA
GeneDynlt2bAuthority66061Mapping file id66061 NCBI fileEvidenceIEA
GeneDynlt5Authority67344Mapping file id67344 NCBI fileEvidenceIEA
GeneIft122Authority81896Mapping file id81896 NCBI fileEvidenceIEA
GeneIft140Authority106633Mapping file id106633 NCBI fileEvidenceIEA
GeneIft172Authority67661Mapping file id67661 NCBI fileEvidenceIEA
GeneIft20Authority55978Mapping file id55978 NCBI fileEvidenceIEA
GeneIft22Authority67286Mapping file id67286 NCBI fileEvidenceIEA
GeneIft25Authority72938Mapping file id72938 NCBI fileEvidenceIEA
GeneIft27Authority67042Mapping file id67042 NCBI fileEvidenceIEA
GeneIft38Authority76779Mapping file id76779 NCBI fileEvidenceIEA
GeneIft43Authority76411Mapping file id76411 NCBI fileEvidenceIEA
GeneIft46Authority76568Mapping file id76568 NCBI fileEvidenceIEA
GeneIft52Authority245866Mapping file id245866 NCBI fileEvidenceIEA
GeneIft54Authority74019Mapping file id74019 NCBI fileEvidenceIEA
GeneIft56Authority264134Mapping file id264134 NCBI fileEvidenceIEA
GeneIft57Authority73916Mapping file id73916 NCBI fileEvidenceIEA
GeneIft70a1Authority78802Mapping file id78802 NCBI fileEvidenceIEA
GeneIft70a2Authority620631Mapping file id620631 NCBI fileEvidenceIEA
GeneIft70bAuthority72421Mapping file id72421 NCBI fileEvidenceIEA
GeneIft74Authority67694Mapping file id67694 NCBI fileEvidenceIEA
GeneIft80Authority68259Mapping file id68259 NCBI fileEvidenceIEA
GeneIft81Authority12589Mapping file id12589 NCBI fileEvidenceIEA
GeneIft88Authority21821Mapping file id21821 NCBI fileEvidenceIEA
GeneKif17Authority16559Mapping file id16559 NCBI fileEvidenceIEA
GeneKif3aAuthority16568Mapping file id16568 NCBI fileEvidenceIEA
GeneKif3bAuthority16569Mapping file id16569 NCBI fileEvidenceIEA
GeneKif3cAuthority16570Mapping file id16570 NCBI fileEvidenceIEA
GeneKifap3Authority16579Mapping file id16579 NCBI fileEvidenceIEA
GeneTnpo1Authority238799Mapping file id238799 NCBI fileEvidenceIEA
GeneTrip11Authority109181Mapping file id109181 NCBI fileEvidenceIEA
GeneTtc21bAuthority73668Mapping file id73668 NCBI fileEvidenceIEA
GeneTuba1aAuthority22142Mapping file id22142 NCBI fileEvidenceIEA
GeneTuba1bAuthority22143Mapping file id22143 NCBI fileEvidenceIEA
GeneTuba1cAuthority22146Mapping file id22146 NCBI fileEvidenceIEA
GeneTuba3aAuthority22144Mapping file id22144 NCBI fileEvidenceIEA
GeneTuba3bAuthority22147Mapping file id22147 NCBI fileEvidenceIEA
GeneTuba4aAuthority22145Mapping file id22145 NCBI fileEvidenceIEA
GeneTubb1Authority545486Mapping file id545486 NCBI fileEvidenceIEA
GeneTubb2aAuthority22151Mapping file id22151 NCBI fileEvidenceIEA
GeneTubb2bAuthority73710Mapping file id73710 NCBI fileEvidenceIEA
GeneTubb3Authority22152Mapping file id22152 NCBI fileEvidenceIEA
GeneTubb4aAuthority22153Mapping file id22153 NCBI fileEvidenceIEA
GeneTubb4bAuthority227613Mapping file id227613 NCBI fileEvidenceIEA
GeneTubb6Authority67951Mapping file id67951 NCBI fileEvidenceIEA
GeneWdr19Authority213081Mapping file id213081 NCBI fileEvidenceIEA
GeneWdr35Authority74682Mapping file id74682 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: the two files disagree on none of the 87,729 mouse pairs both place.

  • Reactome mapping files, the mouse rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Children

None: no pathway of this release's list names this one as a parent.

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the mouse pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.