rPredictorDB exists to make bioinformatics over ribosomal RNA easier.
The rPredictorDB website provides access to various tools you can use over a database of rRNA molecules. We assembled a toolkit for various common bioinformatical tasks, falling into two broad categories:
Search tools retrieve a set of rRNA molecules from our database, both according to some exact criteria (length, organism name or group, type of rRNA, etc.) and similarity criteria (“Find me more sequences like this one”).
Prediction tools take a rRNA sequence and suggest base pairs.
An overview of the available tools is in The rPredictorDB Toolkit. This overview should help you to select the right tools for your work.
A reference manual of the inputs for each individual tool can be found in The rPredictorDB Toolkit Reference. This should help you understand in detail how to use a tool you chose.
Warning
If there is any confusion about the terminology we use and how we use it, refer to the rPredictorDB glossary.
More accurately and technically, the rPredictorDB infrastructure consists of the following components:
Probably of most interest to the casual user is the rWeb component, which is the interface through which you will communicate with the other rPredictorDB components.
The documentation is split into three parts:
Note
Taken from Frequently Asked Questions.
Why build a website for rRNA bioinformatics at all?
While there are several websites dedicated directly to ribosomal RNA, we (Bioinformatics laboratory of the Microbiological Institute of the Czech Academy of Sciences and our team at the Faculty of Mathematics and Physics at Charles University) feel that a better job could have been done.
The main drawbacks of similar bioinformatical websites are a sharp learning curve and missing information or unclear purpose of information. In order to use a website such as the Protein Data bank or the Comparative RNA website, a user first has to have - or obtain - a good general idea of what the site does, why would anyone want such a site and what a lot of terminology means.
After this background knowledge is obtained, the user finds out that certain information is not well-curated or made explicit: no one (at least publicly) keeps track of whether a RNA sequence was obtained directly or from a DNA transcription site, information about the type of rRNA is sparse, sometimes the phylogeny of a molecule is missing, a resolved secondary structure is not sufficiently labeled, it is unclear what constitutes a truly unique identifier of an RNA sequence or structure, etc. For instance, the STRAND database of resolved RNA secondary structures contains a number of structures inconsistently labeled for RNA-protein complexes and duplicate sequences.
Another drawback of such sites is often little or missing support for mass data retrieval. When present, it is usually in the form of pre-packaged archives and the user has little choice over what subset of the data to download. (A notable exception here is the SILVA database of rRNA molecules.)
While perhap such drawbacks are of less concern to biologists, the fast-growing field of bioinformatics is sensitive to this kind of volatility in data sources. Nobody wants to spend a lot of time by finding out what uniquely identifies an RNA sequence or structure, filling in missing fields, etc., let alone downloading a set of several hundred sequences of interest one by one.
The rWeb and rData components of rPredictorDB were designed with overcoming these drawbacks in mind. Our goal is first and foremost clarity: answers to questions such as “Why would I ever want to do that?” should be easy to find (and relatively easy to read).
To start using the rPredictorDB website right away, go search or predict.
If you wish to read more about rPredictorDB: