Managed to fix it by renaming the file and updating trackDb.txt with the new filename. I'd guess this was a glitch in the UCSC cache - is there a way to force the track cache to reload if this happens in future?
Chris On Thu, Mar 15, 2012 at 3:05 PM, Christopher Porter <[email protected]>wrote: > > As of today, one of my bigWig files is generating an error when I try to > display it through the genome browser - "End of file reading 4 bytes (got > 0)". This track is in a track hub, and part of a composite track - the > other track in the composite (in the same directory) is displaying fine. > This track was working yesterday, and has not changed since it was > generated in January (based on file modification time) - its MD5 checksum > is the same as the original copy on another server. Copying the original > file again has not fixed the error. > > Any ideas what might be causing this, and how I can fix it? > > Thanks, > > Chris > _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
