runid in bam != fastq

[mattloose]

Hi,

In the version of dorado currently in MinKNOW (Guppy 7.1.4) the runID reported in the BAM fileis not the same as the runid reported in the fastq file.

In a fastq read header, the runID is not dash separated.
In a bam file the runID in the header is dash separated.

This makes comparing datasets tricky - please could just one runID be used?!

Thanks,

Matt

[mattloose]

As an additional point - I'd rather the runID in the fastq was maintained going forwards as a consistent identifier and not that the fastq was modified to match the BAM file protocol_runID.

[susie-ont]

Hi @mattloose, thanks for flagging this! We will fix it in an upcoming release.