We find 'big' file formats so useful for short-read work that we're thinking about more formal ways to organize mass storage to accommodate the file sets that we'll accumulate.
Today I tried adjusting a track line's bigDataUrl=http://path/my.bw, which pointed to a bigWig file, to point to a symbolic link to the same file, which I'd copied to another location on our filesystem. While the direct reference loaded my.bw to hg18, submitting the track line that pointed to the symbolic link returned only a blank white page. I'm not sure that we've considered all security implications of a link approach to 'big' files at this point, and I'm not the person who'd address such issues. Today's trial was a prototyping test. But we were wondering whether your bigDataUrl mechanism -should- support symbolic links. Thank you. G -- Gordon Robertson BC Cancer Agency Genome Sciences Centre Vancouver BC Canada www.bcgsc.ca Direct: 604-707-5800 x675416 Front desk: 604-707-5800 _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
