FlyAtlas 2 – Gene
For a particular Drosophila gene, find the pattern of expression in different tissues.
Gene Symbol (e.g. vkg) — start typing, then select from the autosuggest menu
Gene Name (e.g. viking)
Annotation Symbol (e.g. CG16858)
Gene ID (e.g. FBgn0016075)
Transcript ID (e.g. FBtr0079036)
Gene Name (e.g. viking)
Annotation Symbol (e.g. CG16858)
Gene ID (e.g. FBgn0016075)
Transcript ID (e.g. FBtr0079036)
Gene:
| Adult Male | Adult Female | Male v. Female | Larval | |||||
|---|---|---|---|---|---|---|---|---|
| Tissue | FPKM | Enrichment | FPKM | Enrichment | M/F | p value | FPKM | Enrichment |
| Head | 40 ± 3.8 | 1.2 | 41 ± 2.4 | 0.7 | 0.97 | n.s. | ||
| Eye | 48 ± 3.5 | 1.4 | 43 ± 0.6 | 0.7 | 1.13 | n.s. | ||
| Brain / CNS | 40 ± 2.4 | 1.2 | 38 ± 4.8 | 0.6 | 1.07 | n.s. | 42 ± 4.1 | 0.9 |
| Thoracicoabdominal ganglion | 31 ± 2.7 | 0.9 | 34 ± 1.8 | 0.6 | 0.91 | n.s. | ||
| Crop | 35 ± 4.3 | 1.0 | 28 ± 7.6 | 0.5 | 1.28 | n.s. | ||
| Midgut | 41 ± 1.8 | 1.2 | 32 ± 1.5 | 0.5 | 1.26 | p < 0.01 | 120 ± 16 | 2.6 |
| Hindgut | 30 ± 1.9 | 0.9 | 33 ± 3.5 | 0.6 | 0.89 | n.s. | 35 ± 4.7 | 0.8 |
| Malpighian Tubules | 42 ± 2.3 | 1.2 | 46 ± 2.3 | 0.8 | 0.91 | n.s. | 68 ± 16 | 1.5 |
| Rectal pad | 26 ± 2.0 | 0.8 | 22 ± 2.3 | 0.4 | 1.17 | n.s. | ||
| Salivary gland | 36 ± 0.1 | 1.1 | 38 ± 6.7 | 0.6 | 0.96 | n.s. | 40 ± 2.5 | 0.9 |
| Fat body | 36 ± 3.4 | 1.0 | 39 ± 4.9 | 0.7 | 0.91 | n.s. | 55 ± 6.3 | 1.2 |
| Heart | 40 ± 7.6 | 1.2 | 50 ± 8.1 | 0.9 | 0.78 | n.s. | ||
| Trachea | 41 ± 5.9 | 0.9 | ||||||
| Ovary | 71 ± 3.5 | 1.2 | ||||||
| Virgin Spermatheca | 39 ± 1.3 | 0.7 | ||||||
| Mated Spermatheca | 40 ± 1.6 | 0.7 | ||||||
| Testis | 69 ± 7.6 | 2.0 | ||||||
| Accessory glands | 31 ± 1.6 | 0.9 | ||||||
| Carcass | 30 ± 1.4 | 0.9 | 36 ± 4.6 | 0.6 | 0.85 | n.s. | 30 ± 9.5 | 0.7 |
| Garland cells | 67 ± 6.5 | 1.5 | ||||||
| Whole body | 34 ± 3.6 | 59 ± 4.4 | 0.58 | p < 0.01 | 46 ± 4.8 | |||
Rotate to see Transcript Table
| Transcript | Male | Female | Larval | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | ID | Hd | Ey | Br | Tg | Cr | Mg | Hg | Tu | Rp | Sg | Fb | Ht | Ts | Ag | Cs | Hd | Ey | Br | Tg | Cr | Mg | Hg | Tu | Rp | Sg | Fb | Ht | Ov | Vs | Ms | Cs | Ns | Mg | Hg | Tu | Sg | Fb | Tr | Cs | Ga |
| RA | FBtr0087786 | ||||||||||||||||||||||||||||||||||||||||
| RB | FBtr0087787 | ||||||||||||||||||||||||||||||||||||||||
*Tissue Comparability: See Docs for info on the chemistry used to sequence different tissues.
WARNING: Transcript Ambiguity for this Gene!
Because FlyBase assigns a unique transcript name and identifier for each unique protein, the rare cases in which such proteins result from alternative translation of the same mRNA give rise to situations in which there are two or more different identifiers for the same physical transcript. RNAseq analysis can only deal with unique sequences, and in such cases arbitrarily assigns the data from a sequence to one of the different transcript identifiers. The result is that some named transcripts will be missing, or data for some transcripts will actually include that for others. In the case of gene FBgn0010488 the situation is:
Because FlyBase assigns a unique transcript name and identifier for each unique protein, the rare cases in which such proteins result from alternative translation of the same mRNA give rise to situations in which there are two or more different identifiers for the same physical transcript. RNAseq analysis can only deal with unique sequences, and in such cases arbitrarily assigns the data from a sequence to one of the different transcript identifiers. The result is that some named transcripts will be missing, or data for some transcripts will actually include that for others. In the case of gene FBgn0010488 the situation is:
No data for FBtr0334772 — included in FBtr0087786: Alternative Start codons in same reading frame
*** More extensive information about transcript ambiguity and its implications can be found in the Docs ***