> For the complete documentation index, see [llms.txt](https://docs.kbase.us/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kbase.us/apps/analysis/chemical-abundance.md). # Chemical Abundance ## Data Cleaning and Statistical Analysis As both chemical abundance and amplicon matrices are similar, similar apps for cleaning, normalizing, and performing statistical comparisons can be done on both types. See the previous page on [Data Matrices](/apps/analysis/matrix.md) for information on using these apps. ## Popular Use Cases of Chemical Abundance Data You can view a few public Narratives that demonstrate popular use cases for chemical abundance tables in KBase. * Metabolomics (and other omics) data representation in Escher pathway maps * * * Cheminformatics expansion of known metabolites (based on known compounds in a metabolic model) and mapping onto unknown peaks from metabolomics data (PNNL Summer School workflows - WHONDRS) * * Reconcile metabolic models to exo-metabolite data - Web of Microbes * --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kbase.us/apps/analysis/chemical-abundance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.