Binned input for Megan
1
0
Entering edit mode
5.5 years ago
ARich ▴ 130

Dear Biostar users,

I have very basic question regarding megan input. I would like classify my binned reads using megan. The question is can i use these binned reads for blastx against nt database or blasting contigs against NT database in only appropriate?

Thank you in advance!

assembly • 1.1k views
ADD COMMENT
1
Entering edit mode

I think we need more info. I assume that you want to know which species are present in your sample. Maybe using metaphlan can help http://huttenhower.sph.harvard.edu/metaphlan2. Also think about the classifying part, just blasting all the reads and classifying them is a bit useless due to things like household genes and other parts of the DNA that are not distinctive for a certain species. MEGAN will say that the read belongs to a certain species but your top 50 blast hit are all a 100% match all with different species. Maybe after binning you can somehow vind marker sequences like 16S, 18S, CO1, ITS depending on your sample and blast those and then use megan if necessary. Megan is only useful if you don't have a significant good blast hit to check the lowest common ancestor.

ADD REPLY
0
Entering edit mode

Can you clarify what "binned reads" means here?

ADD REPLY
0
Entering edit mode

Means reads which are assembled with Spades are then binned based on compositional and taxonomic similarity using CONCOCT,Maxbin etc

ADD REPLY
0
Entering edit mode
5.5 years ago

I think your

Start - normal fastq reads

Assembly with SPADES - Contigs

Neither of these are binned reads. Contigs are essentially contiguously assembled groups of reads.

Maybe you want to restart and try using eg Diamond or similar to compare the initial read set to a database ? Then you can read the results into a tool like MEGAN for analysis.

ADD COMMENT

Login before adding your answer.

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