Team:USTC-Software/safety

From 2011.igem.org

(Difference between revisions)
 
(16 intermediate revisions not shown)
Line 1: Line 1:
__NOTOC__
__NOTOC__
-
{{:Team:USTC-Software/temp}}
+
{{:Team:USTC-Software/header}}
-
 
+
<html xmlns="http://www.w3.org/1999/xhtml">
<html xmlns="http://www.w3.org/1999/xhtml">
-
 
-
<head>
 
-
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 
-
<title>Team:USTC-Software - 2011.igem.org/safety</title>
 
-
<meta name="description" content="safety"/>
 
-
<meta name="keywords" content="USTC-Software,iGEM,synthetic biology"/>
 
-
<meta name="author" content="Ao Xu">
 
-
<meta name="copyright" content="Copyright (c) 2011 iGEM USTC Software" />
 
-
 
-
<style type="text/css">
 
-
 
-
body {
 
-
margin: 0;
 
-
padding: 0;
 
-
line-height: 1.5em;
 
-
font-family: Georgia, "Times New Roman", Times, serif;
 
-
font-size: 12px;
 
-
color: #555a4a;
 
-
    background: #a0c73f;
 
-
}
 
-
 
-
a:link, a:visited { color: #0683ab; text-decoration: none; font-weight: normal; }
 
-
a:active, a:hover { color: #0683ab; text-decoration: underline; }
 
-
 
-
img { margin: 0px; padding: 0px; border: none; }
 
-
 
-
#header_wrapper {
 
-
width: 100%;
 
-
height: 265px;
 
-
background: url(https://static.igem.org/mediawiki/2011/0/04/USTC_Software_header.jpg) no-repeat top center;
 
-
}
 
-
 
-
#header {
 
-
position: relative;
 
-
width: 980px;
 
-
height: 265px;
 
-
padding: 0 10px;
 
-
margin: 0 auto;
 
-
background: url(https://static.igem.org/mediawiki/2011/0/04/USTC_Software_header.jpg) no-repeat top center;
 
-
}
 
-
 
-
/* site title */
 
-
 
-
#header  #site_title {
 
-
float: left;
 
-
width: 180px;
 
-
padding: 33px 0;
 
-
}
 
-
 
-
#site_title h1 {
 
-
margin: 0;
 
-
padding: 3px;
 
-
font-family:"Times New Roman", Times, serif;
 
-
color:#000;
 
-
font-size:24px;
 
-
}
 
-
 
-
 
-
#site_title h1 a {
 
-
margin: 0px;
 
-
padding: 0px;
 
-
font-size: 30px;
 
-
color: #ffffff;
 
-
font-weight: bold;
 
-
text-decoration: none;
 
-
}
 
-
 
-
#site_title h1 a:hover {
 
-
font-weight: bold;
 
-
text-decoration: none;
 
-
}
 
-
 
-
#site_title h1 a span {
 
-
display: block;
 
-
margin-left: 2px;
 
-
font-size: 14px;
 
-
color: #416902;
 
-
font-weight: bold;
 
-
letter-spacing: 2px;
 
-
}
 
-
 
-
/* end of site title */
 
-
 
-
/* ---------- Navigation ---------- */
 
-
 
-
ul  {
 
-
      list-style-image: none;
 
-
}
 
-
 
-
#nav {
 
-
float: right;
 
-
font-family: Arial, Helvetica, sans-serif;
 
-
font-weight: bold;
 
-
font-size: 12px;
 
-
padding-top: 70px;
 
-
height: 43px;
 
-
}
 
-
 
-
#nav .last {
 
-
padding-right: 2px;
 
-
background-image:url(https://static.igem.org/mediawiki/2011/5/59/USTC_Software_nav_button_sep.jpg);
 
-
background-repeat:no-repeat;
 
-
background-position:right;
 
-
}
 
-
 
-
#nav, #nav ul{
 
-
margin:0;
 
-
padding:0;
 
-
list-style-type:none;
 
-
list-style-position:outside;
 
-
position:relative;
 
-
line-height:1.5em;
 
-
}
 
-
 
-
#nav .on {
 
-
color:#fff !important;
 
