ranacapa: An R package and Shiny web app to explore environmental DNA data with exploratory statistics and interactive visualizations

Environmental DNA (eDNA) metabarcoding is becoming a core tool in ecology and conservation biology, and is being used in a growing number of education, biodiversity monitoring, and public outreach programs in which professional research scientists engage community partners in primary research. Results from eDNA analyses can engage and educate natural resource managers, students, community scientists, and naturalists, but without significant training in bioinformatics, it can be difficult for this diverse audience to interact with eDNA results. Here we present the R package ranacapa, at the core of which is a Shiny web app that helps perform exploratory biodiversity analyses and visualizations of eDNA results. The app requires a taxonomy-by-sample matrix and a simple metadata file with descriptive information about each sample. The app enables users to explore the data with interactive figures and presents results from simple community ecology analyses. We demonstrate the value of ranacapa to two groups of community partners engaging with eDNA metabarcoding results.


Introd uction
The targeted amplification and sequencing of DNA that living organisms shed into their physical environment, termed "environmental DNA (eDNA) metabarcoding," is revolutionizing microbiology, ecology, and conservation research (Deiner et al., 2017;Taberlet et al. 2012). Sequencing of eDNA extracted from field-collected soil, water, or sediment samples can yield insight into a range of questions, from profiling the composition of ancient plant and animal communities (Pedersen et al., 2015), to monitoring populations of rare or endangered species (Balasingham et al., 2018). As the cost of eDNA metabarcoding declines and sample collection techniques become more streamlined (e.g. Thomas et al. (2018)), professional research scientists are increasingly using eDNA metabarcoding as a platform to engage a diversity of community partners, including natural resource managers, undergraduate students, and citizen scientists in primary research. However, developing robust and impactful community science programs that engage community partners in all steps of the research process remains a challenge.
eDNA metabarcoding-based projects work well for programs that partner researchers with community scientists because non-experts can be quickly trained to collect samples in the field, and because eDNA metabarcoding is an exciting framework for research pertinent to disciplines such as medicine, agriculture, ecology, and geography (Deiner et al., 2017). Community partners in such programs can have heterogeneous backgrounds, ranging from curious members of the public for whom collecting samples in the field is their first scientific research experience (e.g. University of California's CALeDNA program), to professional natural resource managers who regularly collaborate with research scientists (e.g. Center for Ocean Solutions' eDNA project). A key ingredient to promote sustained success of such programs is that community partners should be able to engage across multiple stages of the research project, not only in sample collection (European Citizen Science Association, 2015;Pandya, 2012). This can be a challenge for community science programs because although it is relatively easy to train community partners to collect eDNA samples, it is far more challenging to train them to independently visualize and analyze results from these studies. Indeed, learning the bioinformatic tools necessary for managing the large, multidimensional datasets generated in these studies can be difficult for professional researchers (Carey & Papin, 2018), let alone for the non-technical audience of some community science programs.
To address this challenge, we created the R package "ranacapa", at the core of which is a Shiny web app that can be used to visualize results from eDNA sequencing studies and perform simple community ecology analyses. ranacapa complements existing visualization platforms (e.g. Phinch (Bik & Phinch Interactive, 2014), Phyloseq-Shiny (McMurdie & Holmes, 2015), QIIME2 Viewer), because in addition to interactive visualizations, ranacapa includes brief explanations of several core analyses used in eDNA studies and includes links to additional educational resources. ranacapa works with community matrices generated via QIIME (Caporaso et al., 2010) or the Anacapa sequence analysis pipeline, the latter being used extensively by the CALeDNA program.
Here, we describe the package and how it is used by two community science partnerships based at the University of California, Los Angeles (UCLA): first, a collaboration between eDNA researchers and resource managers at the National Park Service, and second, a partnership between community ecology researchers and an undergraduate microbiology course at UCLA. As we show in the Use cases, empowering community partners to interact with the data and perform simple but insightful community ecology analyses can help make these collaborations more enriching and valuable to both parties.

