...
These tables are analogous to how the genomic region and gene associations file links each input genomic region to the gene(s) it putatively regulates according to the association rule used. The difference is that only the associations that are relevant for the term of interest are included in the tables. For example, say the user provides an input set of five genomic regions which have the following associations:
| Panelnoformat |
|---|
Input.1 Gene.1 (-100) Input.2 Gene.1 (+500), Gene.2 (-3000) Input.3 NONE Input.4 Gene.4 (+100000) Input.5 Gene.5 (-500), Gene.6 (+600) |
Furthermore, assume an ontology has a term 'Term.A', and the genes Gene.1, Gene.5, Gene.6, Gene.7, Gene.8 are annotated with Term.A. Then the term details page for Term.A would have the following region->gene association table:
| Panelnoformat |
|---|
Input.1 Gene.1 (-100) Input.2 Gene.1 (+500) Input.5 Gene.5 (-500), Gene.6 (+600) |
In particular, the genomic regions Input.3 and Input.4 are not listed since they are not predicted to regulate genes involved in Term.A, and the association of Input.2 to Gene.2 is not listed since Gene.2 is not involved in Term.A.
The gene->region association table provides the identical information as the region->gene table, but grouped by gene rather than by region. So, for the example above, the gene->region table would be:
| Panelnoformat |
|---|
Gene.1 Input.1 (-100), Input.2 (+500) Gene.5 Input.5 (-500) Gene.6 Input.5 (+600) |
Region links
Each genomic region in both tables is a hyperlink. When clicked, the user is taken to the UCSC Genome Browser at the position of that region with custom tracks loaded with the user's data.
...
Each gene in both tables is also a hyperlink. When clicked, the user is taken to the UCSC Genome Browser at the position of the entire regulatory domain used to associate genomic regions to that gene given the association rule used. Additionally, the same custom tracks loaded with the user's data are provided.
...