-
Notifications
You must be signed in to change notification settings - Fork 2
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
tdb webserver trucating my protein #2
Comments
Hi, In the meantime you can download the current TDB files. TDB files represent sequence clusters so you could blast your proteins aginst the TDB sequences to work out which cluster/fold your proteins belong to. |
The fact that TDB files represent sequence clusters is another problem for us. It seems like the PDB database is clustered with very stringent sequence identity (30% or 40%) when the TDB library is created, compared to HHsearch library or I-TASSER library which are clustered by 70%. This means the TDB library does not well cover the full sequence space of PDB database (although it does cover the full structure space). Many times if I blast my protein against TDB, I cannot find anything. But if I blast against HHsearch's pdb70 I do find homolog. |
Sure. Genthreader isn't really a homologue detection tool. It is a fold recognition tool and the library is clustered for that purpose. |
Hi, with regards the TDB generator truncating your protein. Hopefully in the next month I'll have a fixed TDB generator ready |
I have tried to us the tdb webserver for one protein, which is 258 amino acids long, The result is at
http://bioinf.cs.ucl.ac.uk/bio_serf/getresultattached/158534327
which is 9 residues long.
Also, it is inconvenient to use a webserver to construct tdb file for hundreds of proteins on a weekly basis. I wondered whether there is any plan to release the programs used for TDB file generation, specifically that used for assigning relative solvent accessibility.
The text was updated successfully, but these errors were encountered: