Difference between revisions of "Team:Edinburgh UG/Integrated Practices"

Line 12: Line 12:
 
     <title>Collaborations</title>
 
     <title>Collaborations</title>
  
−
 
+
 
  
 
</head>
 
</head>
Line 6,952: Line 6,952:
 
             <div class="container">
 
             <div class="container">
 
                 <h1>Integrated Human Practices</h1>
 
                 <h1>Integrated Human Practices</h1>
−
                <h2>iGem</h2>
 
 
             </div>
 
             </div>
 
         </div>
 
         </div>
Line 6,965: Line 6,964:
 
         <div class="featurette" id="about">
 
         <div class="featurette" id="about">
 
             <img class="featurette-image img-circle img-responsive pull-right" src="http://placehold.it/500x500">
 
             <img class="featurette-image img-circle img-responsive pull-right" src="http://placehold.it/500x500">
−
             <h2 class="featurette-heading">Demo 1
+
             <h2 class="featurette-heading">DR SZYMANSKI AND DR SCHYFTER
−
                <span class="text-muted">Example 1</span>
+
 
             </h2>
 
             </h2>
−
             <p class="lead"> Text 1</p>
+
             <p class="lead">After coming up with a project idea and designing a way to test out our method, we decided it was time to start a discussion about whether or not our project had practical applications. Our first meeting was with Dr Erika Szymanski and Dr Pablo Schyfter of the University of Edinburgh’s Science, Technology and Innovation Studies Department.</p>
 +
            <p class="lead"> Their input really put our project into focus and laid down a track for the rest of our human practices. They told us that we were trying to target too many people with our DNA storage system and that we needed to be practical about who would actually use our product. As reading and writing data in DNA is slower than storing and retrieving something from a USB drive or even downloading a file from the internet, we needed to focus more on long-term, low access data storage. After this meeting we got in contact with local librarians and data experts. Return to the timeline to read more.</p>
 +
            <p class="lead"> Another takeaway point from the meeting was that up until this point we had not thought about the physical storage of our DNA. Were we planning on storing the DNA in some sort of time capsule that was only to be opened at certain times? Or were we going to focus on more practical and accessible storage of DNA in vials? We addressed this when we tested the viability of DNA in different storage conditions.</p>
 +
 
 +
 
 
         </div>
 
         </div>
  
Line 6,976: Line 6,978:
 
         <div class="featurette" id="services">
 
         <div class="featurette" id="services">
 
             <img class="featurette-image img-circle img-responsive pull-left" src="http://placehold.it/500x500">
 
             <img class="featurette-image img-circle img-responsive pull-left" src="http://placehold.it/500x500">
−
             <h2 class="featurette-heading">Demo 2
+
             <h2 class="featurette-heading">DR ANDY TURNER AND DR ADAM CARTER FROM ARCHER/EPCC
−
                <span class="text-muted">Example 2</span>
+
 
             </h2>
 
             </h2>
−
             <p class="lead">Text 2</p>
+
             <p class="lead">Following our meeting with Drs Szymanski and Schyfter, we set up a time to talk to Dr Turner and Dr Carter from ARCHER and EPCC. ARCHER is a supercomputer at the University that runs simulations and calculations that are too resource intensive to be performed on a regular computer. EPCC hosts ARCHER along with other computing and data facilities. Drs Turner and Carter have extensive experience with generating and storing large amounts of data.</p>
 +
            <p class="lead">Though very positive of our idea, they confessed that DNA data storage would not work best for them. The simulations and research they facilitate require data to be generated and stored instantly and in high volumes, whereas DNA has a read and write time that is too slow to accommodate supercomputing. They suggested that we meet with librarians or archivists that store important, historical data for long periods of time. It is important to securely store this kind of data since it is often unique and cannot be regenerated or simulated.</p>
 +
            <p class="lead">They agreed that using Basic English as a proof of concept was very illustrative of our method, however, they pointed out that we should view the information coded in BabbleBricks to be flexible and that we should stress its arbitrary nature to others. Along with saying that this was one of our strengths, they encouraged us to come up with some sort of cost analysis comparing our assembly method to other storage techniques. They said that defining the ‘workflow’ of our project would help us decide whether we envision a BabbleBlock factory that stores all data in DNA, or whether we could scale down the system to a single machine. See how we investigated this with the Edinburgh Genome Foundry here.</p>
 
         </div>
 
         </div>
  
