|
|
| Line 3: |
Line 3: |
| | | | |
| | <html> | | <html> |
| - | <p class="big"> This page is under construction </p>
| + | Background on the construction: some flow this summer showed that pdCas9 with crRNA targeting this GFP1 sequence repressed nicely (as did GFP3 but not GFP2) so we picked this one to try making decoys for. The actual sequence is the 20bp of GFP1, the PAM, and then 10 more bp of spacer that come from the GFP orf. We added the spacer reasoning that dCas9 occupies space outside of just the 20bp matching crRNA, and after eyeballing the crystal structure 4008.pdb (which should be referenced & pictured) it looked like we needed about enough space for 1 additional turn of DNA outside of the 20bp. 10.5bp is ~1 turn, 3 bp is taken care of by PAM, so we added 10 to be safe. MZ was involved in this design stuff |
| | | | |
| - | == This page is under construction ==
| |
| - | The information below was provided by iGEM.
| |
| - |
| |
| - | '''To Fix:'''
| |
| - | * Padding, padding, padding.
| |
| - |
| |
| - | ===Parts Submitted to the Registry===
| |
| - | *What information do I need to start putting my parts on the Registry?
| |
| - | An important aspect of the iGEM competition is the use and creation of standard biological parts. Each team will make new parts during iGEM and will submit them to the <a href="http://partsregistry.org"> Registry of Standard Biological Parts. The iGEM software provides an easy way to present the parts your team has created. The "groupparts" tag will generate a table with all of the parts that your team adds to your team sandbox.
| |
| - |
| |
| - | '''Note that if you want to document a part you need to document it on the [http://partsregistry.org Registry Registry], not on your team wiki.''' Future teams and other users and are much more likely to find parts on the Registry than on your team wiki.
| |
| - |
| |
| - |
| |
| - | Remember that the goal of proper part documentation is to describe and define a part, so that it can be used without a need 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.
| |
| - |
| |
| - | *When should you put parts into the Registry?
| |
| - |
| |
| - | As soon as possible! 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 recall you will have of all details surrounding your parts. Remember you don't need to send us the DNA to create an entry for a part on the Registry. However, you must send us the sample/DNA before the Jamboree. Only parts for which you have sent us samples/DNA are eligible for awards and medal requirements.
| |
| - |
| |
| - | *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. Check out part [http://parts.igem.org/Part:BBa_K404003 BBa_K404003] for an excellent example of a highly characterized part.
| |
| - |
| |
| - | You can add parts to the Registry at our [http://parts.igem.org/Add_a_Part_to_the_Registry Add a Part to the Registry] link.
| |
| - |
| |
| - | Any parts your team has created will appear in this table below:
| |
| | | | |
| | <groupparts>iGEM013 Duke</groupparts> | | <groupparts>iGEM013 Duke</groupparts> |
| | </html> | | </html> |
Background on the construction: some flow this summer showed that pdCas9 with crRNA targeting this GFP1 sequence repressed nicely (as did GFP3 but not GFP2) so we picked this one to try making decoys for. The actual sequence is the 20bp of GFP1, the PAM, and then 10 more bp of spacer that come from the GFP orf. We added the spacer reasoning that dCas9 occupies space outside of just the 20bp matching crRNA, and after eyeballing the crystal structure 4008.pdb (which should be referenced & pictured) it looked like we needed about enough space for 1 additional turn of DNA outside of the 20bp. 10.5bp is ~1 turn, 3 bp is taken care of by PAM, so we added 10 to be safe. MZ was involved in this design stuff
iGEM013 Duke
"
