|
|
| Line 3: |
Line 3: |
| | <div id="gif-title" class="text-project"> | | <div id="gif-title" class="text-project"> |
| | <img src="https://static.igem.org/mediawiki/2018/a/aa/T--TecCEM--Cells.gif" alt="Cell Gif"> | | <img src="https://static.igem.org/mediawiki/2018/a/aa/T--TecCEM--Cells.gif" alt="Cell Gif"> |
| − | <h1>Software</h1> | + | <h1>Measurement</h1> |
| | </div> | | </div> |
| | <div class="wrapper"> | | <div class="wrapper"> |
| Line 17: |
Line 17: |
| | <li class="active"> | | <li class="active"> |
| | <a data-target="#introduction">Introduction</a> | | <a data-target="#introduction">Introduction</a> |
| − | </li>
| |
| − | <li class="active">
| |
| − | <a data-target="#activity">Activity Log</a>
| |
| | </li> | | </li> |
| | <li class="active"> | | <li class="active"> |
| Line 30: |
Line 27: |
| | <div class="row" id="introduction"> | | <div class="row" id="introduction"> |
| | <div class="col"> | | <div class="col"> |
| − | <p class="lead">For this year’s software, we developed a web application with three main | + | <p class="lead">One of the crucial parts in cell culture is the determination of confluency, but with the current techniques this process is slow and imprecise. That is why we developed a software using machine learning to analyze microscope images tha throw the percentage of cell confluence. The importance of having a correctly cell confluency measurement is to avoid cell apoptosis because of the reduced space in the cases of a 80 to 100% of confluency. So, having a software that can give you a more precise result of the cell proliferation that is important to maintain your cell culture in good conditions without contamination and an excessive proliferation in it that would induce cell dead. The manipulation of this software is easy to use for everybody because is carefully realized and automatized so its implementation has a friendly interface. This software represents a revolution in the way cell culture is managed</p> |
| − | functionalities, a cell counter, a BioBrick builder and an activity log for our hardware. Up
| + | |
| − | next, we will explain each one of them!</p>
| + | |
| − | <p>You can download our suite of software from the following link <a href="https://static.igem.org/mediawiki/2018/e/eb/T--TecCEM--Software.zip" download>Download</a></p>
| + | |
| − | <p>Alternatively you could follow our latest improvements in the github page <a class="text-project" href="https://github.com/iGEM-TEC-CEM/Software-iGEM">Github</a></p> | + | |
| | </div> | | </div> |
| | </div> | | </div> |
| − | <div class="row" id="activity">
| |
| − | <div class="col">
| |
| − | <h1>Activity Log</h1>
| |
| − | <p>The activity log is a really simple piece of software, nevertheless very important. This part of
| |
| − | the web application is where the software and the hardware converge into a single solution. The
| |
| − | user interface is really basic and minimalistic and shows the data obtained from the hardware
| |
| − | as a table and as a graph.</p>
| |
| − | <p>To distinguish between all the different projects from different people we use a login.
| |
| − | First-time users need to register into the platform which will create an account for them. Once
| |
| − | this is done, the person can register different projects. </p>
| |
| − | <figure class="figure text-center">
| |
| − | <img class="figure-img img-fluid rounded" src="https://static.igem.org/mediawiki/2018/b/ba/T--TecCEM---sof1.png"
| |
| − | alt="signup activity-log">
| |
| − | <figcaption class="figure-caption text-xs-right">Figure 1. Sign up </figcaption>
| |
| − | </figure>
| |
| − | <p>The project signup is a bit more complex because we need a way to link the automation system
| |
| − | (hardware) with the platform. First of all, it is necessary to have BoB, its automation system
| |
| − | and a computer with Arduino installed on it. </p>
| |
| − | <p>Once we have this two things ready, open the arduino code called “auto.ino” - you can get the
| |
| − | code from this repository <a class="text-project" href="https://github.com/SantiagoMille/BoB_Automation">Github
| |
| − | Link</a>
| |
| − | - and set up your
| |
| − | local wifi network as shown in <strong>Figure 2.</strong>:</p>
| |
| − | <figure class="figure text-center w-100">
| |
| − | <img class="figure-img img-fluid rounded" src="https://static.igem.org/mediawiki/2018/2/29/T--TecCEM---sof2.png"
| |
| − | alt="configuration activity-log">
| |
| − | <figcaption class="figure-caption text-xs-right">Figure 2. Code configuration. </figcaption>
| |
| − | </figure>
| |
| − | <p>Then, we need to connect our NodeMCU board to the computer, load the program and open the serial
| |
| − | monitor. In this monitor a token will be displayed, we need to copy and paste it in the Project
| |
| − | Code input as shown in <strong>Figure 3</strong></p>
| |
| − | <figure class="figure text-center w-100">
| |
| − | <img class="figure-img img-fluid rounded" src="https://static.igem.org/mediawiki/2018/d/d5/T--TecCEM---sof3.png"
| |
| − | alt="Adding Project activity-log">
| |
| − | <figcaption class="figure-caption text-xs-right">Figure 3. Adding a new project. </figcaption>
| |
| − | </figure>
| |
| − | <p>Once we have an account and a project set, we can visualize the data sensed from Bob. The data
| |
| − | can be filtered depending on the date selected. The default setup shows all the data obtained
| |
| − | throughout the projects time. </p>
| |
| − |
| |
| − | <div class="row">
| |
| − | <div class="col">
| |
| − | <figure class="figure text-center w-100">
| |
| − | <img class="figure-img img-fluid rounded" src="https://static.igem.org/mediawiki/2018/c/c9/T--TecCEM--Activity-Log1.png"
| |
| − | alt="Default data activity-log">
| |
| − | <figcaption class="figure-caption text-xs-right">Figure 4. Default data config. vs.
| |
| − | Data filtered by month
| |
| − | </figcaption>
| |
| − | </figure>
| |
| − | </div>
| |
| − | </div>
| |
| | | | |
| − | <p>The advantages of this application are the following:
| |
| − | </p>
| |
| − | <ul>
| |
| − | <li>It keeps track and displays the most relevant data from the experiments in form of a plot.
| |
| − | For example, it could be possible to watch how is it that the color of the medium is
| |
| − | changing and after some time relate this plots to the cell proliferation or the time it
| |
| − | takes for some cell colonies to grow</li>
| |
| − | <li>It can be accessed from anywhere in the world</li>
| |
| − | </ul>
| |
| − | <br>
| |
| − | <p>
| |
| − |
| |
| − | </p>
| |
| − | </div>
| |
| − |
| |
| − | </div>
| |
| | <div class="row" id="cellcount"> | | <div class="row" id="cellcount"> |
| | <div class="col"> | | <div class="col"> |
| Line 197: |
Line 124: |
| | way. This will optimize time, effort and resources letting the scientists do more science and | | way. This will optimize time, effort and resources letting the scientists do more science and |
| | less counting.</p> | | less counting.</p> |
| − | </div>
| |
| − | </div>
| |
| − | <div class="row" id="bbBuilder">
| |
| − | <div class="col">
| |
| − | <h1>BioBrick Builder</h1>
| |
| − | <p>Biobrick building is an extremely important, but also very prone to errors process. One of the most tedious tasks of creating a biobrick is searching each on of the basic parts through the library, comparing its characteristics and trying to find the appropriate one for the wanted outcome. We noticed that most of the times we filter by the top-level needs such as the organism and main standards, then select a set of characteristics that we consider in the filtering of the part and finally we choose the most used and most reliable parts in the iGEM library. Nevertheless, even after the desired biobrick is found, we proceed to a mostly handmade process that consists of copy-pasting the sequence, adding the prefix and suffix and expecting by all cost to avoid human mistake. On top of this, to design a standardized biobrick, we need to check for several characteristics based on our selected RFC, this is a simple task with a small sequence, but the sequence could get more and more complicated and we could forget to design a sequence that complies for the RFC.
| |
| − | </p>
| |
| − |
| |
| − | <h5>Solution</h5>
| |
| − | <br>
| |
| − | <p>We designed a software to facilitate the creation of biobricks, the main functionality is to provide a tool to search for the desired parts such as promoters, rbs and terminators. Once done that, we collect the selected information and produce a final biobrick with prefixes and suffixes integrated, this allows you to copy and paste to a more complex tool such as Snapgene and optimize the sequence or confirm the biobrick in order to send to iGEM for confirmation.
| |
| − | Our software include a scrapper that collects the basic parts of the igem library and adds relevant information for you to observe and analyze. Afterwards, it includes sections for each of the basic parts of a composite biobrick, these being the promoters, rbs and terminators. In these sections you can search by name, filter by type, standard, chassis, and you can read other information depending on the basic part; you can get the sequence as well. At the end a set of basic parts, the constructed biobricks with the scars, the prefixes, and the suffixes will be obtained.</p>
| |
| − | <br>
| |
| − | <p>Our goal with this piece software is to introduce the automation of things into the biotech world by merely simplifying one small area of the biobrick construction. We are aware biobrick building requires more than a block builder type software, but with the continuous improvement, we believe we could create an open source application to facilitate this and many more tasks.</p>
| |
| − | <br>
| |
| − | <h5>Design</h5>
| |
| − | <br>
| |
| − | <p>Our software consists of a simple interface that firstly asks for the organism you will work with and the standard you want to comply to. We currently only support RFC 10 integration, but adding more standards is a trivial task we could expect to do the following days after the Jamboree.
| |
| − | After the main selection screen we enter the promoter selection screen. The parts were obtained with the help of a scrapper which crolls all over the iGEM library, we selected a few characteristics to quickly filter the promoters such as the short description, the regulation, the sample status and the organism we want to develop the biobrick in. This quickly reduces the library by a fraction, we could then proceed to click on the desired promoter and we could inspect even more characteristics of the part, one benefit of the software is that if we want to we could insert our own sequence for the final biobrick.
| |
| − | The following screens consist of the same interaction with different features depending on the part we are selecting such as the rbs and the terminator.</p>
| |
| | </div> | | </div> |
| | </div> | | </div> |
