Difference between revisions of "MG RAST v2.0 FAQ"
FolkerMeyer (talk | contribs) m |
FolkerMeyer (talk | contribs) m |
||
| Line 29: | Line 29: | ||
=== What about HIPAA relevant data? === | === What about HIPAA relevant data? === | ||
MG-RAST is provided under the assumption that all data is anonymized, no [http://en.wikipedia.org/wiki/HIPAA HIPAA] relevant data should be stored on MG-RAST. | MG-RAST is provided under the assumption that all data is anonymized, no [http://en.wikipedia.org/wiki/HIPAA HIPAA] relevant data should be stored on MG-RAST. | ||
| + | |||
| + | |||
| + | === How are the numbers computed? === | ||
| + | <font color="red">NEEDS TO BE FILLED</font> | ||
Revision as of 15:07, 20 June 2008
What are projects?
Projects are related sets of metagenomes. If you for example plan on studying a set of samples from a chronoseries, it might me useful to group them into a project.
What level of privacy does MG-RAST v2.0 provide?
We provide password control and the ability for the submitting entity to control access on a username/password basis to the submitted data sets.
Note that we currently do not provide industry standard encryption as this would put additional load on our server infrastructure and is not strictly required for scientific purposes.
Do you support BLASTing against my private database XYZ?
We currently do not explicitly support this, however the underlying software design end system architecture support this.
How frequently do you update the underlying NR for MG-RAST?
With version 2.0 we have added the support for multiple concurrent sets of sequence similarity results to be stored per metagenome. We can add results for newer NRs. However once you start comparing results for metagenomes (say you are interested in the phylogenetic reconstruction) different versions of the NR used for the underlying data will lead to incorrect comparison results as older versions of NR will miss certain organisms and or annotations.
How long does it take to analyze my Metagenome?
The answer depends on two factors a) the size of your data set and b) the current server load. Under optimal conditions, it takes about 18 hours to run a 100 million basepair 454 metagenome through the pipeline.
How many metagenomes can I submit?
We do not restrict user submission of samples. However the computation required is massive and samples are processed on a first come first serve basis.
What parameters should I use to analyze my data?
The answer depends on your sample. In any case we recommend that you modify e-value, minimal alignment length and percent identity requirements for the BLAST results underlying the results. The effects of this are different for each sample. Depending on sample complexity, sample size, number of species an diversity of species present your results will vary dramatically when modifying these parameters. For RNA based phylogenetic reconstruction, we recommend requiring a minimum alignment length of 50bp for exact matches.
Where can people access my "published" metagenomes?
The MG-RAST v2.0 Homepage has a list of publicly accessible metagenomes.
Future versions will continue to support this feature, also we will provide a metadata based selection tool, that will allow the user to focus on metagenome data sets from the environment or condition etc they are interested in.
What about HIPAA relevant data?
MG-RAST is provided under the assumption that all data is anonymized, no HIPAA relevant data should be stored on MG-RAST.
How are the numbers computed?
NEEDS TO BE FILLED