Implementation
At the core of ranacapa is a Shiny web app (Chang et al., 2018), which is available at http://gauravsk.shinyapps.io/ranacapa or with ranacapa::runRanacapa(). The package also includes two categories of helper functions ( The ranacapa Shiny app allows users to interact with eDNA results through statistical summaries and interactive plots, displayed in the following tabs: • Sequencing depth: Introduces the potential for variation in sequencing depth among samples and explains the basic logic behind rarefying samples in metagenomics studies (Figure 1). Users can rarefy the dataset  to a sampling depth, or can proceed through the rest of the app without rarefying samples. The documentation acknowledges recent disagreement regarding the value of rarefying in metabarcoding and eDNA sequencing studies (McMurdie & Holmes, 2014).
• Taxonomy heatmap: Shows the taxon-by-sample matrix as an interactive heatmap made using heatmaply:: heatmaply() (Galili et al., 2018), where the color of each cell represents the number of times a given taxon was sequenced in a sample ( Figure 2). Users can filter the taxon list by selecting or deselecting specific taxa. • Taxonomy barplot: Shows the taxonomy-by-sample matrix as an interactive barplot ( Figure 3).
• Alpha diversity plots: Introduces the concept of alpha diversity as the local diversity measured in a single habitat or sample. Users can plot alpha diversity as observed taxon richness or as Shannon diversity per sample, or can group samples according to a variable in the metadata file ( Figure 4).
• Alpha diversity statistics: Allows users to choose a variable from the metadata, and generates an alpha diversity ANOVA table according to the user-selected variable. The tab also shows the output from a post-hoc Tukey test.
• Beta diversity plots: Introduces the concept of beta diversity as the turnover in species composition across habitats (or samples). The tab includes an ordination plot generated by phyloseq::plot_ordination(), which in turn uses an ordination object made with phyloseq::ordinate(., method = "PCoA").
Points on the PCoA plot are colored according to a user-selected metadata variable ( Figure 5).
The beta diversity plots tab also includes a dendrogram that groups sites based on Ward's cluster analysis (stats::hclust(distance_object, method = "ward.d2")), where distance_object is made using phyloseq::distance(). For both figures, users can toggle between using Jaccard and Bray-Curtis dissimilarity.
• Beta diversity statistics: Shows results from two statistical tests of species turnover across sites. The first test is a multivariate ANOVA of taxon turnover across sites, implemented with vegan::adonis(). The second statistical test, which is implemented with vegan::betadisper(), is of heterogeneity of variances among samples. This test compares the degree of sample-to-sample variation within habitats (or within other user-selected groups).
Operation ranacapa depends on Bioconductor v 3.7, which in turn relies on R v 3.5.0. The Shiny app has been tested on Chrome and Firefox on Windows, Mac-OSX, and Ubuntu.

Input file structure
The ranacapa Shiny app requires two input files. The first requirement is a taxon-by-sample matrix, uploaded either as a rich, dense .biom table, or as a tab-separated .txt file. Qiime2-generated .qza files generated by QIIME2 are not immediately suitable for ranacapa, as they do not contain full taxonomy information. If the site-by-species matrix is uploaded as a .txt file, the file should match the specifications of the output files from the Anacapa eDNA sequence analysis pipeline. In Anacapa output, each row represents a taxonomic identification, and each column (save one) represents the number of times that taxon appears in each sequenced sample. One column, named sum.taxonomy must contain the taxonomic identification, with taxonomic rank separated by a semicolon, e.g. "Chordata;Actinopteri;Chaetodontiformes;Chaetodontidae;Chaetodon; Chaetodon reticulatus ." A valid input file is structured as follows: The second requirement is a tab-separated .txt file that contains sample metadata. The first column in the metadata file should match the sample names in the taxonomy table; the remaining columns contain sample information for each of the samples in the taxon-by-site matrix. The metadata should contain categorical variables with two or more categories per variable. A valid metadata file for the taxonomy The ranacapa function validate_input_files() verifies that both the taxonomy table and the metadata files match structural requirements, which are documented in the function help files.

