iGEM 2020 — Team UESTC-Software

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UESTC-Software/Notebook

<!DOCTYPE html>

Notebook

[![](https://static.igem.org/mediawiki/2020/a/a5/T--UESTC-Software--nav-logo.png)](https://2020.igem.org/Team%3AUESTC-Software)

[Home](https://2020.igem.org/Team%3AUESTC-Software)

Project

[Description](https://2020.igem.org/Team%3AUESTC-Software/Description)
[Engineering](https://2020.igem.org/Team%3AUESTC-Software/Engineering)
[Proof Of Concept](https://2020.igem.org/Team%3AUESTC-Software/Proof_Of_Concept)
[Implementation](https://2020.igem.org/Team%3AUESTC-Software/Implementation)
[Contribution](https://2020.igem.org/Team%3AUESTC-Software/Contribution)
[Notebook](https://2020.igem.org/Team%3AUESTC-Software/Notebook)

[Model](https://2020.igem.org/Team%3AUESTC-Software/Model)

Human Practices

[Science Communications](https://2020.igem.org/Team%3AUESTC-Software/Education%20)
[lntegrated HP](https://2020.igem.org/Team%3AUESTC-Software/Human_Practices)
[Inclusion](https://2020.igem.org/Team%3AUESTC-Software/Inclusion)

Team

[Team Members](https://2020.igem.org/Team%3AUESTC-Software/Team%20)
[Attributions](https://2020.igem.org/Team%3AUESTC-Software/Attributions)

Collaborations

[Sliver Collaborations](https://2020.igem.org/Team%3AUESTC-Software/Collaborations)
[Partnership](https://2020.igem.org/Team%3AUESTC-Software/Partnership)

[Awards](https://2020.igem.org/Team%3AUESTC-Software/Awards)
[Safety](https://2020.igem.org/Team%3AUESTC-Software/Safety)

![](https://static.igem.org/mediawiki/2020/a/a5/T--UESTC-Software--nav-logo.png)

[Home](https://2020.igem.org/Team%3AUESTC-Software)

Project

[Description](https://2020.igem.org/Team%3AUESTC-Software/Description)
[Engineering](https://2020.igem.org/Team%3AUESTC-Software/Engineering)
[Proof Of Concept](https://2020.igem.org/Team%3AUESTC-Software/Proof_Of_Concept)
[Implementation](https://2020.igem.org/Team%3AUESTC-Software/Implementation)
[Contribution](https://2020.igem.org/Team%3AUESTC-Software/Contribution)
[Notebook](https://2020.igem.org/Team%3AUESTC-Software/Notebook)

[Model](https://2020.igem.org/Team%3AUESTC-Software/Model)

Human Practices

[Science Communications](https://2020.igem.org/Team%3AUESTC-Software/Education%20)
[lntegrated HP](https://2020.igem.org/Team%3AUESTC-Software/Human_Practices)
[Inclusion](https://2020.igem.org/Team%3AUESTC-Software/Inclusion)

Team

[Team Members](https://2020.igem.org/Team%3AUESTC-Software/Team%20)
[Attributions](https://2020.igem.org/Team%3AUESTC-Software/Attributions)

Collaborations

[Sliver Collaborations](https://2020.igem.org/Team%3AUESTC-Software/Collaborations)
[Partnership](https://2020.igem.org/Team%3AUESTC-Software/Partnership)

[Awards](https://2020.igem.org/Team%3AUESTC-Software/Awards)
[Safety](https://2020.igem.org/Team%3AUESTC-Software/Safety)

☰

Sorry, your browser does not support inline SVG.

![](https://static.igem.org/mediawiki/2020/7/79/T--UESTC-Software--Logo.png)

Notebook

[Notebook](#111)

[![](https://static.igem.org/mediawiki/2019/f/fe/T--Thessaly--up.png)](#top)

# Notebook

#### ● 2020.05

(1) Set up 2020 UESTC-Software.
(2)Team Leaders：Wang Bin、Mo Nan
(3)Team members: Dong Haoran、Gao Fan、Han Jingqi、Yang Zhaochang、Liu Mingkang、Mei Yao、Zhou Tao、Min Zhuochao、Qiao Dan、Xiong Huiyu

#### ● 2020.06

(1)Extensive collection of relevant data and synthetic biology are urgently needed
(2)The project was designed to build a Domain part library which can provide convenience for protein design
(3)Team members brainstorm with PI and seek professional guidance from relevant teachers.

#### ● 2020.07

(1)Many proteins and domain databases (UniProtKB, PDB, Pfam, CATH, SCOP/SCOP2, KEGG, OMIM-, etc.) were investigated）
(2)Investigate protein shape matching algorithms.
(3)With domain splicing as the theme, we started to make games.
(4)Domain data in CATH, SCOP and Scop2 databases were integrated, and cd-HIT was used to eliminate redundant data.
(5)A large number of PDB data were crawled and downloaded, and domain-Atom data were extracted and processed.
(6）3D Zernike algorithm is used to process the domain stereo file information after extraction and obtain its surface shape features, and then cluster the 121 dimensional shape feature vectors (mean shift, k-means) according to the extracted information.

#### ● 2020.08

(1)Explore the improvement of clustering algorithm, in-depth study of elbow method and its expansion.
(2)Improved elbow method, compared multiple clustering algorithms, carried out accuracy evaluation, and determined that K-means was the final clustering algorithm
(3)Determination of K-means clustering method, calculation of domain physicochemical properties, collection and annotation of domain-related data information, exploration of domain evolutionary relationship, and construction of evolutionary tree
(4)The design and construction of building blocks model, and the production of project website using VUE

#### ● 2020.09

(1)Domain similarity prediction is carried out.
(2)Collect, process and analyze functional information of Domain.
(3)Domain function information crawling, conduct model validation and project validation.
(4)Build a lego brochure and create the synthetic biology promotion song "You Exist"

#### ● 2020.10

(1)To hold the sichuan Science and Technology Museum synthetic Biology promotion activities.
(2)Organize project documents and summarize project progress.
(3)Write Wiki content and perform aesthetic design related to the project.
(4) We invited many iGEM teams and related workers to use our Software and put forward suggestions for improvement.

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UESTC-Software/Engineering

<!DOCTYPE html>

Engineer

[![](https://static.igem.org/mediawiki/2020/a/a5/T--UESTC-Software--nav-logo.png)](https://2020.igem.org/Team%3AUESTC-Software)

[Home](https://2020.igem.org/Team%3AUESTC-Software)

Project

[Description](https://2020.igem.org/Team%3AUESTC-Software/Description)
[Engineering](https://2020.igem.org/Team%3AUESTC-Software/Engineering)
[Proof Of Concept](https://2020.igem.org/Team%3AUESTC-Software/Proof_Of_Concept)
[Implementation](https://2020.igem.org/Team%3AUESTC-Software/Implementation)
[Contribution](https://2020.igem.org/Team%3AUESTC-Software/Contribution)
[Notebook](https://2020.igem.org/Team%3AUESTC-Software/Notebook)

[Model](https://2020.igem.org/Team%3AUESTC-Software/Model)

Human Practices

[Science Communications](https://2020.igem.org/Team%3AUESTC-Software/Education%20)
[lntegrated HP](https://2020.igem.org/Team%3AUESTC-Software/Human_Practices)
[Inclusion](https://2020.igem.org/Team%3AUESTC-Software/Inclusion)

Team

[Team Members](https://2020.igem.org/Team%3AUESTC-Software/Team%20)
[Attributions](https://2020.igem.org/Team%3AUESTC-Software/Attributions)

Collaborations

[Sliver Collaborations](https://2020.igem.org/Team%3AUESTC-Software/Collaborations)
[Partnership](https://2020.igem.org/Team%3AUESTC-Software/Partnership)

[Awards](https://2020.igem.org/Team%3AUESTC-Software/Awards)
[Safety](https://2020.igem.org/Team%3AUESTC-Software/Safety)

![](https://static.igem.org/mediawiki/2020/a/a5/T--UESTC-Software--nav-logo.png)

[Home](https://2020.igem.org/Team%3AUESTC-Software)

Project

[Description](https://2020.igem.org/Team%3AUESTC-Software/Description)
[Engineering](https://2020.igem.org/Team%3AUESTC-Software/Engineering)
[Proof Of Concept](https://2020.igem.org/Team%3AUESTC-Software/Proof_Of_Concept)
[Implementation](https://2020.igem.org/Team%3AUESTC-Software/Implementation)
[Contribution](https://2020.igem.org/Team%3AUESTC-Software/Contribution)
[Notebook](https://2020.igem.org/Team%3AUESTC-Software/Notebook)

[Model](https://2020.igem.org/Team%3AUESTC-Software/Model)

Human Practices

[Science Communications](https://2020.igem.org/Team%3AUESTC-Software/Education%20)
[lntegrated HP](https://2020.igem.org/Team%3AUESTC-Software/Human_Practices)
[Inclusion](https://2020.igem.org/Team%3AUESTC-Software/Inclusion)

Team

[Team Members](https://2020.igem.org/Team%3AUESTC-Software/Team%20)
[Attributions](https://2020.igem.org/Team%3AUESTC-Software/Attributions)

Collaborations

[Sliver Collaborations](https://2020.igem.org/Team%3AUESTC-Software/Collaborations)
[Partnership](https://2020.igem.org/Team%3AUESTC-Software/Partnership)

[Awards](https://2020.igem.org/Team%3AUESTC-Software/Awards)
[Safety](https://2020.igem.org/Team%3AUESTC-Software/Safety)

☰

Sorry, your browser does not support inline SVG.

![](https://static.igem.org/mediawiki/2020/7/79/T--UESTC-Software--Logo.png)

Engineering

 [Overview of iteration process](#Overview)
[Project Design](#Project)
[Domain processing](#Domain processing)

[![To top](https://static.igem.org/mediawiki/2020/9/97/T--UESTC-Software--top.png)](#top)

# Overview of iteration process

![](https://s1.ax1x.com/2020/11/06/BhEdQs.png)

# Project Design

After many iterations, we built the project in the following way.

## Data Integration

To facilitate user's utilization of the domains we have divided, we made full use of the current mature database resources. Considering the scientificity of protein domain division, we used same naming of domains with CATH and SCOP. We crawled the functional annotations related to our domain classification on Go so that user's could easily know functions in which the domain might be involved. In addition, we also examined the binding score between different shape classifications and gave the recommended binding scheme, so as to minimize the risk that the selected two types of proteins could not bind.

Our project integrates 3 databases, including CATH [1], SCOP [2] /SCOP2 [3], and references 2 databases including PDB [4] and UniProt [5]. All the information is contained in CPD3DS which has been verified by experiments, which ensures the high reliability of the data.

**Integrated Databases**

[**CATH**](http://cathdb. info/)

The CATH database is a free, publicly available online resource that provides information on the evolutionary relationships of protein domains.

**CATH-Plus data includes:**

**FunFams (Functional Families)**

The homologous superfamilies in CATH-Gene3D can often be functionally and structurally diverse even though they share a conserved structural core. Therefore, the superfamilies have been sub-classified into functional families (FunFams) using a subclassification protocol purely based on sequence patterns. Relatives within these FunFams are likely to share highly similar structures and functions. The FunFams are useful in function prediction and in providing information on the evolution of function.

**Structural clusters**

The structures within a homologous superfamily have been clustered at &lt 9 Å RMSD to form structural clusters, also known as structurally-similar groups (SSGs). These structural clusters are useful for understanding the structural diversity of a superfamily.

[**SCOP/SCOP2**](http://scop.mrc-lmb.cam.ac.uk/scop2/0.html)

Belongs to the secondary protein structure database.

The classification of SCOP and SCOP2 is based on four levels: type (secondary structure component), family (spatial geometric relationship), superfamily (distant protein evolution relationship) and folding (close protein evolution relationship).

**Reference Databases**

[**UniProtKB**](http://www. uniprot. org/)

**Its three-level database:**

**UniPrac:**
A large number of protein sequences included in all UniProt database sub-libraries.

**UniRef:**
Summarize several major databases of UniProt and repeat the series after removal.

**UniProtKB:**
Databases with detailed annotations and links to other databases are divided into UniProtKB , Swiss-Prot , UniProtKB and TrEMBL . Among them , the data in Swiss-Prot is obtained from the experiment, and the annotation is completed after manual inspection, and TrEMBL is the annotation completed automatically.

[**PDB**](http://www. rcsb. org/)

The search part displays the basic information about the protein. If you want to see other information, download a . pdb file in PDB format. The file can be opened with Notepad. The file includes: molecular category, keywords, method of determining structure, and primary structure information , Amino acid sequence, modification of standard residues, secondary structure, chemical bonds between residues, 3D coordinates (atomic coordinates), atomic bond information, etc.

## De-redundancy

We downloaded all the PDB files on the PDB database and reduced their redundancy by cd-hit [6,7,8,9,10,11].

The input file of CD-HIT only has a FASTA format file. Generally speaking, the input file of CD-HIT is to cluster the gene or protein sequences of several samples, so the sequences of these samples need to be summarized together as the input file.

Cd-hit has two types of output files: one is a FASTA file that only contains representing sequences without redundancy;The other is a cluster information file ending in. clSTR, the file's format is shown in the figure below.

|  |
| --- |
| >Cluster 0 |
| 0 2799aa, >PF04998.6 |RPOC2\_CHLRE/275-3073... \* |
| >Cluster 1 |
| 0 2214aa, >PF06317.1|Q6Y625\_9VIRU/1-2214... at 80% |
| 1 2215aa, >PF06317.1|009705\_9VIRU/1-2215.. . at 84% |
| 2 2217aa, >PF06317.1lQ6Y630\_9VIRU/1-2217.. . \* |
| 2 2217aa, >PF06317.1lQ6Y630\_9VIRU/1-2217.. . \* |

The one beginning with ">" is a clustering group. Each group is arranged by the sequence number. As shown in the figure above, there are 5 cluster sequences in Cluster 1 group and each of them has a percentage or a sign "\*". The percentage represents the similarity between the sequence and the representative sequence and the sign "\*" represents the sequence is the representative sequence of the cluster.

Preliminary de-redundancy took 80% similarity as the basic parameter to perform de-redundancy operation after which 33, 455 de-redundant data were obtained.

![](https://static.igem.org/mediawiki/2020/3/36/T--UESTC-Software--Engineeringt-1.png)

## Feature extraction algorithm

The 3D-Zernike descriptor ( 3DZD )[13] can be used to effectively compare the surface shapes of single chains, single domains or single complexes in the latest protein database ( PDB ) with all protein structures.

The 3D-Zernike descriptor ( 3DZD ) is a combination of coefficients calculated from a set of well-defined orthogonal 3D basic polynomials that approximate a given 3D function (a grid of discrete surfaces). 3DZD has various ideal characteristics when applied to describe protein surface shape:

|  |
| --- |
| 1.Rotation invariance: Protein comparison does not require prior structural comparison. |
| 2.Tightness: The surface of a protein can be closely represented as an eigenvector with only 121 Numbers (which is called invariant). These vectors can be compared by calculating Euclidean distance in a short time which allows rapid shape retrieval. |
| 3.Layered resolution: The invariant of lower resolution is also part of the higher resolution. For example, the first 12 numbers in 121 invariants represent the same protein at a lower resolution. |

By calculating the Euclidean distance of 121 eigenvector of two proteins, the similarity of the two proteins' shapes can be estimated.

## Clustering

Introduction to Kmeans clustering algorithm

Due to its excellent efficiency and good scalability, K-means clustering [12] algorithm is regarded as one of the most famous clustering method. K-means algorithm is a process of repeatedly moving the center point of a type. The center point of the type also known as centroids is moved to the average position of its containing members, and then its internal members are re-divided.

The K-means algorithm has many good characteristics that make it widely used in many fields.

|  |
| --- |
| First, the algorithm can prune the tree to determine the classification of some samples according to the types of fewer known clustering samples. |
| Second, in order to overcome the inaccuracy of clustering of a small number of samples, the algorithm itself has an optimization iteration function. On the obtained clusters, iterative correction pruning is performed again to determine the clustering of some samples, which optimizes the unreasonable part of the initial supervised learning sample classification. |

Due to the advantages of K-means itself, we think it is suitable for our project.

# Domain processing

After classifying the domains according to the surface shape, we considerd that users may not only need domain's shape classification, but also require domain sequence information, function information and other information.

## Sequence information

Our sequence information mainly comes from PDB database, CATH database, SCOP and SCOP2 . Our domain division is based on the structure domain information recorded in the CATH database, SCOP and SCOP2. In addition, the original files come from the PDB database.

## Function information crawling

In order to associate the function of the protein with the domain, we crawled the function tag corresponding to GeneProduct Annotation in the protein Annotation page on the PDB website. After that, taking the domain type as the unit, we calculate the probability of the occurrence of different function tags and extracted the function tags with high probability.

## Combining recommendation

#### Probability of domain in the same protein

After reducing the redundancy, we calculated the combined probability of the entries in the domain database.

To furnish with constructive suggestions for binding domains of different types during protein design, the probability of each type combining with other type is provided through combining score. Users are able to search the domain type name and get its combination score with other types in our CPD3DS website.

Additionally, the combining score mentioned above is normalized to a 100\*100 binding graph, where the darker the color is, the more likely domain binding is in the corresponding type of that row and that column.

![](https://static.igem.org/mediawiki/2020/2/20/T--UESTC-Software--project-1.png)

## Domain model processing

As it is difficult to perceive domain, we also designed a set of domain building block modules that can be spliced.

![](https://static.igem.org/mediawiki/2020/1/13/T--UESTC-Software--project-3.png)
![](https://static.igem.org/mediawiki/2020/b/b9/T--UESTC-Software--project-4.png)

We have adopted two solutions here to design a series of spliced Domain models.

|  |
| --- |
| 1. Using blender to process VRML2 (a scene model file, its expand name is ". wrl" ) exported from Pymol, or editing the fixed vertex shader processed by MeshLab . |
| 2. Preprocessing for pixel building block model |

**Folded pictures**

![](https://static.igem.org/mediawiki/2020/3/36/T--UESTC-Software--project-5.png)
![](https://static.igem.org/mediawiki/2020/a/af/T--UESTC-Software--project-6.png)

|  |
| --- |
| 3.Using the open source LSculpt [14] program, we converted the 3d model file into a Lego model file that LeoCAD can recognize. |

**Folded pictures**

![](https://s1.ax1x.com/2020/11/09/BT4FXj.png)
![](https://s1.ax1x.com/2020/11/09/BT4Ans.png)

The model we got can be found on this page <http://104.168.165.152/>

## Protein splitting

Considering that users may need to know the structure and composition of natural proteins in protein design, domains of natural proteins can all be found in our database. To ensure the integrity and simplicity of data, we chose the representative domain for each domain type.

References

Database References

[1]Sillitoe I, Dawson N, Lewis TE, et al.CATH: expanding the horizons of structure-based functional annotations forgenome sequences. Nucleic Acids Res. 2019;47(D1):D280-D284.doi:10.1093/nar/ gky1097

[2]Antonina Andreeva, Eugene Kulesha, Julian Gough, Alexey Murzin, TheSCOP database in 2020: expanded classification of representative family andsuperfamily domains of known protein structures. (2020) Nucl. Acid Res., 48(D1): D376-D382

[3]Antonina Andreeva, Dave Howorth, Cyrus Chothia, Eugene Kulesha, Alexey Murzin, SCOP2 prototype: a new approach to protein structu re mining. (2014) Nucl. Acid Res., 42 (D1): D310-D314

[4] Goodsell DS. The Protein Data Bank[M]// Atomic Evidence. Springer International Publishing, 2016.

[5]UniProt Consortium T UniProt: the universal protein knowledgebase. Nucleic Acids Res. 2018;46:2699. doi: 10.1093/ nar/gky092.

CD-hit References

[6]Weizhong Li, Adam Godzik, Cd-hit: a fastprogram for clustering and comparing large sets of protein or nucleotide sequences, Bioinformatics, Volume 22, Issue 13, 1 July 2006, Pages1658–1659, https://doi.org/ 10.1093/bioinformatics/btl158

[7]Ying Huang, Beifang Niu, Ying Gao, LiminFu, Weizhong Li, CD-HIT Suite: a web server for clustering and comparing biologicalsequences, Bioinformatics, Volume 26, Issue 5, 1 March 2010, Pages68 0–682, https: //doi.org/10.1093/bioinformatics/btq003

[8]Ying Huang, Beifang Niu, Ying Gao, Limin Fuand Weizhong Li. CD-HIT Suite: a web server for clustering and comparing biological sequences . Bioinformatics, 2010(26): 680-682.

[9]Weizhong Li and Adam Godzik. Cd-hit: a fastprogram for clustering and comparing large sets of protein or nucleotide sequences. Bioinformatics, 2006(22): 1658-1659.

[10]Weizhong Li, Lukasz Jaroszewski and AdamGodzik. Tolerating some redundancy significantly speeds up clustering of largeprotein databases. Bioinformatics, 2002(18): 77-82.

[11]Weizhong Li, Lukasz Jaroszewski and AdamGodzik. Clustering of highly homologous sequences to reduce the size of largeprotein datab ases. Bioinformatics, 2001(17): 282-283.

[12] MacQueen, J. Some Methods for Classification and Analysis of MultiVariate Observations[C]// Proc of Berkeley Symposium on Mathematical Statistics & Probability. 1965.

[13]David La, Juan Esquivel-Rodriguez, Vishwesh Venkatraman, Bin Li, Lee Sael, Steven Ueng, Steven Ahrendt, and Daisuke Kihara. 3D-SURFER: software for high throughput protein surface comparison and analysis. B ioinformatics 25: 2843-2844 (2009)

Model Reference

[14]LSculpt.Download from https://github.com/RomkoSI/lsculpt.

**Contact Us**

uestcsoftware@vip.qq.com

NO.2006.XiYuan Avenue,UESTC,Chengdu,China

![](https://static.igem.org/mediawiki/2020/9/93/T--UESTC-Software--footer-1.png)

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UESTC-Software/Experiments

# Experiments

Describe the research, experiments, and protocols you used in your iGEM project. These should be detailed enough for another team to repeat your experiments.

If you made Parts this year, please remember to put all information, characterization, and measurement data on the Part's Main Page on the [Registry](http://parts.igem.org/Main_Page).

### What should this page contain?

* Protocols
* Experiments

### Inspiration

* [2014 Colombia](https://2014.igem.org/Team%3AColombia/Protocols)
* [2014 Imperial](https://2014.igem.org/Team%3AImperial/Protocols)
* [2014 Caltech](https://2014.igem.org/Team%3ACaltech/Project/Experiments)

[![](https://static.igem.org/mediawiki/2020/8/8b/HQ_page_logo.jpg)](https://2020.igem.org)

# Team:UESTC-Software/Results

# Results

You can describe the results of your project and your future plans here.

### What should this page contain?

* Clearly and objectively describe the results of your work.
* Future plans for the project.
* Considerations for replicating the experiments.

### Describe what your results mean

* Interpretation of the results obtained during your project. Don't just show a plot/figure/graph/other, tell us what you think the data means. This is an important part of your project that the judges will look for.
* Show data, but remember **all measurement and characterization data must also be on the Part's Main Page on the [Registry](http://parts.igem.org/Main_Page).** Otherwise these data will not be in consideration for any medals or part awards!
* Consider including an analysis summary section to discuss what your results mean. Judges like to read what you think your data means, beyond all the data you have acquired during your project.

### Project Achievements

You can also include a list of bullet points (and links) of the successes and failures you have had over your summer. It is a quick reference page for the judges to see what you achieved during your summer.

* A list of linked bullet points of the successful results during your project
* A list of linked bullet points of the unsuccessful results during your project. This is about being scientifically honest. If you worked on an area for a long time with no success, tell us so we know where you put your effort.

### Inspiration

See how other teams presented their results.

* [2014 TU Darmstadt](https://2014.igem.org/Team%3ATU_Darmstadt/Results/Pathway)
* [2014 Imperial](https://2014.igem.org/Team%3AImperial/Results)
* [2014 Paris Bettencourt](https://2014.igem.org/Team%3AParis_Bettencourt/Results)