JackieLiao (Talk | contribs) |
|||
(17 intermediate revisions by one other user not shown) | |||
Line 123: | Line 123: | ||
.circle { | .circle { | ||
position:absolute; | position:absolute; | ||
− | left: | + | left: 1110px; |
top: 30px; | top: 30px; | ||
width: 180px; | width: 180px; | ||
Line 135: | Line 135: | ||
position: fixed; | position: fixed; | ||
left: 25px; | left: 25px; | ||
− | top: | + | top: 200px; |
font-family: Corbel; | font-family: Corbel; | ||
background: rgba(250, 250, 250, 0.15); | background: rgba(250, 250, 250, 0.15); | ||
Line 292: | Line 292: | ||
<div class="top"> | <div class="top"> | ||
<img alt="" style="position:absolute;z-index:++1;float:left;margin-top:20px;width:390px;height:80px;" src="https://static.igem.org/mediawiki/2016/b/bb/CGU_Taiwan--logo2.jpg"> | <img alt="" style="position:absolute;z-index:++1;float:left;margin-top:20px;width:390px;height:80px;" src="https://static.igem.org/mediawiki/2016/b/bb/CGU_Taiwan--logo2.jpg"> | ||
− | <img style="position:absolute;left: | + | <img style="position:absolute;left:1120px;top:35px;z-index:+1;width:155px;height:180px;" src="https://static.igem.org/mediawiki/2016/8/8a/CGU_Taiwan--logo9.jpg"> |
<a name='anchor0'></a> | <a name='anchor0'></a> | ||
<div class="circle"></div> | <div class="circle"></div> | ||
Line 316: | Line 316: | ||
<div class="left" style="height:225px; border-color:#140731; border-radius:8px;border-width:2px;border-style:solid;"> | <div class="left" style="height:225px; border-color:#140731; border-radius:8px;border-width:2px;border-style:solid;"> | ||
− | <a href="#anchor0"><section class="left-tab" style="position:fixed;top: | + | <a href="#anchor0"><section class="left-tab" style="position:fixed;top:210px;left:35px;" id="myP" onmousedown="mouseDown()" onmouseup="mouseUp()">TOP</section> |
− | <a href="#anchor1"><section class="left-tab" style="position:fixed;top: | + | <a href="#anchor1"><section class="left-tab" style="position:fixed;top:245px;left:50px;">Motivation</section> |
− | <a href="#anchor2"><section class="left-tab" style="position:fixed;top: | + | <a href="#anchor2"><section class="left-tab" style="position:fixed;top:280px;left:50px;">Demo</section> |
<a target="_blank" href="http://163.25.92.36/igemcgu/igemwebhome.htm"><section class="left-tab" style="position:fixed;top:390px;left:50px;">McHug</section> | <a target="_blank" href="http://163.25.92.36/igemcgu/igemwebhome.htm"><section class="left-tab" style="position:fixed;top:390px;left:50px;">McHug</section> | ||
− | <a href="#anchor4"><section class="left-tab" style="position:fixed;top: | + | <a href="#anchor4"><section class="left-tab" style="position:fixed;top:315px;left:50px;">Results</section> |
− | <a href="#anchor5"><section class="left-tab" style="position:fixed;top: | + | <a href="#anchor5"><section class="left-tab" style="position:fixed;top:350px;left:50px;">Notebook</section> |
</div> | </div> | ||
− | <img src="https://static.igem.org/mediawiki/2016/a/a1/Drylab.png" width=550px height=300px style="margin-left: | + | <img src="https://static.igem.org/mediawiki/2016/a/a1/Drylab.png" width=550px height=300px style="border:2px black solid;border-radius:8px;margin-left:400px;margin-top:170px;"></img> |
<div class="mid" style="top:405px;background-color:white;"> | <div class="mid" style="top:405px;background-color:white;"> | ||
<a name='anchor1'></a> | <a name='anchor1'></a> | ||
<br><br><br> | <br><br><br> | ||
− | <h1 style="font-size:30px;color:#FF8800;text-decoration:none;position:absolute;left:200px;top: | + | <h1 style="font-size:30px;color:#FF8800;text-decoration:none;position:absolute;left:200px;top:70px;margin:20px;">Modeling Motivation<HR style="border-color:#FF8800;width:780px;position:absolute;left:300px;top:5px;size:2px;"></h1> |
− | <p style="color:black;text-decoration:none;font-size:15px;position:absolute;left:200px;top: | + | <p style="color:black;text-decoration:none;font-size:15px;position:absolute;left:200px;top:110px;margin-right:80px;margin-left:50px;margin-top:30px;text-align:justify;"> |
In our 2016 iGEM project, immune and protein information searching is inevitably required. Therefore, McHug is a software platform that is created to arrange your data and search the protein infomation from several databases. We will output your data with a user-friendly interface and you can easily browse the results by submitting in a requested form. The concept of McHug software is originated from 2016 CGU iGEM group. We aim to test the potential of Leishmania to be a new vaccine adjuvant by carrying antigens directly into immune cells. The antigen peptides will be presented on MHCI or II molecules to activate T cells. Therefore, McHug is created to predict the peptides on MHC molecules and help to optimize the peptide presentation and T cell activation. Also, cloning efficiency is considered to be an important step of the experiment. We then expect that this platform and help us shorten the antigen sequence so that it can be more effective to subclone the shuttle vector. The major functions of McHug can be sorted into 3 parts:<br> | In our 2016 iGEM project, immune and protein information searching is inevitably required. Therefore, McHug is a software platform that is created to arrange your data and search the protein infomation from several databases. We will output your data with a user-friendly interface and you can easily browse the results by submitting in a requested form. The concept of McHug software is originated from 2016 CGU iGEM group. We aim to test the potential of Leishmania to be a new vaccine adjuvant by carrying antigens directly into immune cells. The antigen peptides will be presented on MHCI or II molecules to activate T cells. Therefore, McHug is created to predict the peptides on MHC molecules and help to optimize the peptide presentation and T cell activation. Also, cloning efficiency is considered to be an important step of the experiment. We then expect that this platform and help us shorten the antigen sequence so that it can be more effective to subclone the shuttle vector. The major functions of McHug can be sorted into 3 parts:<br> | ||
<span style="font-weight:bold;">1. Protein Structure</span><br> | <span style="font-weight:bold;">1. Protein Structure</span><br> | ||
Line 344: | Line 344: | ||
</div> | </div> | ||
− | <div class="mid" style="top: | + | <div class="mid" style="top:1220px;background-color:white;"> |
<a name='anchor2'></a> | <a name='anchor2'></a> | ||
<br><br><br> | <br><br><br> | ||
Line 356: | Line 356: | ||
</div> | </div> | ||
− | <div class="mid" style="top: | + | <div class="mid" style="top:1680px;background-color:white;"> |
<a name='anchor4'></a> | <a name='anchor4'></a> | ||
<br><br><br> | <br><br><br> | ||
Line 364: | Line 364: | ||
<br>McHug was programmed by computer languages such as Php, javascript, css and html. The major sources from published databases are Uniprot, IEDB and PDB. We thank Dr. Chi-Ching Lee for guiding us programming this software platform. We would also like to thank Chang-Gung Molecular Medicine Research Center for providing us server. This work was supported by several faculties of Chang-Gung University. We are grateful for sponsors and donations from all the supporters. <br><br> | <br>McHug was programmed by computer languages such as Php, javascript, css and html. The major sources from published databases are Uniprot, IEDB and PDB. We thank Dr. Chi-Ching Lee for guiding us programming this software platform. We would also like to thank Chang-Gung Molecular Medicine Research Center for providing us server. This work was supported by several faculties of Chang-Gung University. We are grateful for sponsors and donations from all the supporters. <br><br> | ||
<span style="font-weight:bold;font-size:20px;">Result for OVA protein</span><br> | <span style="font-weight:bold;font-size:20px;">Result for OVA protein</span><br> | ||
− | <img src="https://static.igem.org/mediawiki/2016/3/38/OVAchart.png" style="border:2px black solid;border-radius:8px;" width=900px height=500px></img> | + | <img src="https://static.igem.org/mediawiki/2016/3/38/OVAchart.png" style="border:2px black solid;border-radius:8px;" width=900px height=500px></img><br><br> |
+ | Based on our experimental design, this result was analysed under condition of mouse MHC molecules and OVA protein. As the penal shown above, there are two MHC high affinity regions on OVA protein which are amino acid 0-50th and 150-250th. However, the 0-50th sequence is also around the signal peptide sequence rendering a possibility of cutting off. Therefore, we predict that sequence 150-250th is the best part to be a high antigenicity peptide sequence. Besides, this sequence will remain its 3D structure due to enough length of the peptide which means B cell will also able to recognize this antigen-like-sequence by binding on it. In the future, we expect that this can help us shortening the sequence cloned into the shuttle vector and enhance the efficiency of transfection by designing this peptide sequence. Moreover, we will test the actual peptides binding to MHC molecules to directly elucidate this result in our in vitro test.<br><br> | ||
+ | <img src="https://static.igem.org/mediawiki/2016/7/72/OVA3D.png" style="float:left;margin:20px;border:2px black solid;border-radius:8px;" width=400px height=450px></img> | ||
+ | The 150-250th sequence on the 3D structure shows that the sequence is on the shell of the protein. In other words, the sequence has a higher possibility to be a epitope sequence to activate B cell and generate antibody against the OVA antigen. If you further peek into the sequence position, you will find that the 150-250th sequence contains turn structure which is prone to be a high antigenicity part. | ||
</p> | </p> | ||
</div> | </div> | ||
Line 370: | Line 373: | ||
− | <div class="mid" style="top: | + | <div class="mid" style="top:3500px;background-color:white;"> |
<a name='anchor5'></a> | <a name='anchor5'></a> | ||
<br><br><br> | <br><br><br> | ||
Line 376: | Line 379: | ||
<div class="wrapper" style="position:absolute;left:350px;top:130px;"> | <div class="wrapper" style="position:absolute;left:350px;top:130px;"> | ||
<div class="frame"></div> | <div class="frame"></div> | ||
− | <input checked='' data-tooltip=" | + | <input checked='' data-tooltip="June" class='tab1' name='thumbnail' type='radio' /> |
− | + | ||
<input class='tab2' data-tooltip="July" name='thumbnail' type='radio' /> | <input class='tab2' data-tooltip="July" name='thumbnail' type='radio' /> | ||
<input class='tab2' data-tooltip="August" name='thumbnail' type='radio' /> | <input class='tab2' data-tooltip="August" name='thumbnail' type='radio' /> | ||
− | <input class=' | + | <input class='tab2' data-tooltip="September" name='thumbnail' type='radio' /> |
+ | <input class='tab3' data-tooltip="October" name='thumbnail' type='radio' /> | ||
<ul class="tab"> | <ul class="tab"> | ||
<li> | <li> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</li> | </li> | ||
<li> | <li> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</li> | </li> | ||
<li> | <li> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</li> | </li> | ||
<li> | <li> | ||
<h3>Week 1 (8/1~8/7)</h3> | <h3>Week 1 (8/1~8/7)</h3> | ||
− | <p> | + | <p>8/5 Jmol: 3D sturcture |
+ | |||
+ | First, we need to get profile of PDB (protein data bank). We may find a great amount of the same protein under different conditions. As long as you research any protein in any condition, you can submit the data to PDB. | ||
</p> | </p> | ||
<h3>Week 2 (8/8~8/14)</h3> | <h3>Week 2 (8/8~8/14)</h3> | ||
− | <p></p> | + | <p>8/12 1. There is a simple Jsmol model code. We can change the code to meet our goals. |
+ | http://163.25.92.36/igemcgu/jsmol/jmol/jsmol/lite.htm 2.Our goals are : | ||
+ | Auto spin in the beginning. | ||
+ | We need to have buttons, such as, spin on and spin off. | ||
+ | Most important, link "PDB file" to 3D structuer. | ||
+ | |||
+ | 3.In the first goal, we get...... | ||
+ | http://163.25.92.36/igemcgu/jsmol/jmol/jsmol/resize_test.htm </p> | ||
<h3>Week 3 (8/15~8/21)</h3> | <h3>Week 3 (8/15~8/21)</h3> | ||
− | <p></p> | + | <p>8/19 Use " iframe function" to combine each track, such as, MHC class I&II affinity tracks and 3D structure track. |
+ | Ex: <iframe src="target" width="px" height="px" frameborder="px" scrolling="px"></iframe> | ||
+ | |||
+ | Add a new track make user can choose specific amino acids region. | ||
+ | We use " If ( $_POST['APP']) $APP=' ' ; | ||
+ | Else $AAP="slect $_POST['APP']; color: red;" </p> | ||
<h3>Week 4 (8/22~8/28)</h3> | <h3>Week 4 (8/22~8/28)</h3> | ||
− | <p></p> | + | <p>8/26 1.1. We already complete "inframe".We also separate two page, one is home page. The other is data page, such as, 3D structure and MHC binding affinity. 3.In the improvement, we want to add "3D structure information when we select amino acid region". |
− | <h3>Week 5 (8/ | + | 4. And we should find Swiss-Prot ID /PDB ID. http://www.uniprot.org/help/programmatic_access |
− | + | http://www.uniprot.org/uniprot/P12345.txt | |
+ | |||
+ | 2.Next part, we want to put PDB protein informations. </p> | ||
+ | <h3>Week 5 (8/29~9/4)</h3> | ||
+ | <p>8/31 1.use "<div id="a" style="display: none">…......</div>" to define a track and the button 2.json decode (use to catch the p12345,XML and then ) | ||
+ | 1. step 1: catch the p12345,XML shell_exec("Wget URL -0 $jobId/ p12345.XML"); | ||
+ | 2. step 2: read the p12345,XML $XML_content = file_get_contents(" $jobId/ p12345.XML" | ||
+ | 3. step 3: change the XML to Array $a= json_decode ( $XML_content, true) | ||
+ | 4. step 4: print_r($a) first to check | ||
+ | 5. step 5: echo $a["feature"]["modified_residue"][…][….]; | ||
+ | |||
+ | 3.go to http://www.uniprot.org/uniprot/P12345.txt and find the features. | ||
+ | |||
+ | 4.xml_parse_into_struct() can use compare with json_decodegfdgfdgg | ||
+ | |||
+ | 5.Next step, use "html5 " to draw fancy picture. </p> | ||
</li> | </li> | ||
<li> | <li> | ||
<h3>Week 1 (9/5~9/11)</h3> | <h3>Week 1 (9/5~9/11)</h3> | ||
− | <p> | + | <p>9/2 |
+ | 1.altert of word use "onclick" function to restrict user to submit correct codes or words. | ||
+ | |||
+ | 3.use "internal" to show slide of pictures | ||
+ | |||
+ | 4.complete the inframe of information which come from different tracks <br>9/9 1.put MHC class II panel | ||
+ | 2.put xml | ||
+ | 3.PDB viewer | ||
+ | 4.user interface | ||
+ | 5.3D structure : | ||
+ | First, select 130-139, and then select 10 , and then label 10. | ||
+ | Second, use php to catch pdb protein and output the amino acid symbol. | ||
+ | 6.feature table: | ||
+ | Start, end, and features. (ok) | ||
+ | 7.We need to translate these feature word to table or pictures. | ||
</p> | </p> | ||
<h3>Week 2 (9/12~9/18)</h3> | <h3>Week 2 (9/12~9/18)</h3> | ||
<p></p> | <p></p> | ||
<h3>Week 3 (9/19~9/25)</h3> | <h3>Week 3 (9/19~9/25)</h3> | ||
− | <p></p> | + | <p>9/20 We use "canvas" to perform our protein information. 2.use "in_array($knownList, $each[1])" to decrease the FT information overlap</p> |
<h3>Week 4 (9/26~10/2)</h3> | <h3>Week 4 (9/26~10/2)</h3> | ||
− | <p></p> | + | <p>9/30 1. increase the sample number (eg: notch, tp53, HA, ) |
− | <h3>Week 5 ( | + | 2.$infos=array ("helix", "domain","site"….) </p> |
+ | <h3>Week 5 (10/3~10/10)</h3> | ||
<p></p> | <p></p> | ||
</li> | </li> |
Latest revision as of 17:45, 19 October 2016
Leijuvant
Modeling Motivation
In our 2016 iGEM project, immune and protein information searching is inevitably required. Therefore, McHug is a software platform that is created to arrange your data and search the protein infomation from several databases. We will output your data with a user-friendly interface and you can easily browse the results by submitting in a requested form. The concept of McHug software is originated from 2016 CGU iGEM group. We aim to test the potential of Leishmania to be a new vaccine adjuvant by carrying antigens directly into immune cells. The antigen peptides will be presented on MHCI or II molecules to activate T cells. Therefore, McHug is created to predict the peptides on MHC molecules and help to optimize the peptide presentation and T cell activation. Also, cloning efficiency is considered to be an important step of the experiment. We then expect that this platform and help us shorten the antigen sequence so that it can be more effective to subclone the shuttle vector. The major functions of McHug can be sorted into 3 parts:
1. Protein Structure
Protein structure can affect the possibility of being epitope. Peptides in strong structural sequences like alpha-helix have small chance to be antigenic determinant. On the other hand, sequences in loop structure tend to be recognized by the immune system, specifically by antibodies, B cells, or T cells. Here, McHug shows you the 3D structure of your protein and you can select the peptide sequence to be colored. In case you want to design an epitope sequence to generate antibodies, you can choose sequences on the protein surface in a visible way.
2. MHC Affinity Graphs
Pathogenic proteins will be chopped into peptides and presented by MHC molecules to activate T cells. Therefore, the prediction of MHC affinity in your protein sequence can help you design your experiment. McHug is generated to arrange your numerical data into an easy understanding graph. We can show your IEDB prediction result in a trend chart. Also, users can enter the affinity threshold to curtail the signal in low-affinity position. Each affinity of amino acid in the chart stands for the nonamer starting from the specific amino acid position. Users can easily choose the high-affinity sequence and optimize their experiment.
3. Modification Sites
McHug will provide you the basic information of protein modifications. Moreover, the modification sites will be shown correspondingly to the amino acid position of MHC affinity chart. With the information, users can twig the profile of the protein.
4. Conservation Level
Protein conservation level will be given after BLASTing and multiple sequence aligning the submitted protein sequence. The outcome indicates the protein sequence conservation level between homologous protein sequences in different species. The conservation data will also be shown correspondingly to the amino acid position of MHC affinity chart. Users can choose the highly conserved peptide sequence to perform their experiment. In the project of CGU iGEM 2016, highly conserved region of pathogenic antigens sequence indicates a higher common share of pathogens. This can ensure the high coverage of the vaccine. (Future Work)
Demo
This demo clip was filmed to showcase how to use McHug software and explan the function of result page. The protein ID we used in this clip was OVA protein so that you can see the result of our targeting antigen. The ultimate goal of McHug platform is to integrate several protein databases and provide the users with easy-understanding illustrations.
So far, we are able to show you protein 3D structure on the top of the interface. You can easily zoom in and zoom out to peek every part of your protein. And even select a partial peptide sequence. The peptide sequence in the protein will light up and reveal its position in the 3D structure. Moreover, MHC binding affinity and protein annotations are shown below. Amino acid positions are arranged correspondingly so that you can check all the information side by side. McHug 2016 also features the visualized interface which can transform loads of numerical data into legible charts and all basic protein information are integrated into a canvas penal at the buttom of the page.
Results
McHug was programmed by computer languages such as Php, javascript, css and html. The major sources from published databases are Uniprot, IEDB and PDB. We thank Dr. Chi-Ching Lee for guiding us programming this software platform. We would also like to thank Chang-Gung Molecular Medicine Research Center for providing us server. This work was supported by several faculties of Chang-Gung University. We are grateful for sponsors and donations from all the supporters.
Result for OVA protein
Based on our experimental design, this result was analysed under condition of mouse MHC molecules and OVA protein. As the penal shown above, there are two MHC high affinity regions on OVA protein which are amino acid 0-50th and 150-250th. However, the 0-50th sequence is also around the signal peptide sequence rendering a possibility of cutting off. Therefore, we predict that sequence 150-250th is the best part to be a high antigenicity peptide sequence. Besides, this sequence will remain its 3D structure due to enough length of the peptide which means B cell will also able to recognize this antigen-like-sequence by binding on it. In the future, we expect that this can help us shortening the sequence cloned into the shuttle vector and enhance the efficiency of transfection by designing this peptide sequence. Moreover, we will test the actual peptides binding to MHC molecules to directly elucidate this result in our in vitro test.
The 150-250th sequence on the 3D structure shows that the sequence is on the shell of the protein. In other words, the sequence has a higher possibility to be a epitope sequence to activate B cell and generate antibody against the OVA antigen. If you further peek into the sequence position, you will find that the 150-250th sequence contains turn structure which is prone to be a high antigenicity part.
Notebook
-
Week 1 (8/1~8/7)
8/5 Jmol: 3D sturcture First, we need to get profile of PDB (protein data bank). We may find a great amount of the same protein under different conditions. As long as you research any protein in any condition, you can submit the data to PDB.
Week 2 (8/8~8/14)
8/12 1. There is a simple Jsmol model code. We can change the code to meet our goals. http://163.25.92.36/igemcgu/jsmol/jmol/jsmol/lite.htm 2.Our goals are : Auto spin in the beginning. We need to have buttons, such as, spin on and spin off. Most important, link "PDB file" to 3D structuer. 3.In the first goal, we get...... http://163.25.92.36/igemcgu/jsmol/jmol/jsmol/resize_test.htm
Week 3 (8/15~8/21)
8/19 Use " iframe function" to combine each track, such as, MHC class I&II affinity tracks and 3D structure track. Ex: Add a new track make user can choose specific amino acids region. We use " If ( $_POST['APP']) $APP=' ' ; Else $AAP="slect $_POST['APP']; color: red;"
Week 4 (8/22~8/28)
8/26 1.1. We already complete "inframe".We also separate two page, one is home page. The other is data page, such as, 3D structure and MHC binding affinity. 3.In the improvement, we want to add "3D structure information when we select amino acid region". 4. And we should find Swiss-Prot ID /PDB ID. http://www.uniprot.org/help/programmatic_access http://www.uniprot.org/uniprot/P12345.txt 2.Next part, we want to put PDB protein informations.
Week 5 (8/29~9/4)
8/31 1.use "
" to define a track and the button 2.json decode (use to catch the p12345,XML and then ) 1. step 1: catch the p12345,XML shell_exec("Wget URL -0 $jobId/ p12345.XML"); 2. step 2: read the p12345,XML $XML_content = file_get_contents(" $jobId/ p12345.XML" 3. step 3: change the XML to Array $a= json_decode ( $XML_content, true) 4. step 4: print_r($a) first to check 5. step 5: echo $a["feature"]["modified_residue"][…][….]; 3.go to http://www.uniprot.org/uniprot/P12345.txt and find the features. 4.xml_parse_into_struct() can use compare with json_decodegfdgfdgg 5.Next step, use "html5 " to draw fancy picture. -
Week 1 (9/5~9/11)
9/2 1.altert of word use "onclick" function to restrict user to submit correct codes or words. 3.use "internal" to show slide of pictures 4.complete the inframe of information which come from different tracks
9/9 1.put MHC class II panel 2.put xml 3.PDB viewer 4.user interface 5.3D structure : First, select 130-139, and then select 10 , and then label 10. Second, use php to catch pdb protein and output the amino acid symbol. 6.feature table: Start, end, and features. (ok) 7.We need to translate these feature word to table or pictures.Week 2 (9/12~9/18)
Week 3 (9/19~9/25)
9/20 We use "canvas" to perform our protein information. 2.use "in_array($knownList, $each[1])" to decrease the FT information overlap
Week 4 (9/26~10/2)
9/30 1. increase the sample number (eg: notch, tp53, HA, ) 2.$infos=array ("helix", "domain","site"….)
Week 5 (10/3~10/10)