-
background-image: url(https://static.igem.org/mediawiki/2011/0/00/USTC_Software_nav_button_bg.jpg) !important;
 
-
background-position: bottom left !important;
 
-
}
 
-
 
-
#nav a:link, #nav a:active, #nav a:visited{
 
-
    display:block;
 
-
    padding: 14px 35px;
 
-
    color:#a5a5a5;
 
-
    text-decoration:none;
 
-
text-transform: uppercase;
 
-
background-image: url(https://static.igem.org/mediawiki/2011/0/00/USTC_Software_nav_button_bg.jpg);
 
-
background-position: top left;
 
-
}
 
-
 
-
#nav a:hover {
 
-
    color:#fff;
 
-
background-image: url(https://static.igem.org/mediawiki/2011/0/00/USTC_Software_nav_button_bg.jpg);
 
-
background-position: bottom left;
 
-
}
 
-
 
-
#nav li{
 
-
    float:left;
 
-
    position:relative;
 
-
 
-
}
 
-
 
-
#nav ul {
 
-
    position:absolute;
 
-
    width:13em;
 
-
    top:3.8em;
 
-
    display:none;
 
-
z-index: 1;
 
-
}
 
-
 
-
#nav li ul a {
 
-
    width:9em;
 
-
    float:left;
 
-
background-color: #2e2e2e;
 
-
background-image: none !important;
 
-
}
 
-
 
-
#nav li ul a:hover {
 
-
background-color: #292929;
 
-
}
 
-
 
-
#nav ul ul{
 
-
top:auto;
 
-
}
 
-
 
-
#nav li ul ul {
 
-
    left:12em;
 
-
    margin:0px 0 0 10px;
 
-
    }
 
-
 
-
#nav li:hover ul ul, #nav li:hover ul ul ul, #nav li:hover ul ul ul ul{
 
-
    display:none;
 
-
    }
 
-
 
-
#nav li:hover ul, #nav li li:hover ul, #nav li li li:hover ul, #nav li li li li:hover ul{
 
-
    display:block;
 
-
    }
 
-
 
-
/*end of nav*/
 
-
 
-
/* content_wrapper */
 
-
 
-
#content {
 
-
        background-color:#a0c73f;
 
-
        width:auto;
 
-
}
 
-
 
-
#content_wrapper {
 
-
width: 920px;
 
-
margin: 0 auto;
 
-
padding: 30px 40px;
 
-
background: url(https://static.igem.org/mediawiki/2011/b/bc/USTC_Software_content.jpg) repeat-y;
 
-
}
 
-
 
-
#content_wrapper h1 {
 
-
color: #3a5909;
 
-
font-size: 24px;
 
-
padding: 0 0 60px 20px;
 
-
background: url(https://static.igem.org/mediawiki/2011/4/4d/USTC_Software_header_bg.png) no-repeat bottom left;
 
-
}
 
-
 
-
#content_wrapper p {
 
-
font-family: Verdana, Arial;
 
-
font-size: 14px;
 
-
}
 
-
 
-
#content_wrapper_bottom {
 
-
width: 1000px;
 
-
height: 15px;
 
-
margin: 0 auto;
 
-
background: url(https://static.igem.org/mediawiki/2011/a/a5/USTC_Software_content_bottom.jpg) no-repeat;
 
-
    background-color: #a0c73f;
 
-
}
 
-
 
-
/* end of content_wrapper */
 
-
 
-
/* footer */
 
-
 
-
#mfooter {
 
-
width: 980px;
 
-
margin: 0 auto;
 
-
padding: 30px 10px;
 
-
text-align: center;
 
-
color: #333333;
 
-
    background-color: #a0c73f;
 
-
}
 
-
 
-
#mfooter a {
 
-
color:#000;
 
-
}
 
-
 
-
#mfooter .mfooter_menu {
 
-
margin: 0 0 10px 0;
 
-
padding: 0px;
 
-
list-style: none;
 
-
}
 
-
 
-
.mfooter_menu li {
 
-
margin: 0px;
 
-
padding: 0 20px;
 
-
display: inline;
 
-
border-right: 1px solid #000000;
 
-
}
 
-
 
-
.mfooter_menu .last_menu {
 
-
border: none;
 
-
}
 
-
 
-
#footer-box { background-color: transparent; border:none;} /*This is important!*/
 
-
 
-
#totop_box {
 
-
position:fixed;
 
-
width: 77px;
 
-
height: 75px;
 
-
bottom: 21px;
 
-
right: 15px;
 
-
}
 
-
 
-
#totop_box form {
 
-
width: 280px;
 
-
height: 27px;
 
-
margin: 0;
 
-
padding: 25px 0 0 0;
 
-
}
 
-
 
-
#to_org_box {
 
-
position:fixed;
 
-
width: 77px;
 
-
height: 75px;
 
-
bottom: 21px;
 
-
right: 105px;
 
-
}
 
-
 
-
#to_org_box form {
 
-
width: 280px;
 
-
height: 27px;
 
-
margin: 0;
 
-
padding: 25px 0 0 0;
 
-
}
 
-
/* end of footer*/
 
-
 
-
.ul_p{
 
-
font-family: Verdana, Arial;
 
-
font-size: 14px;
 
-
}
 
-
 
-
</style>
 
-
 
-
</head>
 
-
 
<body>
<body>
-
 
-
<div id="header_wrapper">
 
-
 
-
    <div id="header">
 
-
   
 
-
  <div id="site_title">
 
-
            <h1><img src="https://static.igem.org/mediawiki/2011/b/b8/USTC_Software_iGEM_logo.jpg"  width="173" height="150" alt="iGEM" /> </br> </br> USTC-Software </h1>
 
-
        </div>
 
-
       
 
-
<!-- navigation -->
 
-
<ul id="nav">
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software">Home</a></li>
 
-
 
-
   
 
-
    <li><a href="https://2011.igem.org/Team:USTC-Software/project">Project</a>
 
-
<ul>
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/documents">Documents</a></li>
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/models">Models</a></li>
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/views">Views</a></li>
 
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/tech&algo">Technology & Algorithm</a></li>
 
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/tutorial">Tutorial</a></li>
 
-
</ul>
 
-
</li>
 
-
 
-
 
-
                <li><a href="https://2011.igem.org/Team:USTC-Software/notebook">Notebook</a>
 
-
                        <ul>
 
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/judging">Judging Criteria</a></li>
 
-
                        </ul>
 
-
                </li>
 
-
 
-
<li><a href="https://2011.igem.org/Team:USTC-Software/team">Team</a>
 
-
                          <ul>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/members">members</a></li>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/collaboration">collaboration</a></li>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/attribution">attribution</a></li>
 
-
                            <li><a href="https://2011.igem.org/Team:USTC-Software/acknowledgements">acknowledgements</a></li>
 
-
                          </ul>
 
-
                </li>
 
-
 
 
-
  <li><a class="on" href="https://2011.igem.org/Team:USTC-Software/human practice">Human practice</a>             
 
-
  <ul>
 
-
    <li><a href="https://2011.igem.org/Team:USTC-Software/safety">safety</a></li>
 
-
    <li><a href="https://2011.igem.org/Team:USTC-Software/meetup">meetup</a></li>
 
-
  </ul>
 
-
</li> 
 
-
 
-
<li><a class="last" href="https://2011.igem.org/Team:USTC-Software/download">Download</a></li>
 
-
           
 
-
</ul>
 
-
<!-- // end of navigation -->
 
-
     
 
-
      <div class="cleaner"></div>
 
-
    </div> <!-- end of header -->
 
-
 
-
</div>
 
-
<!-- end of header_wrapper -->
 
-
 
<div id="content_wrapper">
<div id="content_wrapper">
-
           <h1> Safety         </h1>
+
           <h2> Safety</h2>
           <table width="912" height="205" border="0">
           <table width="912" height="205" border="0">
             <tr>
             <tr>
Line 368: Line 19:
           and engineering. However, it may cause intentional or accidental harm to humans, agriculture or the environment. </p>
           and engineering. However, it may cause intentional or accidental harm to humans, agriculture or the environment. </p>
            
            
-
           <p>As a software project our work does not raise many safety issues typically associated with biological wet-lab project. Nevertheless we  
+
           <p>As a software project our work does not raise many safety issues typically associated with biological wet-lab project. Nevertheless we will explicitly present the answer to the four safety questions here:
-
            will explicitly present the answer to the four safety questions here:
+
</p>
</p>
            
            
Line 380: Line 30:
            
            
           <p>A:i.Safety for researchers <br/>
           <p>A:i.Safety for researchers <br/>
-
           The development of software requires many hours` work in front of a computer, which is not ergonomic to programmers, as working  
+
           The development of software requires many hours` work in front of a computer, which is not ergonomic to programmers, as working in such environment may cause much exhaust and stress. Therefore, we made a series of rules to guarantee that we can take regular breaks. Furthermore, every time our programmers go to wet labs, to work with our wet team members, we make sure that they are  
-
          in such environment may cause much exhaust and stress. Therefore, we made a series of rules to guarantee that we can take regular  
+
properly equipped and supervised by a well-trained staff.</p>
-
          breaks. Furthermore, every time our programmers go to wet labs, to work with our wet team members, we make sure that they are  
+
-
          properly equipped and supervised by a well-trained staff.</p>
+
            
            
           <p>ii.Safety for public<br/>
           <p>ii.Safety for public<br/>
-
           <em>Lachesis</em>, is ONLY for research use, no medical or diagnostic use for applications of novel BioBrick constructs
+
            
-
          generated through our software, and no military (defense or combat) application will be allowed.</p>
+
 
 +
Because of software bugs, synthetic systems designed and produced by users based on <em>Lachesis</em> could be incongruous from the expectation. Hence, causing latent threat to the public. This kind of bug should be evaded through debugging test while warning users of the relevant risk.</p>
            
            
           <p>iii.Safety for environment<br/>
           <p>iii.Safety for environment<br/>
Line 412: Line 61:
           <i> <a href="http://home.ustc.edu.cn/~feicaiyi/people.html">Pro.Haiyan Liu</a>,</i>
           <i> <a href="http://home.ustc.edu.cn/~feicaiyi/people.html">Pro.Haiyan Liu</a>,</i>
           professor of <a href="http://home.ustc.edu.cn/~feicaiyi/index.html">computational biology </a>
           professor of <a href="http://home.ustc.edu.cn/~feicaiyi/index.html">computational biology </a>
-
           in USTC.)</p>
+
           in USTC.) They approve our project of not having safety problems.</p>
-
         
+
-
          <p>The safety guidelines could be obeyed sufficiently in our working environment during the project.</p>
+
            
            
           <p>4. Do you have any other ideas how to deal with safety issues that  
           <p>4. Do you have any other ideas how to deal with safety issues that  
Line 424: Line 71:
       <img class="logo" src="https://static.igem.org/mediawiki/2011/7/74/USTC_Software_biohaz.gif" width="174" height="168" alt="biohazardsymbol" /> </a>
       <img class="logo" src="https://static.igem.org/mediawiki/2011/7/74/USTC_Software_biohaz.gif" width="174" height="168" alt="biohazardsymbol" /> </a>
            
            
-
           <p>A:i.Yes, A lot of work is expected to be completed in dry lab for the safety issues,  
+
           <p>A:i.Yes, A lot of work is expected to be completed in dry lab for the safety issues, besides what have been finished now. For example, the censorship and caution function of danger sequence and word affiliated to software and database to prevent hidden security threat. Meanwhile, in order to prevent unanticipated danger, openness of the project can be enhanced to encourage supervision.</p>
-
          besides what have been finished now. For example, safety issues for intellectual property should be taken into consideration.
+
           <p>ii.Our software is favorable for the users' anticipation of behavior of parts, devices and systems. Its robust analysis is an important part of biosafety engineering. Therefore, our software can efficiently reduce the possibility of the security problem occurred in the test. Benefit from this, we would be one step closer in integrating with the environment.
-
          Thus we suggest that all source codes and documentation should be granted with copyrights before sharing.</p>
+
</p>
-
           <p>ii.With more detailed and better characterized parts, synthetic biology can be an extremely controlled and safe experience.
+
 
-
          Benefit from this, we would be one step closer in integrating with the environment.</p>   
+
 
-
   <p>&nbsp;</p>
+
  <br/>
-
  <p>&nbsp;</p>
+
   <h2>Security</h2>
-
       
+
 
 +
<p><strong>Preventing Malign Use</strong> :</p>
 +
