> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/decision-intelligence/doe-tools.md).

# DOE Tools

Once an experiment is planned, something has to generate the design table. This page is that tooling rather than the theory itself: two generators from the same author first, then the pyDOE factorial docs, then a worked factorial notebook.

[Design of experiments](https://github.com/tirthajyoti/Design-of-experiment-Python) is tirthajyoti/Design-of-experiment-Python on GitHub, a design-of-experiment (DOE) generator for science, engineering, and statistics. Its packaged successor is [doePy](https://github.com/tirthajyoti/doepy), tirthajyoti/doepy, the Design of Experiment Generator; read the docs at: <https://doepy.readthedocs.io/en/latest/>.

For the classic factorial layouts, [PyDoe](https://pythonhosted.org/pyDOE/factorial.html) is the Factorial Designs page of the pyDOE 0.3.6 documentation. To see one of those layouts worked end to end, the [DOE Notebook](https://charlesreid1.github.io/empirical-model-building/factorial_2level_3factor.html#twolevelfactorial) is the Factorial - Two-Level Three-Factor Design.


---

# 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.mlcompendium.com/decision-intelligence/doe-tools.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.