Usecases
We expect that researchers with expertise in bioinformatics will use the sequence analysis pipeline of their choice to assign taxonomy to eDNA datasets, and generate clean taxonomy and metadata files that can be visualized in ranacapa. Researchers can share these files with their partners, and emphasize the analyses or visualizations most appropriate to their use case. We now show how ranacapa can facilitate authentic communication between researchers and community partners in two settings.
Use case 1: Partnership between eDNA researchers and natural resource managers A team of UCLA researchers partnered with resource managers at the Channel Islands National Park Service to assess the potential for eDNA as a biodiversity monitoring tool to supplement time-intensive visual biodiversity surveys in the Southern California Channel Islands (Deiner et al., 2017;Lessios, 1996;Usseglio, 2015). For this partnership, resource managers collected and filtered 30 unique one-liter water samples for eDNA analysis at permanent monitoring sites inside and adjacent to protected areas, and research scientists at UCLA performed eDNA sequencing of the mitochondrial 12S (Miya et al., 2015) and CO1 (Leray et al., 2013) genes, targeting bony fishes, elasmobranches, and invertebrate taxa. The researchers processed sequences and assigned taxonomy using the Anacapa pipeline, and shared results with the resource managers using the ranacapa Shiny app.
The taxonomy heatmap of species detected using the 12S and CO1 metabarcodes ( Figure 2) was the most valuable visualization to this collaboration, because it allowed the resource managers to filter the large observed species list down to a particular set of key taxa that they regularly monitor. The heatmap showed that this pilot study detected 36 of the 70 key metazoans at the species level, and the remaining 34 at the genus, family, or order level. This indicates that eDNA-based studies can provide critical information for ongoing management efforts and provide new insights into the spatial and temporal distributions of these species. The value of ranacapa in this scenario was to quickly sort through long species lists generated by eDNA sequencing to highlight the strengths and weaknesses in using eDNA to monitor diversity in the Channel Islands. The data from this study are packaged as the demo dataset for the ranacapa Shiny app and are available online (Kandlikar et al., 2018a).
Use case 2: Partnership between eDNA researchers and an undergraduate microbiology course A team of community ecology and environmental DNA researchers in the CALeDNA program collaborated with instructors of a research-based environmental microbiology course at UCLA (Shapiro et al., 2015), in which students used eDNA metabarcoding to study the impact of a local wildfire on the plant and soil microbial community. The goal of this twenty-week course was to provide undergraduate students an authentic experience in basic microbiology and microbial community ecology research. Over the first ten weeks, eDNA researchers on the instructional team sequenced the ITS2 (Gu et al., 2013) and 16S SSU RNA (Caporaso et al., 2012) metabarcoding regions from student-collected soil samples and used the Anacapa pipeline to generate taxon-by-sample tables.
The course instructors used the ranacapa Shiny app to introduce students to the structure of eDNA sequencing results. The students were encouraged to explore data and perform the statistical analyses most pertinent to the hypotheses they had formed at the beginning of the course. A key benefit of using ranacapa was that despite having no prior bioinformatics experience, students could begin exploring the biodiversity in their samples in a matter of minutes by using the online instance of the Shiny app. This allowed the instructors to focus classroom time on biological questions rather than on troubleshooting bioinformatics problems, as had been the case in previous sessions of the course. The course instructors noted that visualizing eDNA data in ranacapa helped students understand the relationships between taxon-by-site matrices and the various metadata they had collected in the field. By significantly reducing the time and difficulty in visualizing basic biodiversity patterns, ranacapa helped students develop and pursue more sophisticated analyses during the remainder of the course, using tools such as STAMP (Parks et al., 2014) and PICRUSt (Langille et al., 2013). The taxonomy tables and metadata files used in this course are available online (Kandlikar et al., 2018b).

Summaryandfuturedirections
Metabarcode sequencing of environmental DNA is becoming a key tool in a wide variety of ecological studies, and results from these studies are of interest to a broad audience. Our R package and Shiny app ranacapa helps users conduct exploratory analyses and visualizations on eDNA datasets, and is a step toward more fully engaging participants in all phases of eDNA sequencing-based community science projects.
We propose three avenues for future work with ranacapa. First, we plan to use ranacapa as the primary tool to present eDNA results from hundreds of samples sequenced by the CALeDNA community science program. Second, ranacapa is being integrated into the upcoming undergraduate curriculum module "Pipeline for Undergraduate Microbiome Analysis", which will be an open-source, comprehensive suite of analysis and data visualization tools for undergraduate researchers. Finally, in the long-term, we believe there is great promise in linking ranacapa with packages that connect with APIs of online biodiversity databases (e.g. Taxize (Chamberlain & Szöcs, 2013), rinat (Barve & Hart, 2017)). This will help users explore a much wider range of biodiversity questions, for example, by programmatically asking whether their samples include invasive species that are absent from other nearby sites. In sum, tools like ranacapa that allow non-technical audiences to easily interact with results from eDNA sequencing studies have great potential to engage community partners with a wide range of backgrounds and interests in primary research. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.

Softwareavailability
platforms. ISME J. 2012; 6(8): 1621-1624. Introduction The sentence "A key ingredient to promote sustained success of such programs is that community partners should be able to engage across multiple stages of the research project, not only in sample collection" is a bit awkward. Perhaps something like the following would be more clear: "Such programs are more likely to succeed if community partners are able to be involved in multiple stages of the research project, not only sample collection" End of paragraph 2: "let alone for the non-technical audience of some community science programs." We suggest "audience" be replaced with "members", "partners", or "collaborators", since they are involved in the project.

Implementation
Paragraph 1, sentence 1: The command "ranacapa::runRanacapa()" does not work. Should it be "ranacapa::runRanacapaApp()"? Figure 4: It would be nice if the results of the Tukey's HSD test be included on the graph using letter codes. Sequencing depth, sentence 2: "Users can rarefy the data set to a sampling depth, or can proceed 1 2 1 2 Sequencing depth, sentence 2: "Users can rarefy the data set to a sampling depth, or can proceed through the rest of the app without rarefying samples." It's nice to have the option, but if sequences are not rarefied, perhaps they should be converted to proportions? The taxon abundance plots (e.g. the heat map) is biased without some correction for sampling depth and proportions would avoid the loss of data associated with rarefaction. While converting to proportions will not remove sample-size bias for alpha and beta diversity analyses, it will remove the bias for taxon abundance analyses for the most part. The conversion to proportions could also be an option in just the taxon abundance analyses. Beta diversity plots, sentence 1: "Introduces the concept of beta diversity as the turnover in species composition across habitats (or samples)." The word "turnover" seems to imply a change over time, rather than a comparison between communities. Perhaps something like: "Introduces the concept of beta diversity as a way to compare community composition across habitats (or samples)." Beta diversity statistics, sentence 1: "Shows results from two statistical tests of species turnover across sites." See comment above on "turnover".

Suggestions on the software
Exploring ranacapa at shows the interactive tools. We https://gauravsk.shinyapps.io/ranacapa suggest that screenshots from the actual shinyapp be presented as figures as they provide the context for exploring the data. For example under Figure 2, the legend states that users can also select or deselect individual taxa' but the figure 2 in the manuscript does not show this. This is confusing. We also suggest giving explicit examples for executing the shiny app on a desktop maybe right after the installation instructions.

Data import
The proper format for input data is described in the article, but it would be nice if it was repeated in the "data import" section of the app as well. You could also include tips to convert common formats to the needed format here.

Sequencing depth
Second paragraph, first sentence: "In eDNA sequencing, such variation in how deeply a given sample is sequenced can happen for a variety for reasons-". Should the "-" be a ":"? Third paragraph, first sentence: You use double quotes for "deeply" in the first paragraph, but single quotes for 'rarefy'. Add proportions as an alternative to rarefaction instead of "none"? The rarefied samples plot is a good idea, but hard to read in its current state. Perhaps change the faceting settings so that there is one column of plots or have a option to choose the sample shown? Taxonomy bar pot: The number of similar colors make this hard to read without selecting individual taxa. We know this is a limitation of stacked barcharts, but it might make it more readable to sort the taxa by average abundance and then stagger the colors like so: For example, if there are 30 taxa, then the first 10 get colors 1, 4, 7, 10, 13, 16, 19, 22, 25, 28 (seq(1,30, 30 / 10)). Also have the most abundant taxa be the lowest on the stacked bars. That way adjacent colors can be differentiated and the colors of rare taxa won't be confused with the colors of the abundant taxa.

Taxonomy heatmap
How about faceting by sample metadata or clustering samples by similarity? You could use the results of the Ward's Hierarchical Clustering like you do in the beta diversity section.
Can you make the height of the plot depend on the number of samples plotted? Also, making the "Select taxa to visualize" box taller would be nice.

Alpha diversity plots
You use the term "species richness" without explicitly defining it, although you implicitly define it. It

Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool? Yes
Are the conclusions about the tool and its performance adequately supported by the findings presented in the article? Yes No competing interests were disclosed.

