Ryancoates (Talk | contribs) |
Ryancoates (Talk | contribs) |
||
Line 14: | Line 14: | ||
<div class="column full_size"> | <div class="column full_size"> | ||
<h1>Collaborations</h1> | <h1>Collaborations</h1> | ||
+ | <br><br><br> | ||
+ | <center><h2>WashU</h2</center> | ||
+ | <p>We engaged in communication with WashU on XX/XX/XXXX to discuss a potential collaboration. Their project aims to detect stem rust in wheat, caused by <i>Puccinia graminis</i>, and potentially find a way to create GM wheat resistant to the fungal infection. The team proposed we collaborated with them in two ways. | ||
+ | <br><br>Firstly, their project uses a poorly characterised bacterial operon that responds to and is activated by the presence of ribulose. Consequently, as not much is known about the sequence, we offered to test the operons control region directly in plants, in case it had some activity. We did this by putting the control region upstream of two reporter genes, Gus and mCherry, with the NosT terminator downstream. We tested their control region both in the presence and absence of ribitol, a hydrogenated version of ribulose. The results can be seen below. In doing this, we had to create a version of their control region that was GoldenGate compatible. This is part <a href="http://parts.igem.org/wiki/index.php?title=Part:BBa_K2810010">BBa_K2810010</a>. | ||
+ | <br><br> | ||
+ | Secondly, they suggested that we 3D print their hardware, a housing unit built for the detection system of the fungus that causes stem rust. We provided extensive details about the 3D printing procedure, and a brief review of the hardware, such as its design, how well it all fit together, and the theoretical ease of use. In addition, we also contacted a local agronomist about the design, asking what sort of role such a product could have in the UK, whether it would be useful, and whether the design seemed innovative. | ||
+ | <br><br> In return, WashU helped extensively with the design of our wiki's navigation bar, helping to debug the system when links and the display did not function as expected.</p> | ||
+ | <br><br><br> | ||
+ | <center><h2>Warwick</h2</center> | ||
+ | <p> | ||
+ | <br><br><br> | ||
<br> | <br> | ||
<ul> | <ul> |
Revision as of 23:26, 23 September 2018
Collaborations
WashU
We engaged in communication with WashU on XX/XX/XXXX to discuss a potential collaboration. Their project aims to detect stem rust in wheat, caused by Puccinia graminis, and potentially find a way to create GM wheat resistant to the fungal infection. The team proposed we collaborated with them in two ways.
Firstly, their project uses a poorly characterised bacterial operon that responds to and is activated by the presence of ribulose. Consequently, as not much is known about the sequence, we offered to test the operons control region directly in plants, in case it had some activity. We did this by putting the control region upstream of two reporter genes, Gus and mCherry, with the NosT terminator downstream. We tested their control region both in the presence and absence of ribitol, a hydrogenated version of ribulose. The results can be seen below. In doing this, we had to create a version of their control region that was GoldenGate compatible. This is part BBa_K2810010.
Secondly, they suggested that we 3D print their hardware, a housing unit built for the detection system of the fungus that causes stem rust. We provided extensive details about the 3D printing procedure, and a brief review of the hardware, such as its design, how well it all fit together, and the theoretical ease of use. In addition, we also contacted a local agronomist about the design, asking what sort of role such a product could have in the UK, whether it would be useful, and whether the design seemed innovative.
In return, WashU helped extensively with the design of our wiki's navigation bar, helping to debug the system when links and the display did not function as expected.
Warwick
- WashU collaboration to test their promoter
- Warwick water sample but with added detail (embed as PDF)
Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.
Silver Medal Criterion #2
Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the 2018 Medals Page for more information.
Which other teams can we work with?
You can work with any other team in the competition, including software, hardware, high school and other tracks. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.
In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
Here are some suggestions for projects you could work on with other teams:
- Improve the function of another team's BioBrick Part or Device
- Characterize another team's part
- Debug a construct
- Model or simulate another team's system
- Test another team's software
- Help build and test another team's hardware project
- Mentor a high-school team