Team:Penn State/Attributions
From 2014.igem.org
Line 112: | Line 112: | ||
<td width="45%" valign="top"> | <td width="45%" valign="top"> | ||
- | <p> | + | <p><font color="red"> |
We have this requirement to help the judges know what you did yourselves and what you had help with. We don't mind if you get help with difficult or complex techniques, just be sure to report the work your team did and the work that was done by others. | We have this requirement to help the judges know what you did yourselves and what you had help with. We don't mind if you get help with difficult or complex techniques, just be sure to report the work your team did and the work that was done by others. | ||
</p> | </p> | ||
Line 122: | Line 122: | ||
<p> | <p> | ||
A great example of complete attribution comes from the <a href="https://2011.igem.org/Team:Imperial_College_London/Team">Imperial College London 2011 team</a> (scroll down to the bottom of their team page to see attributions). | A great example of complete attribution comes from the <a href="https://2011.igem.org/Team:Imperial_College_London/Team">Imperial College London 2011 team</a> (scroll down to the bottom of their team page to see attributions). | ||
- | </p> | + | </p></font> |
</td> | </td> | ||
<td></td> | <td></td> | ||
<td width="45%" valign="top"> | <td width="45%" valign="top"> | ||
- | <p> | + | <p><font color="red"> |
Here are some of the fields we recommend you have on this page. If there are other areas not listed below, but applicable to your team/project, please feel free to also list them on your attributions page. Please feel free to remove any areas not applicable to your project. | Here are some of the fields we recommend you have on this page. If there are other areas not listed below, but applicable to your team/project, please feel free to also list them on your attributions page. Please feel free to remove any areas not applicable to your project. | ||
</p> | </p> |
Revision as of 18:39, 15 July 2014
WELCOME TO PENN STATE iGEM 2014!(Page under construction) |
|||||||||||||
| |||||||||||||
iGEM Team attributions page |
|
||||||||||||
Each team must clearly attribute work done by the student team members on this page. The team must distinguish work done by the students from work done by others, including the host labs, advisors, instructors, and individuals not on the team roster. |
|||||||||||||
Why do we have this requirement? |
Attribution Template |
||||||||||||
We have this requirement to help the judges know what you did yourselves and what you had help with. We don't mind if you get help with difficult or complex techniques, just be sure to report the work your team did and the work that was done by others. For example, you might choose to work with an animal model during your project. Working with animals requires getting a license and applying far in advance to conduct certain experiments in many countries. This is something that is difficult to achieve during the course of a summer, but much easier if you can work with a postdoc or PI who has the right licenses. A great example of complete attribution comes from the Imperial College London 2011 team (scroll down to the bottom of their team page to see attributions). |
Here are some of the fields we recommend you have on this page. If there are other areas not listed below, but applicable to your team/project, please feel free to also list them on your attributions page. Please feel free to remove any areas not applicable to your project.
|
General Support
Dr. Howard Salis and Dr. Tom Richard were our iGEM coordinators and were instrumental in development of the big ideas for our projects as well as with troubleshooting specific experiments.
Project Support and Advice
Chiam Yu Ng was an outstanding mentor, helping us to learn design strategies and develop a cloning plan to set our project into motion. When we ran into problems with cloning, Chiam Yu was very patient and helped us to optimize our experimental processes.
Another great asset to our project was Tian Tian. Because of her desk’s proximity to Clay’s, she skillfully answered an almost constant stream of questions - on everything from optimizing PCR protocols to tips for plasmid prep.
Manish Kushwaha, Iman Farasat, Long Chen and Amin Espah Borujeni all provided critical tips for improving our cloning strategy, as well as assistance developing our programs to optimize the GFPs.
Iman Farasat and Dr. Salis were a big help to the Biodetoxification project. Iman assisted us with forming an experimental plan and ordering primers for Gibson Chew-Back Annealing Assembly. They both taught us how to perform a CBA and homologous recombination and offered advice during our project troubleshooting. Tian Tian, Chiam Yu Ng, and Amin Espah Borujeni answered our random questions and Manish Kushwaha graciously agreed to accompany us to the Jamboree.
Fundraising Help and Advice
Dr. Tom Richard and Dr. Howard Salis took on the burden of finding funding for the undergrads, and we are sincerely thankful for their work.
Lab Support
We are very appreciative of being able to use Dr. Salis’s Lab space and materials. Iman and Chiam Yu were crucial in the wet-lab success of both projects.
Difficult Technique Support
When we experienced problems with a tricky inverse PCR, Chiam Yu helped us to uncover a critical error in one of our primers. Designing an RBS library with the constraints that were present in our constructs was very difficult and Iman helped us to understand and solve this problem. Iman taught the Biodetoxification group the protocol for Gibson CBA and homologous recombination.
Wiki Support
Presentation Coaching
Dr. Howard Salis and Dr. Tom Richard both improved our presentation skills.
Kay Dimarco helped us to find activity kits from the previous iGEM team, which we ended up reinventing but were a source of inspiration for our presentation to the science teachers and the ScienceU students. Matt Johnson and Leah Bug gave us advice on our NewBio Teachers presentation for the Center for Science and the Schools.
Policy and Practices Support
Dr. Tom Richard helped us to refine and implement our ideas for human practices topics.