Visualizing bigwigs on custom tracks

15 views
Skip to first unread message

Deepak Saini

unread,
May 22, 2023, 12:27:55 PM5/22/23
to gen...@soe.ucsc.edu
Hello, 

I have a problem visualizing my custom track bigwigs on the genome browser. I have uploaded my mm10 bigwig files to figshare and I am able to upload the custom track no problem. However, I noticed that if I move to look at different different genes I receive the following error: expected partial content 206: a url of some sort and can't get socket data (picture attached). Sometimes, I can visualize things but more often than not, it seems to crash with this error. 

Is this normal or is there a way around this? I''m currently trying to submit a paper to NAR which requires a browser session link to submit to reviewers. 

Any help on this matter would be greatly appreciated, thank you!

Deepak Saini
hgt_genome_29db3_95d7c0.png

Gerardo Perez

unread,
May 25, 2023, 8:39:05 PM5/25/23
to Deepak Saini, gen...@soe.ucsc.edu

Hello, Deepak.

Thank you for your interest in the Genome Browser and for sending your inquiry.

Could you share the bigWig URLs that result in this error to do more testing? If you don't want to share this information with our publicly-archived mailing list (gen...@soe.ucsc.edu), you can send it to our confidential support list at genom...@soe.ucsc.edu.

Does clicking the "refresh" button in the Genome Browser help?

Please include gen...@soe.ucsc.edu in any replies to ensure visibility by the team. All messages sent to that address are archived on a publicly-accessible Google Groups forum. If your question includes sensitive data, you may send it instead to genom...@soe.ucsc.edu.

Gerardo Perez
UCSC Genomics Institute


--

---
You received this message because you are subscribed to the Google Groups "UCSC Genome Browser Public Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome+un...@soe.ucsc.edu.
To view this discussion on the web visit https://groups.google.com/a/soe.ucsc.edu/d/msgid/genome/YQXPR01MB5240D088EA3AC56CD9075F3EBD7D9%40YQXPR01MB5240.CANPRD01.PROD.OUTLOOK.COM.

Mervin Fansler

unread,
Jun 20, 2024, 11:51:43 AM (12 days ago) Jun 20
to UCSC Genome Browser Public Support, Gerardo Perez, gen...@soe.ucsc.edu, Deepak Saini

Was there any resolution to this? I am seeing the same situation with figshare-hosted bigWig files. I've tried both private and public datasets to same effect.

For testing, here is a track for hg19:

track type=bigWig name="HeLa CPM (Lianoglou 2013)" bigDataUrl=https://figshare.com/ndownloader/files/47127994

It seems to work sporadically and I see no consistent pattern. The only thing that strikes as odd is `rangeEnd=-1` parameter that is also shown in OP.

Thanks for any advice.

Mervin Fansler
MSKCC
Reply all
Reply to author
Forward
0 new messages