Hello,

These results are the expected results. The location on ChrX is the 
default starting position for the Mar. 2006 (hg18) assembly (not a 
random location).

There are two display characteristics to alert a user that a "track data 
point" search query was not found.
1) The text at the top of the result page stating that the search string 
was not found in any tracks.
2) The data point's label is not highlighted with a black box in the 
genome graphic (applies to queries against track contents: genes and 
other features).
Note: For a successful search, the data point's label would be 
highlighted to bring the user's attention quickly to the region of interest.

For failed "position" searches, there is only one display characteristic.
1) The text at the top of the result page stating that the search string 
was not found is displayed.
Note: Failed position searches may be due to an incorrectly formatted 
query or accidentally using the wrong assembly/species browser.

Each assembly's gateway page has example queries and a link to the list 
of the assembly base sequence names/lengths (chromosomes, scaffolds, etc.).

The text stating that a query failed is not as obvious as it could be. 
Internally, the group is discussing alternate display options.

Thank you for your comments,
Jennifer Jackson
UCSC Genome Bioinformatics group

Jeffrey Barrett wrote:
> Hi,
>
> Sometimes, when submitting a search to 
> http://genome.ucsc.edu/cgi-bin/hgTracks, it can't find the landmark I'm 
> looking for. The results page prints an error message at the top, but 
> it's actually easy to miss (since one's eyes tend to go to the tracks, 
> rather than to the bland text at the top of the page).
>
> The real problem, however, is that the track view redirects to an 
> apparently random stretch of the genome! This can be incredibly 
> confusing if you don't notice the error message.
>
> Searching for "ZNF818", for instance, yields a "Sorry couldn't 
> locate..." error, but then shows me chrX:151,073,054-151,383,976!
>
> Is this intentional? Does anyone know why this happens?
>
> Thanks,
> Jeff
>
>
>   
_______________________________________________
Genome maillist  -  [email protected]
https://lists.soe.ucsc.edu/mailman/listinfo/genome

Reply via email to