Just share some disadvantage of bigwig visualization with bigwig. Before bigwig, I usually use bedgraph or wig to show my data with UCSC browser. It is complicated, you need to upload your wig/bedgraph one by one to UCSC. What's worse, the data would be disappeared without visit during 4 month. Therefore, I try to use bigwig to reveal my data. However, new problem is coming:
Generally, It works, however, the performance on large number of bigwig files is exactly very bad.
1, ftp server error on cmd= response=,can't get the data socket: For some tracks, this error were reported since I have two many tracks, in my case, 200 tracks were existed. It seems the FTP server can not support so many connections.
2, Error in TCP non-blocking connection() 111-connection refused, can't get the data socket...Some tracks can not be shown for any reason.
3, Not stable, suppose you have 20 tracks. sometime you can get 10 tracks, sometimes you can get 15 tracks, sometime you can get only 1 tracks to be shown.
What I can say is the usage experience is not very good for bigwig in UCSC browser.