(12 intermediate revisions by 3 users not shown) | |||
Line 21: | Line 21: | ||
<li><a href="https://2016.igem.org/Team:UESTC-software/Project?id=0">PROJECT</a> | <li><a href="https://2016.igem.org/Team:UESTC-software/Project?id=0">PROJECT</a> | ||
<ul class="sub-nav"> | <ul class="sub-nav"> | ||
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Description | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Description">Description</a></li> |
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Design | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Design">Design</a></li> |
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Features | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Features">Features</a></li> |
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Model"> | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Model">Modeling</a></li> |
<li class="three-nav"><a href="https://2016.igem.org/Team:UESTC-software/Proof">Proof</a></li> | <li class="three-nav"><a href="https://2016.igem.org/Team:UESTC-software/Proof">Proof</a></li> | ||
<li class="three-nav"><a href="https://2016.igem.org/Team:UESTC-software/Demonstrate">Results</a></li> | <li class="three-nav"><a href="https://2016.igem.org/Team:UESTC-software/Demonstrate">Results</a></li> | ||
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Future | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Future">Future</a></li> |
− | <li class="three-nav"><a href="https://2016.igem.org/Team:UESTC-software/Extra_work | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Parts">Parts</a></li> |
+ | <li class="three-nav"><a href="https://2016.igem.org/Team:UESTC-software/Extra_work">Extra Work—Bio2048</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
<li><a href="https://2016.igem.org/Team:UESTC-software/Judging?id=1">JUDGING</a> | <li><a href="https://2016.igem.org/Team:UESTC-software/Judging?id=1">JUDGING</a> | ||
<ul class="sub-nav"> | <ul class="sub-nav"> | ||
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Medal_requirements | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Medal_requirements">Medal Requirements</a></li> |
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Safety? | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Safety?">Safety</a></li> |
</ul> | </ul> | ||
</li> | </li> | ||
Line 42: | Line 43: | ||
<li><a href="https://2016.igem.org/Team:UESTC-software/Members?id=2&index=0">Team</a></li> | <li><a href="https://2016.igem.org/Team:UESTC-software/Members?id=2&index=0">Team</a></li> | ||
<li><a href="https://2016.igem.org/Team:UESTC-software/Collaborations">Collaborations</a></li> | <li><a href="https://2016.igem.org/Team:UESTC-software/Collaborations">Collaborations</a></li> | ||
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Notebooks | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Notebooks">Notebooks</a></li> |
</ul> | </ul> | ||
</li> | </li> | ||
<li><a href="https://2016.igem.org/Team:UESTC-software/HP">HUMAN PRACTICES</a> | <li><a href="https://2016.igem.org/Team:UESTC-software/HP">HUMAN PRACTICES</a> | ||
<ul class="sub-nav"> | <ul class="sub-nav"> | ||
− | + | <li><a href="https://2016.igem.org/Team:UESTC-software/HP/Silver">Silver</a></li> | |
− | + | <li><a href="https://2016.igem.org/Team:UESTC-software/HP/Gold">Gold</a></li> | |
+ | |||
<li><a href="https://2016.igem.org/Team:UESTC-software/Integrated_Practices">Integrated Practices</a></li> | <li><a href="https://2016.igem.org/Team:UESTC-software/Integrated_Practices">Integrated Practices</a></li> | ||
<li><a href="https://2016.igem.org/Team:UESTC-software/Engagement">Engagement</a></li> | <li><a href="https://2016.igem.org/Team:UESTC-software/Engagement">Engagement</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
− | <li><a href="https://2016.igem.org/Team:UESTC-software/Document | + | <li><a href="https://2016.igem.org/Team:UESTC-software/Document">DOCUMENTS</a></li> |
<li><a href="https://2016.igem.org/Team:UESTC-software/Attributions">ATTRIBUTIONS</a></li> | <li><a href="https://2016.igem.org/Team:UESTC-software/Attributions">ATTRIBUTIONS</a></li> | ||
Line 66: | Line 68: | ||
<div class="detail-content"> | <div class="detail-content"> | ||
<h2 id="Bio101">Bio101</h2> | <h2 id="Bio101">Bio101</h2> | ||
− | <P> | + | <P>Bio101 is a software system to convert computer files to DNA sequences. There is <b>no</b> direct safety issue related with the use of the software. We also ensure that the encoded DNA sequences as<b> artificial</b> as possible, which means that the encoded sequences are devoid of any actual biological function. The information safety is protected through <b>encryption</b> and the data integrity is ensured through <b>redundancy</b> and <b>error checking algorithm</b>. </P> |
− | <strong>Q1: What function does your software have? </strong> | + | <strong> Q1: <b>What function</b> does your software have? </strong> |
− | <p><B>A1:</B> Bio101 is used to transform | + | <p><B>A1:</B> Bio101 is used to transform computer files to DNA sequences which can be used to synthesize DNA samples for physical data write-in. Our software also provides the decoding function to recover the stored information from DNA samples using the sequencing technology for physical read-out.</p> |
− | <strong>Q2: Who will use your software?</strong> | + | <strong> Q2: <b>Who</b> will use your software?</strong> |
− | <p><B>A2:</B> | + | <p><B>A2:</B> People who want to store information in DNA will use our software.</p> |
− | <strong>Q3: How do you verify the results that your software runs? Are they right?</strong> | + | <strong> Q3: How do you <b>verify the results</b> that your software runs? Are they right?</strong> |
− | <p><B>A3:</B> Bio101 | + | <p><B>A3:</B> Bio101 has been tested internally and externally. We and our collaborators carried out a series software tests from its <b>usability and stability</b> and the results were documented in a detailed testing report. In addition, we went through the whole process of DNA information storage. We used our software to encode a file and used the result to synthesize DNA samples. After a few weeks’ storage and cultivation, we extracted the DNA samples and sequence them. Finally, Bio101 is used to decode the DNA sequences. As a result, we recovered our original file.</p> |
− | <strong>Q4: Does it have any risk in laboratory? </strong> | + | <strong> Q4: Does it have any<b> risk</b> in laboratory? </strong> |
− | <p><B>A4: </B> | + | <p><B>A4:</B> The software itself runs on a computer as a <b>web-app</b>. It has no any direct risk associated with the running of the software. The encoding algorithm ensures that the resulting sequences do not contain any biologically functional segment or dangerous part. This has been tested through <b>blasting</b> against known gene sequences. Therefore, it is safe to use and it does not cause any pollution to our environment either. </p> |
− | <strong>Q5: Does it have any risk in people who use your software? </strong> | + | <strong> Q5: Does it have any <b>risk</b> in people who use your software? </strong> |
− | <p><B>A5:</B>No, it | + | <p><B>A5:</B> No, it has no any direct harm to our environment. The encoded DNA sequences are randomized (and encrypted) using the ISAAC algorithm. It is extremely unlikely to find a sequence with a specific function, not to mention any harm to our environment.</p> |
<h2 id="Bio2048">Bio2048</h2> | <h2 id="Bio2048">Bio2048</h2> | ||
− | <p>As | + | <p>As an edutainment mobile device game, Bio2048 combines the entertainment factor behind the slide-block game 2048 with the biological hierarchy knowledge. It targets young video game players with interest in biology. There is virtually no safety issue to the players other than the harm to the eye-sight related with the prolonged usage of mobile devices.</p> |
− | <strong>Q1: If your product is successful, who will receive benefits and who will be harmed?</strong> | + | <strong> Q1: If your product is successful, who will receive <b>benefits</b> and who will </b>be harmed</b>?</strong> |
− | <p><B>A1:</B> The people who play the | + | <p><B>A1:</B> The young people who play the game properly in their spare time will benefit. The young people who spend all their spare time in playing the game may have their eyes harmed.</p> |
− | <strong>Q2: Where will your product be used? Can it cause pollution?</strong> | + | <strong> Q2: Where will your product be used? Can it cause <b>pollution</b>?</strong> |
− | <p><B>A2:</B>It | + | <p><B>A2:</B> It can be used at any place where the use of mobile devices, e.g. mobile phones and pad computers, is allowed. It does not cause any pollution directly.</p> |
− | <strong>Q3:Does your software open source? </strong> | + | <strong> Q3:Does your software <b>open source</b>? </strong> |
− | <p><B>A3:</B>Yes, | + | <p><B>A3:</B> Yes, the game is <b>open-sourced</b>. </p> |
− | <strong>Q4: Who will use your product?</strong> | + | <strong> Q4: <b>Who</b> will use your product?</strong> |
− | <p><B>A4:</B> | + | <p><B>A4:</B> Our target players are <b>young students</b> but anybody, who is willing to play it to understand a range of important biological concepts in a more interesting way, can play the game. In particular, teachers and parents may use it to teach children on the <b>basic biological hierarchy concepts</b>.</p> |
− | <strong>Q5: Does it have some risks in health of people?</strong> | + | <strong> Q5: Does it have some <b>risks in health</b> of people?</strong> |
− | <p><B>A5:</B> | + | <p><B>A5:</B> Bio2048 is an android-OS based <b>video game</b> which can be installed on android smart phones and pads. If people play the game for too much time, their eyesight may be hurt.</p> |
− | <strong>Q6: Does it have some risks of environment (From the wasting water or others)?</strong> | + | <strong> Q6: Does it have some<b> risks of environment</b> (From the wasting water or others)?</strong> |
− | <p><B>A6:</B>As a game, there is no danger to | + | <p><B>A6:</B> As a video game, there is<b> no danger</b> to our environment in any direct way.</p> |
</div> | </div> | ||
<footer class="footer"> | <footer class="footer"> | ||
<div class="footer-top"> | <div class="footer-top"> | ||
<p>FOLLOW US: | <p>FOLLOW US: | ||
− | <a href="https://github.com/ | + | <a href="https://github.com/igemsoftware2016/UESTC-Software-2016" target="_blank"><img src="https://static.igem.org/mediawiki/igem.org/0/06/Uestc_software-github.png" /></a> |
<a href="http://www.uestc.edu.cn/" target="_blank"><img src="https://static.igem.org/mediawiki/igem.org/a/a4/Uestc_software-school.png" /></a> | <a href="http://www.uestc.edu.cn/" target="_blank"><img src="https://static.igem.org/mediawiki/igem.org/a/a4/Uestc_software-school.png" /></a> | ||
<a href="http://weibo.com/u/5621240588?refer_flag=1001030101_&is_hot=1" target="_blank"><img src="https://static.igem.org/mediawiki/igem.org/b/b1/Uestc_software-weibo.png" /></a> | <a href="http://weibo.com/u/5621240588?refer_flag=1001030101_&is_hot=1" target="_blank"><img src="https://static.igem.org/mediawiki/igem.org/b/b1/Uestc_software-weibo.png" /></a> | ||
Line 126: | Line 128: | ||
</div> | </div> | ||
<script type="text/javascript" src="https://2016.igem.org/Team:UESTC-software/js/basic/jquery?action=raw&ctype=text/javascript"></script> | <script type="text/javascript" src="https://2016.igem.org/Team:UESTC-software/js/basic/jquery?action=raw&ctype=text/javascript"></script> | ||
− | |||
− | |||
− | |||
− | |||
+ | <script type="text/javascript"> | ||
+ | $(".scroll-top img").addClass("active"); | ||
+ | $(".catalog").click(function(){ | ||
+ | $(this).addClass("active"); | ||
+ | $(".catalog-area").addClass("active"); | ||
+ | }); | ||
+ | $(".catalog-area .title").click(function(){ | ||
+ | $(".catalog-area").removeClass("active"); | ||
+ | $(".catalog").removeClass("active"); | ||
+ | }); | ||
+ | $(".scroll-top img").click(function(){ | ||
+ | $('html, body').animate({scrollTop:0}, 'slow'); | ||
+ | }); | ||
+ | $(window).scroll(function(){ | ||
+ | var height = $(document).scrollTop(); | ||
+ | if(height > 300){ | ||
+ | $(".scroll-top img").removeClass("active"); | ||
+ | }else{ | ||
+ | $(".scroll-top img").addClass("active"); | ||
+ | } | ||
}) | }) | ||
</script> | </script> | ||
</body> | </body> | ||
</html> | </html> |
Latest revision as of 01:45, 20 October 2016
Safety
Bio101
Bio101 is a software system to convert computer files to DNA sequences. There is no direct safety issue related with the use of the software. We also ensure that the encoded DNA sequences as artificial as possible, which means that the encoded sequences are devoid of any actual biological function. The information safety is protected through encryption and the data integrity is ensured through redundancy and error checking algorithm.
Q1: What function does your software have?A1: Bio101 is used to transform computer files to DNA sequences which can be used to synthesize DNA samples for physical data write-in. Our software also provides the decoding function to recover the stored information from DNA samples using the sequencing technology for physical read-out.
Q2: Who will use your software?A2: People who want to store information in DNA will use our software.
Q3: How do you verify the results that your software runs? Are they right?A3: Bio101 has been tested internally and externally. We and our collaborators carried out a series software tests from its usability and stability and the results were documented in a detailed testing report. In addition, we went through the whole process of DNA information storage. We used our software to encode a file and used the result to synthesize DNA samples. After a few weeks’ storage and cultivation, we extracted the DNA samples and sequence them. Finally, Bio101 is used to decode the DNA sequences. As a result, we recovered our original file.
Q4: Does it have any risk in laboratory?A4: The software itself runs on a computer as a web-app. It has no any direct risk associated with the running of the software. The encoding algorithm ensures that the resulting sequences do not contain any biologically functional segment or dangerous part. This has been tested through blasting against known gene sequences. Therefore, it is safe to use and it does not cause any pollution to our environment either.
Q5: Does it have any risk in people who use your software?A5: No, it has no any direct harm to our environment. The encoded DNA sequences are randomized (and encrypted) using the ISAAC algorithm. It is extremely unlikely to find a sequence with a specific function, not to mention any harm to our environment.
Bio2048
As an edutainment mobile device game, Bio2048 combines the entertainment factor behind the slide-block game 2048 with the biological hierarchy knowledge. It targets young video game players with interest in biology. There is virtually no safety issue to the players other than the harm to the eye-sight related with the prolonged usage of mobile devices.
Q1: If your product is successful, who will receive benefits and who will be harmed?A1: The young people who play the game properly in their spare time will benefit. The young people who spend all their spare time in playing the game may have their eyes harmed.
Q2: Where will your product be used? Can it cause pollution?A2: It can be used at any place where the use of mobile devices, e.g. mobile phones and pad computers, is allowed. It does not cause any pollution directly.
Q3:Does your software open source?A3: Yes, the game is open-sourced.
Q4: Who will use your product?A4: Our target players are young students but anybody, who is willing to play it to understand a range of important biological concepts in a more interesting way, can play the game. In particular, teachers and parents may use it to teach children on the basic biological hierarchy concepts.
Q5: Does it have some risks in health of people?A5: Bio2048 is an android-OS based video game which can be installed on android smart phones and pads. If people play the game for too much time, their eyesight may be hurt.
Q6: Does it have some risks of environment (From the wasting water or others)?A6: As a video game, there is no danger to our environment in any direct way.