Difference between revisions of "Team:NAWI Graz/Collaborations"

 
(17 intermediate revisions by 3 users not shown)
Line 10: Line 10:
 
             <div class="section-text container">
 
             <div class="section-text container">
 
                 The iGEM Team NAWI_Graz looked for different possibilities to collaborate with other teams. These ranged from simple e-mail
 
                 The iGEM Team NAWI_Graz looked for different possibilities to collaborate with other teams. These ranged from simple e-mail
                 communication to learn more about the competition and the support provided by iGEM, online discussions in
+
                 communication and skype conferences to learn more about the competition and the support provided by iGEM, online discussions in
 
                 the field of security, material support for other teams with our own constructs, and the development of a
 
                 the field of security, material support for other teams with our own constructs, and the development of a
 
                 software to improve our robot algorithm and therefore giving other teams the possibility to support us from
 
                 software to improve our robot algorithm and therefore giving other teams the possibility to support us from
Line 20: Line 20:
  
 
     <div class="section container">
 
     <div class="section container">
         <h2 class="section-sub">European Meet Up</h2>
+
         <h2 id="TUDelft" class="section-sub">European Meet Up</h2>
 
         <div class="section-text container">
 
         <div class="section-text container">
             From the team <a href="https://2017.igem.org/Team:TUDelft">TU Delft</a> we have been noticed by an e-mail that they will organize a European
+
             <a href="https://2017.igem.org/Team:TUDelft">Tu Delft</a> send us an e-mail and invited us to their European meet up. The idea of ​​an earlier, smaller version of the Giant Jamboree in Europe excited the whole team and we decided to send seven people to the Netherlands to get in touch with other iGEM teams.  Due to the meet up we gained our first experiences in poster presentations. With lots of euphoria and motivation we enjoyed the various lectures at the TU Delft. They arranged excursions in Delft and Rotterdam (lovely Pannenkoekenboot, really delicious) and above all, the large poster presentations of all the different teams. It was a great opportunity to meet other iGEMers and to improve our skills by presenting our project to them. The provided summary of all presented posters helped us to find and rework our own poster design for Boston.        </div>
            Meet up. The idea of ​​an earlier, smaller version of the Giant Jamboree in Europe excited the whole team and
+
            we decided to send 7 people to the Netherlands to get in touch with other iGEM teams. Due to the Meet-up we
+
            also gained our first experiences in poster presentations. With lots of euphoria and motivation we enjoyed the
+
            various lectures at the TU Delft. They arranged excursions in Delft and Rotterdam, (lovely Pannenkoekenboot,
+
            really delicious) and above all the large poster presentations of the different teams. It was a great opportunity
+
            to meet other iGEM teams and to improve our skills by presenting our project to them. The send summary of all
+
  
            presented posters helped us to find and rework our own poster design for Boston.
 
        </div>
 
 
     </div>
 
     </div>
 +
 +
<div class="section container">
 +
    <img class="section-image" src="https://static.igem.org/mediawiki/2017/thumb/d/de/Tamsterdam_collab5.jpg/800px-Tamsterdam_collab5.jpg"
 +
        alt="The image cannot be displayed">
 +
    <div class="section-sub-text">
 +
        <b>Fig. 1:</b> All participating teams at the Meet up in Delft.
 +
    </div>
 +
</div>
 +
 
     <br>
 
     <br>
  
 
     <div class="section container">
 
     <div class="section container">
         <h2 class="section-sub">General Support</h2>
+
         <h2 id="TUDarmstadt" class="section-sub">General Support</h2>
 
         <div class="section-text container">
 
         <div class="section-text container">
             Already in Delft, we have communicated more intensively with the team
+
             We have communicated more intensively with the team <a href="https://2017.igem.org/Team:TU_Darmstadt">Tu_Darmstadt</a> in Delft already. Even as the third iGEM team from Graz, we had less information than thought about the competition and standardized support of long-standing partners of the iGEM Foundation. As an example, they have drawn our attention to the free sequencing of MycroSynth. We wanted to form an even closer cooperation by detecting a degradation product from their experiments and thus directly prove that their experimental setup and our construct function. We organised a video conference, but the plan was rejected, because the substrate amounts would not have been high enough to activate our promoter. Although no physical exchange took place, we would like to express our gratitude for the willingness to support and establish a new team in the competition.       </div>
            <a href="https://2017.igem.org/Team:TU_Darmstadt/Collaborations">TU_Darmstadt</a>, because it has been shown that as a relatively fresh Grazer team, the 3rd at all, we had less
