Difference between revisions of "Template:SYSU-Software/statics/html/Safety/DryLabSafety.html"

(Created page with "<div class="page-container"> <div class="header1"> Safety </div> <div class="header2"> Dry-lab Safety </div> <div class="header3">Q:What about the biosafety matters to...")
 
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
<div class="page-container">
 
<div class="page-container">
 +
  <div class="last-page-identify" data-value="29"></div>
 
   <div class="header1"> Safety </div>
 
   <div class="header1"> Safety </div>
 
   <div class="header2"> Dry-lab Safety </div>
 
   <div class="header2"> Dry-lab Safety </div>
  
−
   <div class="header3">Q:What about the biosafety matters to notice while using CO-RAD?</div>
+
   <div class="header3">Q: In biosafety, what items should we pay attention to?</div>
 
   <div class="content">
 
   <div class="content">
−
     A: As a responsible iGEM team, we need to consider about safety level of circuits designed in our collaboration
+
     A: The following two principles should be concerned. Firstly, choose a safe chassis for all your circuits.
−
    platform. There are two major parts in iGEM we need to consider about. First is to choose a safe enough Chassis to
+
     Secondly, only safe parts are available for your design. For more information, please refer to the GEM safety
−
     redesign the circuits. Second, we need a safe enough Parts as material to make a Gene blueprint that benefits human
+
     community announced <a href="https://2018.igem.org/Safety/White_List">2018 White List</a>.
−
     beings. Therefore, this year, iGEM safety community announced <a href="https://2018.igem.org/Safety/White_List">2018
+
−
      White List</a>.
+
 
   </div>
 
   </div>
  
−
   <div class="header3">Q:What about the source of parts and its safety level in CO-RAD?</div>
+
   <div class="header3">Q: What about the safety level of your parts in CO-RAD?</div>
 
   <div class="content">
 
   <div class="content">
−
     A: The source information is stored in our database including the original chassis and the adapted chassis. The
+
     A: Parts safety levels were seriously evaluated based on their original and applied chassis information.
−
     database has been screened manually.For safety in use, we only collected Parts belonged to Risk Group 1 &2, and
+
     Specifically, we rid parts in Risk Group 3 & 4, and graded the rest parts into 3 safety level according to the
−
    prohibited Parts in Risk Group 3 & 4. For the rest parts, we divided them into three three safety level which is
+
     following principles:
−
     judged by two criteria:
+
 
     <ul>
 
     <ul>
 
       <li>1 level: no "Red Flag" tag, belonging Chassis belongs to Risk Group 1.</li>
 
       <li>1 level: no "Red Flag" tag, belonging Chassis belongs to Risk Group 1.</li>
Line 25: Line 23:
 
   </div>
 
   </div>
 
   <img src="https://static.igem.org/mediawiki/2018/2/21/T--SYSU-Software--safety.png" style="width: 50%">
 
   <img src="https://static.igem.org/mediawiki/2018/2/21/T--SYSU-Software--safety.png" style="width: 50%">
−
   <div class="caption">Figure 1: Safety group distribution</div>
+
   <div class="caption">Figure 2: Safety group distribution</div>
  
−
   <div class="header3">Q:Are those Parts stored in the database of CO-RAD safe enough?</div>
+
   <div class="header3">Q: Can safety be ganranteed when we use the parts?</div>
 
   <div class="content">
 
   <div class="content">
−
     A: iGEM safety community has already accessed a series of Parts with Biosafety danger, and the 'Red Flag' tag was
+
     A: Most parts in our database are in Risk 1, which can be used without any concerns, while parts in Risk 2 & 3 may
−
    set in Registry. BY manually screening all Parts in database, we found there were only few that are tagged with
+
     lead to potential danger. To guarantee the safety of your design, CO-RAD will automatically display the safety
−
     'Red Flag'. For safety in use, we will alert users whiling using these parts.
+
    level of parts when referred. Green, yellow, red represent Risk 1, 2, 3 respectively.
 
   </div>
 
   </div>
 
   <img src="https://static.igem.org/mediawiki/2018/e/e4/T--SYSU-Software--Warning.png" style="width: 25%">
 
   <img src="https://static.igem.org/mediawiki/2018/e/e4/T--SYSU-Software--Warning.png" style="width: 25%">
−
   <div class="caption">Figure 2: Warning of dangerous parts</div>
+
   <div class="caption">Figure 3: Warning of dangerous parts</div>
  
−
   <div class="header3">Q:By cooperating with CO-RAD, will there be any potential dangerous operation?</div>
+
   <div class="header3">Q: How can users suggest the potential safety issues of others' circuit design?</div>
 
   <div class="content">
 
   <div class="content">
 
     A:<ol>
 
     A:<ol>
−
       <li>We believe that collaboration is a good way to avoid potential danger. By adding a comment to the the circuit,  
+
       <li>We attach importance to efficient collabaration in finding potential safety issues. Via comments, users can
−
        users can send their partners warnings.</li>
+
        alert their partners in time. (Figure 4)
−
        <img src="https://static.igem.org/mediawiki/2018/0/0c/T--SYSU-Software--save_comment.png" />
+
      </li>
−
       <div class="caption">Figure 3: Comment on the design</div>
+
      <img src="https://static.igem.org/mediawiki/2018/0/0c/T--SYSU-Software--save_comment.png" />
−
       <li>Meanwhile, to prevent users from adding dangerous chassis mistakely, chassis should be selected
+
       <div class="caption">Figure 4: Comment on the design</div>
−
         before collaboration begins. It allows other users to capture unexpected behaviours while cooperating.</li>
+
       <li>Meanwhile, in order to prevent users from using dangerous chassis by mistake, users need to select chassis
 +
         before sharing their circuits, and other users can view its information. (Figure 5) </li>
 
       <img src="https://static.igem.org/mediawiki/2018/8/83/T--SYSU-Software--chassis.png">
 
       <img src="https://static.igem.org/mediawiki/2018/8/83/T--SYSU-Software--chassis.png">
−
       <div class="caption">Figure 4: Select chassis</div>
+
       <div class="caption">Figure 5: Select chassis</div>
 
     </ol>
 
     </ol>
 
   </div>
 
   </div>
 
</div>
 
</div>

Latest revision as of 19:33, 17 October 2018

Safety
Dry-lab Safety
Q: In biosafety, what items should we pay attention to?
   A: The following two principles should be concerned. Firstly, choose a safe chassis for all your circuits.
   Secondly, only safe parts are available for your design. For more information, please refer to the GEM safety
   community announced <a href="https://2018.igem.org/Safety/White_List">2018 White List</a>.
Q: What about the safety level of your parts in CO-RAD?
   A: Parts safety levels were seriously evaluated based on their original and applied chassis information.
   Specifically, we rid parts in Risk Group 3 & 4, and graded the rest parts into 3 safety level according to the
   following principles:
  • 1 level: no "Red Flag" tag, belonging Chassis belongs to Risk Group 1.
  • 2 level: no "Red Flag" tag, belonging Chassis belongs to Risk Group 2.
  • 3 level: with "Red Flag" tag.
 <img src="T--SYSU-Software--safety.png" style="width: 50%">
Figure 2: Safety group distribution
Q: Can safety be ganranteed when we use the parts?
   A: Most parts in our database are in Risk 1, which can be used without any concerns, while parts in Risk 2 & 3 may
   lead to potential danger. To guarantee the safety of your design, CO-RAD will automatically display the safety
   level of parts when referred. Green, yellow, red represent Risk 1, 2, 3 respectively.

 <img src="T--SYSU-Software--Warning.png" style="width: 25%">
Figure 3: Warning of dangerous parts
Q: How can users suggest the potential safety issues of others' circuit design?
A:
  1. We attach importance to efficient collabaration in finding potential safety issues. Via comments, users can alert their partners in time. (Figure 4) 
    2.      <img src="T--SYSU-Software--save_comment.png" />
    Figure 4: Comment on the design
  2. Meanwhile, in order to prevent users from using dangerous chassis by mistake, users need to select chassis before sharing their circuits, and other users can view its information. (Figure 5) 
    3.      <img src="T--SYSU-Software--chassis.png">
    Figure 5: Select chassis