Why he/she disabled the base calling in Guppy?
0
0
Entering edit mode
2.6 years ago
greyman ▴ 190

Hi all, I saw a Guppy output summary (from Nanopore) in which the feature of base calling has been disabled. In that case I thought we would not know whether the reads have passed or failed the algorithm. Is there a reason why the author did this? Is there a limit that Guppy base calling can endure? I can see that the size of sequence is quite big... I am taking over this project because the person who runs it has left no contact detail.

Reads Generated 1.9M

Estimated Bases 9.84 Gb

guppy long-read nanopore base calling • 1.1k views
ADD COMMENT
2
Entering edit mode

I am not too sure I understand but I think you are saying that basecalling was disabled during the actual sequencing run, so you do/did not actually have basecalling information, i.e only raw fast5 files were/are present? and the estimated bases is the number given by minknow during sequencing (based on translocation time)? If this is the case, basecalling may have been disabled during sequencing because they wanted to basecall at a later date, perhaps on a different computer etc. I have done several runs like this as the laptop used for running the minION was not powerful enough to also basecall, and the raw fast5s were basecalled on a cluster.

ADD REPLY
0
Entering edit mode

Yes this is exactly what I mean, and yes it was run on a laptop, it makes total sense now! Thank you, is there a way to set this as the answer?

ADD REPLY
0
Entering edit mode

Since you haven't provided any relevant details, I would suggest to contact author.

ADD REPLY

Login before adding your answer.

Traffic: 1827 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6