Team:Cardiff Wales/Collaborations

Collaborations




WashU

We engaged in communication with WashU on the 8th August 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.

RIBITOL_RESPONSIVE CONSTRUCT RESULTS HERE

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. These details can be seen in the embedded PDF below.

EMBED PDF HERE

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

Our collaboration with Warwick university began just before the UK iGEM meetup in early July. The team contacted several UK teams to ask if we could collect four water samples from the rivers in our local areas to see if they could test Legionella in the water, from different places across the country. However, instead of just providing the water samples, we collected them from specific regions from The River Taff, chosen due to the activities that occur at or near each site. We pinned the locations to a map of Cardiff, and noted the activities that occurred in each area, in case these activities could influence the sample and give them new leads to investigate. The PDF can be seen below. Unfortunately, due to lack of powerful enough equipment at Warwick's disposal, the samples were not used.

INSERT PDF HERE

In return, a team member from Warwick's team, Kurt Hill, provided a solution to incorporating style sheets and scripts into the pages of our wikis. This is because the instructions on the iGEM registry help page did not work for us. Instead he provided working instructions to link these important pages, making coding the wiki much clearer, without the need for extensive in-line styling and scripts.





  • 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