Difference between revisions of "Team:Madrid-OLM/prueba"
| (43 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
{{Madrid-OLM/1}} | {{Madrid-OLM/1}} | ||
<html lang="en"> | <html lang="en"> | ||
| Line 20: | Line 19: | ||
</style> | </style> | ||
| − | + | <body class=" "> | |
| + | |||
<div class="main-container"> | <div class="main-container"> | ||
| − | + | <section class="imageblock switchable feature-large space--sm bg--secondary"> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<div class="container"> | <div class="container"> | ||
| − | <div class="row"> | + | <div class="row justify-content-around"> |
| − | + | <div class="col-sm-4"> | |
| − | < | + | <h2>Embracing our aptamers</h2> |
<p class="lead"> | <p class="lead"> | ||
| − | + | The hardware is the structure that embraces the aptamer to take it to its maximum potentiality. Without an aptamer, our hardware can barely measure anything, and without the hardware, the aptamer is just another molecule. | |
| − | + | <br><br>The structure of the device has evolved in parallel to the role that the aptamer assumes in the hardware. A good example is how the first prototype has mutated into the final version. | |
</p> | </p> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
</div> | </div> | ||
| + | |||
| + | |||
| + | <div class="col-sm-4"> | ||
| + | <h2>More than a piece of hardware</h2> | ||
| + | <p class="lead"> | ||
| + | Depending on the case, a piece of hardware could be only a tool or it could be a bit more than that. When we were brainstorming about how to face the issues related to traditional IoT devices, we concluded that the role of our hardware should walk alongside the aptamer development and integration. | ||
| + | </p> | ||
| + | </div> | ||
| + | |||
</div> | </div> | ||
<!--end of row--> | <!--end of row--> | ||
| Line 55: | Line 47: | ||
<!--end of container--> | <!--end of container--> | ||
</section> | </section> | ||
| − | <section class="imageblock switchable feature-large | + | <section class="imageblock switchable switchable--switch feature-large bg--dark space--sm"> |
<div class="imageblock__content col-lg-6 col-md-4 pos-right"> | <div class="imageblock__content col-lg-6 col-md-4 pos-right"> | ||
<div class="background-image-holder"> | <div class="background-image-holder"> | ||
| − | <img alt="image" src="https://static.igem.org/mediawiki/2018/8/ | + | <img alt="image" src="https://static.igem.org/mediawiki/2018/8/84/T--Madrid-OLM--proto.png" /> |
</div> | </div> | ||
</div> | </div> | ||
<div class="container"> | <div class="container"> | ||
<div class="row"> | <div class="row"> | ||
| − | <div class="col-lg-5 col-md-7"> | + | <div class="col-lg-5 col-md-7 mt--2"> |
| − | < | + | <h1>Our first prototype</h1> |
<p class="lead"> | <p class="lead"> | ||
| − | + | n our first prototype, the aptamer was just a filter, such that it only trapped the target protein. The role of the hardware was automating the extraction of the target protein from the DNA filter and quantifying the total concentration of the remaining protein at 280nm absorbance, once the pollutants were wiped away. | |
</p> | </p> | ||
| + | <a class="btn" href="https://2018.igem.org/Team:Madrid-OLM/FirstPrototype"> | ||
| + | <span class="btn__text">First prototype</span> | ||
| + | </a> | ||
| + | <!--end of modal instance--> | ||
</div> | </div> | ||
</div> | </div> | ||
| Line 74: | Line 70: | ||
<!--end of container--> | <!--end of container--> | ||
</section> | </section> | ||
| − | <section class=" | + | <section class="imageblock switchable feature-large space--sm bg--secondary"> |
| − | <div class=" | + | |
| − | <div class=" | + | <div class="imageblock__content col-lg-6 col-md-4 pos-right"> |
| − | < | + | <div class="background-image-holder"> |
| − | + | <img alt="image" src="https://static.igem.org/mediawiki/2018/5/56/T--Madrid-OLM--final.png" /> | |
| − | + | ||
| − | + | ||
| − | + | ||
</div> | </div> | ||
| − | |||
</div> | </div> | ||
| − | |||
| − | |||
| − | |||
<div class="container"> | <div class="container"> | ||
| − | <div class="row | + | <div class="row"> |
| − | <div class="col- | + | <div class="col-lg-5 col-md-7"> |
| − | <h2> | + | <h2>The final device</h2> |
<p class="lead"> | <p class="lead"> | ||
| − | + | But the concept of “aptamer as a filter” did not last long, as it was not sensitive enough to our purposes. And it evolved towards a different function. | |
| − | + | ||
| + | <br><br>The second prototype demanded a different role for the aptamer. In this new mission, the aptamer was expected to be part of the sensor. It had to adhere to an electrode and obstruct the electrons flow. So the microfluidic chip needed to be adapted to this demand. And thus, the structure of the hardware changed. | ||
| + | |||
| + | <br><br>In this final version, the device is responsible for pumping a variety of solutions and samples through the chip towards the bound aptamer, collecting the resulting data from the electrode.</p> | ||
| + | <a class="btn" href="https://2018.igem.org/Team:Madrid-OLM/FinalPrototype"> | ||
| + | <span class="btn__text">Final Device</span> | ||
| + | </a> | ||
</div> | </div> | ||
</div> | </div> | ||
| Line 101: | Line 96: | ||
<!--end of container--> | <!--end of container--> | ||
</section> | </section> | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<!--end of container--> | <!--end of container--> | ||
| − | </ | + | </footer> |
| − | + | <section class="imageblock switchable switchable--switch feature-large bg--dark space--sm"> | |
| − | <div class=" | + | <div class="imageblock__content col-lg-6 col-md-4 pos-right"> |
| − | + | <div class="background-image-holder"> | |
| − | + | <img alt="image" src="https://static.igem.org/mediawiki/2018/8/8a/T--Madrid-OLM--Device--000.png" /> | |
| − | + | ||
| − | < | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
</div> | </div> | ||
| − | |||
</div> | </div> | ||
| − | |||
| − | |||
| − | |||
<div class="container"> | <div class="container"> | ||
<div class="row"> | <div class="row"> | ||
| − | <div class="col-md- | + | <div class="col-lg-5 col-md-7 mt--2"> |
| − | + | <h1>The IoT ecosystem</h1> | |
| − | + | <p class="lead"> | |
| − | < | + | As we required an IoT device, it had to satisfy other functionalities. The key one is to upload the acquired data to a cloud server. |
| − | + | ||
| − | < | + | <br><br>We have also developed an IoT ecosystem that surrounds the device. We have implemented an iOS app to enable the clients to visualize data on a heat map. We have set up a firebase cloud server to gather the data from our sensors, and a PC application to control directly the final device and test our different protocols </p> |
| − | + | <a class="btn" href="https://2018.igem.org/Team:Madrid-OLM/FirstPrototype"> | |
| − | + | <span class="btn__text">First prototype</span> | |
| − | + | </a> | |
| − | + | <!--end of modal instance--> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | < | + | |
</div> | </div> | ||
</div> | </div> | ||
| Line 225: | Line 123: | ||
<!--end of container--> | <!--end of container--> | ||
</section> | </section> | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | </div> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
</body> | </body> | ||
</html> | </html> | ||
{{Madrid-OLM/footer}} | {{Madrid-OLM/footer}} | ||
Latest revision as of 03:43, 18 October 2018
Embracing our aptamers
The hardware is the structure that embraces the aptamer to take it to its maximum potentiality. Without an aptamer, our hardware can barely measure anything, and without the hardware, the aptamer is just another molecule.
The structure of the device has evolved in parallel to the role that the aptamer assumes in the hardware. A good example is how the first prototype has mutated into the final version.
More than a piece of hardware
Depending on the case, a piece of hardware could be only a tool or it could be a bit more than that. When we were brainstorming about how to face the issues related to traditional IoT devices, we concluded that the role of our hardware should walk alongside the aptamer development and integration.
Our first prototype
n our first prototype, the aptamer was just a filter, such that it only trapped the target protein. The role of the hardware was automating the extraction of the target protein from the DNA filter and quantifying the total concentration of the remaining protein at 280nm absorbance, once the pollutants were wiped away.
First prototype
The final device
But the concept of “aptamer as a filter” did not last long, as it was not sensitive enough to our purposes. And it evolved towards a different function.
The second prototype demanded a different role for the aptamer. In this new mission, the aptamer was expected to be part of the sensor. It had to adhere to an electrode and obstruct the electrons flow. So the microfluidic chip needed to be adapted to this demand. And thus, the structure of the hardware changed.
In this final version, the device is responsible for pumping a variety of solutions and samples through the chip towards the bound aptamer, collecting the resulting data from the electrode.
The IoT ecosystem
As we required an IoT device, it had to satisfy other functionalities. The key one is to upload the acquired data to a cloud server.
We have also developed an IoT ecosystem that surrounds the device. We have implemented an iOS app to enable the clients to visualize data on a heat map. We have set up a firebase cloud server to gather the data from our sensors, and a PC application to control directly the final device and test our different protocols