NanoPlot: NanoPlot crashed with --barcoded flag

Hi @wdecoster ,

Thanks for making NanoPlot, I think it’s a great tool. I’m going to put a few figures generated w/ NanoPlot in to my MS thesis 😃 I’ll make sure to cite your publication.

Anyways…I ran NanoPlot without using the --barcoded flag first, ran perfectly, no issues. Today, I ran NanoPlot using the --barcoded flag and it crashed. I’m thinking it may have to do with the fact that I have a single Nanopore read that was identified as barcode 7, despite the fact that we only used the first 6 native barcodes during our sequencing run.

So I’ve got a lot of reads for BC’s 1 through 6, however only one for barcode 7 and I think that caused the crash.

I’ve attached the log file. NanoPlot_20180530_1824.log

I removed the line from the sequencing_summary.txt that corresponded with that falsely identified BC07 read, re-ran NanoPlot, and no errors this time.

2nd log file (with BC07 read removed). NanoPlot_20180530_1848.log

Figured I’d post this issue as this bug may occur for others running their de-multiplexed nanopore reads through NanoPlot.

Sorry I can’t offer a solution to fix the bug!

Curtis