Line 6,985: Line 6,988:
  
 
         <!-- Third Featurette -->
 
         <!-- Third Featurette -->
 +
        <div class="featurette" id="contact">
 +
            <img class="featurette-image img-circle img-responsive pull-right" src="http://placehold.it/500x500">
 +
            <h2 class="featurette-heading">Demo 3
 +
                <span class="text-muted">Example 3</span>
 +
            </h2>
 +
            <p class="lead">Text 3</p>
 +
        </div>
 +
 +
        <div class="featurette" id="contact">
 +
            <img class="featurette-image img-circle img-responsive pull-right" src="http://placehold.it/500x500">
 +
            <h2 class="featurette-heading">Demo 3
 +
                <span class="text-muted">Example 3</span>
 +
            </h2>
 +
            <p class="lead">Text 3</p>
 +
        </div>
 +
 +
 
         <div class="featurette" id="contact">
 
         <div class="featurette" id="contact">
 
             <img class="featurette-image img-circle img-responsive pull-right" src="http://placehold.it/500x500">
 
             <img class="featurette-image img-circle img-responsive pull-right" src="http://placehold.it/500x500">
Line 6,996: Line 7,016:
  
 
         <!-- Footer -->
 
         <!-- Footer -->
−
       
+
 
  
 
     </div>
 
     </div>
 +
 +
 +
    <div class="row">
 +
            <div class="box">
 +
                <div class="col-lg-12">
 +
                    <hr>
 +
                    <h2 class="intro-text text-center">Follow
 +
                        <strong>Us</strong>
 +
                    </h2>
 +
                    <hr>
 +
                    <div class="intro-text text-center">
 +
                        <ul class="list-inline banner-social-buttons">
 +
                            <li>
 +
                                <a href="https://twitter.com/EdiGEM2016"><img src="https://static.igem.org/mediawiki/2016/9/94/Edinburgh2_t2.jpg"></img></a>
 +
                            </li>
 +
                            <li>
 +
                                <a href="https://www.facebook.com/EdiGEM2016"><img src="https://static.igem.org/mediawiki/2016/c/ce/Edinburgh2_f2.png"></img></a>
 +
                            </li>
 +
                            <li>
 +
                                <a href="https://www.instagram.com/edigem2016/"><img src="https://static.igem.org/mediawiki/2016/6/64/Edinburgh2_insta2.png"></img></a>
 +
                            </li>
 +
                        </ul>
 +
                    </div>
 +
                </div>
 +
            </div>
 +
        </div>
 +
 
     <!-- /.container -->
 
     <!-- /.container -->
  

Revision as of 21:12, 11 October 2016

Collaborations

Integrated Human Practices

DR SZYMANSKI AND DR SCHYFTER

After coming up with a project idea and designing a way to test out our method, we decided it was time to start a discussion about whether or not our project had practical applications. Our first meeting was with Dr Erika Szymanski and Dr Pablo Schyfter of the University of Edinburgh’s Science, Technology and Innovation Studies Department.

Their input really put our project into focus and laid down a track for the rest of our human practices. They told us that we were trying to target too many people with our DNA storage system and that we needed to be practical about who would actually use our product. As reading and writing data in DNA is slower than storing and retrieving something from a USB drive or even downloading a file from the internet, we needed to focus more on long-term, low access data storage. After this meeting we got in contact with local librarians and data experts. Return to the timeline to read more.

Another takeaway point from the meeting was that up until this point we had not thought about the physical storage of our DNA. Were we planning on storing the DNA in some sort of time capsule that was only to be opened at certain times? Or were we going to focus on more practical and accessible storage of DNA in vials? We addressed this when we tested the viability of DNA in different storage conditions.

DR ANDY TURNER AND DR ADAM CARTER FROM ARCHER/EPCC

Following our meeting with Drs Szymanski and Schyfter, we set up a time to talk to Dr Turner and Dr Carter from ARCHER and EPCC. ARCHER is a supercomputer at the University that runs simulations and calculations that are too resource intensive to be performed on a regular computer. EPCC hosts ARCHER along with other computing and data facilities. Drs Turner and Carter have extensive experience with generating and storing large amounts of data.

Though very positive of our idea, they confessed that DNA data storage would not work best for them. The simulations and research they facilitate require data to be generated and stored instantly and in high volumes, whereas DNA has a read and write time that is too slow to accommodate supercomputing. They suggested that we meet with librarians or archivists that store important, historical data for long periods of time. It is important to securely store this kind of data since it is often unique and cannot be regenerated or simulated.

They agreed that using Basic English as a proof of concept was very illustrative of our method, however, they pointed out that we should view the information coded in BabbleBricks to be flexible and that we should stress its arbitrary nature to others. Along with saying that this was one of our strengths, they encouraged us to come up with some sort of cost analysis comparing our assembly method to other storage techniques. They said that defining the ‘workflow’ of our project would help us decide whether we envision a BabbleBlock factory that stores all data in DNA, or whether we could scale down the system to a single machine. See how we investigated this with the Edinburgh Genome Foundry here.

Demo 3 Example 3

Text 3

Demo 3 Example 3

Text 3

Demo 3 Example 3

Text 3

Follow Us