Hi Paula,
The correction has been made on the main servers.
As always, we welcome comments concerning data and overall performance 
of the Browser.
Especially as we are actively building up new & important datasets (such 
as hg19),
Jennifer

Jennifer Jackson wrote:
> Hello Paula,
>
> Thank you for alerting us about this issue. We are actively working to 
> fix the search. You can expect the correction to appear on the main 
> server very soon. If you are still having problems later this week, 
> please write back for an update.
>
> Meanwhile, one option is to export/save locally the complete dataset 
> from the hg19 Table browser or ftp from Downloads (a search from within 
> the Table browser against this table will not function using the 
> identifiers filter). The track is Chromosome Band and the table/file 
> name is "cytoBand". On the Downloads server this same data is located here:
>
> http://hgdownload.cse.ucsc.edu/goldenPath/hg19/database/
> cytoBand.sql      = schema
> cytoBand.txt.gz   = data
>
> Very sorry for the inconvenience,
> Jennifer Jackson
> UCSC Genome Bioinformatics Group
>
> Paula de Vree wrote:
>   
>> Hello,
>>
>>  
>>
>> I couldn't find the answer I was looking for in the archive, maybe it
>> was there.
>>
>> When I post a chromosome region in hg19 of the human genome, say 8q11.2,
>> the database says it cannot find this region.
>>
>> It does work in hg18.
>>
>> Could you tell me when or how I can retrieve chromosome regions in hg19?
>>
>> It was a possibility to convert from hg18 to hg19.
>>
>>  
>>
>> Regards,
>>
>> Paula
>>
>>  
>>
>>  
>>
>>  
>>
>> _______________________________________________
>> Genome maillist  -  [email protected]
>> https://lists.soe.ucsc.edu/mailman/listinfo/genome
>>   
>>     
> _______________________________________________
> Genome maillist  -  [email protected]
> https://lists.soe.ucsc.edu/mailman/listinfo/genome
>   
_______________________________________________
Genome maillist  -  [email protected]
https://lists.soe.ucsc.edu/mailman/listinfo/genome

Reply via email to