+
            information than thought about the competition and standardized support of long-standing partners of the iGEM
+
            Foundation. As an example they have drawn our attention to the free sequencing of MycroSynth. In addition, we
+
            wanted to form an even closer cooperation by demonstrating a degradation product from their experiments and thus
+
            directly prove that their experimental setup and our construct function. For this, there were video conferences,
+
            but the plan was rejected because the substrate amounts would not have been high enough to activate our promoter.
+
            Although no physical exchange has taken place, we would like to express our gratitude for the willingness to
+
            establish a new team in the competition.
+
        </div>
+
 
     </div>
 
     </div>
 
     <br>
 
     <br>
  
 
     <div class="section container">
 
     <div class="section container">
         <h2 class="section-sub">Online Discussion about Safety</h2>
+
         <h2 id="onlinediscussion" class="section-sub">Online Discussion about Safety</h2>
 
         <div class="section-text">
 
         <div class="section-text">
             As part of the preparations for our lab work, we have seen the call for an online discussion of the team <a href="https://2017.igem.org/Team:Uppsala">Uppsala</a> on the
+
             As part of the preparations for our lab work, we have seen the call for an online discussion of the team <a href="https://2017.igem.org/Team:Uppsala">Uppsala</a> on the official iGEM Collaboration page. After the subsequent contact, we got seats in the session #Genetic Engineering with special attention to safety. The questions were focused on the areas of "uncontrolled dissemination" and "harmful abuse of our openly accessible GMO". Together with the teams <a href="https://2017.igem.org/Team:ETH_Zurich">ETH_Zurich</a>,  <a href="https://2017.igem.org/Team:UiOslo_Norway">UiOslo_Norway</a>, <a href="https://2017.igem.org/Team:Lund">Lund</a>, <a href="https://2017.igem.org/Team:Groningen">Groningen</a> and <a href="https://2017.igem.org/Team:Uppsala">Uppsala</a>, we discussed whether and how we could assume our GMOs behaviour in the wilderness. In addition we figured out whether and how GMOs could possibly be misused in a harmful way. The results of this discussion helped us  to complete our <a href="https://2017.igem.org/Team:NAWI_Graz/Safety">Safety Form</a>.
            official iGEM Collaboration page. After the subsequent contact, we got seats in the session about Genetic Engineering
+
            with special attention to safety. The questions were focused on the areas of "uncontrolled dissemination" and
+
            "harmful abuse of our openly accessible GMO". Together with the teams <a href="https://2017.igem.org/Team:ETH_Zurich">ETH_Zurich</a>, <a href="https://2017.igem.org/Team:UiOslo_Norway">UiOslo_Norway</a>, <a href="https://2017.igem.org/Team:Lund">Lund</a>, <a href="https://2017.igem.org/Team:Groningen">Groningen</a>
+
            and the hosting team <a href="https://2017.igem.org/Team:Uppsala">Uppsala</a>
+
            we determined whether and how we could assume our GMOs behaviour in the wild and whether we could imagine any
+
            way possible harmful misuse of our GMO. The results of this discussion helped us to complete our
+
            <a href="https://2017.igem.org/Team:NAWI_Graz/Safety#SAFETY">Safety Form</a>.
+
 
         </div>
 
         </div>
 
  <video class="section-video" width="640" height="480" controls>
 
  <video class="section-video" width="640" height="480" controls>
Line 68: Line 53:
 
        
 
        
 
<div class="section-sub-text container">
 
<div class="section-sub-text container">
            Fig. 1: Our team members Tony and Tino at the #Genetic Engineering conference hosted by the iGEM Team <a href="https://2017.igem.org/Team:Uppsala">Uppsala</a>.   
+
          <b> Vid. 1:</b> Our team members Tony and Tino at the #Genetic Engineering conference hosted by the iGEM Team <a href="https://2017.igem.org/Team:Uppsala">Uppsala</a>.   
 
       </div>
 
       </div>
  
Line 75: Line 60:
  
 
     <div class="section container">
 
     <div class="section container">
         <h2 class="section-sub">Interactive Maze Design</h2>
+
         <h2 id="MazeDesign" class="section-sub">Interactive Maze Design</h2>
 
         <div class="section-text container">
 
         <div class="section-text container">
             After we announced on the official iGEM Collaboration site to help us improving our robot algorithm by being part of our
