Timeline for Customizing bigWig file
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2017 at 12:51 | comment | added | Devon Ryan | Thanks for the update, at least my understanding of bigWig headers was correct :) | |
| Jun 14, 2017 at 12:49 | vote | accept | bli | ||
| Jun 14, 2017 at 12:49 | comment | added | bli |
Using bigWigToWig, I can indeed obtain a wig file from the bigwig and add a custom track name that is displayed in IGV. Then, rebuilding a bigwig using wigToBigWig indeed looses the track name and I get the file name instead in IGV. This is for biwig files obtained directly with bamCoverage. I failed at reconverting wig to bigwig when the initial bigwig file was "manually" generated using pyBigWig. wigToBigWig complained as follows: line 1507430 of tests/tmp.wig: chromosome I has 15072434 bases, but item ends at 15072440. I guess I should post another question regarding this issue.
|
|
| Jun 13, 2017 at 17:41 | history | answered | Devon Ryan | CC BY-SA 3.0 |