<!channel> reminder we have our monthly meeting on...
# meta-omics
j
@channel reminder we have our monthly meeting on this Thursday 13th at 15:00 CET/Berlin time! A major topic can be the upcoming Hackathon! Who is attending? What do you plan to work on? Any common project ideas? Can we coordinate?
✅ 5
j
I promise I'll make it to one of these some day 😓 They unfortunately clash with one of my regularly scheduled meetings...
😢 1
m
I won't be able to join :(. Not much to report, other than my spurious updates on GTDB and antiSMASH ref dbs.
j
Would be very interested to hear how you're getting on with a ref db for GTDB - even briefly over text?
m
Creating one from scratch doesn't seem to be easy enough, these are the instructions to reduce the size of a prod one:
Copy code
Here is what I would try to do:
    Instead of recreating the GTDB-Tk database I would download it and strip the data you don't need.
    To reduce the Memory usage:
        I would run "classify_wf" only with Archaeal genomes, this is the smaller tree we have . ( in the release220/pplacer/gtdb_r220_ar53.refpkg/
        I would pick test genomes I know would be placed in a "small" phylum ( i.e. a phylum with few species like p__Undinarchaeota which has 6 species).
        I would strip the Archaeal Tree used in Tk from all species not in p__Undinarchaeota EXCEPT for  1 per phylum ( This helps to keep a decent tree topology for pplacer)
        I would parse the MSA used for pplacer to only keep species in your now trimmed Archaea tree.
        The size of the new tree would be going from 5,869 species to only 26 species ( 6 for p__Undinarchaeota and 20 for the remaining 20 phyla) so the memory used by pplacer should be less than 16Gb.
        You will need to recreate the pplacer package with this new tree + msa to regenerate the fitting_stats file ( you can find a basic guide under https://github.com/Ecogenomics/GTDBTk/wiki/Prepare-GTDB-Tk-data 4 - Create pplacer Package:
        You can now submit one of the test genomes ( that has to be part of p__Undinarchaeota) with classify_wf ( with the option –skip_ani_screen) to the new GTDB-Tk. GTDB_Tk will pick it as an archaea, will place it in the new trimmed archaeal tree with pplacer under "p__Undinarchaeota" which is the only complete phylum. It will then run an ANI against only  species in this phylum ( maximum 6) 
    To reduce storage used:
        Because the ANI will only happen against 6 genome you can create empty genome files ( or maybe remove) for all genomes in the release220/skani/database folder EXCEPT for the 6 reps of p__Undinarchaeota (GB_GCA_002502135.1, GB_GCA_002495465.1, GB_GCA_002687935.1, GB_GCA_014189685.1, GB_GCA_014189675.1, GB_GCA_027077325.1) 

Again this is purely theoretical but I think it will work
I haven't tried this yet
j
I'm not going to lie, this is reducing my confidence in the quality of this - how much can we trust it if it's not reproducible 😅
m
yup
trust me bro
j
yeah...
And I mean... admittedly I'm not actually that familiar with GTDBtk, but what do they mean 'strip the data you don't need' and strip it - if I'm running an analysis command (
classify_wf
) how is that recreating the database?
m
sort of "strip the data you don’t need" , I was planning on trying to "reverse engineer" those steps as they touch on which files/artefacts I would need to modify...
j
sounds... (not) fun
m
black-hole of time 😞
j
The GDTB database contains
.fna
files of the whole genome for every single genome in GTDB. So I think this seems reasonable - filter down to a sensible subset of phyla, trim the trees, and then you can bin most of those genome files which constitute most of the space on disk. But I don't like the idea of doing it for Archaea given that bacteria are much more common (e.g. the mag test data has bacteria)
party this 1
m
I would rather use bacteria too