Team:SYSU-Software/Safety
From 2012.igem.org
(Prototype team page) |
Nie1234567 (Talk | contribs) |
||
(8 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
- | <!-- | + | {{:Team:SYSU-Software/menu}} |
+ | <html xmlns="http://www.w3.org/1999/xhtml" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office"> | ||
+ | |||
+ | <head> | ||
+ | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> | ||
+ | <title>无标题 1</title> | ||
+ | <link href="https://2012.igem.org/Team:SYSU-Software/template2/style.css?action=raw&ctype=text/css" rel="stylesheet" type="text/css" /> | ||
+ | <script language="javascript" type="text/javascript" src="https://2012.igem.org/Team:SYSU-Software/template2/js/jquery-1.4.2.js?action=raw&ctype=text/javascript"></script> | ||
+ | <script language="javascript" type="text/javascript" src="https://2012.igem.org/Team:SYSU-Software/template2/js/menu.js?action=raw&ctype=text/javascript"></script> | ||
+ | |||
+ | </head> | ||
+ | |||
+ | <body> | ||
+ | <body class="" | ||
+ | style=" | ||
+ | text-align:center; | ||
+ | width:970px; | ||
+ | margin:0 auto;> | ||
+ | <div class="skip-content"></div> | ||
+ | <div id="header" class="clear" style="background-color: #545454"> | ||
+ | <div class="wrapper"> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software" class="sysu-title"></a> | ||
+ | |||
+ | <!--end navigation--> | ||
+ | </div><!--end wrapper--> | ||
+ | </div><!--end header--> | ||
+ | <div class="content-background"> | ||
+ | <div id="blank" ><br/></div> | ||
+ | <div class="wrapper"> | ||
+ | |||
+ | <div id="menu"> | ||
+ | <ul id="nav"> | ||
+ | <li class="mainlevel" id="mainlevel_01"><a href="https://2012.igem.org/Team:SYSU-Software"> Home</a> | ||
+ | |||
+ | </li> | ||
+ | |||
+ | <li class="mainlevel" id="mainlevel_02"><a href="https://2012.igem.org/Team:SYSU-Software/Project">Project</a> | ||
+ | |||
+ | </li> | ||
+ | |||
+ | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Models">Models</a> | ||
+ | </li> | ||
+ | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Tutorial">Tutorial</a> | ||
+ | |||
+ | </li> | ||
+ | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Team">Team</a> | ||
+ | |||
+ | </li> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Notebook">Notebook</a></li> | ||
+ | |||
+ | <li class="mainlevel"><a href="https://2012.igem.org/Team:SYSU-Software/Practice"> | ||
+ | Tips</a><!--input an em tag as a space,IE is gread need--> | ||
+ | |||
+ | </li> | ||
+ | |||
+ | </ul> | ||
- | |||
- | |||
- | |||
- | |||
</div> | </div> | ||
- | < | + | <img src=" https://static.igem.org/mediawiki/2012/6/6d/Little-boy.png" id="little-boy"></img> |
- | + | ||
+ | |||
+ | <div id="content"> <div class="entry page clear"> | ||
+ | <h1 id="doctitle" class="pagetitle">Safety</h1> | ||
+ | <table class="doc-toc"> | ||
+ | <tbody> | ||
+ | <tr> | ||
+ | <td> | ||
+ | <div id="toctitle"> | ||
+ | <h2>Contents</h2> | ||
</div> | </div> | ||
- | <div id=" | + | <ul id="toc-ul"> |
- | + | <li class="toclevel-1"><a href="#r0"><span class="tocnumber"></span> <span class="toctext">Question I</span></a></li> | |
+ | <li class="toclevel-1"><a href="#r1"><span class="tocnumber"></span> <span class="toctext">Question II </span></a></li> | ||
+ | <li class="toclevel-1"><a href="#r2"><span class="tocnumber"></span> <span class="toctext">Question III</span></a></li> | ||
+ | <li class="toclevel-1"><a href="#r3"><span class="tocnumber"></span> <span class="toctext">Question IV</span></a></li> | ||
+ | </ul> | ||
+ | </td> | ||
+ | </tr> | ||
+ | </tbody> | ||
+ | </table> | ||
+ | <div id="doc-contents"> | ||
+ | <h2 id="r0" style="line-height: 1em;">Q1:Would any of your project ideas raise safety issues in terms of: | ||
+ | researcher safety, public safety, or environmental safety?</h2> | ||
+ | <div> | ||
+ | <p> No, just like other office software, it isn't | ||
+ | involved with harmful material or attack. It only can be used to assisting | ||
+ | viewing and analyzing biological data and designing regulatory elements of | ||
+ | metabolic networks, which will scarcely cause any public or environmental | ||
+ | problem. The software itself will not do harm to researcher either.</p> | ||
+ | <p> </p> | ||
+ | </p></div> | ||
+ | <h2 id="r1" style="line-height: 1em;">Q2:Do any of the new BioBrick parts (or devices) that you made this | ||
+ | year raise any safety issues? If yes, did you document these issues in the | ||
+ | Registry? how did you manage to handle the safety issue? How could other teams | ||
+ | learn from your experience?</h2> | ||
+ | <div> | ||
+ | <p> As a software team, we didn't make any | ||
+ | BioBrick. and no safety issues happened from this. For a software, the most | ||
+ | important safety concern is network safety. Our software can be used offline, so | ||
+ | it's safer in some way. Other software team should pay attention on the network | ||
+ | safety of their software.</p> | ||
+ | </p></div> | ||
+ | <h2 id="r2" style="line-height: 1em;">Q3:Is there a local biosafety group, committee, or review board at your institution? | ||
+ | |||
+ | If yes, what does your local biosafety group think about your project? | ||
+ | |||
+ | If no, which specific biosafety rules or guidelines do you have to consider in your country?</h2> | ||
+ | <div> | ||
+ | <p> Yes, there are biosafety committee in our | ||
+ | school, and Center for Disease Control and Prevention in our city. We | ||
+ | consulted them, and they think our project is safety, the reasons are as | ||
+ | follows:</p> | ||
+ | <p> There four part in the software. Among them, | ||
+ | Genome Browser,Network Illustrator and Simulator are all tools assisting | ||
+ | scientists to view or analyze biological data, which will not produce and | ||
+ | harmful substance or destroy anything. The Regulator Designer focus on the | ||
+ | design of regulatory elements of metabolic networks, It's also safety.<br> | ||
+ | </p> | ||
</div> | </div> | ||
+ | <h2 id="r3" style="line-height: 1em;">Q4:Do you have any other ideas how to deal with safety issues that | ||
+ | could be useful for future iGEM competitions? How could parts, devices and | ||
+ | systems be made even safer through biosafety engineering?</h2> | ||
+ | <div> | ||
+ | <p> Set a risk evaluating system, give each BioBrick a safety mark, not by | ||
+ | estimating by man, but by a calculating <span>equation.</span></p> | ||
</div> | </div> | ||
- | </ | + | <div> |
+ | </div> | ||
+ | </div> | ||
+ | </div><!--end entry--> | ||
+ | </div><!--end content--> | ||
+ | |||
+ | <div id="sidebar"> | ||
+ | <div id="doc-nav"> | ||
+ | <div> | ||
+ | <h5>IGEM-SYSU-Software </h5> | ||
+ | <div> | ||
+ | <ul> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software">Main Page</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Team">Album</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/SecondEdition">Second Edition</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Accomplishment">Accomplishment</a> | ||
+ | </li> | ||
+ | |||
+ | </ul> | ||
+ | </div> | ||
+ | </div> | ||
- | < | + | <div> |
+ | <h5>User Guide</h5> | ||
+ | <div> | ||
+ | <ul> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Download">Source Code</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Tutorial">Tutorial</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Video">Video</a> | ||
+ | </li> | ||
+ | |||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Contact">Email</a> | ||
+ | </li> | ||
+ | |||
+ | </ul> | ||
+ | </div> | ||
+ | </div> | ||
- | + | <div> | |
- | + | <h5>FAQ </h5> | |
- | + | <div> | |
- | + | <ul> | |
- | + | <li> | |
- | + | <a href="https://2012.igem.org/Team:SYSU-Software/Faq">Questions</a> | |
- | + | </li> | |
- | + | <li> | |
- | + | <a href="https://2012.igem.org/Team:SYSU-Software/Faq">Troubleshooting</a> | |
- | + | </li> | |
- | + | <li> | |
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Uninstalling">Uninstalling</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="">Contact Us</a> | ||
+ | </li> | ||
+ | </ul> | ||
+ | </div> | ||
+ | </div> | ||
- | + | </div> | |
+ | </div><!--end sidebar--> | ||
+ | <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script> | ||
+ | <script type="text/javascript"> | ||
+ | var name = "#doc-nav"; | ||
+ | var menuYloc = null; | ||
+ | |||
+ | $(document).ready(function(){ | ||
+ | menuYloc = parseInt($(name).css("top").substring(0,$(name).css("top").indexOf("px"))) | ||
+ | $(window).scroll(function () { | ||
+ | offset = menuYloc+$(document).scrollTop()+"px"; | ||
+ | $(name).animate({top:offset},{duration:500,queue:false}); | ||
+ | }); | ||
+ | }); | ||
+ | |||
+ | </script> | ||
+ | |||
+ | </div></div><!--end wrapper--> | ||
+ | </div><!--end content-background--> | ||
+ | <!--end footer--> | ||
+ | |||
+ | <script type="text/javascript"> | ||
+ | |||
+ | var _gaq = _gaq || []; | ||
+ | _gaq.push(['_setAccount', 'UA-15948744-2']); | ||
+ | _gaq.push(['_trackPageview']); | ||
+ | |||
+ | (function() { | ||
+ | var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true; | ||
+ | ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js'; | ||
+ | var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s); | ||
+ | })(); | ||
+ | |||
+ | </script></body><div id="footer"> | ||
+ | <div class="wrapper clear"> | ||
+ | <div id="footer-about" class="footer-column"> | ||
+ | <h2> About</h2> | ||
+ | <ul> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Team">Developers</a> | ||
+ | </li> | ||
+ | <li> | ||
+ | <a href="https://2012.igem.org/Team:SYSU-Software/Contact">Contact Us</a> | ||
+ | </li> | ||
+ | </ul> | ||
+ | </div> | ||
+ | <div id="footer-flickr" class="footer-column"> | ||
+ | <h2> Links</h2> | ||
+ | <ul> | ||
+ | <li><a href="http://www.sysu.edu.cn">SUN YAT-SEN University</a></li> | ||
+ | <li><a href="http://lifescience.sysu.edu.cn/main/default/index.aspx">SYSU LifeScience</a></li> | ||
+ | </ul> | ||
+ | |||
+ | </div> | ||
+ | <div id="footer-search" class="footer-column"> | ||
+ | <h2> Facebook</h2> | ||
+ | |||
+ | </div> | ||
+ | <div id="copyright"> | ||
+ | </div><!--end copyright--> | ||
+ | </div><!--end wrapper--> | ||
+ | </div> | ||
+ | </body> | ||
+ | |||
+ | |||
+ | </html> |
Latest revision as of 11:49, 26 September 2012
Safety
Contents |
Q1:Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?
No, just like other office software, it isn't involved with harmful material or attack. It only can be used to assisting viewing and analyzing biological data and designing regulatory elements of metabolic networks, which will scarcely cause any public or environmental problem. The software itself will not do harm to researcher either.
Q2:Do any of the new BioBrick parts (or devices) that you made this year raise any safety issues? If yes, did you document these issues in the Registry? how did you manage to handle the safety issue? How could other teams learn from your experience?
As a software team, we didn't make any BioBrick. and no safety issues happened from this. For a software, the most important safety concern is network safety. Our software can be used offline, so it's safer in some way. Other software team should pay attention on the network safety of their software.
Q3:Is there a local biosafety group, committee, or review board at your institution? If yes, what does your local biosafety group think about your project? If no, which specific biosafety rules or guidelines do you have to consider in your country?
Yes, there are biosafety committee in our school, and Center for Disease Control and Prevention in our city. We consulted them, and they think our project is safety, the reasons are as follows:
There four part in the software. Among them,
Genome Browser,Network Illustrator and Simulator are all tools assisting
scientists to view or analyze biological data, which will not produce and
harmful substance or destroy anything. The Regulator Designer focus on the
design of regulatory elements of metabolic networks, It's also safety.
Q4:Do you have any other ideas how to deal with safety issues that could be useful for future iGEM competitions? How could parts, devices and systems be made even safer through biosafety engineering?
Set a risk evaluating system, give each BioBrick a safety mark, not by estimating by man, but by a calculating equation.