Difference between revisions of "Team:Judd UK/Pages/Collaborations"

Line 6: Line 6:
 
     <p>After meeting at the UK team meet-up, the Oxford team introduced our modelling team to mass action kinetics, along with the hill equation and some basic Matlab codes as an introduction to programming in Matlab.</p>
 
     <p>After meeting at the UK team meet-up, the Oxford team introduced our modelling team to mass action kinetics, along with the hill equation and some basic Matlab codes as an introduction to programming in Matlab.</p>
 
     <h2 id="CLSB-2">CLSB</h2>
 
     <h2 id="CLSB-2">CLSB</h2>
     <p>We met with CLSB to discuss wiki development and modelling. They gave us a lot of help and advice for the wiki, including what languages it would be useful to learn, and some general advice about iGEM, such as the standard page names, uploading files, and how much time we should expect to spend on the wiki. For the modelling, they introduced the team to ordinary differential equations and how they can be used to represent a series of reactions. They also gave advice during the process, checking over our analytical solutions, as well as our numerical methods in Matlab.</p><p><br></p><p>The CLSB team came to us to test their hardware and their software. Their software was a lab assistant with voice commands to read out part information and protocols. We tested their software, and suggested adding a team lookup feature, the ability to repeat a step (as opposed to just next and back) and a skip command to jump to a particular step in a protocol. They implemented the first two we suggested, but found the last one wouldn't be feasible, as it caused conflicts with their part lookup feature.</p><p>For the hardware, we suggested holding the light sensor more securely, either by using blue tack or superglue instead of the electrical tape that had been using. We also suggested saving the recorded number, as oppose to just noting whether a reading was made and add the ability to download the recorded data. They implemented our recommendations, improving their system by making data analysis easier and the fluorometer more powerful.</p>
+
     <p>We met with CLSB to discuss wiki development and modelling. They gave us a lot of help and advice for the wiki, including what languages it would be useful to learn, and some general advice about iGEM, such as the standard page names, uploading files, and how much time we should expect to spend on the wiki. For the modelling, they introduced the team to ordinary differential equations and how they can be used to represent a series of reactions. They also gave advice during the process, checking over our analytical solutions, as well as our numerical methods in Matlab.</p>
 +
 
 +
<p>The CLSB team came to us to test their software. Their software was a lab assistant with voice commands to read out part information and protocols. We tested their software, and suggested adding a team lookup feature, the ability to repeat a step (as opposed to just next and back) and a skip command to jump to a particular step in a protocol. They implemented the first two we suggested, but found the last one wouldn't be feasible, as it caused conflicts with their part lookup feature.</p>
 +
<img src="https://static.igem.org/mediawiki/2017/5/59/T--CLSB-UK--hardware_judd.jpg">
 +
 
 +
<p>We also tested their hardware- a combined densitometer and fluorometer and suggested a few improvements. Firstly, we noticed that their readings were being slightly skewed by additional light entering the device from the environment because their light sensor was being secured by electrical tape so we suggested blue tac, which overcame this problem. We also thought that when their data was being recorded they would benefit from being able to download that data as well as having a corresponding number to keep track of their measurements – these changes were implemented after our meeting. Take a look at the CSLB wiki to find more information on their software and hardware.</p>
 
</div><html><script data-run='false'>window.location='/Team:Judd_UK/Collaborations'</script></html>
 
</div><html><script data-run='false'>window.location='/Team:Judd_UK/Collaborations'</script></html>

Revision as of 19:22, 1 November 2017

Collaborations

Kent

For our Interlab studies, we asked the Kent iGEM team to help us out because we do not have the equipment to accurately obtain the necessary readings. Laulwa Al Salloum, Dan Brunkow and Laurens Heling from the Kent team offered us a lab to work in as well helping and mentoring Mateo Hoare and Nikita Shukan from the Judd_UK iGEM team with the new equipment including using Gilson Pipettes and a plate reader. The Kent team were unsuccessful in transforming the DNA provided by iGEM into competent E. coli DH5 alpha and, so, as part of a collaborations effort, we offered our Interlab DNA (Distribution Kit Plate 6) for them to work with.

Oxford

After meeting at the UK team meet-up, the Oxford team introduced our modelling team to mass action kinetics, along with the hill equation and some basic Matlab codes as an introduction to programming in Matlab.

CLSB

We met with CLSB to discuss wiki development and modelling. They gave us a lot of help and advice for the wiki, including what languages it would be useful to learn, and some general advice about iGEM, such as the standard page names, uploading files, and how much time we should expect to spend on the wiki. For the modelling, they introduced the team to ordinary differential equations and how they can be used to represent a series of reactions. They also gave advice during the process, checking over our analytical solutions, as well as our numerical methods in Matlab.

The CLSB team came to us to test their software. Their software was a lab assistant with voice commands to read out part information and protocols. We tested their software, and suggested adding a team lookup feature, the ability to repeat a step (as opposed to just next and back) and a skip command to jump to a particular step in a protocol. They implemented the first two we suggested, but found the last one wouldn't be feasible, as it caused conflicts with their part lookup feature.

<img src="T--CLSB-UK--hardware_judd.jpg">

We also tested their hardware- a combined densitometer and fluorometer and suggested a few improvements. Firstly, we noticed that their readings were being slightly skewed by additional light entering the device from the environment because their light sensor was being secured by electrical tape so we suggested blue tac, which overcame this problem. We also thought that when their data was being recorded they would benefit from being able to download that data as well as having a corresponding number to keep track of their measurements – these changes were implemented after our meeting. Take a look at the CSLB wiki to find more information on their software and hardware.