+
             We posted an announcement on the official iGEM Collaboration site to help us improve our robot algorithm. We developed a software to design mazes and therefor test and improve our robot controling code. As it is usual and obligate for software developers, we reached out for beta testers. Other iGEM teams are predistinated for this job, so we invited all other teams to help us. In addition, we set up tools in form of tablet computers at our human practice events. Some day, the iGEM Team <a href="https://2017.igem.org/Team:Groningen">Groningen</a> contacted us. They were our first beta testers. The first mazes of the team, as simple as they were designed, could not be solved by our robot.       </div>
            obligate group of beta testers for our online maze design software, the iGEM Team <a href="https://2017.igem.org/Team:Groningen">Groningen</a>
+
            contacted us. The first mazes of the team, as simple as they were designed, could not be solved by
+
            our robot.
+
        </div>
+
  
 
             <img  class="section-image" src="https://static.igem.org/mediawiki/2017/thumb/7/77/Maze1.png/800px-Maze1.png" alt="Mazepic 1">
 
             <img  class="section-image" src="https://static.igem.org/mediawiki/2017/thumb/7/77/Maze1.png/800px-Maze1.png" alt="Mazepic 1">
  
 
<div class="section-sub-text container">
 
<div class="section-sub-text container">
             Fig. 1: The first maze design with our online maze design software. Designed by the iGEM Team Groningen
+
             <b>Fig. 2:</b> The first maze design with our online maze design software. Designed by the iGEM Team Groningen
 
       </div>
 
       </div>
       
+
        <br>
 
         <div class="section-text container">
 
         <div class="section-text container">
             Due to these feedbacks we have extended the code of the program significantly and found a way to insert a coherent storage
+
             Due to these feedbacks we have extended the code of the program significantly and found a way to insert a coherent storage possibility, which allows the robot to escape much better from angled corners again and find the end of the maze. After sending the link to the updated version, our friends from Groningen sent us several new designs, which were all solved by the robot.       </div>
            possibility, which allows the robot to escape much better from angled corners again and find the end of the maze.
+
            After sending the link to the updated version, our friends from Groningen sent us several new designs, which
+
            were all solved by the robot.
+
        </div>
+
  
             <img class="section-image" src="https://static.igem.org/mediawiki/2017/thumb/9/95/Maze2.png/799px-Maze2.png" alt="Mazepic 2">
+
             <img id="France" class="section-image" src="https://static.igem.org/mediawiki/2017/thumb/9/95/Maze2.png/799px-Maze2.png" alt="Mazepic 2">
  
 
<div class="section-sub-text container">
 
<div class="section-sub-text container">
             Fig. 2: Maze design with extended code
+
             <b>Fig. 3:</b> Maze design with extended code by Groningen
 
       </div>
 
       </div>
  
     
+
      <br>
 
         <div class="section-text container">
 
         <div class="section-text container">
             <a href="https://2017.igem.org/Team:INSA-UPS_France">INSA-UPS_France</a> contacted us some time later to test the labyrinth design software
+
             <a href="https://2017.igem.org/Team:INSA-UPS_France">INSA-UPS_France</a> contacted us some time later to test the maze design software too. Using their highly creative approach to design several chambers, we were able to correct mistakes and validate our results even more.       </div>
            too. Using their highly creative approach to design several mazes, we were able to correct mistakes and validate
+
            our results even more.
+
        </div>
+
 
      
 
      
             <img class="section-image" src="https://static.igem.org/mediawiki/2017/thumb/8/83/Maze3.jpg/800px-Maze3.jpg" alt="Mazepic 3">
+
             <img class="section-image" src="https://static.igem.org/mediawiki/2017/0/01/Mazepic4.png" alt="Mazepic 3">
  
 
<div class="section-sub-text container">
 
<div class="section-sub-text container">
             Fig. 3: Maze design by the iGEM Team from  INSA-UPS_France
+
             <b>Fig. 4:</b> The really creative mazes & chambers of INSA-UPS_France. The iGEM mazes could be solved, but our Thymio had some problems with the other chambers.
 
       </div>
 
       </div>
 
      
 
      
Line 118: Line 92:
  
 
         <div class="section container">
 
         <div class="section container">
             <h2 class="section-sub">Support by sending our Promotor Construct</h2>
