Reports of unbarcoded reads being returned

[mattloose]

Hi,

We have had a user report occasional reads in a barcoded run not receiving a barcode label - i.e they do not get labelled as unclassified they simply have no barcode field.

Please see LooseLab/readfish#329 for more details.

We suspect this is a base caller issue rather than a readfish issue.

Cheers

Matt

[HalfPhoton]

Hi Matt,

Could you be more specific please - do you mean the output bam records have a missing BC tag entirely?

Kind regards.
Rich

[mattloose]

Hi Rich,

When users are calling fragments of reads during a run with pyguppyclient we expect the returned read object to have a barcode classification and for that to be either the barcode or unclassified. In the linked issue the user reports reads being returned (very occasionaly) which have a barcode classification of None - that means they didn't have a barcode entry at all in the read object?

We will keep digging and see if we can get more info for you!

Cheers

Matt

[malton-ont]

This issue has been inactive for some time - I presume there's been no further developments? As we've been unable to reproduce this I'm going to close it - if more information becomes available, please feel free to re-open or log a new issue.