Page History

h1. *BioMate*

Lab-bench biologists find it difficult to use many existing tools for their data analysis. These tools are generally command-line computer programs written by computational biologists. Computational biologists do not have time to create user-friendly interfaces for their programs, and often find themselves spending a lot of time helping lab-bench biologists run their programs. This creates a burden for all involved: lab-bench biologists cannot move forward with their data analysis, and computational biologists cannot move forward with their research.


{html}<MCE:STYLE></MCE:STYLE><STYLE mce_bogus="1"><!--
.pagetree2 a{font-size:16px; }
--></STYLE>{html}
{pagetree2:BioMate}

_Click on a page above for a specific section._

h2. Computer Prototyping

h3. Platform and Software Requirements

Our software can run on any modern browser and any operating system. We have tested our code on several browsers and it seems to work best on Chrome, and Firefox, or Safari.


h3. Instructions

h5. Accessing the Prototype

Our software is accessible at the following URL: [http://mv.ezproxy.com.ezproxy.canberra.edu.au/6.831/GR4].

h5. Tasks to Evaluate

The following tasks can be helpful during the evaluation process:
# Log in as a lab-bench biologist using the following login credentials (the canned data corresponds to what a lab-bench biologist might see):
#* _username_: alpha
#* _password_: beta
# Use "Monte Carlo" script.
# Use "Monte Carlo" script from history.
# Browse your notes and look at your notes on "Monte Carlo".
# Log in as a computational biologist using the following login credentials (the canned data corresponds to what a computational biologist might see):
#* _username_: gamma
#* _password_: delta
# Create a new script.
# Edit "Monte Carlo" script from history.

You might play with the interface. We have implemented enough of the functionality so that you should be  able to see all of the screens we have designed. All buttons on the home  screen should link to the correct screens (notes, history, add/edit a  script, use a script), and buttons on these screens should show popups  and tooltips with canned data. Selecting scripts other than "Monte Carlo" should not cause the interface to crash; you may not see any output or the output you see might not make sense.




h3. Prototype information

h5. Canned Elements

* You can login with only two username-password pairs as mentioned in the instructions.
* You can use only "Monte Carlo" script since we have created all of our screens with canned data corresponding to the "Monte Carlo" script which was used in our paper prototype scenario.
* The notes, instructions and parameters associated with "Monte Carlo" script are all canned.
* Clicking "Edit" for any script in the "History" popup shows an image of the "Create/Edit Script" screen with some items filled in, and is therefore not interactive.

h5. Incompletely Implemented Elements

* Home/Login screen:
** We did not implement the "create account" feature and the "login" functionality is incomplete in the sense that it uses canned data.
* Create/Edit a Script screen:
** The "Delete" and "Edit" buttons do not allow you to delete or edit any parameter or static text.
** The "View/Edit" buttons in the parameters table do not work.
** Changing the "Alias" or "Prefix/Flag" in the parameters table does not update the draggable chunks.
** Setting input type to "Flag" does not disable the "Required" checkbox.
* Use a Script screen:
** From the "Generate Command" popup, Save to Notes and Copy to Clipboard do not work.
* General:
** When you click buttons that would require mostly back-end work such as Save, Share, etc., nothing will be saved, even if feedback is displayed on the UI confirming the action.
** When you click "Send" to send an email, nothing will be sent.