Difference between revisions of "Team:NTHU Taiwan/Collaborations"

 
(37 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{:Team:NTHU_Taiwan/MenuBar}}
 
<html>
 
<html>
  
Line 10: Line 11:
 
#bodyContent {background-color:#f6f6e3;}
 
#bodyContent {background-color:#f6f6e3;}
 
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 
/**************************************************************** MENU ***************************************************************/
 
/* Wrapper for the menu */
 
 
.igem_2017_menu_wrapper {
 
border-bottom: 3px solid #c2dac0;
 
background-color:#f6f6e3;
 
font-family:'Open Sans', sans-serif;
 
overflow: hidden;
 
}
 
 
.igem_2017_menu_wrapper a { 
 
float: left;
 
font-size: 1.2em;
 
color: #6c5070;
 
text-align: center;
 
padding: 25px 20px;
 
text-decoration: none;
 
}
 
 
.munu_img img{
 
position: fixed;
 
height: 9%;
 
}
 
 
/* this hides the scrollbar to keep view consistency */
 
.igem_2017_menu_wrappe::-webkit-scrollbar {
 
display: none;
 
}
 
 
.submenu_wrapper {
 
float: left;
 
  overflow: hidden;
 
}
 
 
.submenu_wrapper .menu_button {
 
letter-spacing: 1px;
 
text-transform: uppercase;
 
font-size: 1.2em;
 
border: none;
 
outline: none;
 
color: #6c5070;
 
padding: 25px 20px;
 
background-color: inherit;
 
}
 
 
.igem_2017_menu_wrapper a:hover, .submenu_wrapper:hover .menu_button {
 
color: #DF6A6A;
 
}
 
 
.submenu_button {
 
display: none;
 
position: absolute;
 
background-color: rgba(246, 246, 227, 0.7);
 
min-width: 160px;
 
z-index: 1;
 
}
 
 
.submenu_button a {
 
float: none;
 
color: #6c5070;
 
padding: 8px 16px;
 
text-decoration: none;
 
display: block;
 
text-align: left;
 
}
 
 
.submenu_button a:hover {
 
font-size: 1.3em;
 
 
}
 
 
.submenu_wrapper:hover .submenu_button {
 
display: block;
 
}
 
 
/*menu_wrapper left space*/
 
.igem_2017_menu_wrapper .menu_right_margin {
 
margin-left: 160px;
 
}
 
 
/*menu_wrapper right space*/
 
.igem_2017_menu_wrapper .menu_bottom_padding {
 
width: 100%;
 
height: 30px;
 
float:left;
 
}
 
 
/* styling for the menu button when it is the current page */
 
.current_page {
 
color:#df6a6a !important;
 
}
 
 
/* when the page size is bigger than 800px, this show/hide control is hidden by default */
 
.igem_2017_menu_wrapper #display_menu_control {
 
display:none;
 
text-align:center;
 
}
 
 
 
  
Line 117: Line 20:
 
display:block;
 
display:block;
 
float:left;
 
float:left;
font-family:'Open Sans', sans-serif;
+
font-family:'Helvetica', sans-serif;
 
background-color: #F6F6E3;
 
background-color: #F6F6E3;
 
}
 
}
Line 136: Line 39:
  
 
.igem_2017_content_wrapper h1, .igem_2017_content_wrapper h2 .igem_2017_content_wrapper h3, .igem_2017_content_wrapper h4, .igem_2017_content_wrapper h5, .igem_2017_content_wrapper h6 {
 
.igem_2017_content_wrapper h1, .igem_2017_content_wrapper h2 .igem_2017_content_wrapper h3, .igem_2017_content_wrapper h4, .igem_2017_content_wrapper h5, .igem_2017_content_wrapper h6 {
padding: 40px 0px 15px 0px;  
+
font-family: Helvetica;
 +
padding: 50px 0px 15px 0px;  
 
border-bottom: 0px;  
 
border-bottom: 0px;  
 
color: #2C2C2C;
 
color: #2C2C2C;
Line 143: Line 47:
 
}
 
}
  
#pdf {
+
 
 +
.igem_2017_content_wrapper .content {
 
width: 950px;
 
width: 950px;
height: 1200px;
 
 
margin: 2em auto;
 
margin: 2em auto;
padding-top: 20px;
 
 
}
 
}
  
#pdf object {
+
.igem_2017_content_wrapper .content p{
 +
font-family:Helvetica;
 +
color: #2C2C2C;
 +
font-size: 1.4em;
 +
line-height: 1.3em;
 +
padding: 0px 0px;
 +
text-align: justify;
 +
text-justify:inter-ideograph;
 +
}
 +
 
 +
.igem_2017_content_wrapper .content img{
 +
margin: auto;
 
display: block;
 
display: block;
border: solid 2px #2c2c2c;
+
float: center;
 +
padding: 20px 0px 30px 0px;
 
}
 
}
  
/***************************************************** RESPONSIVE STYLING ****************************************************/
+
.column .full_size {
 +
width: 100%;
 +
padding-top: 50px;
 +
}
  
/* IF THE SCREEN IS LESS THAN 1200PX */
+
/* class for a half width column */
@media only screen and (max-width: 1200px) {
+
.column .half_size {
 +
width: 50%;
 +
float: left;
 +
}
  
#content {width:100%; }
+
#pdf {
.igem_2017_menu_wrapper {width:100%; right:0;}
+
width: 950px;
.highlight {padding:10px 0px;}
+
height: 1000px;
.igem_2017_menu_wrapper #display_menu_control { display:none; }
+
margin: 2em auto;
#menu_content { display:block;}
+
padding-top: 20px;
.menu_button.direct_to_page {padding-left: 17px;}
+
+
 
}
 
}
  
/* IF THE SCREEN IS LESS THAN 800PX */
+
#pdf object {
@media only screen and (max-width: 800px) {
+
display: block;
 
+
border: solid 2px #2c2c2c;
.igem_2017_menu_wrapper { width:100%; height: 15%; position:relative; left:0%;}
+
.igem_2017_content_wrapper {width:100%; margin-left:0px;}
+
.column.half_size  {width:100%; }
+
.column.full_size img, .column.half_size img {  width: 100%; padding: 10px 0px;}
+
.highlight {padding:15px 5px;}
+
.igem_2017_menu_wrapper #display_menu_control { display:block; }
+
#menu_content { display:none;}
+
.igem_2017_menu_wrapper .menu_button .expand_collapse_icon { width: 5%; }
+
.menu_bottom_padding {display:none;}
+
.menu_button.direct_to_page { padding-left: 36px; }
+
 
}
 
}
 
 
</style>
 
</style>
  
Line 194: Line 102:
 
</head>
 
</head>
  
<!-- <div class="munu_img">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan">
 
<img src="https://static.igem.org/mediawiki/2017/1/1f/T--NTHU_Taiwan--HOME--logo.png">
 
</a>
 
</div> -->
 
  
<div class="igem_2017_menu_wrapper" >
 
<!-- this div is hidden by default and will only be displayed if the screen size is too small -->
 
<div class="menu_button" id="display_menu_control">
 
MENU 
 
</div>
 
 
 
<div id="menu_content">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan">
 
<div class="menu_button menu_right_margin">
 
HOME
 
</div>
 
</a>
 
 
<div class="submenu_wrapper">
 
<button class="menu_button">TEAM</button>
 
<div class="submenu_button">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Team">
 
<div id="Team_page">
 
Team
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Attributions">
 
<div  id="Attributions_page">
 
Attributions
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Collaborations">
 
<div  id="Collaborations_page">
 
Collaborations
 
</div>
 
</a>
 
</div>
 
</div>
 
 
<div class="submenu_wrapper">
 
<button class="menu_button">PROJECT</button>
 
<div class="submenu_button">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Description">
 
<div id="Description_page">
 
Description
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Design">
 
<div  id="Design_page">
 
Design
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Contribution">
 
<div  id="Contribution_page">
 
Contribution
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Model">
 
<div  id="Model_page">
 
Model
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Results">
 
<div  id="Results_page">
 
Results
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Demonstrate">
 
<div  id="Demonstrate_page">
 
Demonstrate
 
</div>
 
</a>
 
 
</div>
 
</div>
 
 
<div class="submenu_wrapper">
 
<button class="menu_button">WET LAB</button>
 
<div class="submenu_button">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Experiments">
 
<div  id="Experiments_page">
 
Experiments
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Protocol">
 
<div  id="Protocol_page">
 
Protocol
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Notebook">
 
<div  id="Notebook_page">
 
Notebook
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/InterLab">
 
<div  id="InterLab_page">
 
InterLab
 
</div>
 
</a>
 
</div>
 
</div>
 
 
<div class="submenu_wrapper">
 
<button class="menu_button">PARTS</button>
 
<div class="submenu_button">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Basic_Part">
 
<div  id="Basic_Part_page">
 
Basic Parts
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Composite_Part">
 
<div  id="Composite_Part_page">
 
Composite Parts
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Part_Collection">
 
<div  id="Part_Collection_page">
 
Part Collection
 
</div>
 
</a>
 
</div>
 
</div>
 
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Safety">
 
<div class="menu_button">
 
SAFETY
 
</div>
 
</a>
 
 
<div class="submenu_wrapper">
 
<button class="menu_button">HUMAN PRACTICES</button>
 
<div class="submenu_button">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/HP/Silver">
 
<div id="Silver_page">
 
Silver HP
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/HP/Gold_Integrated">
 
<div  id="Gold_Integrated_page">
 
Integrated and Gold
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Engagement">
 
<div  id="Engagement_page">
 
Public Engagement
 
</div>
 
</a>
 
</div>
 
</div>
 
 
<div class="submenu_wrapper">
 
<button class="menu_button">AWARDS</button>
 
<div class="submenu_button">
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Applied_Design">
 
<div id="Applied_Design_page">
 
Applied Design
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Entrepreneurship">
 
<div  id="Entrepreneurship_page">
 
Integrated Human Practices
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Hardware">
 
<div  id="Hardware_page">
 
Hardware
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Model">
 
<div  id="Model_page">
 
Model
 
</div>
 
</a>
 
<a href="https://2017.igem.org/Team:NTHU_Taiwan/Software">
 
<div  id="Software_page">
 
Software
 
</div>
 
</a>
 
<a href="#">
 
<div>
 
Criteria
 
</div>
 
</a>
 
</div>
 
</div>
 
 
<a href="https://igem.org/2017_Judging_Form?team=NTHU_Taiwan">
 
<div class="menu_button">
 
JUDGING FORM
 
</div>
 
</a>
 
 
</div>
 
 
</div>
 
  
  
 
<!-- start of content -->
 
<!-- start of content -->
 
<div class="igem_2017_content_wrapper">
 
<div class="igem_2017_content_wrapper">
<img width="25%" src="https://static.igem.org/mediawiki/2017/e/e2/T--NTHU_Taiwan--Notebook--Top.png">
+
        <img width="14%" src="https://static.igem.org/mediawiki/2017/a/ae/T--NTHU_Taiwan--Collaborations--title.png">
 
<div style="text-align: center">
 
<div style="text-align: center">
<h1 style="color:#DF6A6A">Collaborations
+
<h1 style="color:#DF6A6A">Team Collaborations
 
 
 
</h1>
 
</h1>
 
<hr width="20%" />
 
<hr width="20%" />
 
</div>
 
</div>
+
<div class="content">
 
+
<p><font=4>
<style>
+
<b>1. iGEM WLC: Wisconsin Lutheran College ( USA )</b>
p{
+
width:1000px;
+
font-size:20px;
+
text-align: justify;
+
text-justify:inter-ideograph;
+
line-height: 30px;
+
}
+
</style>
+
<body>
+
<center>
+
 
+
 
+
 
+
 
+
<br>
+
<h1 align=center>Team collaboration</h1>
+
 
+
<p align=center><font size=4>
+
<br>
+
 
+
<b>iGEM NTHU x iGEM WLC</b></font>
+
 
</p>
 
</p>
  
<p>
+
<p><font=4>
<font size=4>
+
-independent social investigation
<b>.Collaborate college :
+
</b>
+
<br>Wisconsin Lutheran College ( USA )
+
</font>
+
</p>
+
<br>
+
 
+
 
+
<p>
+
<font size=4>
+
<b> .Collaborate Division : </b>
+
<br>
+
1.Human Practice
+
 
<br>
 
<br>
2.Dry Lab
+
-detector integration: E.coli detecting
</font>
+
 
</p>
 
</p>
<br>
 
  
<p>
+
<p><font=4>
<font size=4>
+
<b>2. iGEM SECA NZ: The University of Auckland ( New Zealand )</b>
<b>  
+
.Collaborate item :  
+
</b>
+
<br>
+
1.Independent social investigation
+
<br>
+
2.Detector integration plan
+
</font>
+
 
</p>
 
</p>
<br>
 
  
<p>
+
<p><font=4>
<font size=4>
+
-independent social investigation
<b>
+
.Collaborate content : 
+
</b>
+
 
<br>
 
<br>
iGEM WLC aims to detect E.coli in water while our team’s goal is to detect the EDCs in water. Because we both focus on water quality, we’ve planned to achieve multiple detection integrations that have the ability to detect various pollution, like a Swiss Knife with many functions! However, it would be very struggling for them to build up a detecting equipment and a 3D model because of a lack of an engineering expert in their team. Fortunately, our team has suggested some software resources that may be useful for them, which have given them an orientation to demonstrate their brilliant work. For the 3D modelling, we had gone through the software composition and made our own model. Based on experience, we could also associate them to learn the original model construction method.                    </font></p>
+
-device blueprint offer: temperature sensing system
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/b/ba/T--NTHU_Taiwan--Collaborations--The_blueprint_of_our_IoT_system.png">
+
</p>
+
 
+
<p> <center><font size=2><blockquote><blockquote><blockquote>
+
[ Figure. 1.1-1 ] The blueprint of our IoT system. This branch chart includes every important element that we integrate with. The left ions are the sensor input ends where is the very place to integrate the E. coli sensor.</font>
+
</blockquote></blockquote></blockquote></p>
+
 
<br>
 
<br>
 
+
-photobioreactor offer
<p><font size=4>
+
NTHU iGEM team’s detection method for EDCs in water is a different aspect of addressing water contamination. In the collaboration between the Taiwan and American team, we were able to help each other survey American’s opinion and knowledge on EDCs as well as Taiwanese knowledge on bacteriophages and their opinion in regard to E. coli contamination. With their help on designing our 3D model system, we were able to use one of the software programs that they suggested and designed a 3D model of our water test kit. We improved each other’s project based on these collaboration experiences, and it was a pleasure to work with them!                    -Jeanie Yu</font></p>
+
<p>
+
<img width="50%"src="https://static.igem.org/mediawiki/2017/3/31/T--NTHU_Taiwan--collaborations--_3D_model_designed_by_iGEM_WLC.png">
+
 
</p>
 
</p>
  
<p><center><font size=2>
+
<p><font=4>
[ Figure. 1.1-2 ] 3D model designed by iGEM WLC with help and suggestion of iGEM NTHU.</font></p>
+
<b>3. iGEM NAU: Nanjing Agricultural University ( China )</b>
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/e/e4/T--NTHU_Taiwan--collaborations--Skype_meeting_with_WLC.png">
+
 
</p>
 
</p>
  
<p><center><font size=2>
+
<p><font=4>
[ Figure. 1.1-3 ] Skype meeting with WLC, we have discussed about how to built up a 3D model for their project.</font></p>
+
-troubleshooting: protocols
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/d/d0/T--NTHU_Taiwan--collaborations--_Second_time_meetup_with_iGEM_WLC.png">
+
</p>
+
 
+
<p><center><font size=2>
+
[ Figure. 1.1-4 ] Second time meetup with iGEM WLC when we talk about further integration plan.</font>
+
</p>
+
 
<br>
 
<br>
 +
-technique exchange: data collection, model designing, and hardware modeling
 
<br>
 
<br>
<p align=center><font size=4>
+
-Data exchange: Aquaculture questionnaire results
<b>
+
iGEM NTHU x iGEM SECA NZ
+
</b></font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>.Collaborate college : </b>
+
 
<br>
 
<br>
The University of Auckland ( New Zealand )
+
-detector integration: nitrate detector integration
</br></font>
+
 
</p>
 
</p>
<br>
 
  
<p><font size=4>
+
<p><font=4>
<b>.Collaborate Division : </b>
+
<b>4. iGEM NCKU: National Cheng Kung University ( Taiwan )</b>
<br>
+
1.Human Practice
+
<br>
+
2.Dry Lab
+
</font>
+
 
</p>
 
</p>
<br>
 
  
 
+
<p><font=4>
<p><font size=4>
+
-data exchange: Aquaculture questionnaire results
<b>.NTHU Collaborate Memo :   </b>
+
 
<br>
 
<br>
In the project of iGEM UoA, they transferred antifreeze protein gene to crops and combined the ability to regulate gene expression. They are aiming for the gene to only be expressed at high levels when the plant is at a cold enough temperature. We thought that our temperature sensing system would be ideal for them to set up the initial temperature database. Because the data would be collected immediately and accurately, they could derive continuous data from different areas and decide whether it is necessary to plant antifreeze crops in every farmland or valley. So far we have provided our design detail including hardware and software to iGEM UoA. We hope it would show a better value for both of us.</br></font>
+
-detector integration: nitrate detector intergration
 
</p>
 
</p>
<br>
 
  
 
+
<p><font=4>
<p><font size=4>
+
<b>5. iGEM TU Delft: Technische Universiteit Delft ( Netherlands )</b>
<b>. SECA NZ Collaborate Memo : </b>
+
<br>
+
This year we, SECA NZ, collaborated with NTHU iGEM in the exchange of international viewpoints and software. NTHU is developing an ingenious system to monitor and adjust the level of contaminants in irrigation drains using copper filters and a Watergates. The filter cleans the water, and a complex set of sensors monitors the output. If the level of contaminants exceeds the capacity of the filter, the water gate will reduce the flow to a manageable level. They are also investigating the water quality in aquaculture. New Zealand’s economy is largely based on agriculture and fishery industries, and so as a team we participated in a questionnaire to assess our opinions on aquaculture and water quality in the agriculture industry. This provided NTHU with both an international and consumer perspective on the issue.
+
<br>
+
Our own project focuses on the development of crop plants capable of surviving snap frosts. NTHU contributed to our project by graciously providing software and specifications on how to build a temperature sensor which would allow us to monitor the temperatures of cropping land.                    -Judith Glasson</font></p>
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/9/9f/T--NTHU_Taiwan--collaborations--_Meetup_with_iGEM_UoA.png">
+
 
</p>
 
</p>
  
<p><center><font size=2>
+
<p><font=4>
[ Figure. 1.3-1 ] Meetup with iGEM UoA. The best part of this meetup is to exchange protocol and troubleshooting. </font>
+
-shield protein offer: protecting protein polypeptide loop
 
</p>
 
</p>
 
<br>
 
<br>
 
<br>
 
<br>
<p align=center><font size=4>
+
<h1 style="color:#6c5070"><center>iGEM NTHU x iGEM WLC</center></h1><br><br><br>
<b>iGEM NTHU x iGEM NAU</b>
+
<h2>.Collaborate college :</h2>
</p>
+
<p>Wisconsin Lutheran College ( USA )</p>
 +
<h2>.Collaborate Division : </h2>
 +
<p>1.Human Practice</p>
 +
<p>2.Dry Lab</p>
 +
<h2>.Collaborate item : </h2>
 +
<p>1.Independent social investigation</p>
 +
<p>2.Detector integration plan </p>
 +
<h2>.Collaborate content :  </h2>
 +
<p><a href="https://2017.igem.org/Team:WLC-Milwaukee">iGEM WLC</a></td> aims to detect <I><I>E. coli</I></I> in water while our team’s goal is to detect the EDCs in water. Because we both focus on water quality, we’ve planned to achieve multiple detection integrations that have the ability to detect various pollution, like a Swiss Knife with many functions! However, it would be very struggling for them to build up a detecting equipment and a 3D model because of a lack of an engineering expert in their team. Fortunately, our team has suggested some software resources that may be useful for them, which have given them an orientation to demonstrate their brilliant work. For the 3D modelling, we had gone through the software composition and made our own model. Based on experience, we could also associate them to learn the original model construction method.</p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/b/ba/T--NTHU_Taiwan--Collaborations--The_blueprint_of_our_IoT_system.png">
 +
<p><center><font size=2><blockquote><blockquote><blockquote>[ Figure. 1.1-1 ] The blueprint of our IoT system. This branch chart includes every important element that we integrate with. The left ions are the sensor input ends where is the very place to integrate the <I>E. coli</I> sensor.</blockquote></blockquote></blockquote></font></center></p>
 +
<p><br><br>NTHU iGEM team’s detection method for EDCs in water is a different aspect of addressing water contamination. In the collaboration between the Taiwan and American team, we were able to help each other survey American’s opinion and knowledge on EDCs as well as Taiwanese knowledge on bacteriophages and their opinion in regard to <I>E. coli</I> contamination. With their help on designing our 3D model system, we were able to use one of the software programs that they suggested and designed a 3D model of our water test kit. We improved each other’s project based on these collaboration experiences, and it was a pleasure to work with them! </p>
 +
<img width="50%"src="https://static.igem.org/mediawiki/2017/3/31/T--NTHU_Taiwan--collaborations--_3D_model_designed_by_iGEM_WLC.png">
 +
<p><center><font size=2>[ Figure. 1.1-2 ] 3D model designed by iGEM WLC with help and suggestion of iGEM NTHU.</font></center></p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/e/e4/T--NTHU_Taiwan--collaborations--Skype_meeting_with_WLC.png">
 +
<p><center><font size=2>[ Figure. 1.1-3 ] Skype meeting with WLC, we have discussed how to build up a 3D model for their project.</font></center></p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/d/d0/T--NTHU_Taiwan--collaborations--_Second_time_meetup_with_iGEM_WLC.png">
 +
<p><center><font size=2>[ Figure. 1.1-4 ] Second-time meetup with iGEM WLC when we talk about further integration plan.</font></center></p>
  
<p><font size=4>
+
<h1 style="color:#6c5070"><center>iGEM NTHU x iGEM SECA NZ</center></h1><br><br><br>
<b>.Collaborate college :</b>  
+
<h2>.Collaborate college :</h2>
<br>
+
<p>The University of Auckland ( New Zealand )</p>
Nanjing Agricultural University ( China )</font>
+
<h2>.Collaborate Division : </h2>
</p>
+
<p>1.Human Practice </p>
<br>
+
<p>2.Dry Lab</p>
 +
<h2>.NTHU Collaborate Memo :</h2>
 +
<p>In the project of <a href="https://2017.igem.org/Team:SECA_NZ">iGEM UoA</a></td>, they transferred antifreeze protein gene to crops and combined the ability to regulate gene expression. They are aiming for the gene to only be expressed at high levels when the plant is at a cold enough temperature. We thought that our temperature sensing system would be ideal for them to set up the initial temperature database. Because the data would be collected immediately and accurately, they could derive continuous data from different areas and decide whether it is necessary to plant antifreeze crops in every farmland or valley. So far we have provided our design detail including hardware and software to iGEM UoA. We hope it would show a better value for both of us.</p>
 +
<h2>. SECA NZ Collaborate Memo :</h2>
 +
<p>This year we, SECA NZ, collaborated with NTHU iGEM in the exchange of international viewpoints and software. NTHU is developing an ingenious system to monitor and adjust the level of contaminants in irrigation drains using copper filters and a Watergates. The filter cleans the water, and a complex set of sensors monitors the output. If the level of contaminants exceeds the capacity of the filter, the water gate will reduce the flow to a manageable level. They are also investigating the water quality in aquaculture. New Zealand’s economy is largely based on agriculture and fishery industries, and so as a team, we participated in a questionnaire to assess our opinions on aquaculture and water quality in the agriculture industry. This provided NTHU with both an international and consumer perspective on the issue.</p>
 +
<p>Our own project focuses on the development of crop plants capable of surviving snap frosts. NTHU contributed to our project by graciously providing software and specifications on how to build a temperature sensor which would allow us to monitor the temperatures of cropping land.</p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/9/9f/T--NTHU_Taiwan--collaborations--_Meetup_with_iGEM_UoA.png">
 +
<p><center><font size=2>[ Figure. 1.3-1 ] Meetup with iGEM UoA. The best part of this meetup is to exchange protocol and troubleshooting. </font></center></p>
  
<p><font size=4>
+
<h1 style="color:#6c5070"><center>iGEM NTHU x iGEM NAU</center></h1><br><br><br>
<b>.Collaborate Division : </b>
+
<h2>.Collaborate college :</h2>
<br>
+
<p>Nanjing Agricultural University ( China )</p>
1.Wet Lab</font>
+
<h2>.Collaborate Division :</h2>
</p>
+
<p>1.Wet Lab</p>
<br>
+
<h2>.Collaborate item :</h2>
 +
<p>1.Data check</p>
 +
<p>2.Technique exchange </p>
 +
<p>3.Design discussion</p>
 +
<h2>.Collaborate content : </h2>
 +
<p>We had been collaborating with <a href="https://2017.igem.org/Team:NAU-CHINA">iGEM NAU</a></td> several times. Each time, we focused on sharing experiment schedules and techniques to solve problems in Wet Lab and Dry Lab. On account of their suggestion, we changed our protocols which made a great breakthrough on the performance of enzymes and solved the problem we made in gene transfer. In Dry Lab, we offered our experimental experience in hardware design. We not only gave them a deep look into measurement analysis and practical application, but also gave our suggestion on data collection method, model designing, and hardware modeling. On the other hand, we both exchange our plasmid for further check and study. Thanks to the profession in molecular biology from iGEM NAU and our outstanding talent in the device, we integrated both our advantages and made a significant improvement in both our project. </p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/2/2c/T--NTHU_Taiwan--collaborations--Meetup_with_iGEM_NAU.png">
 +
<p><center><font size=2>[ Figure. 1.3-1 ] Meetup with iGEM NAU. The best part of this meetup is to exchange protocol and troubleshooting.  </font></center></p>
  
<p><font size=4>
+
<h1 style="color:#6c5070"><center>iGEM NTHU x iGEM NCKU</center></h1><br><br><br>
<b>
+
<h2>.Collaborate college :</h2>
.Collaborate item : </b>
+
<p>National Cheng Kung University ( Taiwan )</p>
<br>
+
<h2>.Collaborate Division :</h2>
1.Data check
+
<p>1.Wet Lab</p>
<br>
+
<p>2.Dry lab</p>
2.Technique exchange
+
<h2>.Collaborate item : </h2>
<br>
+
<p>1.Data check</p>
3.Design discussion
+
<p>2.Troubleshooting</p>
</font>
+
<p>3.Technique exchange</p>
</p>
+
<p>4.Detector integration plan</p>
<br>
+
<h2>.NTHU Collaborate Memo : </h2>
 
+
<p>In the beginning, we were interested in the <a href="https://2016.igem.org/Team:NCKU_Tainan">2016 iGEM NCKU project</a></td> which is about the signal detection on urine samples by single frequency laser reflection. After discussing the whole progress and detail, it inspires us to engage in the UV excitation fluorescence to detect our sample. In addition to mutual inspection and troubleshooting with both projects, we also presented our detector design to iGEM NCKU and shared different experimental strategies. During the last meeting, we learned that we had an identical commercial value in aquaculture. As a result, we offered our investigation results of Aquaculture questionnaire to them to strengthen their data integrity by the information of market demand and consumer’s ideas. Furthermore, we looked for other teams who were also participating in pollution detection and trying to combine all the detectors in our demo-board. Nitrate detector from iGEM NCKU offers us a great opportunity to strengthen this idea. On the other hand, they also developed a special boat combining several extra functions other than nitrate sensor, like GPS, radio, motor etc., which is also an independent and integral equipment ready for adding other sensors like our IoT system. Thus, we are also happy to offer them our blueprint of EDCs sensor which might also offer them a chance to broaden their sensing target! </p>
<p><font size=4>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/c/c1/T--NTHU_Taiwan--collaborations--Cross_section_of_EDCs_sensor_based_on_fluorescence_.png">
<b>.Collaborate content : 
+
<p><center><font size=2>[ Figure. 1.4-1 ] Cross section of EDCs sensor based on fluorescence. </font></center></p>
</b>
+
<h2><br>. NCKU Collaborate Memo : </h2>
<br>
+
<p>In this September, we received the invitation to have a collaboration with NTHU. NTHU detected environmentally hazardous substances while our project is focusing on the sensing of nitrate concentration. They try to give a broader aspect. However, we try to give a more detail sensing system. Thus, we had a profound discussion of both teams’ projects. Moreover, we also shared our fluorescence idea of 2016 and 2017 with them.</p>
We had been collaborating with iGEM NAU several times. Each time, we focused on sharing experiment schedules and techniques to solve problems in Wet Lab and Dry Lab. On account of their suggestion, we changed our protocols which made a great breakthrough on the performance of enzymes and solved the problem we made in gene transfer. In Dry Lab, we offered our experimental experience in hardware design. We not only gave them a deep look into measurement analysis and practical application, but also gave our suggestion on data collection method, model designing, and hardware modeling. On the other hand, we both exchange our plasmid for further check and study. Thanks to the profession in molecular biology from iGEM NAU and our outstanding talent in the device, we integrated both our advantages and made a significant improvement in both our project.                 
+
<p>After mutual inspection and troubleshooting with both projects, we were enlightened to expand our sensing device to detect more substances like environmental hormone even heavy metal in the future, which would make our project more practical. Also, NTHU offered their investigation results of aquaculture questionnaire to us. These questionnaires strengthened our data integrity and made our project more fit to the market demand.</p>
</font></p>
+
<p>This collaboration combined both teams’ detecting projects. We exchanged our hardware design, principle, commercial value, strategies so can make both projects more compatible. In the following paragraph, we will briefly show the function and mechanism of our nitrate sensor.</p>
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/0/0f/T--NTHU_Taiwan--collaborations--_Structure_of_nitrate_sensor_based_on_fluorescence.png">
<img width="50%" src="https://static.igem.org/mediawiki/2017/2/2c/T--NTHU_Taiwan--collaborations--Meetup_with_iGEM_NAU.png">
+
<p><center><font size=2>[ Figure. 1.4-2 ] Structure of nitrate sensor based on fluorescence. </font></center></p>
</p>
+
<h2><br>. Sensor design</h2>
 
+
<p>We use a 450nm laser to excite our <I>E. coli.</I> Then, <I>E. coli.</I> will emit 510 nm green light and the green light will be received by the light sensor. By analyzing different fluorescence intensity. We will get concentration value of nitrate in the water..</p>
<p><center><font size=2>
+
<h2>. Mechanism</h2>
[ Figure. 1.3-1 ] Meetup with iGEM NAU. The best part of this meetup is to exchange protocol and troubleshooting.  </font>
+
<p>1. The water will enter the boat and flow through two solenoid valves.
</p>
+
<br>
<br>
+
2. With the specific controlling, we can gather quantitative water for nitrate sensing.
<br>
+
<br>
<p align=center><b>
+
3. The sample of water will react with our <I>E. coli</I> in a tube fixed in a light absorber.   
iGEM NTHU x iGEM NCKU</b>
+
<br>
</p>
+
4. The laser will excite the <I>E. coli</I>, and the <I>E. coli</I> will emit the fluorescence.
 
+
<br>
<p><font size=4>
+
5. The fluorescence will be received by a light sensor.
<b>.Collaborate college : </b>
+
<br>
<br>
+
6. The Arduino will process the fluorescence we collected and send the data to server.  
National Cheng Kung University ( Taiwan )
+
<br>
</font>
+
7. Our server will calculate fluorescence into the concentration of nitrate in the water.
</p>
+
</p>
 
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/e/e2/T--NTHU_Taiwan--collaborations--future.png">
<p>
+
<p><center><font size=2>[ Figure. 1.4-3 ] 3D model of nitrate sensor based on fluorescence. </font></center></p>
<font size=4>
+
<b>
+
.Collaborate Division :  
+
</b>
+
<br>
+
1.Wet Lab
+
<br>
+
2.Dry lab
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
.Collaborate item :  
+
</b>
+
<br>
+
1.Data check
+
<br>
+
2.Troubleshooting
+
<br>
+
3.Technique exchange
+
<br>
+
4.Detector integration plan
+
</p>
+
 
+
 
