Difference between revisions of "Team:USTC-Software/Safety"

(Prototype team page)
 
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{USTC-Software}}
 
{{USTC-Software}}
 
<html>
 
<html>
−
<h2>Safety in iGEM</h2>
+
<img src="/wiki/images/5/52/USTC-Software-Safetyhead.jpeg" style="width:100%" >
 +
<div>
  
−
<p>Please visit <a href="https://2015.igem.org/Safety">the main Safety page</a> to find this year's safety requirements & deadlines, and to learn about safe & responsible research in iGEM.</p>
+
</div>
 +
<br><br><br>
 +
<div class="safetycon" style="padding-left: 15%;padding-right: 15%">
  
−
<p>On this page of your wiki, you should write about how you are addressing any safety issues in your project. The wiki is a place where you can <strong>go beyond the questions on the safety forms</strong>, and write about whatever safety topics are most interesting in your project. (You do not need to copy your safety forms onto this wiki page.)</p>
+
<h1>Safety</h1>
 +
<h2>About Our Software</h2><br>
 +
<p>Q1: Are you using the iGEM Software repository at github.com/igemsoftware? If you have instead stored your code elsewhere, please explain where and why you have put it there. If your code is not in the iGEM repository, are you using any version control system such as Git, CVS, or SVN?</p>
 +
<br><p>A1: Yes, finally, we use the iGEM Software repository at <a class="blue" href="https://github.com/igemsoftware/USTC-Software_2015">GitHub</a>. Besides, at the beginning of the project, we use the <a style="color:red">Gitlab</a> for the testing.</p>
 +
<br><hr /><br>
 +
<p>Q2: Does your software store any private data supplied by the user? (For example: the user's name and email address, passwords, DNA sequences, circuit designs, etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this question and move on to question 3.</p>
 +
<br><p>
  
 +
A2: No, we won't store any private data about the users.</p>
 +
<br><hr /><br>
 +
<p>Q3: Does your software let the users create a design by choosing parts/genes from a list/database, such as the Registry? If so, which lists/databases are included? Is there any restriction on which parts/ genes the user can choose?</p>
 +
<br><p>
  
−
<h4>Safe Project Design</h4>
+
A3: No, uses won't choose parts or genes from any database. Instead, we have some built-in gates whose components are derived from the <a class="blue" href="http://parts.igem.org/Main_Page">Registry of Standard Biological Parts</a>.</p>
 +
<br><hr /><br>
 +
<p>Q4: Does your software allow users to submit new data into any public lists or databases? If so, do you check the new data for errors before allowing it to be written?</p>
 +
<br><p>
  
−
<p>Does your project include any safety features? Have you made certain decisions about the design to reduce risks? Write about them here! For example:</p>
+
A4: No, we don't allow users to submit new data into any public lists or databases. However, users could try to create new gates and store them in the local documents supposed that they download our software.</p>
 +
<br><hr /><br>
 +
<p>Q5: Is your team also doing biological work in a wet lab ?
  
−
<ul>
+
</p>
−
<li>Choosing a non-pathogenic chassis</li>
+
<br><p>A5: No, we do not work in any wet lab capacity. We complete our project via computers.</p>
−
<li>Choosing parts that will not harm humans / animals / plants</li>
+
<br><hr /><br>
−
<li>Substituting safer materials for dangerous materials in a proof-of-concept experiment</li>
+
<br><br>
−
<li>Including an "induced lethality" or "kill-switch" device</li>
+
<h2>Safety Form</h2><br>
−
</ul>
+
<p>Q1: What is your chassis organism? Do you plan to experiment with any other organisms, besides your chassis?
  
−
<h4>Safe Lab Work</h4>
+
</p> <br><p>A1: Our track is Software, as a result, we would not submit any parts to the iGEM. Hence, we don't have chassis organism.</p>
 +
<br><hr /><br>
 +
<p>Q2: How will your project work?</p>
 +
<br><p>
  
−
<p>What safety procedures do you use every day in the lab? Did you perform any unusual experiments, or face any unusual safety issues? Write about them here!</p>
+
A2: The Synthetic Biologists could use our software to transform truth table into Logic Gates with definitive biological substance, besides, they could use our Simulation feature to verify whether the result is satisfactory. If the result is good, they could use the DNA sequence to wet lab experiments.</p>
 +
<br><hr /><br>
 +
<p>Q3: What risks does your project pose at the laboratory stage? What actions are you taking to reduce those risks?</p>
 +
<br><p>
  
−
<h4>Safe Shipment</h4>
+
A3: We do not work in any wet lab capacity. We complete our project via computers.</p>
 +
<br><hr /><br>
 +
<p>Q4: How would your project be used in the real world?</p>
 +
<br><p>
  
−
<p>Did you face any safety problems in sending your DNA parts to the Registry? How did you solve those problems?</p>
+
A4: They could use our software to assist them to design gene circuits and validate them by wet lab experiments.</p>
 +
<br><hr /><br>
 +
<p>Q5: What risks might your project pose, if it were fully developed into a real product that real people could use? What future work might you do to reduce those risks?
  
−
 
+
</p>
−
</div>
+
<br><p>A5: This project has been constructed exclusively in silico. Therefore, we anticipate no risks or safety issues from any wet lab experiment. Since we focused only on developing software and did not interacting at all with any biological components, we cannot foresee any new safety risks in combining pathogens in any new and novel way. Working and constructing new and novel biological circuits are at the risk of the experimenter. We won't take responsibility for any kind of hazards or risks arising from the results returned from our work. The safety of our fellow scientists is one of our utmost priorities, hence, any lab that wishes to use SBiDer for their own research purposes must, at all times, keep the biosafety regulations of their own institution and country in mind.</p>
 +
</div>
 +
<script>USTC.load_css_wiki("style/Attributions");</script>
 
</html>
 
</html>
 +
{{USTC-Software/End}}

Latest revision as of 02:54, 19 September 2015




Safety

About Our Software


Q1: Are you using the iGEM Software repository at github.com/igemsoftware? If you have instead stored your code elsewhere, please explain where and why you have put it there. If your code is not in the iGEM repository, are you using any version control system such as Git, CVS, or SVN?


A1: Yes, finally, we use the iGEM Software repository at GitHub. Besides, at the beginning of the project, we use the Gitlab for the testing.



Q2: Does your software store any private data supplied by the user? (For example: the user's name and email address, passwords, DNA sequences, circuit designs, etc.) If yes, please describe what kind of data is stored. If no, skip the rest of this question and move on to question 3.


A2: No, we won't store any private data about the users.



Q3: Does your software let the users create a design by choosing parts/genes from a list/database, such as the Registry? If so, which lists/databases are included? Is there any restriction on which parts/ genes the user can choose?


A3: No, uses won't choose parts or genes from any database. Instead, we have some built-in gates whose components are derived from the Registry of Standard Biological Parts.



Q4: Does your software allow users to submit new data into any public lists or databases? If so, do you check the new data for errors before allowing it to be written?


A4: No, we don't allow users to submit new data into any public lists or databases. However, users could try to create new gates and store them in the local documents supposed that they download our software.



Q5: Is your team also doing biological work in a wet lab ?


A5: No, we do not work in any wet lab capacity. We complete our project via computers.





Safety Form


Q1: What is your chassis organism? Do you plan to experiment with any other organisms, besides your chassis?


A1: Our track is Software, as a result, we would not submit any parts to the iGEM. Hence, we don't have chassis organism.



Q2: How will your project work?


A2: The Synthetic Biologists could use our software to transform truth table into Logic Gates with definitive biological substance, besides, they could use our Simulation feature to verify whether the result is satisfactory. If the result is good, they could use the DNA sequence to wet lab experiments.



Q3: What risks does your project pose at the laboratory stage? What actions are you taking to reduce those risks?


A3: We do not work in any wet lab capacity. We complete our project via computers.



Q4: How would your project be used in the real world?


A4: They could use our software to assist them to design gene circuits and validate them by wet lab experiments.



Q5: What risks might your project pose, if it were fully developed into a real product that real people could use? What future work might you do to reduce those risks?


A5: This project has been constructed exclusively in silico. Therefore, we anticipate no risks or safety issues from any wet lab experiment. Since we focused only on developing software and did not interacting at all with any biological components, we cannot foresee any new safety risks in combining pathogens in any new and novel way. Working and constructing new and novel biological circuits are at the risk of the experimenter. We won't take responsibility for any kind of hazards or risks arising from the results returned from our work. The safety of our fellow scientists is one of our utmost priorities, hence, any lab that wishes to use SBiDer for their own research purposes must, at all times, keep the biosafety regulations of their own institution and country in mind.

University of Science and Technology of China
No.96, Jinzhai Road, Hefei, Anhui, P.R.China
USTC-Software 2015

University of Science and Technology of China

We are here for you

Sponsered by