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

Line 1: Line 1:
 
{{NAWI_Graz:navbar}}
 
{{NAWI_Graz:navbar}}
−
<html>
 
  
 +
  <div class="section section-heading container">
 +
    <h1>COLLABORATIONS</h1>
 +
  </div>
 +
  <br>
 +
 
 +
  <div class="section 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
 +
      communication 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.
 +
    </div>
 +
  </div>
 +
  <br>
  
 +
  <div class="section container">
 +
    <h2 class="section-sub">European Meet Up</h2>
 +
    <div class="section-text container">
 +
      From the team [Tu Delft] we have been noticed by an e-mail that they will organise a 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 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>
 +
  <br>
  
 +
  <div class="section container">
 +
    <h2 class="section-sub">General Support</h2>
 +
    <div class="section-text container">
 +
      Already in Delft, we have communicated more intensively with the team [Tu_Darmstadt], 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>
 +
  <br>
  
 +
  <div class="section container">
 +
    <h2 class="section-sub">Online Discussion about Safety</h2>
 +
    <div class="row">
 +
      <div class="section-text col-sm">
 +
        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 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 [ETH_Zurich], [UiOslo_Norway], [Lund], [Groningen] and
 +
        [Uppsala], 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 [Safety Form].
 +
      </div>
 +
      <div class="section-image col-sm border border-secondary">
 +
        <img src="" alt="Screenshot of the online video conference discussion.">
 +
      </div>
 +
    </div>
 +
  </div>
 +
  <br>
  
 +
  <div class="section container">
 +
    <h2 class="section-sub">Interactive Maze Design</h2>
 +
    <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
 +
      obligate group of beta testers for our online maze design software, the iGEM Team [Groningen] contacted us. The first
 +
      mazes of the team, as simple as they were designed, could not be solved by our robot.
 +
    </div>
 +
    <div class="section-image col-sm border border-secondary">
 +
      <img src="" alt="Mazepic 1">
 +
    </div>
 +
    <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
 +
      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>
 +
    <div class="section-image col-sm border border-secondary">
 +
      <img src="" alt="Mazepic 2">
 +
    </div>
 +
    <div class="section-text container">
 +
      [INSA-UPS_France] contacted us some time later to test the labyrinth design software too. Using their highly creative approach
 +
      to design several mazes, we were able to correct mistakes and validate our results even more.
 +
    </div>
 +
    <div class="section-image col-sm border border-secondary">
 +
      <img src="" alt="Mazepic 3">
 +
    </div>
 +
    <br>
  
 +
    <div class="section container">
 +
      <h2 class="section-sub">Support by sending our Promotor Construct</h2>
 +
      <div class="section-text col-sm">
 +
        We reached out for [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 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. Since they had some amplification issues with
 +
        their gBlock, we also shipped them our alx gBlock so that they could work with it.
 +
      </div>
 +
    </div>
 +
</body>
 +
<br>
  
−
<div class="clear"></div>
+
<div class="section container">
−
 
+
  <h2 class="section-sub">Augmented Reality at the Giant Jamboree</h2>
−
<div class="column full_size">
+
  <div class="row">
−
<h1>Collaborations</h1>
+
    <div class="section-text col-sm">
−
 
+
      We reached out for [SVCE_Chennai] after reading their collaboration proposal on the iGEM Collaborations page. We realized
−
<p>
+
      we had many similarities in our project as both of us were working on pH as well as temperature regulatory systems
−
Sharing and collaboration are core values of iGEM. We encourage you to reach out and work with other teams on difficult problems that you can more easily solve together.
+
      and the alkaline inducible promotor was actually the same, alx. A skype call between both teams,which gave us a chance
−
</p>
+
      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. Since they had some amplification issues with their
−
<h3>Silver Medal Criterion #2</h3>
+
      gBlock, we also shipped them our alx gBlock so that they could work with it.
−
<p>
+
    </div>
−
Complete this page if you intend to compete for the silver medal criterion #2 on collaboration. Please see the <a href="https://2017.igem.org/Judging/Medals">2017 Medals Page</a> for more information.
+
  </div>
−
</p>
+
−
 
+
−
<div class="column half_size">
+
−
 
+
−
<h4> Which other teams can we work with? </h4>
+
−
<p>
+
−
You can work with any other team in the competition, including software, hardware, high school and other tracks. You can also work with non-iGEM research groups, but they do not count towards the iGEM team collaboration silver medal criterion.
+
−
</p>
+
−
 
+
−
<p>
+
−
In order to meet the silver medal criteria on helping another team, you must complete this page and detail the nature of your collaboration with another iGEM team.
+
−
</p>
+
−
 
+
 
</div>
 
</div>
  
−
 
−
 
−
<div class="column half_size">
 
−
<p>
 
−
Here are some suggestions for projects you could work on with other teams:
 
−
</p>
 
−
 
−
<ul>
 
−
<li> Improve the function of another team's BioBrick Part or Device</li>
 
−
<li> Characterize another team's part </li>
 
−
<li> Debug a construct </li>
 
−
<li> Model or simulating another team's system </li>
 
−
<li> Test another team's software</li>
 
−
<li> Help build and test another team's hardware project</li>
 
−
<li> Mentor a high-school team</li>
 
−
</ul>
 
−
</div>
 
−
 
−
 
−
</html>
 
 
{{NAWI_Graz:footer}}
 
{{NAWI_Graz:footer}}

Revision as of 14:15, 24 October 2017

COLLABORATIONS

 

 

     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 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

     From the team [Tu Delft] we have been noticed by an e-mail that they will organise a 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 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.

General Support

     Already in Delft, we have communicated more intensively with the team [Tu_Darmstadt], 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.

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 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 [ETH_Zurich], [UiOslo_Norway], [Lund], [Groningen] and
       [Uppsala], 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 [Safety Form].

       <img src="" alt="Screenshot of the online video conference discussion.">

Interactive Maze Design

     After we announced on the official iGEM Collaboration site to help us improving our robot algorithm by being part of our
     obligate group of beta testers for our online maze design software, the iGEM Team [Groningen] contacted us. The first
     mazes of the team, as simple as they were designed, could not be solved by our robot.

     <img src="" alt="Mazepic 1">

     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.

     <img src="" alt="Mazepic 2">

     [INSA-UPS_France] contacted us some time later to test the labyrinth design software too. Using their highly creative approach
     to design several mazes, we were able to correct mistakes and validate our results even more.

     <img src="" alt="Mazepic 3">

Support by sending our Promotor Construct

       We reached out for [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 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. Since they had some amplification issues with
       their gBlock, we also shipped them our alx gBlock so that they could work with it.

</body>

Augmented Reality at the Giant Jamboree

     We reached out for [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 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. Since they had some amplification issues with their
     gBlock, we also shipped them our alx gBlock so that they could work with it.