Difference between revisions of "Part:BBa K1041002"

(→‎Characterisation)
(→‎Sequencing)
Line 22: Line 22:
 
The biobrick was sent off to a company for sequencing.
 
The biobrick was sent off to a company for sequencing.
  
−
[[image:3a vf2 0-540.JPG|thumb|left|K1041000 sequencing data part 1]]
+
[[image:K1041002 1.JPG|thumb|left|K1041002 sequencing data part 1]]
−
[[image:3a vf2 440-860.JPG|thumb|left|K1041000 sequencing data part 2 ]]
+
[[image:K1041002 2.JPG|thumb|left|K1041002 sequencing data part 2 ]]
−
[[image:3a vf2 860-.JPG|thumb|left|K1041000 sequencing data part 3]]
+
[[image:K1041002 3.JPG|thumb|left|K1041002 sequencing data part 3]]
  
 
<br>
 
<br>
Line 35: Line 35:
 
<br>
 
<br>
 
<br>
 
<br>
 +
 
===BLAST Analysis===
 
===BLAST Analysis===
 
The data we recieved back from the sequencing company was aligned using BLAST with the expected DNA sequence ''fig.2''
 
The data we recieved back from the sequencing company was aligned using BLAST with the expected DNA sequence ''fig.2''

Revision as of 19:52, 19 September 2013

AntG Promoter + RFP Coding Device

Team NRP-UEA_Norwich 2013 created this part using biobricks BBa_K1041000 and BBa_K1041001. These biobricks both contain a Nde1 site after their promoter sequence, enabling a restriction digest to be performed. The RFP coding gene was excised from BBa_K1041000 and ligated in front of the AntG promoter of BBa_K1041001 to create a new biobrick.

Sequence and Features


Assembly Compatibility:
  • 10
    COMPATIBLE WITH RFC[10]
  • 12
    COMPATIBLE WITH RFC[12]
  • 21
    COMPATIBLE WITH RFC[21]
  • 23
    COMPATIBLE WITH RFC[23]
  • 25
    INCOMPATIBLE WITH RFC[25]
    Illegal AgeI site found at 683
    Illegal AgeI site found at 795
  • 1000
    COMPATIBLE WITH RFC[1000]


Characterisation

Characterisation of this biobrick involved sequencing, restriction digests and BLAST analysis.

Sequencing

The biobrick was sent off to a company for sequencing.

K1041002 sequencing data part 1
K1041002 sequencing data part 2
K1041002 sequencing data part 3










BLAST Analysis

The data we recieved back from the sequencing company was aligned using BLAST with the expected DNA sequence fig.2