You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can think of a couple of ways to do this - but perhaps the providing a --skip flag that takes a file containing read_ids would be best? Then you could either use a new output file with > or append to the prior one with >>.
I am using bonito version 0.5.1 and I'm also interested in restarting a run, and supplying read-ids that bonito can skip. I looked into the --skip argument, but I cannot use it in the way that is described above, because I cannot supply a file with read_ids to the --skip argument.
Is this a bug, or am I misunderstanding the use of the --skip argument?
Hi @cdebuck - sorry, it wasn't implemented exactly as described here. You can supply a file of read ids with the --read-id option and add --skip to change the behaviour to skip the reads instead of basecall only those reads.
Hi,
I am wondering -- if bonito terminates for whatsoever reason during a run, is there a way to restart the run and pick up from where it left off?
Thanks!
The text was updated successfully, but these errors were encountered: