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

Line 1: Line 1:
 
{{:Team:NTHU_Taiwan/MenuBar}}
 
{{:Team:NTHU_Taiwan/MenuBar}}
 
<html>
 
<html>
{{:Team:Oxford/Templates/Navi}}
 
  
 +
<style>
 +
/***************************************************** DEFAULT SETTINGS  ****************************************************/
 +
/* Clear the default wiki settings */
 +
#home_logo, #sideMenu { display:none; }
 +
#sideMenu, #top_title, .patrollink  {display:none;}
 +
#content { width:100%; padding:0px;  margin-top:-7px; margin-left:0px;overflow-x: hidden;}
 +
body {background-color:#f6f6e3;}
 +
#bodyContent {background-color:#f6f6e3;}
 +
#bodyContent h1, #bodyContent h2, #bodyContent h3, #bodyContent h4, #bodyContent h5 { margin-bottom: 0px; }
 +
 +
 +
/***************************************************** CONTENT OF THE PAGE ****************************************************/
 +
/* Wrapper for the content */
 +
.igem_2017_content_wrapper {
 +
width: 100%;
 +
margin: 2%;
 +
display:block;
 +
float:left;
 +
font-family:'Open Sans', sans-serif;
 +
background-color: #F6F6E3;
 +
}
 +
 +
.igem_2017_content_wrapper hr{
 +
margin: auto;
 +
height: 3px;
 +
border: none;
 +
background-color: #DF6A6A;
 +
}
 +
 +
.igem_2017_content_wrapper img{
 +
margin: auto;
 +
display: block;
 +
padding: 50px 0px 0px 0px;
 +
float: center;
 +
}
 +
 +
.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: 50px 0px 15px 0px;
 +
border-bottom: 0px;
 +
color: #2C2C2C;
 +
letter-spacing: 1px;
 +
 +
}
 +
 +
.igem_2017_content_wrapper .content {
 +
width: 950px;
 +
margin: 2em auto;
 +
}
 +
 +
.igem_2017_content_wrapper .content p{
 +
color: #2C2C2C;
 +
font-size: 1.4em;
 +
line-height: 1.3em;
 +
padding: 0px 0px;
 +
}
 +
 +
.igem_2017_content_wrapper .content img{
 +
margin: auto;
 +
display: block;
 +
float: center;
 +
padding: 20px 0px 30px 0px;
 +
}
 +
 +
.column .full_size {
 +
width: 100%;
 +
padding-top: 50px;
 +
}
 +
 +
/* class for a half width column */
 +
.column .half_size {
 +
width: 50%;
 +
float: left;
 +
}
 +
 +
#pdf {
 +
width: 950px;
 +
height: 1200px;
 +
margin: 2em auto;
 +
padding-top: 20px;
 +
}
 +
 +
#pdf object {
 +
display: block;
 +
border: solid 2px #2c2c2c;
 +
}
 +
</style>
 +
 +
 +
<head>
 +
 +
<!-- This tells the browser that your page is responsive -->
 +
<meta name="viewport" content="width=device-width, initial-scale=1">
 +
 +
</head>
 +
 +
 +
 +
 +
<!-- start of content -->
 +
<div class="igem_2017_content_wrapper">
 +
<div style="text-align: center">
 +
<h1 style="color:#DF6A6A">Team Collaborations
 +
 +
</h1>
 +
<hr width="20%" />
 +
</div>
 +
<div class="content">
 +
<h1 style="color:#6c5070">iGEM NTHU x iGEM WLC</h1>
 +
<h2>.Collaborate college :</h2>
 +
<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>iGEM WLC 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.</font></center></p>
 +
</div>
 
</html>
 
</html>

Revision as of 09:20, 31 October 2017

Team Collaborations


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.