Team:USTC-Software/safety

From 2011.igem.org

(Difference between revisions)
Line 307: Line 307:
<li><a href="https://2011.igem.org/Team:USTC-Software">Home</a></li>
<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>
     <li><a href="https://2011.igem.org/Team:USTC-Software/project">Project</a>
<ul>
<ul>
-
<li><a href="https://2011.igem.org/Team:USTC-Software/documents">Documents Parser</a></li>
+
<li><a href="https://2011.igem.org/Team:USTC-Software/documents">Documents Parser & Models </a></li>
-
<li><a href="https://2011.igem.org/Team:USTC-Software/models">Models</a></li>
+
<li><a href="#">Views</a>
-
    <li><a href="#">Views</a>
+
                                  <ul>
-
                            <ul>
+
                                      <li><a href="https://2011.igem.org/Team:USTC-Software/aview">Assembly View</a></li>
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/aview">Assembly View</a></li>
+
                                      <li><a href="https://2011.igem.org/Team:USTC-Software/bview">Behavior View</a></li>
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/bview">Behavior View</a></li>
+
                                      <li><a href="https://2011.igem.org/Team:USTC-Software/nview">Network View</a></li>                     
-
                                 <li><a href="https://2011.igem.org/Team:USTC-Software/nview">Network View</a></li>                      
+
                                  </ul>
-
                            </ul>
+
                                </li>
-
                                <li><a href="https://2011.igem.org/Team:USTC-Software/tech&algo">Technology & Algorithm</a></li>
+
 
 +
                                 <li><a href="#">Technology & Algorithm</a>
 +
                                  <ul>
 +
                                    <li><a href="https://2011.igem.org/Team:USTC-Software/parameter">parameter analysis</a></li>
 +
                                    <li><a href="https://2011.igem.org/Team:USTC-Software/model">MoDeL</a></li>
 +
                                  </ul>
 +
                                </li>
 +
                                   
                                 <li><a href="https://2011.igem.org/Team:USTC-Software/tutorial">Tutorial & Demo</a></li>
                                 <li><a href="https://2011.igem.org/Team:USTC-Software/tutorial">Tutorial & Demo</a></li>
</ul>
</ul>

Revision as of 11:43, 5 October 2011


Team:USTC-Software - 2011.igem.org/safety

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

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.)

The safety guidelines could be obeyed sufficiently in our working environment during the project.

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, safety issues for intellectual property should be taken into consideration. Thus we suggest that all source codes and documentation should be granted with copyrights before sharing.

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.