Conservation, Evolutionary: Difference between revisions
From Proteopedia
Jump to navigationJump to search
Eric Martz (talk | contribs) →The ConSurf-DB Mechanism: describing ConSurf-DB Mechanism |
Eric Martz (talk | contribs) →The ConSurf-DB Mechanism: describing ConSurf-DB Mechanism |
||
| Line 66: | Line 66: | ||
#Redundant sequences are removed using CD-HIT<ref>PMID: 16731699</ref>. | #Redundant sequences are removed using CD-HIT<ref>PMID: 16731699</ref>. | ||
#A maximum of 300 sequences meeting the above criteria is used (the 300 with the lowest expectation values, that is, most closely related to the query sequence). | #A maximum of 300 sequences meeting the above criteria is used (the 300 with the lowest expectation values, that is, most closely related to the query sequence). | ||
#If the above process yields fewer than 50 sequences, the entire process is repeated using the Clean_UniProt database, which is about ten times larger than UniProtKB/Swiss-Prot. Clean_UniProt is a version of the UniProt database that attempts to exclude mutant or dubious sequences. | |||
==The ConSurf Server== | ==The ConSurf Server== | ||
