> ## Documentation Index
> Fetch the complete documentation index at: https://docs.consensus.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Find published process conditions for a manufacturing step

> See what temperature, time, atmosphere, and concentration ranges others have published for a process, so you start from precedent rather than from scratch.

## What you get

A table of published process conditions for your step — each with the material system it applied to, the outcome achieved, and the paper it came from. A starting envelope for your own DOE instead of a blank one.

## Who it's for

Process engineers standing up a new process, transferring one between sites or tools, or trying to widen a window that keeps drifting out of spec.

## Why this needs full text

Process conditions live in methods sections. Abstracts report that a process worked; they almost never report the temperature ramp, the dwell, the atmosphere, or the concentration. This use case depends on `include_full_text_chunks=true` and on phrasing the query as the conditions themselves.

<Note>
  Full-text excerpts require a paid plan or an Enterprise API key and currently cover open-access papers. Process literature is heavily represented in closed conference proceedings, so expect partial coverage and treat what you get as a starting point rather than a survey.
</Note>

## The extraction schema

Fix these columns before you start, or you will end up with values you cannot compare:

| Column                | Why                                                  |
| --------------------- | ---------------------------------------------------- |
| Process step          | The specific operation, not the overall flow         |
| Parameter and value   | With units exactly as published                      |
| Range or single point | A window is far more useful than one setting         |
| Material system       | Conditions rarely transfer across substrates         |
| Tool or method        | Equipment differences change achievable ranges       |
| Outcome achieved      | The condition means nothing without what it produced |
| Source                | DOI plus the excerpt the value came from             |

## The API call

```bash theme={null}
curl -G "https://api.consensus.app/v1/search" \
  -H "x-api-key: $CONSENSUS_API_KEY" \
  --data-urlencode "query=atomic layer deposition alumina process temperature precursor pulse time conditions" \
  --data-urlencode "domain=mat,eng,chem" \
  --data-urlencode "include_full_text_chunks=true" \
  --data-urlencode "page_size=100"
```

Phrase the query as the parameter you want, not the process in general — excerpts are selected for relevance to your query, so `deposition temperature precursor pulse` returns methods paragraphs while the bare process name returns introductions.

## What to check before you trust it

* **Never transfer conditions without checking the material system and tool.** Published conditions are specific to a substrate, a reactor geometry, and a precursor. They are a starting point for a DOE, not a recipe.
* **Watch for missing parameters.** Papers routinely omit one condition that turns out to be load-bearing. Mark those as NOT REPORTED rather than assuming a standard value.
* **Prefer papers reporting a window over a single point.** A range tells you the sensitivity; a point tells you almost nothing about robustness.
* **Check the outcome definition.** "Successful deposition" means different things across groups; align on the metric before comparing conditions.

## Related

<CardGroup cols={2}>
  <Card title="Extract numbers and formulas from full-text papers" icon="table-cells" href="/use-cases/extract-values-from-full-text">
    The general extraction discipline underneath this.
  </Card>

  <Card title="Find published work on a failure or degradation mechanism" icon="triangle-exclamation" href="/use-cases/failure-mode-scan">
    When the process window keeps producing defects.
  </Card>

  <Card title="Best practices" icon="shapes" href="/use-cases/best-practices">
    Excerpt-first extraction and the rest of the primitives.
  </Card>

  <Card title="All use cases" icon="grid-2" href="/use-cases">
    Browse the gallery by persona.
  </Card>
</CardGroup>