Difference between revisions of "Team:NUS Singapore/Parts"

(Prototype team page)
 
Line 1: Line 1:
−
{{NUS_Singapore}}
 
−
<html>
 
  
  
 +
{{Team:NUS_Singapore/new_template}}
 +
{{Team:NUS_Singapore/Project_Main_CSS}}
 +
{{Team:NUS_Singapore/CSS}}
 +
{{Team:NUS_Singapore/CSS-Spatial}}
 +
<html lang="en" class="no-js">
 +
    <head>
 +
        <meta charset="UTF-8" />
 +
        <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
 +
        <meta name="viewport" content="width=device-width, initial-scale=1">
 +
        <title>Interactive Points | Codrops</title>
 +
        <meta name="keywords" content="opacity, background, hover, transparency, effect, css, html, javascript, template, point of interest, map" />
 +
        <meta name="author" content="Codrops" />
 +
        <link rel="shortcut icon" href="favicon.ico">
  
 +
        <!-- <script src="js/modernizr.custom.js"></script> -->
  
 +
        <!--[if IE]>
 +
        <script src="http://html5shiv.googlecode.com/svn/trunk/html5.js"></script>
 +
        <![endif]-->
 +
    </head>
 +
    <body>
 +
        <main>
 +
            <div id="st-container" class="st-container" style="background-color: white;">
 +
                <div class="st-pusher">
  
 +
                    <!--Sidebar button-->
 +
                    <div id="st-trigger-effects">
 +
                        <button data-effect="st-effect-1" class="button button--rayen button--border button--round-m" data-text="More" style="left: -83px; font-size: 50px; z-index: 100;">
 +
                            <span><img src="https://static.igem.org/mediawiki/2016/c/ce/T--NUS_Singapore--scroll-down-arrow.png"></span>
 +
                        </button>
 +
                    </div>
 +
                    <!--End of Sidebar button-->
  
−
<div class="column full_size">
+
                    <!--Header-->
 +
                    <header id="ha-header" class="ha-header ha-header-large">
 +
                        <div class="ha-header-perspective">
 +
                            <div id="header1" class="ha-header-front" style="height: 120px">
 +
                                <a href="https://2016.igem.org/Team:NUS_Singapore"><img id="nus_logo" src="https://static.igem.org/mediawiki/2016/1/1d/T--NUS_Singapore--header_left.png" style="height: 130%; margin-top: -10px; left: 0px; position: absolute;"/></a>
 +
                                <a href="http://www.science.nus.edu.sg"><img id="sci_logo" src="https://static.igem.org/mediawiki/2016/2/21/T--NUS_Singapore--NUS_Science_logo_grey.png" style="height: 70%; margin-top: 25px; right: 0px; position: absolute;"/></a>
 +
                                <a href="http://sps.nus.edu.sg/alpha"><img id="sps_logo" src="https://static.igem.org/mediawiki/2016/e/ec/T--NUS_Singapore--SPS_Logo_High_Res_grey.png" style="height: 60%; margin-top: 25px; right: 280px; position: absolute;"/></a>
 +
                                <div style="height: 7%; background-color: rgb(217, 215, 215); width: 100%; bottom: 0px; left: 0px; position: absolute;"></div>
 +
                            </div>
 +
                            <div class="ha-header-bottom" style="text-align: center;">
 +
                                <a><h1><a href="https://2016.igem.org/Team:NUS_Singapore" style="color: black; font-weight: lighter;">iGEM 2016 &nbsp; &nbsp; &nbsp; &nbsp; NUS SINGAPORE</a></h1></a>
 +
                            </div>
 +
                        </div>
 +
                    </header>
 +
                    <!--End of Header-->
  
 +
                    <!--Side Bar-->
 +
<nav class="st-menu st-effect-1 list-group panel" id="menu-1" style="overflow: auto; z-index: 100; background-color: rgb(179, 179, 179);">
 +
<span><img src="https://static.igem.org/mediawiki/2016/1/1e/T--NUS_Singapore--practice.png" style="width: 30px; height: auto; top: 30px; left: 35px; position: absolute;"><h4 style=" left: 75px; top: 20px; position: absolute; font-size: 17px;">NUS_SINGAPORE</h4></span>
 +
<ul style="margin-top: 36%; font-size: 14px;">
 +
<li><a class="icon icon-home" id="menu-item-1" href="https://2016.igem.org/Team:NUS_Singapore">Home</a></li>
 +
<li><a class="icon icon-project" onclick="growDiv('2')" id="menu-item-2" href="https://2016.igem.org/Team:NUS_Singapore/Project">Project
 +
<span><img id="sidebar-arrow-2" src="https://static.igem.org/mediawiki/2016/c/ce/T--NUS_Singapore--scroll-down-arrow.png" style="position: relative; height: 20px; float: right;"></span></a>
 +
<div class="grow" id="grow-2">
 +
<div class='measuringWrapper'>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Project/Wet_Lab" class="list-group-item" style="color: rgb(179, 179, 179);">Overview</a>
 +
 
 +
<a href="https://2016.igem.org/Team:NUS_Singapore/Model" class="list-group-item" style="color: rgb(179, 179, 179);">Modelling</a>
 +
</div>
 +
</div>
 +
</li>
 +
<li><a class="icon icon-notebook"  id="menu-item-9" onclick="growDiv('9')"  href="https://2016.igem.org/Team:NUS_Singapore/Notebook">RIOTSensor
 +
<span><img id="sidebar-arrow-9" src="https://static.igem.org/mediawiki/2016/c/ce/T--NUS_Singapore--scroll-down-arrow.png" style="position: relative; height: 20px; float: right;"></span></a>
 +
<div class="grow" id="grow-9">
 +
<div class='measuringWrapper'>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Description" class="list-group-item" style="color: rgb(179, 179, 179);">Description</a>
 +
<a href="https://2016.igem.org/Team:NUS_Singapore/Proof" class="list-group-item" style="color: rgb(179, 179, 179);">Proof of Concept</a>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Demonstrate" class="list-group-item" style="color: rgb(179, 179, 179);">Demonstration</a>
 +
 +
</div>
 +
</div>
 +
</li>
 +
<li><a class="icon icon-notebook" id="menu-item-5" href="https://2016.igem.org/Team:NUS_Singapore/RIOTResponder">RIOTResponder</a></li>
 +
<li><a class="icon icon-notebook" id="menu-item-5" href="https://2016.igem.org/Team:NUS_Singapore/RIOTInvader">RIOTInvader</a></li>
 +
<li><a class="icon icon-practice" onclick="growDiv('3')" id="menu-item-3" href="#">Human Practices
 +
<span><img id="sidebar-arrow-3" src="https://static.igem.org/mediawiki/2016/c/ce/T--NUS_Singapore--scroll-down-arrow.png" style="position: relative; height: 20px; float: right;"><span></a>
 +
<div class="grow" id="grow-3">
 +
<div class='measuringWrapper'>
 +
                                                                          <a href="https://2016.igem.org/Team:NUS_Singapore/HP/Silver" class="list-group-item" style="color: rgb(179, 179, 179);">Survey</a>
 +
                                                                          <a href="https://2016.igem.org/Team:NUS_Singapore/HP/Gold" class="list-group-item" style="color: rgb(179, 179, 179);">Business Plan</a>
 +
<a href="https://2016.igem.org/Team:NUS_Singapore/Integrated_Practices" class="list-group-item" style="color: rgb(179, 179, 179);">Integration</a>
 +
</div>
 +
</div>
 +
</li>
 +
<li><a class="icon icon-collaboration" onclick="growDiv('4')" id="menu-item-4" href="#">Collaborations
 +
                                                                <span><img id="sidebar-arrow-4" src="https://static.igem.org/mediawiki/2016/c/ce/T--NUS_Singapore--scroll-down-arrow.png" style="position: relative; height: 20px; float: right;"></span></a>
 +
<div class="grow" id="grow-4">
 +
<div class='measuringWrapper'>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Collaborations" class="list-group-item" style="color: rgb(179, 179, 179);">Melbourne</a>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Collaborations" class="list-group-item" style="color: rgb(179, 179, 179);">Hong_Kong_HKU</a>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Collaborations" class="list-group-item" style="color: rgb(179, 179, 179);">ETH_Zurich</a>
 +
</div>
 +
</div>
 +
</li>
 +
                                                        <li><a class="icon icon-notebook" id="menu-item-5" href="https://2016.igem.org/Team:NUS_Singapore/Parts">Parts Registry</a></li>
 +
<li><a class="icon icon-safety" id="menu-item-5" href="https://2016.igem.org/Team:NUS_Singapore/Safety">Safety</a></li>
  
−
<p>Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <code>&lt;groupparts&gt;</code> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.</p>
+
<li><a class="icon icon-team" id="menu-item-6" href="https://2016.igem.org/Team:NUS_Singapore/Team">Team</a></li>
−
<p>Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.</p>
+
<li><a class="icon icon-notebook"  id="menu-item-7" onclick="growDiv('7')"  href="https://2016.igem.org/Team:NUS_Singapore/Notebook">Notebook
 +
<span><img id="sidebar-arrow-7" src="https://static.igem.org/mediawiki/2016/c/ce/T--NUS_Singapore--scroll-down-arrow.png" style="position: relative; height: 20px; float: right;"></span></a>
 +
<div class="grow" id="grow-7">
 +
<div class='measuringWrapper'>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Notebook/Group1" class="list-group-item" style="color: rgb(179, 179, 179);">I. RIOT Sensor</a>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Notebook/Group2" class="list-group-item" style="color: rgb(179, 179, 179);">II. RIOT Responder</a>
 +
  <a href="https://2016.igem.org/Team:NUS_Singapore/Notebook/Group3" class="list-group-item" style="color: rgb(179, 179, 179);">III. RIOT Invader</a>
 +
</div>
 +
</div>
 +
</li>
 +
<li><a class="icon icon-acknowledgement" id="menu-item-8" href="https://2016.igem.org/Team:NUS_Singapore/Attributions">Attributions</a></li>
 +
                            <li><a class="icon icon-cup" id="menu-item-8" href="https://2016.igem.org/Team:NUS_Singapore/Medals">Medals</a></li>
 +
</ul>
 +
</nav>
 +
<!--End of Side Bar-->
  
 +
                    <section id="main" class="wrapper">
 +
<div class="container" style="width: 85%; padding-top: 0px;">
 +
<header class="major special">
 +
<h2>Parts Registry</h2>
 +
</header>
 +
<hr/>
  
−
</div>
+
<header>
 +
                            <a name="gold"></a>
 +
    <p class="medium">RIOT Sensor</p>
 +
</header>
 +
 +
<p>Based on the survey results, especially those obtained from Singapore, we found that the participants are generally receptive to bacteria cancer diagnosis and therapy. Hence, to better set up for a potential release of our tool in the field, we proposed to tackle the issues of environment, safety and sustainability via the drafting of a business plan. By integrating the marketing of the RIOT System with manufacturing and financial legislations, we aim to reduce the cost of production of such a tool and the safety-related stigma attached with a new, unknown medical procedure. Every aspect of the RIOT System is meticulously examined in the business plan to ascertain the best possible ways to market, manufacture and measure its retail value whilst still ensuring that it is done in the most safe and sustainable manner possible. </p>
 +
 +
<hr>
 +
 +
 +
 +
<header>
 +
<!--h3></h3-->
 +
<p class="medium">RIOT Sensor</p>
 +
</header>
 +
<p align=justify>NUS_Singapore is a start-up company formed by a group of undergraduates from the National University of Singapore (NUS), interested in developing new diagnostic tools for cancer using synthetic biology technology. Our start-up uses synthetic biological technology to create the Regulated Invasive Organism Targeting System (RIOT System) which consists of three components: The RIOT Sensor, RIOT Responder and the RIOT Invader. Taken together, this system employs a modular concept of integrating different genetic circuits that serve individual functions with crosstalk capability. For the full and detailed business plan of our start-up, please <a href="https://static.igem.org/mediawiki/2016/7/70/T--NUS_Singapore--BusinessPlanFinal.pdf" style="font-weight: bold;">CLICK HERE.</a></p><br/>
 +
 +
<hr/>
 +
 +
<header>
 +
<!--h3></h3-->
 +
<p class="medium">RIOT Invader</p>
 +
</header>
 +
<p>In cancer treatment, specificity, sensitivity and reliability of diagnosis is the gold criteria of any diagnostic method. The RIOT System employs a novel method of cancer detection, relying on spatial markers that are intrinsic to the tumour microenvironment. Two types of spatial markers are used to increase specificity and ensure that only cancerous cells are targeted. The first spatial marker would be the elevated concentration of lactate usually found around tumours due to the Warburg effect. The second marker would be the detection of CD44v6, a cell surface marker that is upregulated on a variety of cancers. These spatial markers were specially chosen to circumvent a common problem in cancer research, where heterogeneity in different types of cancers results in the lack of a specific diagnostic for a variety of cancers. As elevated lactate concentration is ubiquitous among solid tumours and CD44v6 is present in different types of cancers, our RIOT System has the potential to be a diagnostic that can be applied to multiple cancers, which is advantageous in the current market where broad spectrum diagnostics for cancer are currently lacking. Furthermore, the utility of RIOT System can extend beyond just being a diagnostic and can be modified to deliver a drug payload, potentially acting as both a diagnostic and therapeutic. </p></br>
  
 +
<p>Based on our preliminary market analysis of the diagnostics industry, our proposed RIOT System stands out as one of the few in vivo options available for cancer detection. Current cancer diagnostics rely mainly on in vitro laboratory tests for detection of cancer biomarkers (e.g. blood, urine), imaging scans (e.g. CT scans, MRI) or physical examinations to detect the tumour. Thus, our RIOT System offers a radically different diagnostic option that sets itself apart from the current diagnostics. </p></br>
 +
 +
<hr>
 +
 +
 +
 +
 +
<!--header>
 +
<!--h4>Heading with a Subtitle</h4-->
 +
<!--p>Lorem ipsum dolor sit amet nullam id egestas urna aliquam</p-->
 +
<!--/header-->
 +
<!--p>Nunc lacinia ante nunc ac lobortis. Interdum adipiscing gravida odio porttit or sem non mi integer non faucibus ornare mi ut ante amet placerat aliquet. Volutpat eu sed ante lacinia sapien lorem accumsan varius montes viverra nibh in adipiscing blandit tempus accumsan.</p-->
  
 +
<hr/>
 +
  
 +
</div>
 +
</section>
  
  
−
<div class="column half_size">
+
                    <section class="content content--related">
−
<div class="highlight">
+
                        <ul class="copyright">
−
<h5>Note</h5>
+
                            <li>&copy; NUS_Singapore iGEM 2016</li>
−
<p>Note that parts must be documented on the <a href="http://parts.igem.org/Main_Page"> Registry</a>. This page serves to <i>showcase</i> the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.</p>
+
                        </ul>
−
</div>
+
                    </section>
−
</div>
+
<a href="#" class="go-top">Go To Top</a>
−
 
+
                </div><!-- /st-pusher -->
−
 
+
            </div><!-- /st-container -->
−
 
+
        </main>
−
 
+
<script>
−
<div class="column half_size">
+
(function($) {
−
 
+
−
<h5>Adding parts to the registry</h5>
+
−
<p>You can add parts to the Registry at our <a href="http://parts.igem.org/Add_a_Part_to_the_Registry">Add a Part to the Registry</a> link.</p>
+
−
<p>We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you <b>do</b> need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)</p>
+
−
</div>
+
−
 
+
−
 
+
−
 
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>What information do I need to start putting my parts on the Registry?</h5>
+
−
<p>The information needed to initially create a part on the Registry is:</p>
+
−
<ul>
+
−
<li>Part Name</li>
+
−
<li>Part type</li>
+
−
<li>Creator</li>
+
−
<li>Sequence</li>
+
−
<li>Short Description (60 characters on what the DNA does)</li>
+
−
<li>Long Description (Longer description of what the DNA does)</li>
+
−
<li>Design considerations</li>
+
−
</ul>
+
−
 
+
−
<p>
+
−
We encourage you to put up <em>much more</em> information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page. </p>
+
−
 
+
−
</div>
+
−
 
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h5>Inspiration</h5>
+
−
<p>We have a created  a <a href="http://parts.igem.org/Well_Documented_Parts">collection of well documented parts</a> that can help you get started.</p>
+
−
 
+
−
<p> You can also take a look at how other teams have documented their parts in their wiki:</p>
+
−
<ul>
+
−
<li><a href="https://2014.igem.org/Team:MIT/Parts"> 2014 MIT </a></li>
+
−
<li><a href="https://2014.igem.org/Team:Heidelberg/Parts"> 2014 Heidelberg</a></li>
+
−
<li><a href="https://2014.igem.org/Team:Tokyo_Tech/Parts">2014 Tokyo Tech</a></li>
+
−
</ul>
+
−
</div>
+
−
 
+
−
<div class="column full_size">
+
−
<h5>Part Table </h5>
+
−
<div class="highlight">
+
−
 
+
−
 
+
−
</html>
+
−
<groupparts>iGEM2016 Example</groupparts>
+
−
<html>
+
−
</div>
+
−
</div>
+
−
 
+
  
 +
                var setCss = function() {
 +
                    if($(window).width() <= 900) {
 +
                        $('#nus_logo').css('left', "10%");
 +
                        $('#sci_logo').css('display', "none");
 +
                        $('#sps_logo').css('display', "none");
 +
                    }else{
 +
                        $('#nus_logo').css('left', "0%");
 +
                        $('#sci_logo').css('display', "block");
 +
                        $('#sps_logo').css('display', "block");
 +
                    }
 +
                };
  
 +
                $(document).ready(function() {
 +
                    setCss();
 +
                    $(window).resize(setCss);
 +
                    });
  
 +
            })(jQuery);
 +
        </script>
 +
    </body>
 
