Team:Edinburgh/HP/hierarchy
From 2014.igem.org
Samireland (Talk | contribs) |
|||
Line 51: | Line 51: | ||
</div> | </div> | ||
</div> | </div> | ||
+ | <div id="tourleftbottom"><a href="https://2014.igem.org/Team:Edinburgh/HP/robustness">← PP robustness</a></div> | ||
+ | <div id="tourrightbottom"><a href="https://2014.igem.org/Team:Edinburgh/HP/supervision">PP supervision →</a></div> | ||
</html> | </html> |
Revision as of 03:53, 18 October 2014
HierarchyIn several systems, a hierarchical structure can be observed, i.e. rather than everyone being equal, such positions as ‘team leader’ or similar may arise. Going back to Edwin Hutchin’s example of navigating a ship into a port, it is obvious that the social structure of the crew plays an essential role. The navigator needs to be higher ranked than the sailors. That way he can give them the necessary orders for the efficient gathering of the essential information about the ship’s location. On the other hand, many other systems perform better if all individuals have equal levels of authority. Thinking back to our bacterial system, do we need a ‘master strain’, with higher control/power? We asked the teams whether they felt that they had a team leader, and whether they felt they needed one.
Relevance for bacterial system designThis picks up on the idea by Wittebolle and colleagues (2009) that there is a need for an even distribution of functionally redundant members. They found that if the community depends too much on a dominant strain the population is more susceptible to fluctuations. Taken together with our findings from the iGEM interviews we are inclined to believe that it might be better to have no hierarchy in our system and ensure equal contribution of all components. This is in accordance with the horizontal structure of hierarchy we wanted to achieve with population control. |