Team:SUSTC-Shenzhen-A/Safety

From 2012.igem.org

(Difference between revisions)
Line 96: Line 96:
#talkbubble_c1 {
#talkbubble_c1 {
   width: 859px;  
   width: 859px;  
-
   height:400px;  
+
   height:800px;  
-
  background:#EFEFEF;
+
//  background:#EFEFEF;
-
//  background:#ffffff;
+
  background:#ffffff;
   position: relative;
   position: relative;
   -moz-border-radius:    0px;  
   -moz-border-radius:    0px;  
Line 160: Line 160:
<body >
<body >
-
<table width="899" border="0" cellspacing="10px" cellpadding="10px">
 
-
        <tr>
 
-
          <td valign="top"><div id="talkbubble_a">
 
-
<p class="title"><strong>Project Overview</strong></p>
 
-
 
-
 
-
 
-
<div id="talkbubble_b">           
 
-
</div>
 
-
</td>
 
-
 
-
 
-
        <td><div id="talkbubble1"><div class="sidebar_box"><div class="sidebar_box_top"></div>
 
-
<div class="sidebar_box_content">           
 
-
<p class="title1">Project</p>
 
-
<img src="https://static.igem.org/mediawiki/2012/c/c9/Devidingline_side.jpg">
 
-
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Project"><strong>overview</strong></a></p>
 
-
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Biosearch"><strong>Biosearch</strong></a></p>
 
-
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Biosearch_Tutorial">Tutorial</a></p>
 
-
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Biosearch_Intro">Introduction</a></p>
 
-
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Biodesign"><strong>Biodesign</strong></a></p>
 
-
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Biodesign_Tutorial">Tutorial</a></p>
 
-
<p>&nbsp;&nbsp;<a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Biodesign_Intro">Introduction</a></p>
 
-
<p><a href="https://2012.igem.org/Team:SUSTC-Shenzhen-A/Sponsor"><strong>Sponsor</strong></a></p>
 
-
<div class="sidebar_box_bottom"></div>                   
 
-
          </div>
 
-
</td>
 
-
            </tr>
 
-
</table>
 
<table width="899" border="0" cellspacing="10" cellpadding="10">
<table width="899" border="0" cellspacing="10" cellpadding="10">
   <tr>
   <tr>
     <td><div id="talkbubble_c1">
     <td><div id="talkbubble_c1">
-
 
+
<p class="title"><strong>Safety</strong></p>
 +
<p>&nbsp;</p>
 +
<p>&nbsp;</p>
 +
<p>As a software team, our team work does not include any wet lab part. Nonetheless, we take safety into account as well as measures from a variety of aspects.</p>
 +
<p>&nbsp;</p>
 +
<p>1 Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?</p>
 +
<p>&nbsp;</p>
 +
<p>Researcher safety: </p>
 +
<p>As a team working out software program, our main problem of this part is the radiation-effect of computers while all the members are programming. For health of programmers and ergonomically working, we formulate several rules such as limitation of working time (the upper limit is 8 hour) and team members need to relax their eyes by taking a walk of view scenes every hour.  </p>
 +
<p>&nbsp;</p>
 +
<p>Public safety: </p>
 +
<p>Our projects are set in iPhone OS, whose underlying code can't be changed by user, leading to almost antivirus. Besides, with our hard work and the serious examine and verify of app store,  the possible error has been estimated and reduced to guarantee user informations. We also aware to show a concise and academic user interface which has no academic irrelevant content.</p>
 +
<p>&nbsp;</p>
 +
<p>Environmental safety：</p>
 +
<p>We solemn promise that we didn't have or create any experiment product which can effect the environment.</p>
 +
<p>&nbsp;</p>
 +
<p>&nbsp;</p>
 +
<p>2 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?</p>
 +
<p>&nbsp;</p>
 +
<p>As a software team, we didn't make any BioBrick. and no safety issues happened from this.</p>
 +
<p>&nbsp;</p>
 +
<p>&nbsp;</p>
 +
<p>3 Is there a local biosafety group, committee, or review board at your institution?</p>
 +
<p>If yes, what does your local biosafety group think about your project?</p>
 +
<p>If no, which specific biosafety rules or guidelines do you have to consider in your country?</p>
 +
<p>&nbsp;</p>
 +
<p>No biosafety group or committee protested our project, but we do consult our professors of Department of Biology during the programming progress.</p>
 +
<p>&nbsp;</p>
 +
<p>&nbsp;</p>
 +
<p>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?</p>
 +
<p>&nbsp;</p>
 +
<p>For safety development in dry lab, we notice that there are few safety rules for programmers. As software is also an essential part of bio research, the safety of both programmers and program need to be concerned. </p>
 +
<p>For safety development in wet lab, the copyright of Biobrick is also need to be protected. </p>
 +
<p>&nbsp;</p>
 +
<p>&nbsp;</p>
</div>
</div>
</td>
</td>

Revision as of 15:42, 6 September 2012

Barnew.jpg

Safety

 

 

As a software team, our team work does not include any wet lab part. Nonetheless, we take safety into account as well as measures from a variety of aspects.

 

1 Would any of your project ideas raise safety issues in terms of: researcher safety, public safety, or environmental safety?

 

Researcher safety:

As a team working out software program, our main problem of this part is the radiation-effect of computers while all the members are programming. For health of programmers and ergonomically working, we formulate several rules such as limitation of working time (the upper limit is 8 hour) and team members need to relax their eyes by taking a walk of view scenes every hour.

 

Public safety:

Our projects are set in iPhone OS, whose underlying code can't be changed by user, leading to almost antivirus. Besides, with our hard work and the serious examine and verify of app store, the possible error has been estimated and reduced to guarantee user informations. We also aware to show a concise and academic user interface which has no academic irrelevant content.

 

Environmental safety：

We solemn promise that we didn't have or create any experiment product which can effect the environment.

 

 

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

 

 

3 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?

 

No biosafety group or committee protested our project, but we do consult our professors of Department of Biology during the programming progress.

 

 

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?

 

For safety development in dry lab, we notice that there are few safety rules for programmers. As software is also an essential part of bio research, the safety of both programmers and program need to be concerned.

For safety development in wet lab, the copyright of Biobrick is also need to be protected.

 

 
Footbar.jpg

Retrieved from "http://2012.igem.org/Team:SUSTC-Shenzhen-A/Safety"