Difference between revisions of "Team:SCSU-New Haven/Parts"

(Prototype team page)
 
(Prototype team page)
(No difference)

Revision as of 18:34, 30 June 2016

SCSU IGEM SCSU IGEM

SCSU iGEM

What if

TB could be Diagnosed in just a few minutes

One Breath = One Result

As synthetic biologists continue to construct increasingly complex gene regulatory networks, the need for accurate quantitative characterization of their regulatory components becomes more pressing. Despite the BioBrick registry's thorough characterization of the average strength of promoters, there is insufficient description of the variability in their expression. Our project aims to characterize this variability, or noise, for the most commonly used promoters in synthetic biology and provide additional tools for the regulation of these promoters.

About Us

As synthetic biologists continue to construct increasingly complex gene regulatory networks, the need for accurate quantitative characterization of their regulatory components becomes more pressing. Despite the BioBrick registry's thorough characterization of the average strength of promoters, there is insufficient description of the variability in their expression. Our project aims to characterize this variability, or noise, for the most commonly used promoters in synthetic biology and provide additional tools for the regulation of these promoters.

Accomplishments

  • ABCs with Elmo
  • 123s with the Count
  • Singing with Big Bird
  • Being grouchy with Oscar
  • First team from SCSU
  • Created a part that believe that does x-men related things
  • Wiki Freeze sounds so final

Each team will make new parts during iGEM and will submit them to the Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The <groupparts> tag (see below) will generate a table with all of the parts that your team adds to your team sandbox.

Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without needing to refer to the primary literature. Registry users in future years should be able to read your documentation and be able to use the part successfully. Also, you should provide proper references to acknowledge previous authors and to provide for users who wish to know more.

Note

Note that parts must be documented on the Registry. This page serves to showcase the parts you have made. Future teams and other users and are much more likely to find parts by looking in the Registry than by looking at your team wiki.

Adding parts to the registry

You can add parts to the Registry at our Add a Part to the Registry link.

We encourage teams to start completing documentation for their parts on the Registry as soon as you have it available. The sooner you put up your parts, the better you will remember all the details about your parts. Remember, you don't need to send us the DNA sample before you create an entry for a part on the Registry. (However, you do need to send us the DNA sample before the Jamboree. If you don't send us a DNA sample of a part, that part will not be eligible for awards and medal criteria.)

What information do I need to start putting my parts on the Registry?

The information needed to initially create a part on the Registry is:

  • Part Name
  • Part type
  • Creator
  • Sequence
  • Short Description (60 characters on what the DNA does)
  • Long Description (Longer description of what the DNA does)
  • Design considerations

We encourage you to put up much more information as you gather it over the summer. If you have images, plots, characterization data and other information, please also put it up on the part page.

Inspiration

We have a created a collection of well documented parts that can help you get started.

You can also take a look at how other teams have documented their parts in their wiki:

Part Table
<groupparts>iGEM2016 Example</groupparts>