"
Team:Calgary/8 July 2009
From 2009.igem.org
PatrickKing (Talk | contribs) |
|||
| Line 452: | Line 452: | ||
<br> | <br> | ||
<div class="heading"> | <div class="heading"> | ||
| - | + | Tidying up my DNA | |
</div> | </div> | ||
<br> | <br> | ||
<div class="desc"> | <div class="desc"> | ||
</html> | </html> | ||
| - | + | Retrospective Notebook: This entry was not written on this day, but derived later from working notes I made that day. | |
| + | |||
| + | Originally, I had planned to keep most of the functionality for my DNA parts in a single script. But, the DNA needed to know some hardcoded information about itself: what its name is, what the name of the next part in the DNA polymer is, what type of DNA element it is, and what protein it is repressed by / activated by / produces, and I didn't want to generate a new version of the script (with different hardcoded values) for every single DNA part I made. I decided to use a second script, which would have unique hardcoded information for each DNA part, this information could also be modified for purposes of building custom DNA devices later. I had thought I could make this 'identity script' nice and short, and contain most of the changes to each part in the main 'dna script'. The problem is that this introduced an extra level of communication between the main DNA script and its identity script... and because so much of the DNA's function relates to what it is, the identity script wound up being longer than the DNA script! | ||
| + | |||
| + | I wanted to merge these two scripts into something better organized, but I still needed a way to record the DNA's important details. I briefly used an internal notecard (text document) to store this information, but Second Life doesn't allow objects to edit notecards, which would be a problem when we get to building custom DNA in the Biobricker. In the end I settled on storing this information in the part's name and description fields, the only text fields that are persistent across sessions and resets, but also editable. The only problem with doing this is that these fields are user accessible, it's very possible for someone to edit their object's name and break its functionality the next time it resets or is moved from inventory! Yet, it's the only way I could find to get the DNA construction system to work, and it also has a hidden feature: capable users can change the traits of their biobrick parts without needing to build entire new devices in the HUD. | ||
| + | |||
| + | The new DNA script uses a much simplified system to keep track of what it is, and what it can do. There are three parameters: number one is the part's type, with each of constituitive promoter, repressable promoter, coding sequence... etc as possible types. The DNA learns its type when it is created from inventory or reset, and that type is permanent until the next reset or recreation. Type also informs the DNA of what transcription factor it should pay attention to, if any. | ||
| + | |||
| + | The type of the DNA determines the second parameter: possible behaviours with respect to RNA Polymerase: | ||
| + | * Permit to bind, and pass through (like a promoter) | ||
| + | * Permit to pass through, but not bind (like regular DNA) | ||
| + | * Do not permit binding or passing through (like a terminator) | ||
| + | |||
| + | The DNA's behaviour is set to one of these when its type is determined, but this behaviour can then change depending on the state of a third parameter: whether it is bound by a repressor or activator or not. The information of which type of protein is binding or unbinding, combined with the DNAs type, is enough to determine what behaviour the DNA is now responsible for. | ||
<html> | <html> | ||
Revision as of 20:48, 21 August 2009
|
CAROL
Descriptive Title of What You’re Doing
WIKI CODING HERE
|
|
CHINMOYEE
Adjusting Model frame work
Me , Carol and Kevin adjusted our model frame work . Then the whole modelling team had a good discussion with Thane . Before that I read more journals dealing with parameter estimation and looked for rates . I looked at the parameter fit function in simbiology and tried to use this function for our purpose.
|
|
EMILY
DNA Sequencing and cloning of B0015
|
|
FAHD
Marketing, Ethics and Outreach for July 8th 2009
Today I sent out our June newsletters to media organizations that had done on a story on our project. I also read some ethics papers regarding the importance of ethics in Synthetic Biology and Quorum Sensing. For outreach, I sent my highschool biology teacher an e-mail regarding doing presentations about synthetic biology and iGEM in Bio 30 Classes. Me and my teacher agreed on doing the presentations somewhere in October.
|
|
IMAN
Descriptive Title of What You're Doing
WIKI CODING HERE
|
|
JAMIE
Descriptive Title of What You're Doing
WIKI CODING HERE
|
|
JEREMY
Descriptive Title of What You're Doing
WIKI CODING HERE
|
|
KATIE
Creation and Modification of Scripts and Notecards
I have completed creating instructional and information note cards for the various activities within the virtual lab on our island, including:
Note cards that are almost finished and will be completed by tomorrow include:
I have also been creating and modifying the scripts for PCR, Gel Electrophoresis, Restriction Digest and have just started Bacterial Transformation. They have been modified to use a more user friendly prompt system (using llDialog function in second life scripting language) so asking avatars for information and having them answer looks cleaner and is more intuitive.
I am hoping to have restriction digest functioning by Friday and will be working on finishing notecards, Restriction Digest and Bacterial Transformation in the upcoming days. I will also be organizing a sequencing station, which may be used for a section of the lab activities.
|
|
KEVIN
Restreak of the glowing cells
A brightest colony from yesterday's transformation were restreaked. These cells have to grow overnight, once again.
Blog update
A weekly blog is being done by all sections of our team, including wetlab and modelling which I am part of. Every wednesday is wetlab blog day, so one was written. The following is the link to my post:
Kevin Loves Rainbows
|
|
MANDY
Descriptive Title of What You're Doing
WIKI CODING HERE
|
|
PATRICK
Tidying up my DNA
Retrospective Notebook: This entry was not written on this day, but derived later from working notes I made that day.
Originally, I had planned to keep most of the functionality for my DNA parts in a single script. But, the DNA needed to know some hardcoded information about itself: what its name is, what the name of the next part in the DNA polymer is, what type of DNA element it is, and what protein it is repressed by / activated by / produces, and I didn't want to generate a new version of the script (with different hardcoded values) for every single DNA part I made. I decided to use a second script, which would have unique hardcoded information for each DNA part, this information could also be modified for purposes of building custom DNA devices later. I had thought I could make this 'identity script' nice and short, and contain most of the changes to each part in the main 'dna script'. The problem is that this introduced an extra level of communication between the main DNA script and its identity script... and because so much of the DNA's function relates to what it is, the identity script wound up being longer than the DNA script! I wanted to merge these two scripts into something better organized, but I still needed a way to record the DNA's important details. I briefly used an internal notecard (text document) to store this information, but Second Life doesn't allow objects to edit notecards, which would be a problem when we get to building custom DNA in the Biobricker. In the end I settled on storing this information in the part's name and description fields, the only text fields that are persistent across sessions and resets, but also editable. The only problem with doing this is that these fields are user accessible, it's very possible for someone to edit their object's name and break its functionality the next time it resets or is moved from inventory! Yet, it's the only way I could find to get the DNA construction system to work, and it also has a hidden feature: capable users can change the traits of their biobrick parts without needing to build entire new devices in the HUD. The new DNA script uses a much simplified system to keep track of what it is, and what it can do. There are three parameters: number one is the part's type, with each of constituitive promoter, repressable promoter, coding sequence... etc as possible types. The DNA learns its type when it is created from inventory or reset, and that type is permanent until the next reset or recreation. Type also informs the DNA of what transcription factor it should pay attention to, if any. The type of the DNA determines the second parameter: possible behaviours with respect to RNA Polymerase:
The DNA's behaviour is set to one of these when its type is determined, but this behaviour can then change depending on the state of a third parameter: whether it is bound by a repressor or activator or not. The information of which type of protein is binding or unbinding, combined with the DNAs type, is enough to determine what behaviour the DNA is now responsible for.
|
|
PRIMA
Marketing
I began looking at Westjet and Air Canada flights flying to Boston. I had callled a few travel agencies to try to get a quote. I also looked at Hotels at MIT. I need to detmerine how far it is from MIT, whether it would be economical to stay there and take a cab or get a hotel closer (but a little bit more expensive) and walk to MIT. I also made a list of hotels including their rates, discounts, services, distance from MIT, etc.
I began following up with comapnies via phone and email. I found 16 mor companies that I could contact. I began researching those companies and writing up emails to them. The team also sat down to discuss logo designs, colors, shapes, etc.
|
|
STEFAN
Descriptive Title of What You're Doing
WIKI CODING HERE
|
|
VICKI
Glycerol stock preparation of successfully-biobricked parts
Today was a day of plasmid isolation and glycerol stock preparation. I made overnight cultures and restreaks last night of the parts that I had biobricked. We need some isolated DNA for the registry, as well as glycerol stocks for long-term storage. We have samples of everything that I prepared, with concentrations on the order of 100 ng/uL. One of the sets - the LuxO D47A BBk - was not isolated well, so I made new overnights and will prepare glycerol stocks of those tomorrow.
|
