"
Team:Virginia Tech/Notebook
From 2011.igem.org
| Line 23: | Line 23: | ||
| - | + | =Notebook= | |
You should make use of the calendar feature on the wiki and start a lab notebook. This may be looked at by the judges to see how your work progressed throughout the summer. It is a very useful organizational tool as well. | You should make use of the calendar feature on the wiki and start a lab notebook. This may be looked at by the judges to see how your work progressed throughout the summer. It is a very useful organizational tool as well. | ||
| - | + | ==Week of 5/23/2011== | |
<p><big><b> Design Team: </b></big> Started collecting sequences of relevant fluorescent proteins and entering them into GenoCAD. Learned about attribute grammars. | <p><big><b> Design Team: </b></big> Started collecting sequences of relevant fluorescent proteins and entering them into GenoCAD. Learned about attribute grammars. | ||
</p> | </p> | ||
| Line 35: | Line 35: | ||
</p> | </p> | ||
| - | + | ==Week of 5/30/2011== | |
<p><big><b> Design Team: </b></big> Created first draft of attribute grammar. Collected more fluorescent proteins for GenoCAD. Started looking at modeling aspect of project - explored modeling software that can handle SBML (Systems Biology Markup Language) input - Matlb Simbiology looks nice. | <p><big><b> Design Team: </b></big> Created first draft of attribute grammar. Collected more fluorescent proteins for GenoCAD. Started looking at modeling aspect of project - explored modeling software that can handle SBML (Systems Biology Markup Language) input - Matlb Simbiology looks nice. | ||
</p> | </p> | ||
| Line 43: | Line 43: | ||
</p> | </p> | ||
| - | + | ==Week of 6/6/2011== | |
<p><big><b> Design Team: </b></big> Small changes to grammar (fixing stop codon issues) and big changes to grammar (changing how parts are ordered and thus how GenoCAD constructs the sequence of a construct we make). Looked further into modeling, how our attribute grammar will connect to that. Collected more fluorescent proteins, started to look into degradation tags and linker sequences for fusion proteins. | <p><big><b> Design Team: </b></big> Small changes to grammar (fixing stop codon issues) and big changes to grammar (changing how parts are ordered and thus how GenoCAD constructs the sequence of a construct we make). Looked further into modeling, how our attribute grammar will connect to that. Collected more fluorescent proteins, started to look into degradation tags and linker sequences for fusion proteins. | ||
</p> | </p> | ||
| Line 51: | Line 51: | ||
</p> | </p> | ||
| - | + | ==Week of 6/13/2011== | |
<p><big><b> Design Team: </b></big> Started working on Prolog compiler which will take a construct from GenoCAD and use it to write a Java file, which will in turn write an SBML file for modeling (this is a good way to do it, we promise). | <p><big><b> Design Team: </b></big> Started working on Prolog compiler which will take a construct from GenoCAD and use it to write a Java file, which will in turn write an SBML file for modeling (this is a good way to do it, we promise). | ||
</p> | </p> | ||
| Line 59: | Line 59: | ||
</p> | </p> | ||
| - | + | ==Week of 6/20/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
| Line 67: | Line 67: | ||
</p> | </p> | ||
| - | + | ==Week of 6/27/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
| Line 75: | Line 75: | ||
</p> | </p> | ||
| - | + | ==Week of 7/4/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
| Line 91: | Line 91: | ||
</p> | </p> | ||
| - | + | ==Week of 7/18/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
| Line 99: | Line 99: | ||
</p> | </p> | ||
| - | + | ==Week of 7/25/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
| Line 107: | Line 107: | ||
</p> | </p> | ||
| - | + | ==Week of 8/1/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
| Line 115: | Line 115: | ||
</p> | </p> | ||
| - | + | ==Week of 8/8/2011== | |
<p><big><b> Design Team: </b></big> blah blah blah | <p><big><b> Design Team: </b></big> blah blah blah | ||
</p> | </p> | ||
Revision as of 03:12, 29 September 2011
| Home | Team | Official Team Profile | Project | Parts Submitted to the Registry | Notebook | Safety | Attributions |
|---|
Contents |
Notebook
You should make use of the calendar feature on the wiki and start a lab notebook. This may be looked at by the judges to see how your work progressed throughout the summer. It is a very useful organizational tool as well.
Week of 5/23/2011
Design Team: Started collecting sequences of relevant fluorescent proteins and entering them into GenoCAD. Learned about attribute grammars.
Fabrication Team: blah
Characterization Team: blah
Week of 5/30/2011
Design Team: Created first draft of attribute grammar. Collected more fluorescent proteins for GenoCAD. Started looking at modeling aspect of project - explored modeling software that can handle SBML (Systems Biology Markup Language) input - Matlb Simbiology looks nice.
Fabrication Team: blah
Characterization Team: blah
Week of 6/6/2011
Design Team: Small changes to grammar (fixing stop codon issues) and big changes to grammar (changing how parts are ordered and thus how GenoCAD constructs the sequence of a construct we make). Looked further into modeling, how our attribute grammar will connect to that. Collected more fluorescent proteins, started to look into degradation tags and linker sequences for fusion proteins.
Fabrication Team: blah
Characterization Team: blah
Week of 6/13/2011
Design Team: Started working on Prolog compiler which will take a construct from GenoCAD and use it to write a Java file, which will in turn write an SBML file for modeling (this is a good way to do it, we promise).
Fabrication Team: blah
Characterization Team: blah
Week of 6/20/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 6/27/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 7/4/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 7/11/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 7/18/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 7/25/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 8/1/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
Week of 8/8/2011
Design Team: blah blah blah
Fabrication Team: blah
Characterization Team: blah
