From: Ian H. <ih...@be...> - 2010-10-11 17:45:57
|
Hi David, We did receive your email - thanks. There is actually a lighthouse ticket for this issue already, though it is somewhat cryptic: http://jbrowse.lighthouseapp.com/projects/23792/tickets/19-handle-wiggle-regions-that-span-tile-boundaries If you get a chance, it'd be great if you could post your files for recreating the issue as a comment/footnote to this ticket (I would do this myself but I seem to have misplaced your original email unfortunately) Best wishes Ian On 10/11/10 4:41 AM, David Breimann wrote: > Hello again, > > I just wanted to verify you have received this email. > > Best, > Dave > > On Wed, Oct 6, 2010 at 10:59 PM, David Breimann<dav...@gm...>wrote: > >> Hi Mitch, >> >> I didn't send this to the mailing list to avoid sharing the large files >> with everyone, but feel free to cc your reply to the list. >> >> I've encountered a strange phenomena: some peaks appear in tracks created >> from WIG files with no apparent reason. The WIG doesn't have any value that >> supports a "peak" in those positions. >> >> Recreate the situation: >> * start with a clean JBrowse clone. >> * prepare-refseq with the attached fasta file (in the archive). >> * wig-to-json with the attached WIG file (in the archive). >> * Now zoom in to position 68000. Attached is a print-screen of what I see. >> Inspect the WIG and see all the values at this area are 2-3 and there's no >> peak. >> >> Keep up the good work! >> Dave >> > |