Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to get a tree containing all my MAGs #567

Closed
Sh1von opened this issue Jan 12, 2024 · 1 comment
Closed

How to get a tree containing all my MAGs #567

Sh1von opened this issue Jan 12, 2024 · 1 comment

Comments

@Sh1von
Copy link

Sh1von commented Jan 12, 2024

Hello, I noticed that "GTDB-TK now uses a divide-and-conquer approach where the bacterial reference tree is split into multiple order-level subtrees." I would like to obtain a tree that includes all of my MAGs, however, I don't have 320G of memory to run --full-tree, although I did get multiple tree files by using gtdbtk classfy-wf with --mash_db. Strangely, some MAGs (corresponding to their fastani_id) do not exist in any of the trees.
I inputted 50 MAGs FASTA files, but strangely, the gtdbtk.bac120.user_msa.fasta.gz file only includes two MAGs. Additionally, when I check the log, it mentions "48 genome(s) have been classified using the ANI pre-screening step." and coincidentally, these are the two genomes needed for "Identifying markers in 2 genome."

I have also uploaded the log file. In summary, I hope to obtain a tree that includes all of my MAGs without running the --full-tree parameter.
gtdbtk.log

@pchaumeil
Copy link
Collaborator

Hello,
In order to have all the genomes placed in the reference tree ( split or not split ) you need to use the flag --skip_ani_screen . it will skip the first screening.
Unfortunately, by default you will get multiple sub trees for the placement of your genomes. There is no way around the 320G requirement for the --full_tree option.

Cheers,
Pierre

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants