Closed samuelmontgomery closed 3 months ago
Hi @samuelmontgomery - thank you for reporting the error! Indeed looks like we have a bug in freeing a pointer on Windows which is causing the segafult. We will push a fix for this ASAP. Are you able to run this on a Linux platform (or WSL) by any chance?
Hi @samuelmontgomery - this was fixed with dorado v0.7.1. Please use the latest binary and let us know if you run into any issues!
Hi,
I am trying out dorado correct on a 100x coverage set of reads of a bacteria for de novo assembly (~1GB of data), and it just doesn't seem to run at all? This is using the windows binary with 24 CPUs, 64Gb system RAM, RTX4090 GPU
Running the following command gets some output initially, but after looking for the index it just exits the process back out to shell
C:\dorado_0.7.0\bin\dorado.exe correct -t 12 --verbose .\PAO1_subset.fastq > .\PAO1_corrected.fasta
Is there a specific way I need to prepare my fastq file? This data is simply SUP basecalled and subset into a smaller set, but looking at the herro github, do they need to be mapped then extracted back as fastq files from the BAM?
As a side note - may want to specify in the readme that you cannot use a fastq.gz compressed using gzip and need to use bgzip instead - as i think gzip is still very common