+
<p>
+
<font size=4>
+
<b>
+
.NTHU Collaborate Memo :  
+
</b>
+
<br>
+
In the beginning, we were interested in the 2016 iGEM NCKU project which is about the signal detection on urine samples by single frequency laser reflection. After discussing the whole progress and detail, it inspires us to engage in the UV excitation fluorescence to detect our sample. In addition to mutual inspection and troubleshooting with both projects, we also presented our detector design to iGEM NCKU and shared different experimental strategies. During the last meeting, we learned that we had an identical commercial value in aquaculture. As a result, we offered our investigation results of Aquaculture questionnaire to them to strengthen their data integrity by the information of market demand and consumer’s ideas. Furthermore, we looked for other teams who were also participating in pollution detection and trying to combine all the detectors in our demo-board. Nitrate detector from iGEM NCKU offers us a great opportunity to strengthen this idea. On the other hand, they also developed a special boat combining several extra functions other than nitrate sensor, like GPS, radio, motor etc., which is also an independent and integral equipment ready for adding other sensors like our IoT system. Thus, we are also happy to offer them our blueprint of EDCs sensor which might also offer them a chance to broaden their sensing target!                 </p>
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/c/c1/T--NTHU_Taiwan--collaborations--Cross_section_of_EDCs_sensor_based_on_fluorescence_.png">
+
</p>
+
 
+
<p><center><font size=2>
+
[ Figure. 1.4-1 ] Cross section of EDCs sensor based on fluorescence . </font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
. NCKU Collaborate Memo :  
+
</b>
+
<br>
+
In this September, we received the invitation to have a collaboration with NTHU. NTHU detected environmentally hazardous substances while our project is focusing on the sensing of nitrate concentration. They try to give a broader aspect. However, we try to give a more detail sensing system. Thus, we had a profound discussion of both teams’ projects. Moreover, we also shared our fluorescence idea of 2016 and 2017 with them.
+
<br>
+
After mutual inspection and troubleshooting with both projects, we were enlightened to expand our sensing device to detect more substances like environmental hormone even heavy metal in the future, which would make our project more practical. Also, NTHU offered their investigation results of aquaculture questionnaire to us. These questionnaires strengthened our data integrity and made our project more fit to the market demand.
+
<br>
+
This collaboration combined both teams’ detecting projects. We exchanged our hardware design, principle, commercial value, strategies so can make both projects more compatible. In the following paragraph, we will briefly show the function and mechanism of our nitrate sensor.                     </p>
+
 
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/0/0f/T--NTHU_Taiwan--collaborations--_Structure_of_nitrate_sensor_based_on_fluorescence.png">
+
</p>
+
 
+
<p><center><font size=2>
+
[ Figure. 1.4-2 ] Structure of nitrate sensor based on fluorescence. </font>
+
</p>
+
 
+
<p align=center>
+
<font size=4>
+
<b>
+
. Sensor design
+
</b></font>
+
</p>
+
 
+
<p><font size=4>
+
We use 450nm laser to excite our E. coli. Then, E. coli will emit 510 nm green light and the green light will be received by light sensor. By analyzing different fluorescence intensity. We will get concentration value of nitrate in the water.
+
</p>
+
 
+
<p align=center><font size=4>
+
<b>. Mechanism</b>
+
</font>
+
 
+
<p><font size=4>
+
1.   The water will enter the boat and flow through two solenoid valves.
+
<br>
+
2.   With the specific controlling, we can gather quantitative water for nitrate sensing.
+
<br>
+
3.   The sample of water will react with our E. coli in a tube fixed in a light absorber.   
+
<br>
+
4.   The laser will excite the E. coli, and the E. coli will emit the fluorescence.
+
<br>
+
5. The fluorescence will be received by light sensor.
+
<br>
+
6.   The Arduino will process the fluorescence we collected and send the data into server.
+
<br>
+
7.   Our server will calculate fluorescence into the concentration of nitrate in the water.
+
</p>
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/e/e2/T--NTHU_Taiwan--collaborations--future.png">
+
</p>
+
 
+
<p><center><font size=2>
+
[ Figure. 1.4-3 ] 3D model of nitrate sensor based on fluorescence. </font>
+
</p>
+
<br>
+
<br>
+
<p align=center><font size=4>
+
<b>iGEM NTHU x iGEM TU Delft</b></font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
.Collaborate college :
+
</b>
+
<br>
+
Technische Universiteit Delft ( Netherlands )
+
</font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
.Collaborate Division :
+
</b>
+
<br>
+
1.Wet Lab
+
<font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
.Collaborate item :
+
</b>
+
<br>
+
1.Data check
+
<br>
+
2.Troubleshooting
+
<br>
+
3.Enzyme improvement plan
+
</font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
.NTHU Collaborate Memo : 
+
</b>
+
<br>
+
iGEM TU Delft is the first team we had Skype meeting with. They provided a method they had designed in which enzymes would be produced, packaged and released in vesicles in combination with “Tardigrade intrinsically disordered proteins” (TDPs)  stabilize enzymes just with a simple drying step rendering a functional enzyme upon subsequent rehydration. However, after a closer look to the integration of TU Delft’s approach, we reported some of our concerns about it: vesicles, could affect our  degradation ability, as  the volume might not be great enough as to carry enough ER-alpha or GFP and the variability in a number of enzymes packaged in the vesicles could compromise the reliability of the system. Nonetheless,  we believe the method should still be tested in the future.
+
<br>
+
As time went by, we met some problems in the cloning and they helped us to inspect parts in detail and try to solve the problems. As a result, we changed the way of collaboration. Based on their advice, we transformed the plasmids of ER-INP and monobody into E.coli successfully(Figure.1.5-1) and we very much appreciated their help.</font>
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/a/a3/T--NTHU_Taiwan--collaborations--f2_.png">
+
</p>
+
 
+
<p><blockquote><blockquote><blockquote><center><font size=2>
+
[ Figure. 1.5-2 ]  1 : RFP ( mRFP F-primer and mRFP R-primer ); 2 : IPTG (promoter) + INP + RFP2 (ER F-primer and ER R-primer ); 3 : IPTG (promoter) + INP + RFP 1 (ER F-primer and ER R-primer ) ; 4 : IPTG (promoter) + ER with red spot  (ER F-primer and ER R-primer ); 5 : IPTG (promoter) + ER2  (ER F-primer and ER R-primer ); 6 : IPTG (promoter) + ER1  (ER F-primer and ER R-primer ); 7 : IPTG (promoter) + Monobody with red spot (Monobody F-primer and Monobody R-primer ); 8 : IPTG (promoter) + Monobody 2 (Monobody F-primer and Monobody R-primer ) ; 9 : IPTG (promoter) + Monobody 1 (Monobody F-primer and Monobody R-primer ); 10 : RFP ( VR primer and VF2 primer ); 11 : IPTG (promoter) + INP + RFP 2 ( VR primer and VF2 primer ); 12 : IPTG (promoter) + INP + RFP 1 ( VR primer and VF2 primer ); 13 : IPTG (promoter) + ER with red spot  ( VR primer and VF2 primer ); 14 : IPTG (promoter) + ER2  ( VR primer and VF2 primer ); 15 : IPTG (promoter) + ER1  ( VR primer and VF2 primer ); 16 : IPTG (promoter) + Monobody with red spot ( VR primer and VF2 primer ); 17 : IPTG (promoter) + Monobody 2 ( VR primer and VF2 primer ); 18 : IPTG (promoter) + Monobody 1 ( VR primer and VF2 primer )</font></center>
+
</blockquote></blockquote></blockquote></p>
+
 
+
<p>
+
<font size=4>
+
The collaboration with team TU Delft is a brilliant experiment, the Skype meeting and part correction not only helps our team’s lab work but also build a nice friendship between two teams. We appreciate the works and really look forward to meeting TU Delft in Boston!                    -Gustavo Chan</font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
<b>
+
.TU Delft Collaborate Memo :
+
</b>
+
<br>
+
After stumbling upon the description of our project, NTHU Taiwan initiated conversations with us via Facebook.
+
<br>
+
Their project also consisted in a biosensor device, on this case featuring a series of overexpressed receptors and enzymes capable of both sensing and degrading EDC’s (Endocrine Disruptor Chemicals) that could be used on-site with sewage waters. A series of Skype meetings followed, in which the usefulness of the inclusion of any of our accomplished BioBricks into their project was discussed. Initially, vesicles and TDPs were deemed potentially interesting for NTHU Taiwan.However, after a closer study of our vesicles BioBrick by Taiwan, they came back to us with a series of points such as the variability in the content and size of vesicles, that made us aware of the weaknesses of our approach for packaging Cas13a and TDPs in our vesicles. Such a feedback resulted important for TU Delft iGEM 2017, as it made us aware of more aspects that should be addressed and optimised in our vesicles prior to its integration in our project.
+
<br>
+
However, the collaboration took a different direction when Taiwan reported difficulties in the transformation involving their plasmids.</p>
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/7/70/T--NTHU_Taiwan--collaborations--f3_.png">
+
</p>
+
 
