| Frequently Asked Questions: Custom Annotation Tracks
|
|
|
|
Displaying personal annotation data in the Genome Browser |
|
|
|
| |
Question:
"How do I display my own personal annotation data in the Genome Browser?"
Response:
To create an annotation track that will display on the Genome Browser, you
must first organize your data into one of the four formats supported by the
browser: GTF, GFF, BED, or PSL. The formatted data is then pasted in or uploaded into
the
Genome Browser. Once you've created your annotation track, you can share it with
others over the internet by putting your annotation file on your website, then
creating a custom URL that will allow others to directly start the browser with your
track displayed.
Read Displaying Your Own Annotations in the Genome Browser
for a step-by-step description of how to
format and display a custom annotation track, and how to create a custom URL.
| |
|
|
|
Adding a personal annotation track to the Genome Browser website |
|
|
|
| |
Question:
"I have an annotation track that I think might be of general interest to the
research community. Will UCSC consider including my track in their browser?"
Response:
We are always interested in receiving new annotation tracks for the Genome Browser, and
encourage our users to share their tracks with us and others in the research
community. Please send the URL for your track -- along with a description of the
methods, data, and format used -- to lowe @ soe.ucsc.edu.
If your track is of general interest to distribute as part of our browser, we'll work
with you to include it.
| |
|
|
|
Defining filter parameters for custom tracks |
|
|
|
| |
Question:
"Is it possible to define a filter parameter for a custom track to
highlight certain features?"
Response:
This feature is not currently implemented.
| |
|
|
|
Coloring a custom track using the useScore parameter |
|
|
|
| |
Question:
"When designing a custom track, is there a way to assign specific colors
to each segment, as is done in the mouse/rat synteny tracks? Is there a way
to assign
a value range for the useScore variable such that I can have four shades
and specify the value range for each?"
Response:
Currently useScore works only with tracks that are black or specific shades of
brown or blue. The score range is 0-1000. To display four shades, use the scores 0, 333, 666,
and 1000.
| |
|
|
|
Contructing a Genome Browser URL |
|
|
|
| |
Question:
"How can I construct a URL to retrieve data from the Genome Browser?
What do the various parameters in the Genome Browser URLs mean?"
Response:
One way to determine how to construct a correct URL is to open a Genome Browser link
in which you are interested and examine how the Genome Browser constructs the URL.
See the Custom
Annotation Track documentation for a discussion of the basic
components of a Genome Browser URL. Note that the c parameter that appears
in some URLs specifies the chromosome name or the chromosome name and position.
| |
|
|
|
Using the hgsid parameter in a URL |
|
|
|
| |
Question:
"Should I use the hgsid parameter in my URL?"
Response:
You should try to avoid using hgsid. It is a temporary identifier,
and will typically stop working after a day.
| |
|
|
|
Creating a details page for a custom annotation track |
|
|
|
| |
Question:
"While working on a custom track, we noticed that the feature details page
for custom track looks different from regular tracks on the site. Is the
details page for a custom track customizable?"
Response:
This feature is not currently implemented.
| |
|
|
|
Custom annotation track troubleshooting |
|
|
|
| |
Question:
"When I click the Submit button, I get the error message
"line # of custom input: BED chromStarts[i] must be in ascending order"."
Response:
We have tightened up the input checking on custom tracks. This error
is caused by a logical conflict in the Genome Browser software. It
accepts custom GFF tracks that have multiple "exons" at the
same position, but not BED tracks that have this feature. Because the
browser translates GFF tracks to BED format before storing the custom
track data, GFF tracks with multiple exons will cause an error when
the BED is read back in. To work around this problem, remove duplicate
lines in the GFF track.
| |
|
|
| |