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
Whereas here the focus is fast execution using a GPU, the tools and pipeline are interesting and not so different from what you already implemented.
[1] flye --nano-raw barcode06.fastq --threads 8 --iterations 2 --plasmids -g 3m --out-dir barcode06
This is the flye command used here. Interesting: --iterations parameter that already seems to do some kind of polishing. Maybe we also want to have this.
[2]
The other really interesting part in my eyes:
Not only using the short reads for polishing but instead, integrate them again into the assembly process while using the long-read-only assembly as a real backbone. For this, the author use SPAdes with the --trusted-contigs option and passes the long-read polished contigs as a trusted set of sequences. Then they use pilon for polishing the SPAdes result using the short reads. I think you also tried pilon at some point?
The question is: do we really need this in our case? Or: how difficult would it be for you to also implement a SPAdes rule that uses the Nanopore assembly with the error-corrected short reads as an input? So that we can compare?
The text was updated successfully, but these errors were encountered:
So, now we'll use the pipeline:
flye (w/ default polishing - 1 iteration) -> 4x Racon LR -> 1x medaka LR -> 4x Racon SR -> SPAdes w/ trusted contig option
I would try flye with 2 Iterations. Let's see if this significantlly
increases runtime.
Otherwise yes to your pipeline proposal. After the 4xraconSR step we
already have our nice assemblies and can then check if the additional
spades step does further improvement
sandraTriebel <notifications@github.com> schrieb am Mo., 16. Dez. 2019,
13:36:
So, now we'll use the pipeline:
flye (w/ default polishing - 1 iteration) -> 4x Racon LR -> 1x medaka LR
-> 4x Racon SR -> SPAdes w/ trusted contig option
or flye with 2 iterations?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#10>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADN2CZ5EPISUZRFZEJPSVS3QY5747ANCNFSM4J23MHAA>
.
@sandraTriebel see here a nice guide for Nanopore/ hybrid genome assembly:
https://achri.blogspot.com/2019/12/nanopore-bacterial-genome-assemblies.html?m=1
Whereas here the focus is fast execution using a GPU, the tools and pipeline are interesting and not so different from what you already implemented.
[1]
flye --nano-raw barcode06.fastq --threads 8 --iterations 2 --plasmids -g 3m --out-dir barcode06
This is the flye command used here. Interesting:
--iterations
parameter that already seems to do some kind of polishing. Maybe we also want to have this.[2]
The other really interesting part in my eyes:
Not only using the short reads for polishing but instead, integrate them again into the assembly process while using the long-read-only assembly as a real backbone. For this, the author use SPAdes with the
--trusted-contigs
option and passes the long-read polished contigs as a trusted set of sequences. Then they use pilon for polishing the SPAdes result using the short reads. I think you also tried pilon at some point?The question is: do we really need this in our case? Or: how difficult would it be for you to also implement a SPAdes rule that uses the Nanopore assembly with the error-corrected short reads as an input? So that we can compare?
The text was updated successfully, but these errors were encountered: