-
<p align="left">Create a page on your team wiki with clear attribution of each aspect of your project. This page must
...any other registered iGEM team in a meaningful way. For example, mentor a team, characterize a part, troubleshoot a project, model/simulate a system or va
21 KB (3,342 words) - 17:16, 22 July 2017
-
{{
TU-Eindhoven_menu}}
<li><a href="#"><img src="https://static.igem.org/mediawiki/2017/8/80/T--
TU-Eindhoven--Human_Practices.png" width="128" height="60" alt="Human_Practice
15 KB (2,567 words) - 17:17, 1 November 2017
-
...uring iGEM; a cozy ML-1 lab in the new Applied Sciences building of the
TU Delft campus. ML-1 is the lowest safety level when working with genetically engin
<p>Before we started with this work in the lab, all
team members had to pass different safety tests and receive training during an i
9 KB (1,440 words) - 10:45, 14 December 2017
-
We are very thankful to the Make Munich team for inviting us to this fascinating tech event. This was our very first pub
...her, as well as each other’s projects. During this three-day event, each team presented their project along with updates on their progress and participat
19 KB (2,970 words) - 20:40, 1 November 2017
-
...ject, describe what moves you and why this is something important for your team.</p>
<li align="left">A detailed explanation of why your team chose to work on this particular project.</li>
26 KB (3,857 words) - 00:57, 30 May 2017
-
...ject, describe what moves you and why this is something important for your team.</p>
<li align="left">A detailed explanation of why your team chose to work on this particular project.</li>
26 KB (3,857 words) - 17:15, 22 July 2017
-
...stakeholders participated in our project <i><a href="https://2017.igem.org/Team:TUDelft/Engagement#videos" target="_blank" >How can iGEM teams best include
...height: 3%; width: 40%;" class="modal-trigger" href="https://2017.igem.org/Team:TUDelft/Design#vesicles"></a>
133 KB (11,560 words) - 16:51, 14 December 2017
-
<link rel="stylesheet" type="text/css" href="https://2017.igem.org/Team:SDU-Denmark/core/bootstrapcss?action=raw&ctype=text/css">
<link rel="stylesheet" type="text/css" href="https://2017.igem.org/Team:SDU-Denmark/css/general?action=raw&ctype=text/css">
9 KB (1,435 words) - 01:14, 2 November 2017
-
...r/>TUDelft · Building 58 Room E0.120 <br>Van der Maasweg 9 · Delft, Zh 2628 CJ · The Netherlands<br/><br/> Phonenumber: +31 152 78 77 5
21 KB (2,826 words) - 13:23, 7 August 2017
-
...r/>TUDelft · Building 58 Room E0.120 <br>Van der Maasweg 9 · Delft, Zh 2628 CJ · The Netherlands<br/><br/> Phonenumber: +31 152 78 77 5
21 KB (2,808 words) - 12:25, 7 August 2017
-
...xecute our project, we decided to join our teams together to form the iGEM Team
...Senior Scientist and Cofounder of ACIB GmbH and Prof. for Biotechnology at TU Graz; Supervisor and primary
23 KB (2,249 words) - 00:44, 2 November 2017
-
<li><a href="/
Team:Munich/Results">Overview</a></li>
<li><a href="/
Team:Munich/Cas13a">Cas13a</a></li>
23 KB (3,320 words) - 12:59, 15 December 2017
-
Inspired by the team TU-Delft (2013), we simplified the promoters P2 to serve as a binary switch between
...2013.igem.org/Team:TU-Delft/Timer_Plus_Sumo">https://2013.igem.org/Team:TU-Delft/Timer_Plus_Sumo</a><br>
28 KB (3,510 words) - 04:03, 27 November 2017
-
<link href="https://2017.igem.org/Team:Amsterdam/assets/css/normalize?action=raw&ctype=text/css" rel="styleshe
<link href="https://2017.igem.org/Team:Amsterdam/assets/css/all?action=raw&ctype=text/css" rel="stylesheet"/>
42 KB (5,102 words) - 15:35, 15 December 2017
-
<link href="https://2017.igem.org/Team:Amsterdam/assets/css/normalize?action=raw&ctype=text/css" rel="styleshe
<link href="https://2017.igem.org/Team:Amsterdam/assets/css/all?action=raw&ctype=text/css" rel="stylesheet"/>
42 KB (5,034 words) - 00:50, 2 November 2017
-
<link href="https://2017.igem.org/team:amsterdam/team:amsterdam/assets/css/normalize?action=raw&ctype=text/css" rel="styleshe
<link href="https://2017.igem.org/team:amsterdam/team:amsterdam/assets/css/all?action=raw&ctype=text/css" rel="stylesheet"/>
42 KB (5,018 words) - 23:55, 1 November 2017
-
<link href="https://2017.igem.org/Team:Amsterdam/assets/css/normalize?action=raw&ctype=text/css" rel="styleshe
<link href="https://2017.igem.org/Team:Amsterdam/assets/css/all?action=raw&ctype=text/css" rel="stylesheet"/>
41 KB (4,995 words) - 20:12, 1 November 2017
-
<link href="https://2017.igem.org/Team:Amsterdam/test/max/assets/css/normalize?action=raw&ctype=text/css" rel=
<link href="https://2017.igem.org/Team:Amsterdam/test/max/assets/css/all?action=raw&ctype=text/css" rel="style
42 KB (5,025 words) - 22:23, 1 November 2017
-
<link href="https://2017.igem.org/team:amsterdam/team:amsterdam/assets/css/normalize?action=raw&ctype=text/css" rel="styleshe
<link href="https://2017.igem.org/team:amsterdam/team:amsterdam/assets/css/all?action=raw&ctype=text/css" rel="stylesheet"/>
42 KB (5,016 words) - 22:56, 1 November 2017
-
...signed our parts, circuits and experiments, distributed tasks, managed our team and our lab. Since July, we have been spending long hours in the lab, tryin
...working in the expected way. Daniel and Claude were part of the 2014 iGEM team of ETH Zürich, which is why they were not surprised about our many moments
11 KB (1,567 words) - 03:47, 2 November 2017
