"
Team:Wellesley Desyne/zTree
From 2013.igem.org
| Line 109: | Line 109: | ||
<tr align="center"> | <tr align="center"> | ||
| - | <td align="center"><img src="https://static.igem.org/mediawiki/2013/5/5d/Wellesley_zTree4.jpg" width="300" height="300" margin="100" align="center"><br><br><div style="width: 300px"><figcaption width="300">Users can search by part type, such as promoter or terminator. </figcaption></div></td> | + | <td align="center"><img src="https://static.igem.org/mediawiki/2013/5/5d/Wellesley_zTree4.jpg" width="300" height="300" margin="100" align="center"><br><br><div style="width: 300px"><figcaption width="300">Users can search by part type, such as promoter or terminator, in the topmost carousel. </figcaption></div></td> |
| - | <td align="center"><img src="https://static.igem.org/mediawiki/2013/6/6a/Wellesley_zTree3.jpg" width="300" height="300" margin="100" align="center"><br><div style="width: 300px"><figcaption width="300">A second carousel appears beneath the first one to choose a more specific part type.</figcaption></div></td> | + | <td align="center"><img src="https://static.igem.org/mediawiki/2013/6/6a/Wellesley_zTree3.jpg" width="300" height="300" margin="100" align="center"><br><div style="width: 300px"><figcaption width="300">A second carousel appears beneath the first one, allowing the user to choose a more specific part type.</figcaption></div></td> |
</tr> | </tr> | ||
| Line 117: | Line 117: | ||
<td align="center"><img src="https://static.igem.org/mediawiki/2013/1/1e/Wellesley_zTree2.jpg" width="300" height="300" margin="100" align="center"><br><div style="width: 300px"><figcaption width="300">Choosing yet a more specific part type.</figcaption></div></td> | <td align="center"><img src="https://static.igem.org/mediawiki/2013/1/1e/Wellesley_zTree2.jpg" width="300" height="300" margin="100" align="center"><br><div style="width: 300px"><figcaption width="300">Choosing yet a more specific part type.</figcaption></div></td> | ||
| - | <td align="center"><img src="https://static.igem.org/mediawiki/2013/1/17/Wellesley_zTree1.jpg" width="300" height="300" margin="100" align="center"><br><div style="width: 300px"><figcaption width="300">Users can then choose | + | <td align="center"><img src="https://static.igem.org/mediawiki/2013/1/17/Wellesley_zTree1.jpg" width="300" height="300" margin="100" align="center"><br><div style="width: 300px"><figcaption width="300">Users can then choose an individual part to view more information about it. They can also view the hierarchy of the part.</figcaption></div></td> |
</tr> | </tr> | ||
Revision as of 21:45, 25 September 2013
Wellesley HCI iGEM 2013zTree
TOOL OVERVIEW
zTree is an interactive, 3D visualization of the Registry of Standard Biological Parts that draws upon Parc’s Cone Trees visualization technique for representing hierarchical information. The top of the hierarchy represents a particular library, with nodes drawn like index cards to represent a generic part type—marked using Synthetic Biology Open Language—or a concrete biological part.
In zTree, a user can browse or search for a part of interest, display the data sheet for the part, and export any selected parts to a plain text file, which can then be imported into other programs for further use. The program also features an action log for user testing.
Implementation
zTree was built in Unity, a game engine, using the zSpace SDK programmed in C#. The meshes were rendered in Blender and the data are pulled via the Registry API. zTree was implemented for the zSpace system, a 3D holographic display that provides six degrees of freedom when interacting with objects on screen. The display takes advantage of binocular vision and motion parallax to render a realistic image.
Purpose
2D representations of large data sets typically do not fit within the confines of a standard screen, forcing the user to scroll or resize to see the data in its entirety. zTree's use of 3D carousels maximizes screen real estate, thereby allowing the user to visualize the whole structure at once.
- Our goals for zTree this summer were twofold:
- Provide users with an intuitive, interactive way to navigate the Registry of Standard Biological Parts
- Make a modular enough solution so that the application could eventually be used for a wide array of data sets
 |
 |
 |
 |
RESULTS
We conducted a preliminary usability study of zTree with 9 Wellesley College students. The study employed a within subjects design, aiming to compare how students accomplished a series of simple tasks on zTree versus the Registry of Standard Biological Parts website. The students were asked to browse for a specific part, estimate the number of parts in a category, and compare two different part types.
- The task list was devised to:
- Study the effect of zTree's carousel structure on the user’s ability to understand hierarchical relationships and estimate the size of the data space.
- Improve functionality and evaluate overall experience through qualitative user feedback and survey responses.
After the study, participants were asked to choose the application that was easier to use, zTree or the Registry website, for individual subtasks. People generally found zTree more helpful than the registry in terms of visualizing the entire structure and understanding hierarchy (see Figure at right).
- User quotes consistently provided support for these findings:
- “It's great how easy it is to compare and view relationships of the different parts.”
- "I really liked being able to browse through multiple hierarchies at once."
- "I liked the visual structure of the data. It made it really easy to understand the hierarchy of the information I was viewing."
6 of the 9 users also "Agreed" or “Strongly Agreed” that the zTree application was visually appealing.
DEMO
FUTURE WORK
- Animate carousels on and off screen
- Improve search function for specific parts
- Allow use of data sets from other databases
- Eliminate "ghosting" to improve visualization
- Allow use of pen for navigation and spinning of carousels