</html>
 
</html>
 +
{{Team:NUS_Singapore/JS}}

Revision as of 04:01, 18 October 2016


Interactive Points | Codrops

iGEM 2016         NUS SINGAPORE

Parts Registry

RIOT Sensor

Based on the survey results, especially those obtained from Singapore, we found that the participants are generally receptive to bacteria cancer diagnosis and therapy. Hence, to better set up for a potential release of our tool in the field, we proposed to tackle the issues of environment, safety and sustainability via the drafting of a business plan. By integrating the marketing of the RIOT System with manufacturing and financial legislations, we aim to reduce the cost of production of such a tool and the safety-related stigma attached with a new, unknown medical procedure. Every aspect of the RIOT System is meticulously examined in the business plan to ascertain the best possible ways to market, manufacture and measure its retail value whilst still ensuring that it is done in the most safe and sustainable manner possible.

RIOT Sensor

NUS_Singapore is a start-up company formed by a group of undergraduates from the National University of Singapore (NUS), interested in developing new diagnostic tools for cancer using synthetic biology technology. Our start-up uses synthetic biological technology to create the Regulated Invasive Organism Targeting System (RIOT System) which consists of three components: The RIOT Sensor, RIOT Responder and the RIOT Invader. Taken together, this system employs a modular concept of integrating different genetic circuits that serve individual functions with crosstalk capability. For the full and detailed business plan of our start-up, please CLICK HERE.


RIOT Invader

In cancer treatment, specificity, sensitivity and reliability of diagnosis is the gold criteria of any diagnostic method. The RIOT System employs a novel method of cancer detection, relying on spatial markers that are intrinsic to the tumour microenvironment. Two types of spatial markers are used to increase specificity and ensure that only cancerous cells are targeted. The first spatial marker would be the elevated concentration of lactate usually found around tumours due to the Warburg effect. The second marker would be the detection of CD44v6, a cell surface marker that is upregulated on a variety of cancers. These spatial markers were specially chosen to circumvent a common problem in cancer research, where heterogeneity in different types of cancers results in the lack of a specific diagnostic for a variety of cancers. As elevated lactate concentration is ubiquitous among solid tumours and CD44v6 is present in different types of cancers, our RIOT System has the potential to be a diagnostic that can be applied to multiple cancers, which is advantageous in the current market where broad spectrum diagnostics for cancer are currently lacking. Furthermore, the utility of RIOT System can extend beyond just being a diagnostic and can be modified to deliver a drug payload, potentially acting as both a diagnostic and therapeutic.


Based on our preliminary market analysis of the diagnostics industry, our proposed RIOT System stands out as one of the few in vivo options available for cancer detection. Current cancer diagnostics rely mainly on in vitro laboratory tests for detection of cancer biomarkers (e.g. blood, urine), imaging scans (e.g. CT scans, MRI) or physical examinations to detect the tumour. Thus, our RIOT System offers a radically different diagnostic option that sets itself apart from the current diagnostics.


  • © NUS_Singapore iGEM 2016
Go To Top