Team:Wellesley HCI
From 2012.igem.org
(Difference between revisions)
(8 intermediate revisions not shown) | |||
Line 110: | Line 110: | ||
<ul id="nav"> | <ul id="nav"> | ||
<li><a href="https://2012.igem.org/Team:Wellesley_HCI/Team">Team</a> | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Team">Team</a> | ||
- | <ul> | + | <ul> |
+ | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Team">Team Members</a></li> | ||
<li><a href="https://2012.igem.org/Team:Wellesley_HCI/Notebook">Notebook</a></li> | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Notebook">Notebook</a></li> | ||
+ | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Acknowledgement">Acknowledgement</a></li> | ||
+ | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Tips_Tricks">Tips & Tricks</a></li> | ||
+ | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Social">Fun</a></li> | ||
</ul> | </ul> | ||
</li> | </li> | ||
Line 124: | Line 128: | ||
</li> | </li> | ||
- | <li><a href=" | + | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Human_Practices">Human Practices</a> |
<ul> | <ul> | ||
- | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Methodology">Methodology</a></li> | + | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Human_Practices">User Research</a></li> |
+ | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Methodology">Methodology</a></li> | ||
<li><a href="https://2012.igem.org/Team:Wellesley_HCI/Safety">Safety</a></li> | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Safety">Safety</a></li> | ||
<li><a href="https://2012.igem.org/Team:Wellesley_HCI/Outreach">Outreach</a></li> | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Outreach">Outreach</a></li> | ||
Line 132: | Line 137: | ||
</li> | </li> | ||
<li><a href="https://2012.igem.org/Team:Wellesley_HCI/Gold">Medal Fulfillment</a></li> | <li><a href="https://2012.igem.org/Team:Wellesley_HCI/Gold">Medal Fulfillment</a></li> | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
</ul> | </ul> | ||
<!--End NavBar--> | <!--End NavBar--> | ||
Line 161: | Line 160: | ||
<a href="https://2012.igem.org/Team:Wellesley_HCI/SynBio_Search"><div class="projectBar"> | <a href="https://2012.igem.org/Team:Wellesley_HCI/SynBio_Search"><div class="projectBar"> | ||
<div><div class="projectAbout"> | <div><div class="projectAbout"> | ||
- | A synthetic-biology search engine that aggregates biological -data from multiple databases | + | A synthetic-biology search engine that aggregates biological -data from multiple databases for the research process. |
</div></div> | </div></div> | ||
<div class="projectName"> | <div class="projectName"> | ||
Line 178: | Line 177: | ||
</div> | </div> | ||
</div></a> | </div></a> | ||
- | <img src="http://cs.wellesley.edu/~hcilab/iGEM2012/images/ | + | <img src="http://cs.wellesley.edu/~hcilab/iGEM2012/images/moclo/moclo2withhands.png" alt="MoClo Planner" |
style="width:500px; margin:-20px 0 0 -150px;"> | style="width:500px; margin:-20px 0 0 -150px;"> | ||
</div> | </div> | ||
Line 190: | Line 189: | ||
</div> | </div> | ||
</div></a> | </div></a> | ||
- | <img src="http://cs.wellesley.edu/~hcilab/iGEM2012/images/ | + | <img src="http://cs.wellesley.edu/~hcilab/iGEM2012/images/vortex.jpg" alt="SynFlo in action" |
- | style="width: | + | style="width:350px; margin:-20px 0 0 -50px;"> |
</div> | </div> | ||
Latest revision as of 00:15, 4 October 2012
Welcome!
Synthetic biology will require a multidisciplinary, collaborative design environment in order to engineer the complex biological systems of the future. Our team will create a collection of software tools which address specific technical synthetic biology challenges while simultaneously advancing the way in which users interact with computing environments. Our software will support the scientific workflow process by supporting each step: research, brainstorming, building, test, troubleshooting, iteration, and analysis. The combination of human computer interaction, bio-design automation, and experimental design makes our effort unique in the iGEM experience and closes the loop on the design-build-test methodology.