Team:Edinburgh/HP/supervision

From 2014.igem.org

(Difference between revisions)
 
(4 intermediate revisions not shown)
Line 2: Line 2:
<link href='http://fonts.googleapis.com/css?family=Roboto+Slab' rel='stylesheet' type='text/css'>
<link href='http://fonts.googleapis.com/css?family=Roboto+Slab' rel='stylesheet' type='text/css'>
<link rel="stylesheet" href="https://2014.igem.org/Template:Team:Edinburgh/CSS?action=raw&ctype=text/css" type="text/css" />
<link rel="stylesheet" href="https://2014.igem.org/Template:Team:Edinburgh/CSS?action=raw&ctype=text/css" type="text/css" />
-
 
+
<div id="topbit" style="margin-bottom: 40px;">
 +
<table align="center" style="border-spacing: 5px;"><tr><td><a href="https://2014.igem.org/"><img src="https://static.igem.org/mediawiki/2014/archive/3/3f/20140702191450%21Igem.png" width="50px" height="45px"></a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh">Home</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/team/">Team</a></td><td id="navlink"><a href="https://igem.org/Team.cgi?id=1399">Profile</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/logic/">Background</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/project/">Project</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/HP/">Policy and Practices</a></td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/modelling/">Modelling</td><td id="navlink"><a href="https://2014.igem.org/Team:Edinburgh/log">Daily log</a></td></table></div>
 +
<div id="tourleft"><a href="https://2014.igem.org/Team:Edinburgh/HP/hierarchy">&#8592; PP hierarchy</a></div>
 +
<div id="tourright"><a href="https://2014.igem.org/Team:Edinburgh/HP/summary">PP summary &#8594;</a></div>
<div id="igem">
<div id="igem">
<div id="header">
<div id="header">
   <a href="https://2014.igem.org/Team:Edinburgh"><img id="logo" src="https://static.igem.org/mediawiki/2014/8/8e/Ed14_logo.png" width="200" height="200"></a>
   <a href="https://2014.igem.org/Team:Edinburgh"><img id="logo" src="https://static.igem.org/mediawiki/2014/8/8e/Ed14_logo.png" width="200" height="200"></a>
-
   <h1>Human Practices</h1>
+
   <h1>Policy and Practices</h1>
</div>
</div>
<div id="HPpage">
<div id="HPpage">
Line 41: Line 44:
<p>Hence, the bacterial system needs to be provided with some form of a monitoring and control protocol. First, there needs to be a physical output that can be measured. We used for example reporter proteins like GFP and degrons as monitoring tools. Following this monitoring we then need to be able to control the system accordingly.</p>
<p>Hence, the bacterial system needs to be provided with some form of a monitoring and control protocol. First, there needs to be a physical output that can be measured. We used for example reporter proteins like GFP and degrons as monitoring tools. Following this monitoring we then need to be able to control the system accordingly.</p>
-
</td></tr>
+
 
 +
<br><br><br><br></td></tr>
</div>
</div>
</div>
</div>
 +
<div id="tourleftbottom"><a href="https://2014.igem.org/Team:Edinburgh/HP/hierarchy">&#8592; PP hierarchy</a></div>
 +
<div id="tourrightbottom"><a href="https://2014.igem.org/Team:Edinburgh/HP/summary">PP summary &#8594;</a></div>
</html>
</html>

Latest revision as of 03:53, 18 October 2014

Supervision

Finally, we are interested in the boundary conditions of our system - is it capable of existing as an independent entity? Or do we need somebody to look after it? We asked the teams about their instructors and advisors, their role and their contribution to their work.

  • We found that, for most teams, the supervisors had a guiding role, rather than a forceful, authoritative one; they were usually there to check that the work is going fine and everyone's on track. Most teams acknowledged that this worked well. -- It is useful to have someone monitoring and double-checking the progress.
    Supervisors keep us in check and make sure we stay on track. They will tell us if we lack some part.
    Our supervisor would sometimes check our constructs etc, because we didn't want to make a silly mistake. That was very good.
  • The importance of having supervisors was also acknowledged by most teams; most teams said they depended quite a lot on the advice from those with more experience.
    We don't get almost any supervision, and our work has suffered because of that.
    We depend on the supervisors quite a bit, especially when we try something new, because there are a lot of things we don't quite know.
  • Most teams had regular meetings to check in with their instructors; in most cases, the teams found this very useful. Regular check-in points may be needed, to ensure things are still on track.

Relevance to bacterial systems

In an iGEM team, supervisors and advisors usually take a monitoring and control role, which is a significant part of the execution of a project or a piece of work. From engineering project definitions, monitoring is the process of checking that as a project progresses, it will actually turn out the way it was planned; control involves the processes that need to be undertaken in order to bring the project back to the way it was originally intended.

The monitoring method used depends on the type of a project; the frequency of monitoring needs to be set. As found from iGEM interviews, regular checks helped the teams a lot to keep on track.

Hence, the bacterial system needs to be provided with some form of a monitoring and control protocol. First, there needs to be a physical output that can be measured. We used for example reporter proteins like GFP and degrons as monitoring tools. Following this monitoring we then need to be able to control the system accordingly.