When to use Genome assembly and when to use short read alignment for consensus genration??
1
0
Entering edit mode
2.2 years ago

Let's say I have Illumina short-reads for a virus and its reference sequence is also available in the Database.

In this case what I should use to get a full-length genome from my Illumina short-reads?

  • Genome assembly
  • Or, short-read alignment for consensus generation.

Many times I get confused about when I should use which option.

Thanks in advance.

short-read assembly consensus alignment • 1.2k views
ADD COMMENT
1
Entering edit mode

You can do a reference based de-novo assembly. See this review for more info: https://bmcbioinformatics.biomedcentral.com/articles/10.1186/s12859-017-1911-6

ADD REPLY
1
Entering edit mode

I would say this boils down mostly to what you intend to do downstream, and how good the reference is.

If the reference is a complete genome with lots of validation, and you only care about variant identification, I'd say just mapping the reads is the way to go.

If the reference isn't that good, or you intend to do further analysis, there's no harm in assembling the genome.

Of course, you can do both pretty quickly.

ADD REPLY
0
Entering edit mode
ADD REPLY
0
Entering edit mode
2.2 years ago
shelkmike ★ 1.4k

If you want a full-length genome, you should do a de novo assembly. The reason is that if there are long indels or structural mutations between your genome and the reference, your reads may not align to those regions.

ADD COMMENT
0
Entering edit mode

long indels or structural mutations

Unless one is dealing with really large viruses those should not be applicable?

ADD REPLY
0
Entering edit mode

I'm not a specialist in viral genomics and don't know what is considered very large, but structural mutations difinitely happen in viruses sometimes, for example https://pubmed.ncbi.nlm.nih.gov/20018465/

ADD REPLY

Login before adding your answer.

Traffic: 2014 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