Window parameter cannot deal with complicated fasta headers about methplotlib HOT 4 CLOSED

Hi Bastian,

I assume you then aligned your data to that one fastq you used as pseudo-reference?
I think not the entire fasta identifier will be used in the sam/bam/cram file - and it might look like 37b7bed0-436a-4676-a61a-023255f80bee without the rest of the information.

Wouter

from methplotlib.

Actually, Guppy had directly outputted a BAM file, so I had converted it to CRAM with the fastq as reference. Turns out that the identifiers between both are different, and the SAM/BAM didn't have a header, so there's a bunch of issues more, I guess :/, and all not related to methplotlib. Sorry for bothering you.
(although it would be handy to directly load the Guppy output)

from methplotlib.

I assume guppy created a BAM file with unaliged reads, i.e. ubam?

from methplotlib.

Sorry, I'm getting back to this so late. Yes, I had run Guppy without a reference at that time. In the meantime I've run it again with a human reference, I've not tested methplotlib yet, but I do not expect any issues with that :).

from methplotlib.