Difference between revisions of "Team:Imperial College/IHP"

Line 20: Line 20:
 
<p1>In order to identify potential issues and applications of our system, we engaged in direct dialogue with stakeholders, as per the <b><a href="https://2018.igem.org/Team:Imperial_College/scicomm">Communication Strategies Guide (CSG)</a></b>. This approach allowed us to devise potential applications for our system, as well as correct design flaws such as the use of toxic pyocyanin as a redox-cycling molecule. This led us to repurpose our system with a safer molecule (phenazine methosulfate -PMS-), which also resulted in being a cheaper inducer molecule even when compared with broadly used inducers.  We also identified that internal friction in teams is a common issue as proven to us by our experience as well as a survey that we conducted amongst 67 iGEM members from 14 other teams. To address this issue we developed our <a href="https://2018.igem.org/Team:Imperial_College/ltat"><b>team communication app (LTAT)</b></a> to help improve team communication both internally and in other teams. </p1>
 
<p1>In order to identify potential issues and applications of our system, we engaged in direct dialogue with stakeholders, as per the <b><a href="https://2018.igem.org/Team:Imperial_College/scicomm">Communication Strategies Guide (CSG)</a></b>. This approach allowed us to devise potential applications for our system, as well as correct design flaws such as the use of toxic pyocyanin as a redox-cycling molecule. This led us to repurpose our system with a safer molecule (phenazine methosulfate -PMS-), which also resulted in being a cheaper inducer molecule even when compared with broadly used inducers.  We also identified that internal friction in teams is a common issue as proven to us by our experience as well as a survey that we conducted amongst 67 iGEM members from 14 other teams. To address this issue we developed our <a href="https://2018.igem.org/Team:Imperial_College/ltat"><b>team communication app (LTAT)</b></a> to help improve team communication both internally and in other teams. </p1>
 
</br>
 
</br>
 +
<div id="safety"></div>
 
<h3>Safety</h3>
 
<h3>Safety</h3>
 
</br>
 
</br>

Revision as of 03:29, 17 October 2018


Integrated HP



Summary of Integrated Human Practices


In order to identify potential issues and applications of our system, we engaged in direct dialogue with stakeholders, as per the Communication Strategies Guide (CSG). This approach allowed us to devise potential applications for our system, as well as correct design flaws such as the use of toxic pyocyanin as a redox-cycling molecule. This led us to repurpose our system with a safer molecule (phenazine methosulfate -PMS-), which also resulted in being a cheaper inducer molecule even when compared with broadly used inducers. We also identified that internal friction in teams is a common issue as proven to us by our experience as well as a survey that we conducted amongst 67 iGEM members from 14 other teams. To address this issue we developed our team communication app (LTAT) to help improve team communication both internally and in other teams.

Safety


Our genetic circuit is activated/deactivated by the redox state of the transcription factor (SoxR). SoxR oxidation is modulated by small redox molecules, such as pyocyanin. However, after Dr. Francesca Ceroni, a PI at Imperial who was pregnant at the time declined to meet us in the lab out of concern of toxic substances as well as public concern on the toxicity of our system, we realized that toxicity is a huge factor in downstream implementation of our system. Pyocyanin is a toxin synthesised by the pathogen Pseudomonas aeruginosa and is implicated in its virulence (Ho Sui et. al., 2012). We also realized that using another cheaper redox molecule could not only make our system cheaper to use, but also replace inducer molecules such as IPTG due to their price. Using PMS which is a small redox molecule, we can activate a gene much like IPTG would with plac. Not only is PMS far cheaper than both pyocyanin and IPTG, it is also non-toxic and makes our system more applicable for real world applications.

Toxicity comparison between Pyocyanin and PMS


The 2012 OSHA Hazard Communication Standard ranks hazard ratings with the use of categories, with Category 0 being the lowest risk and Category 4 being the highest. With regards to toxicity, pyocyanin is a Category 4 substance (Santa Cruz Biotechnology, 2010) and extreme care was taken during our wet lab to ensure our own safety and any contact with pyocyanin would warrant immediate medical attention, PMS on the other hand is a Category 0 substance (Santa Cruz Biotechnology, 2017) and thus is far easier and safer to handle.

Cost comparison between PMS and common inducer molecules


A cursory look at the costs of PMS, pyocyanin and common inducer molecules (such as IPTG) already reveal stark differences in costs per gram. When accounting for working concentrations, this difference is further magnified, with PMS being 407 times cheaper than IPTG and 6600 times cheaper than pyocyanin. These costs are summarized in a table below, where costs per gram are obtained using the lowest price per gram on Sigma-Aldrich. However costs only matter if it can be shown that PMS can have a similar fold induction to common inducer molecules such as IPTG and experimental results for fold induction suggesting that is the case can be found below.

Inducer Working Concentrations Price per gram (£) Mass per liter of media (mg) Price per liter of media (pence) CAS No. Relative price to PMS (%)
PMS 0.2 uM 15.76 0.0613 0.0966 299-11-6 n/a
Pyocyanin 2.5 uM 12,120 0.526 638 85-66-5 660,000
IPTG 40 uM (https://www.neb.com/protocols/1/01/01/protein-expression-using-bl21de3-c2527) 41.2 9.53 39.3 367-93-1 40,700
L-Arabinose 6.66 M (https://microbialcellfactories.biomedcentral.com/articles/10.1186/1475-2859-9-14) 0.785 1000 78.5 5328-37-0 81,300
aTc 0.214 uM (https://openwetware.org/wiki/ATc) 1650 0.0991 16.4 13803-65-1 17,000


Click here for experimental results

Environment


Biocontainment



A big socio-ethical issue with using genetically engineered organisms is the issue of biocontainment. We recognized this as an issue by talking to members of the public as well as from the socio-ethics discussion. These organisms should not be released where they could potentially cause ecological damage by outcompeting or harming native species. While some may debate the impact of this ecological damage, it would be easier to persuade governments and its people to use GMOs when proper biocontainment measures are in place. Public and governmental opposition to widespread implementation of synthetic biology products will greatly affect the downstream applications of our system. This problem rings especially true as (for now) EU laws and regulations require that any release of GMOs into the environment proper risk assessments and containment strategies must be in place (http://www.loc.gov/law/help/restrictions-on-gmos/eu.php). By controlling transcription of growth retardants or toxins, like gp2 and MazF respectively, we can control where our bacteria will live and thus add a layer of biocontainment.



Click here for experimental results

Fabric Bioprinter


Placeholder for Fabric Bioprinter GIF
In preparation for our art exhibition, we discussed the integration of science and art with a student, Alice, from the RCA. She mentioned that in fashion, chemical pollution as a result of the usage of dyes is prominent. Further reading made us aware that textile dyeing is the second largest polluter of clean water globally (https://www.independent.co.uk/life-style/fashion/environment-costs-fast-fashion-pollution-waste-sustainability-a8139386.html). We realized that using bacteria to synthesize dyes could provide for an ecologically friendly solution. Moreover, with the ability to pattern using our electrode array, we can design simple prints using MelA which is a step in the right direction for the fashion industry. We have also succeeded in cloning the MelA gene into our construct design.

Click here for experimental results

Wellbeing


When we started our project, many of us had personal as well as interpersonal issues that threatened the viability of our project as well as our own well-being. We made it a point to reflect upon this experience and wondered if any other teams had similar issues to us. We surveyed 67 people from 13 different iGEM teams and developed a team-communication application called Let's Talk about It! as a aid for resolving these issues both for us and future iGEM teams. Most importantly, we have used the app to raise important issues with our PIs and supervisors and have these issues responded to as fast as possible. Knowing that this tool exists has made us more open about our issues and help each other communicate solutions for these issues. This has raised our productivity and made us more cooperative. More information on our Team-communication application can be found here