Line 138: | Line 138: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar1 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar1 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/e/eb/T--USTC-Software--project05.png" /> | <img src="https://static.igem.org/mediawiki/2016/e/eb/T--USTC-Software--project05.png" /> | ||
</div> | </div> | ||
Line 146: | Line 146: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar3 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar3 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/a/a4/T--USTC-Software--project06.png" /> | <img src="https://static.igem.org/mediawiki/2016/a/a4/T--USTC-Software--project06.png" /> | ||
</div> | </div> | ||
Line 154: | Line 154: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar5 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar5 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/1/16/T--USTC-Software--project07.png" /> | <img src="https://static.igem.org/mediawiki/2016/1/16/T--USTC-Software--project07.png" /> | ||
</div> | </div> | ||
Line 162: | Line 162: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar7 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar7 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/c/c9/T--USTC-Software--project08.png" /> | <img src="https://static.igem.org/mediawiki/2016/c/c9/T--USTC-Software--project08.png" /> | ||
</div> | </div> | ||
Line 170: | Line 170: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar9 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar9 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/9/95/T--USTC-Software--project09.png" /> | <img src="https://static.igem.org/mediawiki/2016/9/95/T--USTC-Software--project09.png" /> | ||
</div> | </div> | ||
Line 178: | Line 178: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar11 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar11 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/c/c2/T--USTC-Software--project10.png" /> | <img src="https://static.igem.org/mediawiki/2016/c/c2/T--USTC-Software--project10.png" /> | ||
</div> | </div> | ||
Line 186: | Line 186: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar13 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar13 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/b/b9/T--USTC-Software--project11.png" /> | <img src="https://static.igem.org/mediawiki/2016/b/b9/T--USTC-Software--project11.png" /> | ||
</div> | </div> | ||
Line 252: | Line 252: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar3 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar3 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/b/bf/T--USTC-Software--project04.png" /> | <img src="https://static.igem.org/mediawiki/2016/b/bf/T--USTC-Software--project04.png" /> | ||
</div> | </div> | ||
Line 276: | Line 276: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar1 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar1 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/e/ee/T--USTC-Software--project01.png" /> | <img src="https://static.igem.org/mediawiki/2016/e/ee/T--USTC-Software--project01.png" /> | ||
</div> | </div> | ||
Line 287: | Line 287: | ||
</p> | </p> | ||
</div> | </div> | ||
− | <div class="column small-8 small-offset-2 ar3 imgcontainer"> | + | <div class="column small-8 small-offset-2 end ar3 imgcontainer"> |
<img src="https://static.igem.org/mediawiki/2016/b/b1/T--USTC-Software--project02.png" /> | <img src="https://static.igem.org/mediawiki/2016/b/b1/T--USTC-Software--project02.png" /> | ||
</div> | </div> |
Revision as of 21:12, 19 October 2016
Welcome to Biohub! This is a open and fantastic platform with practical functions for synthetic biologists. For scientists whose goal is to make discoveries in biology, steps using bioinformatics can be seen as the most basic but rather troublesome part. To solve this, our team created Biohub.
Biohub is a platform with several plug-ins, which means that users can not only employ the functions we provide, but also develop new and useful ones which can meet their special needs, without caring for servers and network transmission.Others include Pathway_finder, which means find the correlation among genes, Pano, meaning designing genetic circuits like an artist, Simulation, which can imitate real experimental circumstances, and other splendid functions.
Module:Pano
Pano is a visualized editing interface which is designed to arrange the relationship between genes and to find paths between genes and simulate related substances according to known data.
The relationships of genes are represented by graphs, which include nodes and edges. Each node represents a gene while each edge represents a relationship. Users shall build up a graph in order to input a relationship network among genes. Users will be capable to process the network further such as operating a simulation and so on.
Module:Pathway_finder
Pathway_finder is one of the most powerful plug-ins of Biohub. In traditional circumstances, searching for the relationships among components in the genetic circuit can be rather arduous, so users must read plenty of papers and inquire several databases. To rescue biologists from this, Pathway_finder is born now. Select any two components in genetic circuit, and by searching the database of gene routes in the server we can rapidly know whether they have strong relationship, and whether the feature is of interest. It combines metabolic network databases, cell signaling pathway databases and gene interaction databases, and the path between components means produce, combine, influence activation, promote degradation or others.
Pathway_finder is a module integrated in the Pano to provide more convenient and faster ways to find paths from a specific source node to another target node, select appropriate paths, and add them to the Pano. Biologic scientific workers using the Pathway_finder, nodes and edges will be added under the rules provided by the database of the backend.
1. Select a node as a source node in the pano, and click “PATH FINDER… ” at the sidebar.
2. Select another node as a target, then a modal dialog will be opened.
3. Change the amount and the maximum depth, then click “GO”.
4. Wait for a while until the paths shows on the screen.
5. Delete paths that you do not want.
6. Then click “OK”. Cheers!
7. “SMART MAP” can be used to make it better.
Module:Forum
In order to make communication in Biohub easier, we designed the 'Forum' feature to provide users an area to communicate, view others' projects and write comments on them. They are also able to share different ideas and generate new thoughts.
In Forum, users can write, edit and remove his comments freely just like operating on any other forums. They will harvest enlightenment as well as fun.
Module:Simulation
After you have run the module 'Pathway_finder', you may get some nodes. Here you can use this module to simulate the concentration of the substances involved in this reaction.
Simulation is a simulator designed to solve the concentration function with respect to time based on the differential equations given by the user. After the user has submitted control functions, this module will upload relative data to a high performance server, which will be able to return results in minutes or hours, based on the quantity of control functions and the width of time domain. The concentration of all nodes will be displayed visualized, meanwhile a proper notice will pop up if an instability is detected in order to warn the user to be cautious about the result after the critical point.
Module:BLAST
Biohub provide users with convenient one-key BLAST. In graphical interface,the user select the components which he or she wants to align the sequence, and by just pressing one build-in button, Biohub will read the sequence and align it with sequences in online databases using BLAST interface provided by NCBI, and show the outcome simply and elegantly to the users.
Tips: BLAST is available only online. When using NCBI BLAST API, any user should obey their usage guidelines.
Module:ABACUS
A plugin design to design amino acid sequence from the .pdb file provided by user. The uploaded .pdb file will be evaluated by several progress, with support of simulated annealing algorithm, then the server will generate a .zip file containing several .pdb files and .fasta files for user to download. It’s recommended to run this plugin on a high performance server, because the plugin will invoke computationally intensive programs. So please be patient while this plugin is running, it may take several hours to get results on a high performance server. You can press get status button to check if the calculation is done.
ABACUS can be a really useful function, because for synthetic biologists who want to design new protein, they may need to know the amino acid sequence for proteins in specific structure. For some researchers, they also need to design new protein which should in maximum degree resemble their original structure, which is needed to purify the protein. This steps can be really time-consuming, because if you make some mistakes in designing amino acid sequences, months of experiments can be of no use.This kind of demand make the ABACUS really useful.
Users can design amino acid sequence from the provided structure. Just input the number of result files and tag name(optional), then upload the .pdb file(which represents the structure) and click UPLOAD AND CALCULATE. Then the server will generate amino acid sequence file you want. Just follow the steps below, then your file can be evaluated. And there is one thing you should pay attention to: Every time you upload pdb file, the server will clean old .pdb file and overwrite old results.
While server is calculating, you can click GET STATUS to know whether processes are done. If your file is still being processed, you will get a dialog below:
If files are generated successfully, the 'GET STATUS' button will change to 'DOWNLOAD FILE', then you can get your result as a .zip file.
There is possibility that something go wrong during designing, so if any error happens, you will get a dialog about error information.
Module:Biobrick_manager
The iGEM Registry has over 20,000 documented parts organized by type, chassis, function and more. Recognizing that this is a great asset in the field of synthetic biology, we believe that it is necessary to let users explore Biobricks on BioHub. As a result, this function was implemented as an official plugin for BioHub. Users can search for Biobricks they desire and easily browse all the information about the searching results.
Users can directly visit BioBrick page from the 'BioBrick' button in the navigation bar of homepage, project manage Page or Forum’s right side when they are in need of searching some BioBricks. This page provides a search Widget in which user can input keywords to search for BioBricks.
This user-friendly UI based on Google’s Material Design implemented from MaterializeCss. The neat and simple workspace can provide a more efficient work environment which is important for researchers.
All needed to be done is inputting keywords and hitting ENTER, and the result will appear in no time like this.
In search result,we provide a hint according to the SBOL visual standard by analysing the description of the brick. Also, if the user is interested in the BioBrick and want more intel,he or she can click on the link icon to jump to the official site of iGEM for more detailed information. Export of SBOL version xml file is provided, just click the SBOL download key, and download the SBOL form file.
Plugins & Dockers
The great thing about BioHub is that we have designed a unified, extensible plugin platform, which not only have the powerful tools provided by the development team, but also is easy to learn and use by other developers to provide better features. Each specific feature of BioHub is provided by a plugin, whose developer do not need to care about details such as server and network requests. Plugins can just focus on performing their own tasks and manage user's design results. With BioHub's plugin platform, once any of the latest tools or algorithms in the field of synthetic biology got programmed, developers can easily transform it into a BioHub plugin by studying the sample files we provide, making it a new blade of the powerful Swiss Saber - BioHub.
In order to make BioHub easy to install, configure and use, we carefully selected the program architecture and package format. The use of server - client architecture makes it possible for labs to run the server on a high-performance computer, and easily access it from any device. Also, we use Docker to package the program, which makes the server very easy to start, update and shutdown. Normally, users may never encounter any compatibility issues. What's more, we also released a virtual machine image file for non-Linux platforms.
Outlook
Since our project is a software designed for synthetic biologists to simplify their work as well as give them effective auxiliary, there are undoubtedly dozens of chances of this software to be improved, just like the previous work 'Biopano'. In the future, we will upgrade our program in order to implement more functions as well as enhance the current ones. For example, we may enable the 'Pathway_finder' module to find the strength of the connection between genes, which our software cannot do this at present. Meanwhile, we will introduce our software and its background to our juniors to attract them to join us and to participate in the following iGEM competitions.