+
<p><center><font size=2>
+
[ Figure. 1.5-3 ] Snapgene overview of NTHU Taiwan’s construct.</font>
+
</p>
+
 
+
<p>
+
<font size=4>
+
TU Delft offered to revise their SnapGene files featuring their construct to discard a faulty design as the cause and shared a series of recommendations on how to make their design clearer in Snapgene and how to achieve transformations with higher yields.
+
<br>
+
Nonetheless, a series of recommendations were still made by TU Delft as to eliminate redundancies and make their design in SnapGene clearer and more organized.
+
<br>
+
Finally, NTHU communicated the accomplishment of their transformation after reordering their plasmids.
+
<br>
+
We wish all the best to our fellow iGEMers of NTHU Taiwan and look forward to meeting them at the Giant Jamboree!
+
</font>
+
<p>
+
<img width="50%" src="https://static.igem.org/mediawiki/2017/5/54/T--NTHU_Taiwan--collaborations--iGEM_TU_Delft.png">
+
</p>
+
 
+
</p><p><center><font size=2>
+
[ Figure. 2.5-5 ] iGEM TU Delft offers many suggestions for improving our project including to provide us one kind of protection protein to encapsulate our enzyme.</font>
+
</p>
+
 
+
</center>
+
</body>
+
 
+
 
+
+
</div>
+
 
+
<script type="Text/JavaScript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.6/jquery.min.js"></script>
+
 
+
<script>
+
 
+
// This is the jquery part of your template. 
+
// Try not modify any of this code too much since it makes your menu work.
+
 
+
$(document).ready(function() {
+
 
+
$("#HQ_page").attr('id','');
+
 
+
// call the functions that control the menu
+
menu_functionality();
+
hide_show_menu();
+
 
+
 
+
 
+
//this function controls the expand and collapse buttons of the menu and changes the +/- symbols
+
function menu_functionality() {
+
 
+
//when clicking on a "menu_button", it will change the "+/-" accordingly and it will show/hide the corresponding submenu
+
$(".menu_button").click(function(){
+
 
+
// add or remove the class "open" , this class holds the "-"
+
$(this).children().toggleClass("open");
+
// show or hide the submenu
+
$(this).next('.submenu_wrapper').fadeToggle(400);
+
});
+
 
+
// when the screen size is smaller than 800px, the display_menu_control button appears and will show/hide the whole menu
+
$("#display_menu_control").click(function(){
+
$('#menu_content').fadeToggle(400);
+
});
+
 
+
// call the current page highlight function
+
highlight_current_page();
+
}
+
 
+
 
+
// call the highlight current page function to show it on the menu with a different background color
+
function highlight_current_page() {
+
 
+
// select a page from the menu based on the id assigned to it and the current page name and add the class "current page" to make it change background color
+
$("#"+  wgPageName.substring(wgPageName.lastIndexOf("/")+1, wgPageName.length ) + "_page").addClass("current_page");
+
 
+
// now that the current_page class has been added to a menu item, make the submenu fade in
+
$(".current_page").parents(".submenu_wrapper").fadeIn(400);
+
// change the +/- symbol of the corresponding menu button
+
$(".current_page").parents(".submenu_wrapper").prev().children().toggleClass("open");
+
+
}
+
 
+
 
+
 
+
// allow button on the black menu bar to show/hide the side menu
+
function hide_show_menu() {
+
+
// in case you preview mode is selected, the menu is hidden for better visibility
+
if (window.location.href.indexOf("submit") >= 0) {
+
$(".igem_2017_menu_wrapper").hide();
+
}
+
 
+
// if the black menu bar has been loaded
+
  if (document.getElementById('bars_item')) {
+
 
+
// when the "bars_item" has been clicked
+
$("#bars_item").click(function() {
+
$("#sideMenu").hide();
+
 
+
// show/hide the menu wrapper
+
$(".igem_2017_menu_wrapper").fadeToggle("100");
+
});
+
  }
+
 
+
// because the black menu bars loads at a different time than the rest of the page, this function is set on a time out so it can run again in case it has not been loaded yet
+
else {
+
    setTimeout(hide_show_menu, 15);
+
}
+
}
+
 
+
 
+
});
+
 
+
 
+
</script>
+
  
 +
<h1 style="color:#6c5070"><center>GEM NTHU x iGEM TU Delft</center></h1><br><br><br>
 +
<h2>.Collaborate college :</h2>
 +
<p>Technische Universiteit Delft ( Netherlands )</p>
 +
<h2>.Collaborate Division :</h2>
 +
<p>1.Wet Lab</p>
 +
<h2>.Collaborate item : </h2>
 +
<p>1.Data check</p>
 +
<p>2.Troubleshooting</p>
 +
<p>3.Enzyme improvement plan</p>
 +
<h2>.NTHU Collaborate Memo :  </h2>
 +
<p><a href="https://2017.igem.org/Team:TUDelft">iGEM TU Delft</a></td> is the first team we had Skype meeting with. They provided a method they had designed in which enzymes would be produced, packaged and released in vesicles in combination with “Tardigrade intrinsically disordered proteins” (TDPs)  stabilize enzymes just with a simple drying step rendering a functional enzyme upon subsequent rehydration. However, after a closer look to the integration of TU Delft’s approach, we reported some of our concerns about it: vesicles, could affect our  degradation ability, as  the volume might not be great enough as to carry enough ER-alpha or GFP and the variability in a number of enzymes packaged in the vesicles could compromise the reliability of the system. Nonetheless,  we believe the method should still be tested in the future.<br>As time went by, we met some problems in the cloning and they helped us to inspect parts in detail and try to solve the problems. As a result, we changed the way of collaboration. Based on their advice, we transformed the plasmids of ER-INP and monobody into <I><I>E. coli</I></I> successfully(Figure.1.5-1) and we very much appreciated their help.</p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/a/a3/T--NTHU_Taiwan--collaborations--f2_.png">
 +
<p><blockquote><blockquote><blockquote><center><font size=2>[ Figure. 1.5-2 ]  1 : RFP ( mRFP F-primer and mRFP R-primer ); 2 : IPTG (promoter) + INP + RFP2 (ER F-primer and ER R-primer ); 3 : IPTG (promoter) + INP + RFP 1 (ER F-primer and ER R-primer ) ; 4 : IPTG (promoter) + ER with red spot  (ER F-primer and ER R-primer ); 5 : IPTG (promoter) + ER2  (ER F-primer and ER R-primer ); 6 : IPTG (promoter) + ER1  (ER F-primer and ER R-primer ); 7 : IPTG (promoter) + Monobody with red spot (Monobody F-primer and Monobody R-primer ); 8 : IPTG (promoter) + Monobody 2 (Monobody F-primer and Monobody R-primer ) ; 9 : IPTG (promoter) + Monobody 1 (Monobody F-primer and Monobody R-primer ); 10 : RFP ( VR primer and VF2 primer ); 11 : IPTG (promoter) + INP + RFP 2 ( VR primer and VF2 primer ); 12 : IPTG (promoter) + INP + RFP 1 ( VR primer and VF2 primer ); 13 : IPTG (promoter) + ER with red spot  ( VR primer and VF2 primer ); 14 : IPTG (promoter) + ER2  ( VR primer and VF2 primer ); 15 : IPTG (promoter) + ER1  ( VR primer and VF2 primer ); 16 : IPTG (promoter) + Monobody with red spot ( VR primer and VF2 primer ); 17 : IPTG (promoter) + Monobody 2 ( VR primer and VF2 primer ); 18 : IPTG (promoter) + Monobody 1 ( VR primer and VF2 primer )</font></center></blockquote></blockquote></blockquote></p>
 +
