Difference between revisions of "Team:Waterloo/Software"

(corrected formatting error in dropdown panels)
(done content!)
 
(7 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<div class="container main-container">
 
<div class="container main-container">
 
     <h1>Software</h1>
 
     <h1>Software</h1>
     <section id="Modelling" title="Model Code">
+
     <section id="Modelling" title="GitHub">
         <h2>Mathematical Modelling</h2>
+
         <p>Software played an important role in CRISPieR project, since mathematical and computational modelling is a major area of interest for Waterloo iGEM. The team maintained <a href="https://github.com/igem-waterloo">a GitHub organization</a> throughout 2015- our nearly 600 commit messages and more than 100 pull requests can be browsed at your convenience.</p>
         <p>
+
         <figure>
            Give an overview of our GitHub code here.
+
        <img src="/wiki/images/c/ca/Waterloo_github_contributions.png" class="img-responsive" />
         </p>
+
        <figcaption>The mounting graph of contributions in our <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015">2015 repository</a>.</figcaption>
 +
        </figure>
 +
        <h3>Summary of uwaterloo-igem-2015/models</h3>
 +
        <ul>
 +
        <li><strong>targeting</strong>: Python code from <a href="https://2015.igem.org/Team:Waterloo/Modeling/Cas9_Dynamics">CRISPR/Cas9 model</a>, run <em>genome_simulation.py</em> to see results for a single genome, <em>genome_multisimulation.py</em> gives averaged results for many simulaitons</li>
 +
         <li><strong>tridimensional</strong>: various bash and Python/PyRosetta scripts for <a href="https://2015.igem.org/Team:Waterloo/Modeling/PAM_Flexibility">rational design</a> of cas9 mutants with engineered PAM specificity, see notes below</li>
 +
        <li><strong>viralassembly</strong>: MATLAB code for the <a href="https://2015.igem.org/Team:Waterloo/Modeling/CaMV_Replication">CaMV Replication</a> model, run <em>viralAssemblyTimeSeries.m</em> to see time series plots</li>
 +
        <li><strong>viralspread</strong>: NetLogo code for the <a href="https://2015.igem.org/Team:Waterloo/Modeling/Intercellular_Spread">viral spread</a> model, run <em>ViralSpreadFullODE.nlogo</em> to see results incorporating Euler's method approximation of viral spread ODE</li>
 +
        </ul>
 
     </section>
 
     </section>
 
     <section id="pyrosetta" title="PyRosetta & PyMOL">
 
     <section id="pyrosetta" title="PyRosetta & PyMOL">
 
         <h2>PyRosetta and PyMOL</h2>
 
         <h2>PyRosetta and PyMOL</h2>
         <h3>Installation Instructions</h3>
+
        <p>We used PyRosetta and PyMOL quite extensively when <a href="https://2015.igem.org/Team:Waterloo/Modeling/PAM_Flexibility">modelling engineered PAM specificity</a>. The documentation for PyRosetta is rather sparse and we have often encountered our <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/wiki/PyRosetta-Fold-Trees">hastily-written</a> <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/wiki/Building-PyRosetta-from-Source">GitHub</a> <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/wiki/PyMOL-and-PyRosetta-Setup-for-Windows">wiki</a> <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/wiki/PyMOL-and-PyRosetta-Setup-for-Linux">pages</a> on the software rather distressingly near the top of Google results.</p>
 +
<p>The sections below, in addition to our <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/tree/master/models/tridimensional/docking_validation">scripts</a> and the <a href="https://2015.igem.org/Team:Waterloo/Modeling/PAM_Flexibility">PAM Flexibility page</a>, provide some documentation for other iGEM teams looking to model protein binding with PyRosetta.</p>
 +
 
 +
         <h3>Setup Instructions</h3>
 
         <div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
 
         <div class="panel-group" id="accordion" role="tablist" aria-multiselectable="true">
 
             <div class="panel panel-default">
 
             <div class="panel panel-default">
Line 171: Line 182:
 
                 <div id="source-collapse" class="panel-collapse collapse" role="tabpanel" aria-labelledby="source-install">
 
                 <div id="source-collapse" class="panel-collapse collapse" role="tabpanel" aria-labelledby="source-install">
 
                     <div class="panel-body">
 
                     <div class="panel-body">
 +
<p> This guide was developed following instructions from the <a href-"http://www.pyrosetta.org/documentation#TOC-Building-PyRosetta-from-source">PyRosetta online documentation</a>. All installs are local to the user.</p>
  
                    FILL IN HERE
+
<p>It is recommended to use the default binaries provided by PyRosetta. However, the following scenarios are reasons for installing PyRosetta from source:</p>
 +
<ul>
 +
<li>You need to have bindings for your own custom C++ code that is not part of Rosetta master branch</li>
 +
<li>PyRosetta needs to run custom-build Python (for example if you would like to use some Python packages from MacPorts, Fink or Homebrew who deploy its own version of Python)</li>
 +
<li>You need to use a different version of Python</li>
 +
<li>You can't install GLIBC required by pre-build binaries</li>
 +
<li>You are running on a 32Bit system</li>
 +
</ul>
 +
 
 +
<h3>Deploying PyRosetta Build Environment</h3>
 +
<h4>Dependencies</h4>
 +
<strong>Rosetta Source</strong>
 +
 
 +
<p>Download the Academic Version of Rosetta software, and extract the archive
 +
<pre><code>tar xvzf rosetta_bin_linux_####.##.#####_bundle.tgz ~/rosetta_bin_linux</code></pre>
 +
 
 +
<p>To easily install all of the following dependencies, run the following:</p>
 +
<pre><code>cd rosetta_bin_linux/
 +
cd tools/PyRosetta.develop/
 +
./DeployPyRosetta.py</code></pre>
 +
 
 +
<p>This should take some time. If at the end everything installs correctly, skip to Building PyRosetta. Otherwise, keep reading the following subsections.</p>
 +
 
 +
<strong>Python</strong>
 +
<p>Install Python >= 2.5. Most systems come with this installed, but if not, it's available <a href="https://www.python.org/">here</a></p>
 +
 
 +
<strong>CMake</strong>
 +
 
 +
<p>Like Python, most systems have this installed by default. Install <a href="http://www.cmake.org/install/">Cmake</a> from here if not.
 +
<pre><code>./bootstrap --prefix=~/Applications/
 +
make
 +
make install</code></pre>
 +
 
 +
<strong>GCCXML</strong>
 +
<pre><code>mkdir gccxml-cvs
 +
cd gccxml-cvs
 +
cvs -d :pserver:anoncvs@www.gccxml.org:/cvsroot/GCC_XML co -D 2009-04-15 gccxml
 +
mkdir gccxml-build
 +
cd gccxml-build
 +
cmake ../gccxml -DCMAKE_INSTALL_PREFIX:PATH=~/Applications/
 +
make && make install</code></pre>
 +
 
 +
<strong>PyGCCXML and Py++</strong>
 +
 
 +
<p>Download PyGCCXML and Py++ archives from <a href="https://sourceforge.net/project/showfiles.php?group_id=118209">SourceForge</a>, and extract the zip file.</p>
 +
<pre><code>unzip pygccxml-1.0.0.zip
 +
cd pygccxml-1.0.0
 +
python setup.py install --user
 +
cd ..
 +
unzip Py++-1.0.0.zip
 +
cd Py++-1.0.0
 +
python setup.py install --user</code></pre>
 +
 
 +
<p>Check that all of the above are installed correctly</p>
 +
<pre><code>python
 +
>>> import pygccxml, pyplusplus
 +
>>> print pygccxml.__version__, pyplusplus.__version__</code></pre>
 +
 
 +
<p>If installed correctly, the output is</p>
 +
<pre><code>1.0.0 1.0.0</code></pre>
 +
 
 +
<strong>LibBoost</strong>
 +
 
 +
<p>Install Boost (download from <a href="http://boost.org">here</a> or <a href="http://sourceforge.net/projects/boost/files/boost/">here</a>). Most Linux distributions will come with boost. If so, skip to the next step. If not, run the following commands</p>
 +
<pre><code>tar xvzf boost_1_58_0.tar.gz
 +
cd boost_1_58_0/
 +
./bootstrap.sh --prefix=/home/<username>/Applications/
 +
./b2 install --prefix=/home/<username>/Applications/</code></pre>
 +
 
 +
<p>In the bootstrap command, the prefix must be an absolute path.</p>
 +
<strong>Building Rosetta</strong>
 +
 
 +
<p>Test the installation by navigating to ~/rosetta_bin_linux/main/source/src/python/bindings/ and running</p>
 +
 
 +
<pre><code>./BuildBindings.py -I ~/Applications/include -L ~/Applications/lib -L ~/./local/lib</code></pre>
 +
 
 +
<p>(This takes a very long time, there are lots of files to build)</p>
 +
<strong>Building PyRosetta</strong>
 +
<p>After successfully deploying the PyRosetta build environment, copy the generated BuildPyRosetta.sh into the main Rosetta source directory: <pre><code>/rosetta/main/source/BuildPyRosetta.sh</code></pre> and run it within this directory to build PyRosetta.
  
 
                 </div>
 
                 </div>
Line 182: Line 272:
 
                     <h4 class="panel-title">
 
                     <h4 class="panel-title">
 
                     <a role="button" data-toggle="collapse" data-parent="#accordion" href="#waterloo-collapse" aria-expanded="false" aria-controls="waterloo-collapse">
 
                     <a role="button" data-toggle="collapse" data-parent="#accordion" href="#waterloo-collapse" aria-expanded="false" aria-controls="waterloo-collapse">
                     Using Waterloo Scripts
+
                     Using Team Waterloo Scripts
 
                     <span class="hidden-xs toggle-arrow pull-right">Panel Toggle</span>
 
                     <span class="hidden-xs toggle-arrow pull-right">Panel Toggle</span>
 
                     </a>
 
                     </a>
Line 191: Line 281:
 
<h3>Recommended Directory Structure</h3>
 
<h3>Recommended Directory Structure</h3>
  
<p>The scripts developed by the Waterloo iGEM team can be called from different computers without errors using the following directory structure:</p>
+
<p>The scripts developed by the Waterloo iGEM team were developed using the following directory structure. Setting up a similar structure should allow you to use the same the scripts on different computers, making development significantly easier.</p>
 
<ol>
 
<ol>
<li>In the same directory as the PyRosetta folder, create another folder called working.</li>
+
<li>In the same directory as the PyRosetta folder, create another folder called <em>working</em>.</li>
<li>Within the working directory create folders pdb/, results/, and scripts/</li>
+
<li>Within the working directory create folders <em>pdb/</em>, <em>results/</em>, and <em>scripts/</em></li>
<li>Create subdirectories pdb/wt/, results/batch/, and results/batch/log/</li>
+
<li>Create subdirectories <em>results/batch/</em>, and <em>results/batch/log/</em></li>
<li>Download the files dock_variants.py, results.csv, and dock_caller.sh into the scripts directory.</li>
+
<li>Download the files in the <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/tree/master/models/tridimensional/docking_validation">models/tridimensional/docking_validation folder</a> on the Waterloo iGEM 2015 github into the <em>working/scripts</em> directory.</li>
 
</ol>
 
</ol>
<p>This sets up a directory structure that scripts can be called from different computers without errors.</p>
+
 
 +
<h3>Getting Started with Cas9-DNA docking</h3>
 +
<p> The batch_dock.sh script <a href="https://github.com/igem-waterloo/uwaterloo-igem-2015/tree/master/models/tridimensional/docking_validation">found here</a> is designed to perform docking of cas9/dsDNA pdb files with different 3 and 4 nucleotide pams. The script includes basic usage documentation for performing a docking run. If you have any questions regarding scrip usage, please contact the Waterloo iGEM team.</p>
  
 
                 </div>
 
                 </div>
Line 208: Line 300:
 
     <section id="lab" title="Lab Software">
 
     <section id="lab" title="Lab Software">
  
         <h2>Lab Team Calculators</h2>
+
         <h2>Restriction Digest Calculator</h2>
         <p>
+
         <div class="row">
    <a href="https://igem-waterloo.github.io/uwaterloo-igem-2015/digest-calculator/"> Digest Calculator</a>
+
        <div class="col-sm-6">
    <a href="https://igem-waterloo.github.io/uwaterloo-igem-2015/ligation-calculator/"> Ligation Calculator</a>
+
        <a href="https://igem-waterloo.github.io/uwaterloo-igem-2015/digest-calculator/"><img src="/wiki/images/1/1b/Waterloo_digest_calculator_screenshot.png" alt="digest calculator screenshot" class="img-responsive" /></a>
        </p>
+
        </div>
 +
        <div class="col-sm-6">
 +
        </div>
 +
<p>The team often makes very repetitive calculations when doing restriction digests. One of the lab team members ended up creating an online spreadsheet to assist with the calculations and the modelling team decided to convert it into an online tool for others to use.
 +
<p>The <a href="https://igem-waterloo.github.io/uwaterloo-igem-2015/digest-calculator/">Digest Calculator</a> made available on our website allows iGEM teams to easily and automatically find the volumes needed for their restriction digests.</p>
 
     </section>
 
     </section>
 
   </div>
 
   </div>

Latest revision as of 04:32, 18 September 2015

Software

Software played an important role in CRISPieR project, since mathematical and computational modelling is a major area of interest for Waterloo iGEM. The team maintained a GitHub organization throughout 2015- our nearly 600 commit messages and more than 100 pull requests can be browsed at your convenience.

The mounting graph of contributions in our 2015 repository.

Summary of uwaterloo-igem-2015/models

  • targeting: Python code from CRISPR/Cas9 model, run genome_simulation.py to see results for a single genome, genome_multisimulation.py gives averaged results for many simulaitons
  • tridimensional: various bash and Python/PyRosetta scripts for rational design of cas9 mutants with engineered PAM specificity, see notes below
  • viralassembly: MATLAB code for the CaMV Replication model, run viralAssemblyTimeSeries.m to see time series plots
  • viralspread: NetLogo code for the viral spread model, run ViralSpreadFullODE.nlogo to see results incorporating Euler's method approximation of viral spread ODE

PyRosetta and PyMOL

We used PyRosetta and PyMOL quite extensively when modelling engineered PAM specificity. The documentation for PyRosetta is rather sparse and we have often encountered our hastily-written GitHub wiki pages on the software rather distressingly near the top of Google results.

The sections below, in addition to our scripts and the PAM Flexibility page, provide some documentation for other iGEM teams looking to model protein binding with PyRosetta.

Setup Instructions

PyRosetta

Adapted from this guide.

PyRosetta is fairly simple to install on Windows, assuming Python is installed. However, it does take large amounts of RAM (you'll need a computer with >4GB), so you may need to use the Linux version for older computers.

  1. Download Python 2.7. You MUST use the 64-bit version, and make sure to select the option to add python to your path.
  2. Install iPython. Open a command prompt, and type python -m pip install ipython. This should download and install ipython in one step.
  3. Get pyreadline (Download the 64-bit version, pyreadline-2.0.win-amd64.exe). Run the exe once download is complete. This provides a bunch of tab-completion and other handy features, it isn't necessary, but is very helpful.
  4. Get a PyRosetta license. These are free for academic/non-commercial use.
  5. Once your license is processed (which should only take a couple minutes), you'll receive an email with a username and password, and a link to the download.
  6. Download the most recent version of the PyRosetta windows. You'll want the .exe for the latest release.
  7. When the download completes, run the exe to install PyRosetta.
  8. Two shortcuts should appear on the desktop, one for "iPython PyRosetta shell" and on for "PyMOL PyRosetta Link". Delete the second one, as it doesn't work with the version of PyMOL we'll be using.
  9. Open the ipython shell using the remaining shortcut. type:
    from rosetta import *
                rosetta.init()
                
  10. If you get a message ending with something like the following, you've successfully installed PyRosetta.
    core.init.random: RandomGenerator:init: Normal mode, seed=-1088387864 RG_type=mt19937

PyMOL

Adapted from this guide

  1. Create a folder (e.g. C:\PyMOL_Install) to hold the files>
  2. Download:
    • pymol-1.7.6.0-cp27-none-win_amd64.whl
    • pymol_launcher-1.0-cp27-none-win_amd64.whl
    • numpy-1.9.2+mkl-cp27-none-win_amd64.whl
    • Pmw-2.0.0-py2-none-any.whl
  3. Move the files to the folder you created.
  4. Start a command prompt, and move to the directory you saved the files in:
    cd C:\PyMOL_Install
  5. Assuming you added python to you path earlier, run the command:
    python -m pip install --no-index --find-link="%CD%" --pre pymol_launcher-1.0-cp27-none-win_amd64.whl
    1. If there are errors, try installing the .whl files in this order: numpy, Pmw, pymol-1.7.6.0, pymol_launcher
    2. If there are no errors, you should be able start PyMOL using C:\Python27\PyMOL.exe
  6. Create a shortcut on your desktop to make starting PyMOL easier.

Linking PyMOL and PyRosetta

Adapted from this guide.

  1. Start PyMOL
  2. In the command line (upper window), type
    run C:\Program Files\PyRosetta\PyMOLPyRosettaServer.py
  3. You should see a message just above saying:
    
                    PyMOL <---> PyRosetta link started!
                    at 127.0.0.1 port 65000
    If it doesn't work, check if PyRosetta installed to the above path (which it should have if you followed the instructions on this page). If the path is different, modify the run command to match.
  4. Go to the 'File' menu and select 'Edit pymolrc'.
  5. Add the same run command to the file, then save it. This will start the PyRosetta link automatically every time you run PyMOL.

PyRosetta

For Mac OSX (vanilla)

Adapted from this guide and this guide.

  1. A license must be obtained prior to installation, to obtain an academic license (it's free by the way) please visit this site to get one.
  2. After obtaining a license, go back to the download page and choose the PyRosetta monolith release for Mac. (NOTE: Do not use the download link provided in the license email for Linux and Mac installations! It does not include links to the latest version of PyRosetta.
  3. Create a new directory (new folder) in the space you'd like to install it (I would personally recommend creating a workspace directory and then un-tarring the pyrosetta.tar.bz2 in workspace, so the path to the .tar.bz2 file would be
    users/'YOURUSERNAME'/workspace/PyRosetta.monolith.mac.release-55.tar.bz2
  4. In the terminal type in
    tar -vjxf PyRosetta-monolith.mac.release-55.tar.bz2
    to un-tar the file, or alternatively just click on it to decompress it.
  5. Since Mac already comes with Python 2.7, python does not have to be installed. Open a terminal window and paste in
    cd ~/workspace/PyRosetta.monolith.mac.release-55
    to move to the PyRosetta directory.
  6. Once you're in the directory, start python by typing
    python
    in the terminal, and import the PyRosetta library with the following commands:
    import rosetta
    rosetta.init() 
    
  7. If no errors or complaints have been made by your machine, congratulations, you have just installed software that is notoriously difficult to install!

PyRosetta for Mac OSX with a Package Manager (e.g. Homebrew)

Unfortunately, for Mac users that use either homebrew, fink, or macports, PyRosetta must be built from source, since custom versions of python are used when one of the above are installed. If you don't know what homebrew, fink, or macports is, you probably don't have it installed so use the instructions above.

  1. Obtain an academic Rosetta License from here.
  2. Once you have a license and have been prompted to the download page, download the latest source version of Rosetta. At the moment it is Rosetta 2015.19.
  3. After downloading the .tgz and un-tarring rosetta into the directory of your choice, go into the directory where rosetta is in and find
    building.txt
    located in the following path
    main/source/src/python/bindings/
    which contains specific instructions to build and deploy pyrosetta.

PyMOL

PyRosetta

Please ensure you're running at 64-bit version of Ubuntu or your preferred Linux flavour, as PyRosetta is available in 64-bit only.

  1. Installing iPython first is useful, as it allows much easier interaction with PyRosetta:
    sudo apt-get install ipython
  2. Download the latest release.namespace build for Ubuntu (you will have to sign up for a free academic license).
  3. Place the file where you want to use it (Note: Somewhere convenient to access, such as the your home folder, is recommened since you will be running files from this folder each time to use PyRosetta/PyRosetta+PyMOL).
  4. In terminal, navigate to the folder above, and use
    tar -vjxf PyRosetta-.tar.bz2
    to extract the file.
  5. Run the script which sets up your environment by typing
    source SetPyRosettaEnvironment.sh
    while in the PyRosetta folder. This must be done each time you want to use Rosetta.
  6. Open IPython (ipython) and try running PyRosetta to see that it set up properly:
    import rosetta
    rosetta.init()
    .

PyMOL

Run this command in terminal:

sudo apt-get install pymol

This will install the version of PyMOL which is hosted on Ubuntu's package directory. This is not the newest version, but it's reasonably up-to-date, and this method has the added bonus of automatically installing all dependencies that are need for PyMOL.

This guide was developed following instructions from the PyRosetta online documentation. All installs are local to the user.

It is recommended to use the default binaries provided by PyRosetta. However, the following scenarios are reasons for installing PyRosetta from source:

  • You need to have bindings for your own custom C++ code that is not part of Rosetta master branch
  • PyRosetta needs to run custom-build Python (for example if you would like to use some Python packages from MacPorts, Fink or Homebrew who deploy its own version of Python)
  • You need to use a different version of Python
  • You can't install GLIBC required by pre-build binaries
  • You are running on a 32Bit system

Deploying PyRosetta Build Environment

Dependencies

Rosetta Source

Download the Academic Version of Rosetta software, and extract the archive

tar xvzf rosetta_bin_linux_####.##.#####_bundle.tgz ~/rosetta_bin_linux

To easily install all of the following dependencies, run the following:

cd rosetta_bin_linux/
cd tools/PyRosetta.develop/
./DeployPyRosetta.py

This should take some time. If at the end everything installs correctly, skip to Building PyRosetta. Otherwise, keep reading the following subsections.

Python

Install Python >= 2.5. Most systems come with this installed, but if not, it's available here

CMake

Like Python, most systems have this installed by default. Install Cmake from here if not.

./bootstrap --prefix=~/Applications/
make
make install
GCCXML
mkdir gccxml-cvs
cd gccxml-cvs
cvs -d :pserver:anoncvs@www.gccxml.org:/cvsroot/GCC_XML co -D 2009-04-15 gccxml
mkdir gccxml-build
cd gccxml-build
cmake ../gccxml -DCMAKE_INSTALL_PREFIX:PATH=~/Applications/
make && make install
PyGCCXML and Py++

Download PyGCCXML and Py++ archives from SourceForge, and extract the zip file.

unzip pygccxml-1.0.0.zip
cd pygccxml-1.0.0
python setup.py install --user
cd ..
unzip Py++-1.0.0.zip
cd Py++-1.0.0
python setup.py install --user

Check that all of the above are installed correctly

python
>>> import pygccxml, pyplusplus
>>> print pygccxml.__version__, pyplusplus.__version__

If installed correctly, the output is

1.0.0 1.0.0
LibBoost

Install Boost (download from here or here). Most Linux distributions will come with boost. If so, skip to the next step. If not, run the following commands

tar xvzf boost_1_58_0.tar.gz
cd boost_1_58_0/
./bootstrap.sh --prefix=/home//Applications/
./b2 install --prefix=/home//Applications/

In the bootstrap command, the prefix must be an absolute path.

Building Rosetta

Test the installation by navigating to ~/rosetta_bin_linux/main/source/src/python/bindings/ and running

./BuildBindings.py -I ~/Applications/include -L ~/Applications/lib -L ~/./local/lib

(This takes a very long time, there are lots of files to build)

Building PyRosetta

After successfully deploying the PyRosetta build environment, copy the generated BuildPyRosetta.sh into the main Rosetta source directory:

/rosetta/main/source/BuildPyRosetta.sh
and run it within this directory to build PyRosetta.

Recommended Directory Structure

The scripts developed by the Waterloo iGEM team were developed using the following directory structure. Setting up a similar structure should allow you to use the same the scripts on different computers, making development significantly easier.

  1. In the same directory as the PyRosetta folder, create another folder called working.
  2. Within the working directory create folders pdb/, results/, and scripts/
  3. Create subdirectories results/batch/, and results/batch/log/
  4. Download the files in the models/tridimensional/docking_validation folder on the Waterloo iGEM 2015 github into the working/scripts directory.

Getting Started with Cas9-DNA docking

The batch_dock.sh script found here is designed to perform docking of cas9/dsDNA pdb files with different 3 and 4 nucleotide pams. The script includes basic usage documentation for performing a docking run. If you have any questions regarding scrip usage, please contact the Waterloo iGEM team.

Restriction Digest Calculator

digest calculator screenshot

The team often makes very repetitive calculations when doing restriction digests. One of the lab team members ended up creating an online spreadsheet to assist with the calculations and the modelling team decided to convert it into an online tool for others to use.

The Digest Calculator made available on our website allows iGEM teams to easily and automatically find the volumes needed for their restriction digests.

Top