FFCP PHASE1:Mm9::chr8:107058530..107058546,-: Difference between revisions
From FANTOM5_SSTAR
(Created page with "{{FFCP
|id=chr8:107058530..107058546,-
|short_description=p2@Nae1
|description=CAGE_peak_2_at_Nae1_5end
|association_with_transcript=0bp_to_ENSMUST00000034349,ENSMUST00000...") |
m (moved FFCP PHASE1 mm9::chr8:107058530..107058546,- to FFCP PHASE1:Mm9::chr8:107058530..107058546,-: NSchange) |
(No difference)
| |
Revision as of 19:23, 6 March 2012
| Short description: | p2@Nae1 |
|---|---|
| Species: | Mouse (Mus musculus) |
| DPI dataset: | NA |
| TSS-like-by-RIKEN-classifier(Yes/No): | NA |
| DHS support(Yes/No): | NA |
| Description: | CAGE_peak_2_at_Nae1_5end |
| Coexpression cluster: | NA |
| Association with transcript: | 0bp_to_ENSMUST00000034349, ENSMUST00000162466, NM_144931, uc009nas.2_5end |
| EntrezGene: | Nae1 |
| Link to Zenbu: | ZENBU |
View on UCSC genome browser
Mouse over to see Genome browser image, Click image to go to Genome browser
CAGE Expression
| Sample | p2@Nae1 |
|---|
- Click each plot point to find sample in table
Ontology-based sample term enrichment analysis<b>Summary:</b>This analysis has been performed by utilizing wilcoxon rank sum test.When the number of associated cells/tissues are > n , randomly sampled n cells/tissues are used for P value calculation with rank sum test. this process are repeated several times, and the P values are averaged on the log space <br><b>Analyst:</b> Hideya Kawaji<br><br>link to source dataset<br>data
Property "Dpi dataset" (as page type) with input value "{{{DPIdataset}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "TSS like by RIKEN classifier" (as page type) with input value "{{{TSSclassifier}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "DHS support" (as page type) with input value "{{{DHSsupport}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