<p></p>
 +
<p><br>The collaboration with team TU Delft is a brilliant experiment, the Skype meeting and part correction not only helps our team’s lab work but also build a nice friendship between two teams. We appreciate the works and really look forward to meeting TU Delft in Boston!</p>
 +
<h2><br>.TU Delft Collaborate Memo :</h2>
 +
<p>After stumbling upon the description of our project, NTHU Taiwan initiated conversations with us via Facebook.
 +
Their project also consisted of a biosensor device, on this case featuring a series of overexpressed receptors and enzymes capable of both sensing and degrading EDC’s (Endocrine Disruptor Chemicals) that could be used on-site with sewage waters. A series of Skype meetings followed, in which the usefulness of the inclusion of any of our accomplished BioBricks into their project was discussed. Initially, vesicles and TDPs were deemed potentially interesting for NTHU Taiwan.However, after a closer study of our vesicles BioBrick by Taiwan, they came back to us with a series of points such as the variability in the content and size of vesicles, that made us aware of the weaknesses of our approach for packaging Cas13a and TDPs in our vesicles. Such a feedback resulted important for TU Delft iGEM 2017, as it made us aware of more aspects that should be addressed and optimised in our vesicles prior to its integration in our project.However, the collaboration took a different direction when Taiwan reported difficulties in the transformation involving their plasmids.</p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/7/70/T--NTHU_Taiwan--collaborations--f3_.png">
 +
<p><center><font size=2>[ Figure. 1.5-3 ] Snapgene overview of NTHU Taiwan’s construct.</font></center></p>
 +
<p><br><br>TU Delft offered to revise their SnapGene files featuring their construct to discard a faulty design as the cause and shared a series of recommendations on how to make their design clearer in Snapgene and how to achieve transformations with higher yields.<br><br>Nonetheless, a series of recommendations were still made by TU Delft as to eliminate redundancies and make their design in SnapGene clearer and more organized.<br><br>Finally, NTHU communicated the accomplishment of their transformation after reordering their plasmids.<br>We wish all the best to our fellow iGEMers of NTHU Taiwan and look forward to meeting them at the Giant Jamboree!</p>
 +
<img width="50%" src="https://static.igem.org/mediawiki/2017/5/54/T--NTHU_Taiwan--collaborations--iGEM_TU_Delft.png">
 +
</p><p><center><font size=2>[ Figure. 2.5-5 ] iGEM TU Delft offers many suggestions for improving our project including to provide us one kind of protection protein to encapsulate our enzyme.</font></center></p>
 +
<div id="pdf">
 +
<object data="https://static.igem.org/mediawiki/2017/b/b5/T--NTHU_Taiwan--Collaborations--pp1.pdf#toolbar=1&amp;navpanes=0&amp;scrollbar=1&amp;page=1&amp;view=FitH"
 +
type="application/pdf"
 +
width="100%"
 +
height="100%">
 +
</object>
 +
</div>
 +
<P><center>The hardware blueprint we offer to the collaborating teams.</p>
 +
</div>
 
</html>
 
</html>

Latest revision as of 13:20, 1 November 2017

Team Collaborations


1. iGEM WLC: Wisconsin Lutheran College ( USA )

-independent social investigation
-detector integration: E.coli detecting

2. iGEM SECA NZ: The University of Auckland ( New Zealand )

-independent social investigation
-device blueprint offer: temperature sensing system
-photobioreactor offer

3. iGEM NAU: Nanjing Agricultural University ( China )

-troubleshooting: protocols
-technique exchange: data collection, model designing, and hardware modeling
-Data exchange: Aquaculture questionnaire results
-detector integration: nitrate detector integration

4. iGEM NCKU: National Cheng Kung University ( Taiwan )

-data exchange: Aquaculture questionnaire results
-detector integration: nitrate detector intergration

5. iGEM TU Delft: Technische Universiteit Delft ( Netherlands )

-shield protein offer: protecting protein polypeptide loop



iGEM NTHU x iGEM WLC




.Collaborate college :

Wisconsin Lutheran College ( USA )

.Collaborate Division :

1.Human Practice

2.Dry Lab

.Collaborate item :

1.Independent social investigation

2.Detector integration plan

.Collaborate content :

iGEM WLC aims to detect E. coli in water while our team’s goal is to detect the EDCs in water. Because we both focus on water quality, we’ve planned to achieve multiple detection integrations that have the ability to detect various pollution, like a Swiss Knife with many functions! However, it would be very struggling for them to build up a detecting equipment and a 3D model because of a lack of an engineering expert in their team. Fortunately, our team has suggested some software resources that may be useful for them, which have given them an orientation to demonstrate their brilliant work. For the 3D modelling, we had gone through the software composition and made our own model. Based on experience, we could also associate them to learn the original model construction method.

[ Figure. 1.1-1 ] The blueprint of our IoT system. This branch chart includes every important element that we integrate with. The left ions are the sensor input ends where is the very place to integrate the E. coli sensor.



NTHU iGEM team’s detection method for EDCs in water is a different aspect of addressing water contamination. In the collaboration between the Taiwan and American team, we were able to help each other survey American’s opinion and knowledge on EDCs as well as Taiwanese knowledge on bacteriophages and their opinion in regard to E. coli contamination. With their help on designing our 3D model system, we were able to use one of the software programs that they suggested and designed a 3D model of our water test kit. We improved each other’s project based on these collaboration experiences, and it was a pleasure to work with them!

[ Figure. 1.1-2 ] 3D model designed by iGEM WLC with help and suggestion of iGEM NTHU.

[ Figure. 1.1-3 ] Skype meeting with WLC, we have discussed how to build up a 3D model for their project.

[ Figure. 1.1-4 ] Second-time meetup with iGEM WLC when we talk about further integration plan.

iGEM NTHU x iGEM SECA NZ




.Collaborate college :

The University of Auckland ( New Zealand )

.Collaborate Division :

1.Human Practice

2.Dry Lab

.NTHU Collaborate Memo :

In the project of iGEM UoA, they transferred antifreeze protein gene to crops and combined the ability to regulate gene expression. They are aiming for the gene to only be expressed at high levels when the plant is at a cold enough temperature. We thought that our temperature sensing system would be ideal for them to set up the initial temperature database. Because the data would be collected immediately and accurately, they could derive continuous data from different areas and decide whether it is necessary to plant antifreeze crops in every farmland or valley. So far we have provided our design detail including hardware and software to iGEM UoA. We hope it would show a better value for both of us.

. SECA NZ Collaborate Memo :

This year we, SECA NZ, collaborated with NTHU iGEM in the exchange of international viewpoints and software. NTHU is developing an ingenious system to monitor and adjust the level of contaminants in irrigation drains using copper filters and a Watergates. The filter cleans the water, and a complex set of sensors monitors the output. If the level of contaminants exceeds the capacity of the filter, the water gate will reduce the flow to a manageable level. They are also investigating the water quality in aquaculture. New Zealand’s economy is largely based on agriculture and fishery industries, and so as a team, we participated in a questionnaire to assess our opinions on aquaculture and water quality in the agriculture industry. This provided NTHU with both an international and consumer perspective on the issue.

Our own project focuses on the development of crop plants capable of surviving snap frosts. NTHU contributed to our project by graciously providing software and specifications on how to build a temperature sensor which would allow us to monitor the temperatures of cropping land.

[ Figure. 1.3-1 ] Meetup with iGEM UoA. The best part of this meetup is to exchange protocol and troubleshooting.

iGEM NTHU x iGEM NAU




.Collaborate college :

Nanjing Agricultural University ( China )

.Collaborate Division :

1.Wet Lab

.Collaborate item :

1.Data check

2.Technique exchange

3.Design discussion

.Collaborate content :

We had been collaborating with iGEM NAU several times. Each time, we focused on sharing experiment schedules and techniques to solve problems in Wet Lab and Dry Lab. On account of their suggestion, we changed our protocols which made a great breakthrough on the performance of enzymes and solved the problem we made in gene transfer. In Dry Lab, we offered our experimental experience in hardware design. We not only gave them a deep look into measurement analysis and practical application, but also gave our suggestion on data collection method, model designing, and hardware modeling. On the other hand, we both exchange our plasmid for further check and study. Thanks to the profession in molecular biology from iGEM NAU and our outstanding talent in the device, we integrated both our advantages and made a significant improvement in both our project.