<p><em>Lachesis</em>, is ONLY for research use, no medical or diagnostic use for applications of novel BioBrick constructs generated through our software, and no military (defense or combat) application will be allowed.</p>
 +
 
 +
<p><strong>Working Within the Law</strong> :</p>
 +
 
 +
<p>There is an international treaty that prohibits the use of biology for hostile or malign purposes. If you intend to use biology to do harm you will be breaking international law.</p>
 +
 
 +
<p>Many countries also have their own laws about using biology in this way. They are increasingly backed up with regulations and guidelines that are relevant to the day to day functioning of a laboratory. It is important that we are all familiar with the rules that cover our work. Whilst we are commonly taught how we should work safely, we are less often taught how to work securely.</p>
 +
 
 +
<p>Here we provide a gateway to details of <a href="http://www.unog.ch/80256EDD006B8954/(httpAssets)/BBCCCC514AA386A3C1257355003AA13D/$file/BWC_NID_Report-070912.htm#chi">Laws in China relevant to work with biological agents</a>. We hoping that you will use this to make sure you know all you need to know about staying out of trouble.</p>  
 +
 
</div>  
</div>  

Latest revision as of 13:28, 23 October 2011


Team:USTC-Software - 2011.igem.org

Safety


Synthetic Biology is a revolutionary field which combines several disciplines such as biology, chemistry, mathematics, physics and engineering. However, it may cause intentional or accidental harm to humans, agriculture or the environment.

As a software project our work does not raise many safety issues typically associated with biological wet-lab project. Nevertheless we will explicitly present the answer to the four safety questions here:

1.Q: Would any of your project ideas raise safety issues in terms of:

  • researcher safety,
  • public safety, or
  • environmental safety?

A:i.Safety for researchers
The development of software requires many hours` work in front of a computer, which is not ergonomic to programmers, as working in such environment may cause much exhaust and stress. Therefore, we made a series of rules to guarantee that we can take regular breaks. Furthermore, every time our programmers go to wet labs, to work with our wet team members, we make sure that they are properly equipped and supervised by a well-trained staff.

ii.Safety for public
Because of software bugs, synthetic systems designed and produced by users based on Lachesis could be incongruous from the expectation. Hence, causing latent threat to the public. This kind of bug should be evaded through debugging test while warning users of the relevant risk.

iii.Safety for environment
We do not perform any work that put the environment at any risk.

2.Q: 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?

A: Lachesis, does not create any new BioBrick parts (or devices) in reality, and the BioBricks we used are only encoding non-hazardous genes. No safety issues would arouse as a result.

3.Q: 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?

A:Yes. School of Life Sciences, University of Science and Technology of China is aware of our project and we are working under the instruction of our instructors. ( Pro.Jiong Hong , associate professor of synthetic biology lab in USTC. Pro.Haiyan Liu, professor of computational biology in USTC.) They approve our project of not having safety problems.

4. 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?

A:i.Yes, A lot of work is expected to be completed in dry lab for the safety issues, besides what have been finished now. For example, the censorship and caution function of danger sequence and word affiliated to software and database to prevent hidden security threat. Meanwhile, in order to prevent unanticipated danger, openness of the project can be enhanced to encourage supervision.

ii.Our software is favorable for the users' anticipation of behavior of parts, devices and systems. Its robust analysis is an important part of biosafety engineering. Therefore, our software can efficiently reduce the possibility of the security problem occurred in the test. Benefit from this, we would be one step closer in integrating with the environment.


Security

Preventing Malign Use :

Lachesis, is ONLY for research use, no medical or diagnostic use for applications of novel BioBrick constructs generated through our software, and no military (defense or combat) application will be allowed.

Working Within the Law :

There is an international treaty that prohibits the use of biology for hostile or malign purposes. If you intend to use biology to do harm you will be breaking international law.

Many countries also have their own laws about using biology in this way. They are increasingly backed up with regulations and guidelines that are relevant to the day to day functioning of a laboratory. It is important that we are all familiar with the rules that cover our work. Whilst we are commonly taught how we should work safely, we are less often taught how to work securely.

Here we provide a gateway to details of Laws in China relevant to work with biological agents. We hoping that you will use this to make sure you know all you need to know about staying out of trouble.