> For the complete documentation index, see [llms.txt](https://www.microbiomestat.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.microbiomestat.wiki/introduction/the-edge-of-microbiomestat-why-it-should-be-on-your-shortlist.md).

# Exploring MicrobiomeStat: A Consideration for Your Research Toolkit

MicrobiomeStat provides a user-centric, adaptable, and supportive environment for insightful microbiome data exploration.

MicrobiomeStat provides comprehensive support for a wide array of input formats, accommodating the majority of formats utilized in microbiome research, including but not limited to qiime2, dada2, biom, mothur, phyloseq, DGEList, DESeqDataSet, and SummarizedExperiment. This compatibility facilitates an easy data import process. We encourage users to contact us if you encounter a format used in microbiome research that is not currently supported.

MicrobiomeStat offers a wide array of visualization styles, tailored for microbiome research. It optimizes data analysis for paired and longitudinal studies, and generates high-quality, publication-ready figures. Beyond its comprehensive support for longitudinal data analysis and visualization, MicrobiomeStat offers the flexibility to analyze and visualize individual time points. It can also be applied to cross-sectional/case-control data analysis.

MicrobiomeStat provides customizable parameters, allowing users to adapt analysis outputs to their research needs. Built with a high degree of flexibility, MicrobiomeStat is not confined to the analysis of microbiome data alone. Its versatile design extends its capabilities to accommodate and effectively analyze other omics data, making it a candidate tool for omics research and data interpretation.

Our team with rich experience in collaborative microbiome research and statistical methodological development, is committed to delivering rigorous and reproducible analysis of microbiome data.

MicrobiomeStat's outputs are compatible with the 'plotly' package, enabling users to create interactive graphics for further manipulation and customization post-analysis. The combination of time-series and individual time point analysis, along with paired samples analysis, makes MicrobiomeStat a versatile tool for comprehensive microbiome data analysis.

<figure><img src="https://3375851868-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhFAmY4z7d1R15Cv49vXQ%2Fuploads%2Fmj4UDzBH56eJGuenbc2m%2FDALL%C2%B7E%202024-10-12%2023.41.05%20-%20An%20illustration%20showcasing%20the%20capabilities%20of%20MicrobiomeStat%20for%20microbiome%20research.%20The%20image%20should%20highlight%20support%20for%20various%20input%20formats%20su.webp?alt=media&amp;token=883e6ba9-808d-4dd9-b6fa-379b3c62322a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.microbiomestat.wiki/introduction/the-edge-of-microbiomestat-why-it-should-be-on-your-shortlist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.