Difference between revisions of "Team:Michigan Software/Improve"
| Line 51: | Line 51: | ||
<h1 class="grey-text heading-weight" align = "center">Visual Protocol History</h1> | <h1 class="grey-text heading-weight" align = "center">Visual Protocol History</h1> | ||
<div class="row" style="border-bottom:thin solid;"></div> | <div class="row" style="border-bottom:thin solid;"></div> | ||
| − | <img src="https://static.igem.org/mediawiki/2017/a/a2/Michigan_software_visual_history.png"> | + | <img src="https://static.igem.org/mediawiki/2017/a/a2/Michigan_software_visual_history.png" class="sample_img"> |
<p id = "doubleSpace" class="p-font grey-text"> | <p id = "doubleSpace" class="p-font grey-text"> | ||
ProtoCat enables users to 'version control' their protocols; anyone can create a variant of a protocol and make modifications as they see fit. However, once multiple revisions are made, and the subsequent tree of protocol revisions gets unruly, it can be quite difficult to figure out which version one should be using. To address this issue, we have created a way for a user to view the history of protocols visually to make navigating to the best version of a protocol as efficient as possible. | ProtoCat enables users to 'version control' their protocols; anyone can create a variant of a protocol and make modifications as they see fit. However, once multiple revisions are made, and the subsequent tree of protocol revisions gets unruly, it can be quite difficult to figure out which version one should be using. To address this issue, we have created a way for a user to view the history of protocols visually to make navigating to the best version of a protocol as efficient as possible. | ||
Revision as of 19:28, 31 October 2017
Improvements
ProtoMetrics
ProtoCat is meant to enable lab researchers to get feedback on their lab procedures; in order to improve efficiency or gather feedback. But how can they quantify which version of a protocol is better? What if a researcher wants to gather feedback about a specific step, or specific product? Ask for the calibration of the equipment that other people are using? And even if they can get it in the comments, how will they get that information in a readily accessible and usable form? This need gave rise to ProtoMetrics, our way to allow researchers to get quantitative metrics on their protocols.
ProtoMetrics allows users to specify three types of questions: Text, Numeric, or Polls. Text and Numeric are relatively straightforward; the former asks for a text response (ex: describe the resulting solution), whereas the latter is for strictly numeric responses (ex: How many grams of product were you able to produce?). Polls allow for a respondent to choose from a selection of responses, which can be used for specific equipment calibration. Once the users have submitted the responses, the publisher of the protocol can download the results in a Comma Seperated Value (csv) file for easy import into Excel, MATLAB, or a similar analysis too.
ProtoChat
Describe ProtoChat Here
Protocols.io Import Tool
Find out more about this import tool here.
Visual Protocol History
ProtoCat enables users to 'version control' their protocols; anyone can create a variant of a protocol and make modifications as they see fit. However, once multiple revisions are made, and the subsequent tree of protocol revisions gets unruly, it can be quite difficult to figure out which version one should be using. To address this issue, we have created a way for a user to view the history of protocols visually to make navigating to the best version of a protocol as efficient as possible.
Protocol nodes are color coded from red (1 star) to green (5 star), and are transparent should they be hidden from search. These visual cues
Group Accounts
Group Accounts goes here!
Improved Security
Describe Security Upgrades here
Misc Improvements
Improved Search Algorithm, Scalable Server Infrastructure. Adopted Pair Programming Techniques
