I create a lot of bigWig files from the output of MACS2 to view on the UCSC genome browser. But occasionally I get a bigWig file that has problems.
The problem manifests as when certain areas of the genome are zoomed in the server/browser connection times out. Whole chromosomes can be viewed, but below a certain resolution the time out error occurs.
I have tried recreating the bigWig files, but the "same" output is generated (as determined by md5sum). I do not know where the problem lies.
Has anyone found/developed a way to "debug" a faulty bigWig file?