> 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/setting-up-microbiomestat-installation-and-data-preparation/laying-the-foundation-creating-the-microbiomestat-data-object/loading-dgelist-data-into-microbiomestat.md).
# Converting DGEList Data into MicrobiomeStat
Learn the steps to convert DGEList data format into MicrobiomeStat data format.
This guide will assist you in converting DGEList data format into MicrobiomeStat format.
Before we proceed with the conversion, let's examine the original structure of our DGEList data:
Original structure of the DGEList data.
Now, follow the steps below to convert the DGEList data:
```r
# Load necessary packages
library(airway)
library(DESeq2)
library(edgeR)
# Load dataset
data("airway")
dds <- DESeqDataSet(airway, design = ~ cell + dex)
dge <- DGEList(counts = counts(dds), group = dds$dex)
# Convert DGEList to MicrobiomeStat data object
data.obj <- mStat_convert_DGEList_to_data_obj(dge)
```
After conversion, let's take a look at the transformed data structure:
Structure of the MicrobiomeStat data object after importing DGEList data.
By using the `mStat_convert_DGEList_to_data_obj` function, you can effectively convert:
* **dge.obj**: Your existing DGEList object.
The resultant **MicrobiomeStat data object** includes:
* **feature.tab**: A matrix populated with counts data.
* **meta.dat**: A data frame detailing the sample information.
As part of the conversion process, features with a sum of zero from the counts data are filtered out to maintain data relevance.
---
# 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/setting-up-microbiomestat-installation-and-data-preparation/laying-the-foundation-creating-the-microbiomestat-data-object/loading-dgelist-data-into-microbiomestat.md?ask=&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.
