"
Team:Bielefeld-Germany/Labjournal/week9
From 2012.igem.org
(Difference between revisions)
(→Monday June 25th) |
|||
| Line 30: | Line 30: | ||
** Is there something wrong with the transformed construct, maybe a mutation? | ** Is there something wrong with the transformed construct, maybe a mutation? | ||
** Was the laccase synthesized but is inactive for some reason? | ** Was the laccase synthesized but is inactive for some reason? | ||
| - | ** Was the laccase produced but not in | + | ** Was the laccase produced but not in a high enough amount so that we can´t detect its activity in the first place? |
| - | Another thought was that there might be copper missing. Since laccase is a copper-enzyme it might necessary to add copper to the medium whenever it is produced in such high amounts. So we first divided each sample and added 2mM or 4mM to the halfs, respectively. We incubated our samples for 2h and hoped that the concentration gradient would cause the laccases to exchange the ion they have integrated instead against copper. | + | Another thought was that there might be copper missing. Since laccase is a copper-enzyme it might be necessary to add copper to the medium whenever it is produced in such high amounts. So we first divided each sample and added 2mM or 4mM to the halfs, respectively. We incubated our samples for 2h and hoped that the concentration gradient would cause the laccases to exchange the ion they have integrated instead against copper. |
We measured their activity again after those 2h but there was no change seen. | We measured their activity again after those 2h but there was no change seen. | ||
Team Cultivation plans to add copper from the very beginning of cultivation next time. | Team Cultivation plans to add copper from the very beginning of cultivation next time. | ||
| Line 41: | Line 41: | ||
===Thursday June 28th=== | ===Thursday June 28th=== | ||
* '''Team Wiki''': Today we browsed our wiki and were not very impressed: it's a lonesome place. So we started to think of how we could blow a little more life into it. For this, texts should appear soon on our wiki. To manage this bunch of work, we divided the subtopics of our wiki and appointed them to group members. Now everyone has a topic which he is responsible for. And that includes writing the texts, uploading pictures and keeping the represented information updated. Before anybody had the chance to disappear behind his/her notebook being busy editing his own page, we had to establish our <span style="text-decoration: underline;">'''wiki rules'''</span>: | * '''Team Wiki''': Today we browsed our wiki and were not very impressed: it's a lonesome place. So we started to think of how we could blow a little more life into it. For this, texts should appear soon on our wiki. To manage this bunch of work, we divided the subtopics of our wiki and appointed them to group members. Now everyone has a topic which he is responsible for. And that includes writing the texts, uploading pictures and keeping the represented information updated. Before anybody had the chance to disappear behind his/her notebook being busy editing his own page, we had to establish our <span style="text-decoration: underline;">'''wiki rules'''</span>: | ||
| - | **Use the standardized formatting as presented in our [https://2012.igem.org/Team:Bielefeld-Germany/Example | + | **Use the standardized formatting as presented in our [https://2012.igem.org/Team:Bielefeld-Germany/Example example page]. |
| - | **Try to edit your text without using HTML code as far as possible and use wiki code instead. Useful advices when using wiki code are represented on our [https://2012.igem.org/Team:Bielefeld-Germany/Example | + | **Try to edit your text without using HTML code as far as possible and use wiki code instead. Useful advices when using wiki code are represented on our [https://2012.igem.org/Team:Bielefeld-Germany/Example example page], too. |
**If you want to change anything that does not belong to your scope of duties, ask kindly the person of charge and make sure he/she is fine with it. | **If you want to change anything that does not belong to your scope of duties, ask kindly the person of charge and make sure he/she is fine with it. | ||
**Make your text more understandable by using images and charts. But remember: you are only allowed to upload pictures if you own them or if they are published without licenses. | **Make your text more understandable by using images and charts. But remember: you are only allowed to upload pictures if you own them or if they are published without licenses. | ||
Revision as of 17:42, 17 August 2012
Contents |
Labjournal
Week1 Week2 Week3 Week4 Week5 Week6 Week7 Week8 Week9 Week10 Week11 Week12 Week13 Week14 Week15 Week16 Week17 Week18
Week 9 (06/25 - 07/01/12)
Monday June 25th
- Team Sequencing: Sequencing of the next finished biobricks.
- Team Activity Test: Today we felt like we could not take the lazyness of our laccases. We thought and discussed what the reason for them to be inactive could be.
- Is there something wrong with the transformed construct, maybe a mutation?
- Was the laccase synthesized but is inactive for some reason?
- Was the laccase produced but not in a high enough amount so that we can´t detect its activity in the first place?
Another thought was that there might be copper missing. Since laccase is a copper-enzyme it might be necessary to add copper to the medium whenever it is produced in such high amounts. So we first divided each sample and added 2mM or 4mM to the halfs, respectively. We incubated our samples for 2h and hoped that the concentration gradient would cause the laccases to exchange the ion they have integrated instead against copper. We measured their activity again after those 2h but there was no change seen. Team Cultivation plans to add copper from the very beginning of cultivation next time.
Tuesday June 26th
- Team A. thaliana laccase: The thing about plants is that they have to grow. Fortunately we got 6 beautiful 4 weeks-old wildtype plants from Patrick Treffon from the Institute of Plant Physiology and Biochemistry at Bielefeld University. With the help of the [http://bar.utoronto.ca/efp/cgi-bin/efpWeb.cgi efp-Browser] we found out that the [http://www.ncbi.nlm.nih.gov/protein/AAM77221.1 laccase] in A. thaliana is only expressed in the developing seeds. So we now have to wait for the siliques to develop.
Wednesday June 27th
Thursday June 28th
- Team Wiki: Today we browsed our wiki and were not very impressed: it's a lonesome place. So we started to think of how we could blow a little more life into it. For this, texts should appear soon on our wiki. To manage this bunch of work, we divided the subtopics of our wiki and appointed them to group members. Now everyone has a topic which he is responsible for. And that includes writing the texts, uploading pictures and keeping the represented information updated. Before anybody had the chance to disappear behind his/her notebook being busy editing his own page, we had to establish our wiki rules:
- Use the standardized formatting as presented in our example page.
- Try to edit your text without using HTML code as far as possible and use wiki code instead. Useful advices when using wiki code are represented on our example page, too.
- If you want to change anything that does not belong to your scope of duties, ask kindly the person of charge and make sure he/she is fine with it.
- Make your text more understandable by using images and charts. But remember: you are only allowed to upload pictures if you own them or if they are published without licenses.