Competing Interests:
Referee Expertise: R programing, biology, bioinformatics We have read this submission. We believe that we have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.
14 December 2018 Referee Report https://doi.org/10.5256/f1000research.18233.r40129 Holly M. Bik Department of Nematology, University of California, Riverside, Riverside, CA, USA This article presents a new R software package and shiny app called "ranacapa", aimed at producing rapid visualization and exploration of eDNA metabarcoding datasets. Overall I found this software tool to be exciting and user friendly, and the outlined use cases provided good examples of the need for such tools amongst end users including researchers and undergraduate students. The R shiny app was easy to explore using the demo dataset, and the plots were responsive and visually useful.
When trying to install ranacapa in RStudio (via install.packages), I am consistently getting an error message stating that "package 'ranacapa' is not available (for R version 3.3.2)". Furthermore, ranacapa does not appear to be listed as a package currently available in CRAN (https://cran.r-project.org/web/packages/available_packages_by_name.html#available-packages-R). Further investigation suggests that this package requires R 3.5.0 or higher to run, but this is not obvious for end users with older versions of R installed. Is it possible to add back compatibility to older versions of R? Especially for end users using HPC facilities who may be unable to update the base R version on their cluster.
"Taxonomy-by-sample matrix" -since ranacapa uses a non-standard input (essentially an OTU table summarized by taxonomy), it would be useful to provide specific instructions and/or a conversion script where users can take their QIIME BIOM files or tab-delimited OTU tables and convert them into a format that is suitable for uploading into ranacapa. Users with minimal technical expertise may struggle to convert their data in the correct way. Especially useful would be R scripts or package commands (e.g. phyloseq) that will output taxonomy-by-sample-matrixes in the correct format.
The R shiny web app does not provide much information regarding file formatting (users must read the F1000 article for specific information). The only documentation online states that the imported files should be in .biom or .txt formats. What format(s) are supported for the header row (commented out vs. plain text)? Are there any limitations on sparse vs. dense or JSON vs. HDF5 BIOM files (e.g. from QIIME 1 or QIIME2)? Detailed information and documentation should be provided on the website itself in addition to QIIME2)? Detailed information and documentation should be provided on the website itself in addition to the F1000 article.
For the metdatata file -can users directly import QIIME-formatted mapping files (e.g. with a header row beginning with #SampleID that has been validated via Keemi)? Or does this file need to be be edited further for ranacapa?
For the demo file on the web server -what study did this file come from? It would be useful to have some contextual information about the file, eDNA markers used, questions/hypotheses, and study design so that end users can explore the demo dataset in a more thoughtful way.
Some components of the R Shiny web app do not always seem to function correctly over a slow internet connection -it seems to freeze up and require re-loading, and/or users are presented with an error message. This error message sometimes goes away and the plots pop up as expected after a few minutes. Better error dialogs or "please wait" message boxes would be much less frustrating for the end user to figure out what is happening. Sequencing Depth -the rarefaction depth slider bar is straightforward and should be familiar to most users, however, what impact do multiple rarefactions have on the displayed graphs? Are the rarefaction curves averaged somehow before being displayed? Further information on this parameter would be useful to include in the explanatory text.
Taxonomy heatmap -when choosing a lower taxonomic level, the taxonomy strings are overlapping and unreadable. Zooming in cuts off some of the categories on the x-axis. It would be better to be able to expand the heatmap along the y-axis (stretch it out) so you can read the taxonomy labels while still being able to view all of the heatmap information.
Taxonomy heatmap -when selecting a taxon to visualize, users might want to see more detail at lower taxonomic levels, however, selecting a taxon to visualize and then choosing a different taxonomic rank currently removes this filter choice and reverts back to showing all taxa at that level.
Alpha Diversity Plots -what is the difference between Observed vs. Shannon diversity visualizations? The explanatory text only partially explains the difference between these two options, and could be clarified to explicitly state the important differences in these two calculations. Furthermore, what do high vs. low numerical values mean for each of the two indices, in biological terms (e.g. lower number of species)? These kind of diversity statistics may be familiar for ecologists and microbiome researchers, but are likely to be confusing for citizen scientists, students, or scientists outside of these fields.
Alpha Diversity Stats -Unless you have a strong statistical background, it is impossible to interpret the numbers and outputs listed in this tab in the ranacapa shiny app. More explanation is needed to guide users in what they should be looking for -what columns are most important in the ANOVA table to see if samples are in fact unequal in terms of their diversity? In the post-hoc tests, should users be looking for P values <0.05 in the last column?
Beta Diversity -the Jaccard and Bray-Curtis indexes could be explained more plainly. Jaccard is the simplest measure of shared taxa/OTUs, while Bray-Curtis is an index focused on the most abundant taxa/OTUs in the dataset. Also some explanation of the PCoA axes (e.g. that they explain variation but do not relate to metadata) would be useful. Adding the Canberra index might also be useful here, as this is another useful index which ignores the most abundant taxa and looks at differences across rare species.
will provide a nice complement to a project report for people that want to dive into the results, or explore the robustness of the conclusion that are highlighted in a report. I also agree with the authors that such tools are particularly interesting for sharing results with non-expert enthusiasts and students. I appreciate the accompanying text to present the specificity of composition (count) data and the possible flaws when analyzing such data. The website "Gusta Me" ( ) could maybe be mentioned as an external resource for guiding further https://mb3is.megx.net/gustame the users for the interpretation of results, or to guide any additional analysis. I wonder how such application is intended to be deployed. Do the authors plan to let research scientists deploy the app within their own computational resources or do they plan to make the application accessible ( ) opened to the community? https://gauravsk.shinyapps.io/ranacapa/ I made few comments on the GUI that the authors may or may not follow. The most important point to address would be to allow users to write their PERMANOVA model.

Data import:
Maybe add the expected format, with a toy example, indicating the separator character (tab or comma or semi-comma?). This is mentioned in the GitHub page of the project (not the separator though), but I think this would be nice to have it here also. My guess is that many users would not even get to the GitHub page before using the app. Sequencing depth: Would it be possible to add a "free" input field? As it is now, it is not easy to get a precise value. The slider does not allow this kind of precision, it increases or decreases by 1000 but on the demo example, it is stuck to 10006. Would it be possible to include normalization as an option? At least the relative abundance for a start, because as you mention on the accompanying text, we are far from having reach a consensus on that matter. What means the first field "select the variable", do you mean to rarefy not samples but something else? I don't understand. Taxonomy barplot: I personally don't like taxonomic barplots, but I recognize that they can be useful to easily illustrate some obvious differences (or similarities) between experimental treatments to an audience unfamiliar with metabarcoding data. The lowest taxonomic ranks return a (way) too many categories. In the presented example. Even the highest taxonomic rank (phylum), it yields too many categories to easily visualize what is actually in the samples, because colors are too close to each other. There is no solution, I just don't like these plots. But it is nice to have this option in the app anyway. Taxonomy heatmap: Is there an option to scale differently the X and Y axis? In the example dataset, it is actually a similar problem as for taxonomy barplot, lowest taxonomic rank gives too many rows on the plots. A way to better see is to zoom in, but then the horizontal axis is quite messed up. Maybe it would be nice to have input fields to manage those axes and font size. Alpha-diversity plots: I guess the data behind is the rarefied version of the dataset, but this should be clear. Maybe the box can be there, but in grey to show that it would not make sense to use the raw dataset? Alpha-diversity stats: I think this is fine. Beta-diversity plots: The users should be able to refine the ordination plots, its size, the size of each axis. Why the ordination plots configuration (and the cluster analysis) is changing when we select different variables to group the dot shapes and colors? Beta-diversity analyses: Would it be possible to let the user write his own model? As for now, it is not possible to have an Would it be possible to let the user write his own model? As for now, it is not possible to have an interaction term, or a nested model. To be able to select the sample as variable does not make sense.

Is the rationale for developing the new software tool clearly explained? Yes
Is the description of the software tool technically sound? Yes Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others? Yes

Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool? Yes
Are the conclusions about the tool and its performance adequately supported by the findings presented in the article? Partly No competing interests were disclosed.

Competing Interests:
Referee Expertise: Molecular ecology, environmental genomics, bioinformatics I have read this submission. I believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.
The benefits of publishing with F1000Research: Your article is published within days, with no editorial bias You can publish traditional articles, null/negative results, case reports, data notes and more The peer review process is transparent and collaborative Your article is indexed in PubMed after passing peer review Dedicated customer support at every stage For pre-submission enquiries, contact research@f1000.com