Difference between revisions of "Part:BBa K299812:Experience"

(→‎User Reviews)
(→‎User Reviews)
Line 14: Line 14:
 
|width='60%' valign='top'|
 
|width='60%' valign='top'|
  
−
In general, the full suffix is missing within the construct that we have received from the headquarters (only Pstl is present). This result in the inability to sequence the construct using primers that were designed based on the documented nucleotide sequence. Instead, We had to use universal primers to sequence the first 1kb, then design new primers for the next kb, resulting in 3 staggered rounds of sequencing.  
+
In general, the  sequence of the construct we've received differs significantly from the documented nucleotide sequence.
 +
In addition, the full suffix is missing within the construct we received (only Pstl is present). This resulted in our inability to sequence the construct using prefix&suffix primers, or primers that were designed based on the documented nucleotide sequence. We had to use universal primers to sequence the first 1kb, then design new primers for the next kb, and so on, resulting in 3 staggered rounds of sequencing.  
  
−
The sequencing results point us to a few major and potentially destructive problem:
+
The sequencing results point us to a few major and potentially destructive problems:
  
 
'''''Segment containing Invasin:'''''
 
'''''Segment containing Invasin:'''''
  
−
There is very little nucleotide similarity between the obtained sequence and the documented sequence on the website. The provided nucleotide sequence given for Invasin was found to be the reverse complement of the sequence of Invasin from the actual construct that we have received. Furthermore, according to the entry for BBa_K299810, the Invasin sequence contains the inv gene from ''Yersinia pestis'' obtained through horizontal gene transfer from ''Yersinia pseudotuberculosis''. Attempts to determine the origin of the inv gene through BLAST shows a 100% match with the sequence from ''Yersinia enterocolitica" but partial match against that from ''Yersinia pseudotuberculosis''.
+
There is very little nucleotide similarity between the obtained sequence and the documented sequence on the website. Even the translated amino acid sequences have only 55% identity. According to the entry for BBa_K299810, the Invasin sequence contains the ''inv'' gene from ''Yersinia pestis'' obtained through horizontal gene transfer from ''Yersinia pseudotuberculosis''. Attempts to determine the origin of the inv gene through BLAST shows a 100% match with the sequence from ''Yersinia enterocolitica" but partial match against that from ''Yersinia pseudotuberculosis''.
 +
 
 +
In addition, the origin and function of the additional 300bp between the Invasin and Listerolysin fragment within the construct itself (just before the 2nd RBS) is not known to us. The size of the construct received is actually 4460bp (PstI site excluded) instead of 4146bp.
 +
 
 +
Furthermore, the documented nucleotide sequence for Invasin (part BBa_K177010) was found to be the reverse complement of the sequence of Invasin from the actual construct that we have received.  
  
−
The origin and function of the additional 300bp between the Invasin and Listerolysin fragment within the construct itself (on top of the already existing RBS) is not known to us.
 
  
 
'''''Segment containing Listerolysin:'''''
 
'''''Segment containing Listerolysin:'''''
  
−
The Listerolysin sequence provided online conatins numerous mismatch when aligned with the sequence that we have obtained through sequencing even though there is 99% similarity in the translated amino acid sequence. The stop codon for Listerolysin is also missing.
+
The Listerolysin sequence documented online contains numerous mismatches when aligned with the sequence that we have obtained through sequencing, although there is 99% similarity in the translated amino acid sequence (perhaps the sequence had been codon-optimised, but documentation does not reflect this). The stop codon for Listerolysin is also missing.
 
|}
 
|}
 
<!-- End of the user review template -->
 
<!-- End of the user review template -->

Revision as of 01:48, 18 September 2015

This experience page is provided so that any user may enter their experience using this part.
Please enter how you used this part and how it worked out.

Applications of BBa_K299812

User Reviews

UNIQa2375f5e262fc662-partinfo-00000000-QINU

No review score entered. yunting and xinyi from SPSingapore 2015

In general, the sequence of the construct we've received differs significantly from the documented nucleotide sequence. In addition, the full suffix is missing within the construct we received (only Pstl is present). This resulted in our inability to sequence the construct using prefix&suffix primers, or primers that were designed based on the documented nucleotide sequence. We had to use universal primers to sequence the first 1kb, then design new primers for the next kb, and so on, resulting in 3 staggered rounds of sequencing.

The sequencing results point us to a few major and potentially destructive problems:

Segment containing Invasin:

There is very little nucleotide similarity between the obtained sequence and the documented sequence on the website. Even the translated amino acid sequences have only 55% identity. According to the entry for BBa_K299810, the Invasin sequence contains the inv gene from Yersinia pestis obtained through horizontal gene transfer from Yersinia pseudotuberculosis. Attempts to determine the origin of the inv gene through BLAST shows a 100% match with the sequence from Yersinia enterocolitica" but partial match against that from Yersinia pseudotuberculosis.

In addition, the origin and function of the additional 300bp between the Invasin and Listerolysin fragment within the construct itself (just before the 2nd RBS) is not known to us. The size of the construct received is actually 4460bp (PstI site excluded) instead of 4146bp.

Furthermore, the documented nucleotide sequence for Invasin (part BBa_K177010) was found to be the reverse complement of the sequence of Invasin from the actual construct that we have received.


Segment containing Listerolysin:

The Listerolysin sequence documented online contains numerous mismatches when aligned with the sequence that we have obtained through sequencing, although there is 99% similarity in the translated amino acid sequence (perhaps the sequence had been codon-optimised, but documentation does not reflect this). The stop codon for Listerolysin is also missing.

UNIQa2375f5e262fc662-partinfo-00000002-QINU

UNIQa2375f5e262fc662-partinfo-00000003-QINU