+
             <h2 id="SVCEChennai" class="section-sub">Support by sending our Promotor Construct</h2>
 
             <div class="row">
 
             <div class="row">
 
                 <div class="section-text">
 
                 <div class="section-text">
                         We reached out for <a href="https://2017.igem.org/Team:SVCE_CHENNAI">SVCE_Chennai</a> after reading their collaboration proposal on the
+
                         We contacted <a href="https://2017.igem.org/Team:SVCE_CHENNAI">SVCE_Chennai</a> after reading their collaboration proposal on the iGEM Collaborations page. We realized we had many similarities in our project as both of us were working on pH as well as temperature regulated systems. The alkaline inducible promotor alx was actually the same. A Skype conference between both teams was organised, which gave us the chance to talk directly to each other and express any difficulties we were faced with so far. Since they had some issues with changing pH in their media, we helped them out by giving them some useful suggestions, like our protocol about what base we use and the concret amount of it to raise the neutral pH of LB and M9 media to 8,5 to induce the promoter.  Since they had some amplification issues with their gBlock, we also shipped them our alx gBlock so that they could work with it. At the end of the summer, they send us their data about how the promoter activity increased with the pH and as we had similar results, we came to the conclusion that our experiments were successful.
                    iGEM Collaborations page. We realized we had many similarities in our project as both of us were working
+
                    on pH as well as temperature regulatory systems and the alkaline inducible promotor was actually the
+
                    same, alx. A skype call between both teams, which gave us a chance to interact and express any difficulties
+
                    we had, was organised. Since they had some issues with changing pH in their medium, we helped them out
+
                    by giving them some useful suggestions, like our protocol about what base we use on the concret amount of it to raise the neutral pH of LB and M9 media to 8,5 to induce the promoter. Since they had some amplification issues with their gBlock, we
+
                    also shipped them our alx gBlock so that they could work with it. At the end of the summer, they send us their data about how the promoteractivity increased with the pH and as we had kind of the same results, we came to the conclusion our experiments were successfull.
+
 
                 </div>
 
                 </div>
 
             </div>
 
             </div>
Line 134: Line 102:
  
 
         <div class="section container">
 
         <div class="section container">
             <h2 class="section-sub">Augmented Reality at the Giant Jamboree</h2>
+
             <h2 id="Franconia" class="section-sub">Augmented Reality at the Giant Jamboree</h2>
 
             <div class="row">
 
             <div class="row">
 
                 <div class="section-text">
 
                 <div class="section-text">
                     After seeing the post of the iGEM team <a href="https://2017.igem.org/Team:Franconia">Franconia</a> on the official Collaboration Site,
+
                     After seeing the post of the iGEM team <a href="https://2017.igem.org/Team:Franconia">Franconia</a> on the official Collaboration Site, and declaring it as a very creative, interesting and amusing one, we decided to support them. They organise an augmented reality game for smartphones with the help of QR codes distributed throughout the Giant Jamboree. A "plague" breaks out at the event and the QR codes represent either "cure" or “infection” for the respective scanning smartphone. The goal of the game is that at the end of the conference, all virus outbreaks are cured. With little effort, this game can create a very special component of the Giant Jamboree 2017 and this is why we want to support and be part of it.
                    and declining it as a very creative, interesting and amusing one, we decided to support them. They organise
+
                    an augmented reality game for smartphones with the help of QR codes distributed throughout the Giant
+
                    Jamboree. A "plague" breaks out at the event and the QR codes represent either "cure" or infect the respective
+
                    scanning smartphone. The goal of the game is that at the end of the conference all virus outbreaks are
+
                    cured. This game can create a very special component of the Giant
+
                    Jamboree 2017 and this is why we want to be part of it.
+
 
                 </div>
 
                 </div>
 
             </div>
 
             </div>

Latest revision as of 03:02, 2 November 2017

COLLABORATIONS


The iGEM Team NAWI_Graz looked for different possibilities to collaborate with other teams. These ranged from simple e-mail communication and skype conferences to learn more about the competition and the support provided by iGEM, online discussions in the field of security, material support for other teams with our own constructs, and the development of a software to improve our robot algorithm and therefore giving other teams the possibility to support us from their own location. They all looked much more difficult and complicated than we originally thought, but they all helped us to realise our project in this form.

European Meet Up

