Questions about assembly with merged paired-end reads #765
-
Hello, could you tell me if there are constraints for files which can be passed via Can merged reads extend outwards, too, i.e. additional extension to the left of read 1 and to the right of read 2? Or does SPAdes expect that the merged reads start with and end with one of the reads of the merged read pair, respectively? What are the benefits of using Should the paired-end file |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
Hello! SPAdes expects that merged reads directly correspond to the original paired-end reads. In many cases is treats them as paired-end one (e.g. for the purposes of repeat resolution). In order to correctly estimate the original fragment length distribution the unmerged part should be provided as paired-end part of a sequencing library. Also, using merged reads could allow one to increase the maximum k-mer length in some cases (e.g. merged 2x100 bp reads could allow k-mer lengths up to 77 like 2x150 bp). Some additional information also could be found here: https://currentprotocols.onlinelibrary.wiley.com/doi/abs/10.1002/cpbi.102 |
Beta Was this translation helpful? Give feedback.
Hello!
SPAdes expects that merged reads directly correspond to the original paired-end reads. In many cases is treats them as paired-end one (e.g. for the purposes of repeat resolution). In order to correctly estimate the original fragment length distribution the unmerged part should be provided as paired-end part of a sequencing library.
Also, using merged reads could allow one to increase the maximum k-mer length in some cases (e.g. merged 2x100 bp reads could allow k-mer lengths up to 77 like 2x150 bp). Some additional information also could be found here: https://currentprotocols.onlinelibrary.wiley.com/doi/abs/10.1002/cpbi.102