[ Figure. 1.3-1 ] Meetup with iGEM NAU. The best part of this meetup is to exchange protocol and troubleshooting.

iGEM NTHU x iGEM NCKU




.Collaborate college :

National Cheng Kung University ( Taiwan )

.Collaborate Division :

1.Wet Lab

2.Dry lab

.Collaborate item :

1.Data check

2.Troubleshooting

3.Technique exchange

4.Detector integration plan

.NTHU Collaborate Memo :

In the beginning, we were interested in the 2016 iGEM NCKU project which is about the signal detection on urine samples by single frequency laser reflection. After discussing the whole progress and detail, it inspires us to engage in the UV excitation fluorescence to detect our sample. In addition to mutual inspection and troubleshooting with both projects, we also presented our detector design to iGEM NCKU and shared different experimental strategies. During the last meeting, we learned that we had an identical commercial value in aquaculture. As a result, we offered our investigation results of Aquaculture questionnaire to them to strengthen their data integrity by the information of market demand and consumer’s ideas. Furthermore, we looked for other teams who were also participating in pollution detection and trying to combine all the detectors in our demo-board. Nitrate detector from iGEM NCKU offers us a great opportunity to strengthen this idea. On the other hand, they also developed a special boat combining several extra functions other than nitrate sensor, like GPS, radio, motor etc., which is also an independent and integral equipment ready for adding other sensors like our IoT system. Thus, we are also happy to offer them our blueprint of EDCs sensor which might also offer them a chance to broaden their sensing target!

[ Figure. 1.4-1 ] Cross section of EDCs sensor based on fluorescence.


. NCKU Collaborate Memo :

In this September, we received the invitation to have a collaboration with NTHU. NTHU detected environmentally hazardous substances while our project is focusing on the sensing of nitrate concentration. They try to give a broader aspect. However, we try to give a more detail sensing system. Thus, we had a profound discussion of both teams’ projects. Moreover, we also shared our fluorescence idea of 2016 and 2017 with them.

After mutual inspection and troubleshooting with both projects, we were enlightened to expand our sensing device to detect more substances like environmental hormone even heavy metal in the future, which would make our project more practical. Also, NTHU offered their investigation results of aquaculture questionnaire to us. These questionnaires strengthened our data integrity and made our project more fit to the market demand.

This collaboration combined both teams’ detecting projects. We exchanged our hardware design, principle, commercial value, strategies so can make both projects more compatible. In the following paragraph, we will briefly show the function and mechanism of our nitrate sensor.

[ Figure. 1.4-2 ] Structure of nitrate sensor based on fluorescence.


. Sensor design

We use a 450nm laser to excite our E. coli. Then, E. coli. will emit 510 nm green light and the green light will be received by the light sensor. By analyzing different fluorescence intensity. We will get concentration value of nitrate in the water..

. Mechanism

1. The water will enter the boat and flow through two solenoid valves.
2. With the specific controlling, we can gather quantitative water for nitrate sensing.
3. The sample of water will react with our E. coli in a tube fixed in a light absorber.
4. The laser will excite the E. coli, and the E. coli will emit the fluorescence.
5. The fluorescence will be received by a light sensor.
6. The Arduino will process the fluorescence we collected and send the data to server.
7. Our server will calculate fluorescence into the concentration of nitrate in the water.

[ Figure. 1.4-3 ] 3D model of nitrate sensor based on fluorescence.

GEM NTHU x iGEM TU Delft




.Collaborate college :

Technische Universiteit Delft ( Netherlands )

.Collaborate Division :

1.Wet Lab

.Collaborate item :

1.Data check

2.Troubleshooting

3.Enzyme improvement plan

.NTHU Collaborate Memo :

iGEM TU Delft is the first team we had Skype meeting with. They provided a method they had designed in which enzymes would be produced, packaged and released in vesicles in combination with “Tardigrade intrinsically disordered proteins” (TDPs) stabilize enzymes just with a simple drying step rendering a functional enzyme upon subsequent rehydration. However, after a closer look to the integration of TU Delft’s approach, we reported some of our concerns about it: vesicles, could affect our degradation ability, as the volume might not be great enough as to carry enough ER-alpha or GFP and the variability in a number of enzymes packaged in the vesicles could compromise the reliability of the system. Nonetheless, we believe the method should still be tested in the future.
As time went by, we met some problems in the cloning and they helped us to inspect parts in detail and try to solve the problems. As a result, we changed the way of collaboration. Based on their advice, we transformed the plasmids of ER-INP and monobody into E. coli successfully(Figure.1.5-1) and we very much appreciated their help.

[ Figure. 1.5-2 ] 1 : RFP ( mRFP F-primer and mRFP R-primer ); 2 : IPTG (promoter) + INP + RFP2 (ER F-primer and ER R-primer ); 3 : IPTG (promoter) + INP + RFP 1 (ER F-primer and ER R-primer ) ; 4 : IPTG (promoter) + ER with red spot (ER F-primer and ER R-primer ); 5 : IPTG (promoter) + ER2 (ER F-primer and ER R-primer ); 6 : IPTG (promoter) + ER1 (ER F-primer and ER R-primer ); 7 : IPTG (promoter) + Monobody with red spot (Monobody F-primer and Monobody R-primer ); 8 : IPTG (promoter) + Monobody 2 (Monobody F-primer and Monobody R-primer ) ; 9 : IPTG (promoter) + Monobody 1 (Monobody F-primer and Monobody R-primer ); 10 : RFP ( VR primer and VF2 primer ); 11 : IPTG (promoter) + INP + RFP 2 ( VR primer and VF2 primer ); 12 : IPTG (promoter) + INP + RFP 1 ( VR primer and VF2 primer ); 13 : IPTG (promoter) + ER with red spot ( VR primer and VF2 primer ); 14 : IPTG (promoter) + ER2 ( VR primer and VF2 primer ); 15 : IPTG (promoter) + ER1 ( VR primer and VF2 primer ); 16 : IPTG (promoter) + Monobody with red spot ( VR primer and VF2 primer ); 17 : IPTG (promoter) + Monobody 2 ( VR primer and VF2 primer ); 18 : IPTG (promoter) + Monobody 1 ( VR primer and VF2 primer )


The collaboration with team TU Delft is a brilliant experiment, the Skype meeting and part correction not only helps our team’s lab work but also build a nice friendship between two teams. We appreciate the works and really look forward to meeting TU Delft in Boston!


.TU Delft Collaborate Memo :

After stumbling upon the description of our project, NTHU Taiwan initiated conversations with us via Facebook. Their project also consisted of a biosensor device, on this case featuring a series of overexpressed receptors and enzymes capable of both sensing and degrading EDC’s (Endocrine Disruptor Chemicals) that could be used on-site with sewage waters. A series of Skype meetings followed, in which the usefulness of the inclusion of any of our accomplished BioBricks into their project was discussed. Initially, vesicles and TDPs were deemed potentially interesting for NTHU Taiwan.However, after a closer study of our vesicles BioBrick by Taiwan, they came back to us with a series of points such as the variability in the content and size of vesicles, that made us aware of the weaknesses of our approach for packaging Cas13a and TDPs in our vesicles. Such a feedback resulted important for TU Delft iGEM 2017, as it made us aware of more aspects that should be addressed and optimised in our vesicles prior to its integration in our project.However, the collaboration took a different direction when Taiwan reported difficulties in the transformation involving their plasmids.

[ Figure. 1.5-3 ] Snapgene overview of NTHU Taiwan’s construct.



TU Delft offered to revise their SnapGene files featuring their construct to discard a faulty design as the cause and shared a series of recommendations on how to make their design clearer in Snapgene and how to achieve transformations with higher yields.

Nonetheless, a series of recommendations were still made by TU Delft as to eliminate redundancies and make their design in SnapGene clearer and more organized.

Finally, NTHU communicated the accomplishment of their transformation after reordering their plasmids.
We wish all the best to our fellow iGEMers of NTHU Taiwan and look forward to meeting them at the Giant Jamboree!

[ Figure. 2.5-5 ] iGEM TU Delft offers many suggestions for improving our project including to provide us one kind of protection protein to encapsulate our enzyme.

The hardware blueprint we offer to the collaborating teams.