Tu Delft send us an e-mail and invited us to their European meet up. The idea of ​​an earlier, smaller version of the Giant Jamboree in Europe excited the whole team and we decided to send seven people to the Netherlands to get in touch with other iGEM teams.  Due to the meet up we gained our first experiences in poster presentations. With lots of euphoria and motivation we enjoyed the various lectures at the TU Delft. They arranged excursions in Delft and Rotterdam (lovely Pannenkoekenboot, really delicious) and above all, the large poster presentations of all the different teams. It was a great opportunity to meet other iGEMers and to improve our skills by presenting our project to them. The provided summary of all presented posters helped us to find and rework our own poster design for Boston.
The image cannot be displayed
Fig. 1: All participating teams at the Meet up in Delft.

General Support

We have communicated more intensively with the team Tu_Darmstadt in Delft already. Even as the third iGEM team from Graz, we had less information than thought about the competition and standardized support of long-standing partners of the iGEM Foundation. As an example, they have drawn our attention to the free sequencing of MycroSynth. We wanted to form an even closer cooperation by detecting a degradation product from their experiments and thus directly prove that their experimental setup and our construct function. We organised a video conference, but the plan was rejected, because the substrate amounts would not have been high enough to activate our promoter. Although no physical exchange took place, we would like to express our gratitude for the willingness to support and establish a new team in the competition.

Online Discussion about Safety

As part of the preparations for our lab work, we have seen the call for an online discussion of the team Uppsala on the official iGEM Collaboration page. After the subsequent contact, we got seats in the session #Genetic Engineering with special attention to safety. The questions were focused on the areas of "uncontrolled dissemination" and "harmful abuse of our openly accessible GMO". Together with the teams ETH_Zurich,  UiOslo_Norway, Lund, Groningen and Uppsala, we discussed whether and how we could assume our GMOs behaviour in the wilderness. In addition we figured out whether and how GMOs could possibly be misused in a harmful way. The results of this discussion helped us  to complete our Safety Form.
Vid. 1: Our team members Tony and Tino at the #Genetic Engineering conference hosted by the iGEM Team Uppsala.

Interactive Maze Design

We posted an announcement on the official iGEM Collaboration site to help us improve our robot algorithm. We developed a software to design mazes and therefor test and improve our robot controling code. As it is usual and obligate for software developers, we reached out for beta testers. Other iGEM teams are predistinated for this job, so we invited all other teams to help us. In addition, we set up tools in form of tablet computers at our human practice events. Some day, the iGEM Team Groningen contacted us. They were our first beta testers. The first mazes of the team, as simple as they were designed, could not be solved by our robot.
Mazepic 1
Fig. 2: The first maze design with our online maze design software. Designed by the iGEM Team Groningen

Due to these feedbacks we have extended the code of the program significantly and found a way to insert a coherent storage possibility, which allows the robot to escape much better from angled corners again and find the end of the maze. After sending the link to the updated version, our friends from Groningen sent us several new designs, which were all solved by the robot.
Mazepic 2
Fig. 3: Maze design with extended code by Groningen

INSA-UPS_France contacted us some time later to test the maze design software too. Using their highly creative approach to design several chambers, we were able to correct mistakes and validate our results even more.
Mazepic 3
Fig. 4: The really creative mazes & chambers of INSA-UPS_France. The iGEM mazes could be solved, but our Thymio had some problems with the other chambers.

Support by sending our Promotor Construct

We contacted SVCE_Chennai after reading their collaboration proposal on the iGEM Collaborations page. We realized we had many similarities in our project as both of us were working on pH as well as temperature regulated systems. The alkaline inducible promotor alx was actually the same. A Skype conference between both teams was organised, which gave us the chance to talk directly to each other and express any difficulties we were faced with so far. Since they had some issues with changing pH in their media, we helped them out by giving them some useful suggestions, like our protocol about what base we use and the concret amount of it to raise the neutral pH of LB and M9 media to 8,5 to induce the promoter.  Since they had some amplification issues with their gBlock, we also shipped them our alx gBlock so that they could work with it. At the end of the summer, they send us their data about how the promoter activity increased with the pH and as we had similar results, we came to the conclusion that our experiments were successful.

Augmented Reality at the Giant Jamboree

After seeing the post of the iGEM team Franconia on the official Collaboration Site, and declaring it as a very creative, interesting and amusing one, we decided to support them. They organise an augmented reality game for smartphones with the help of QR codes distributed throughout the Giant Jamboree. A "plague" breaks out at the event and the QR codes represent either "cure" or “infection” for the respective scanning smartphone. The goal of the game is that at the end of the conference, all virus outbreaks are cured. With little effort, this game can create a very special component of the Giant Jamboree 2017 and this is why we want to support and be part of it.