Team:Northwestern/Notebook
From 2013.igem.org
2013.igem.nu (Talk | contribs) |
2013.igem.nu (Talk | contribs) |
||
Line 37: | Line 37: | ||
<b> Day 1, June 17 </b> <br> | <b> Day 1, June 17 </b> <br> | ||
- | Each team member prepared 5 ideas, and the team selected the top five ideas. These ideas include a biosensor for common parasites in water, a biosensor for UV damage, a bacteria that fights cavity, bacteria to produce diesel from food oil, and a composite biosensor that incorporates several biosensors. | + | Each team member prepared 5 ideas, and the team selected the top five ideas. These ideas include a biosensor for common parasites in water, a biosensor for UV damage, a bacteria that fights cavity, bacteria to produce diesel from food oil, and a composite biosensor that incorporates several biosensors. <br> |
<b> Day 2, June 18 </b> <br> | <b> Day 2, June 18 </b> <br> | ||
- | + | Each member focused on one idea. The goal for the day was to determine a possible mechanism. The goal for the day was to determine the feasibility of the idea. The team also considered several new ideas such as MSG detection, urine detection, and biofertilizer. <br> | |
<b> Day 3, June 19 </b> <br> | <b> Day 3, June 19 </b> <br> | ||
+ | |||
+ | This day was a continuation of the previous day. Emphasis today was to research previous iGEM teams for inspiration and possible mechanisms and biobricks. <br> | ||
+ | |||
<b> Day 4, June 20 </b> <br> | <b> Day 4, June 20 </b> <br> | ||
+ | |||
+ | We tried to find one more idea that will be feasible. After meeting with advisors, we tried to focus more on the mechanistic details rather than a high level discussion of the project idea. We also took an inventory of the lab space and began sending out sponsorship emails. <br> | ||
+ | |||
<b> Day 5, June 21 </b> <br> | <b> Day 5, June 21 </b> <br> | ||
+ | |||
+ | After deciding most of the ideas we have come up with are far from feasible, we focused again on previous iGEM teams, hoping to build on a previous team's work. Each team member was tasked with coming up with a new idea for the next week. <br> | ||
+ | |||
+ | <h2> Week 2 </h2> | ||
Revision as of 18:00, 20 July 2013
Home | Team | Official Team Profile | Project | Parts Submitted to the Registry | Modeling | Notebook | Safety | Attributions |
---|
Team Notebook: Format will be changed!!!
Week 1
The team started the project June 17, 2013, the immediate week following finals week. The team spent the first two weeks deciding on an iGEM project. The first week consists of a high level discussion about different areas of interest.
Day 1, June 17
Each team member prepared 5 ideas, and the team selected the top five ideas. These ideas include a biosensor for common parasites in water, a biosensor for UV damage, a bacteria that fights cavity, bacteria to produce diesel from food oil, and a composite biosensor that incorporates several biosensors.
Day 2, June 18
Each member focused on one idea. The goal for the day was to determine a possible mechanism. The goal for the day was to determine the feasibility of the idea. The team also considered several new ideas such as MSG detection, urine detection, and biofertilizer.
Day 3, June 19
This day was a continuation of the previous day. Emphasis today was to research previous iGEM teams for inspiration and possible mechanisms and biobricks.
Day 4, June 20
We tried to find one more idea that will be feasible. After meeting with advisors, we tried to focus more on the mechanistic details rather than a high level discussion of the project idea. We also took an inventory of the lab space and began sending out sponsorship emails.
Day 5, June 21
After deciding most of the ideas we have come up with are far from feasible, we focused again on previous iGEM teams, hoping to build on a previous team's work. Each team member was tasked with coming up with a new idea for the next week.
Week 2
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.