> For the complete documentation index, see [llms.txt](https://dante-solutions-inc.gitbook.io/dante-6.3-help-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dante-solutions-inc.gitbook.io/dante-6.3-help-documentation/introduction-2/general/fitting-type.md).

# Fitting Type

DANTE currently has 4 fitting tools: **Dilot Fit, HTC Fit, Mec Fit, and TTT Fit**

The fitting type section sets the inputs for the type of data that are going to be fit by the utility tool. Each fitting tool has slightly different options based on the data the utility is designed to fit.

A more depth description of the fitting options can be found in the specific utility page.

### [**Dilot Fit**](/dante-6.3-help-documentation/introduction-2/dilot-fit.md)

The **Dilot Fit** utility offers two different fitting types, **Strain** and **Phase Fraction**.

![](/files/ciHt3EAjbn7qWjgzbMOG)

#### Strain Fitting Type

* Should be used when the user has classic dilatometry data consisting of time, temperature, and strain

#### Phase Fraction Fitting Type

* Should be used when the user has experimental data in the format of time, temperature, and phase volume fraction

### [**HTC Fit**](/dante-6.3-help-documentation/introduction-2/htc-fit.md)

In the **HTC Fit** utility, the fitting type can be found under the **Controls** tab. The HTC can be fit by **Time** or **Temperature** depending on the type of process the data is extracted from.

![](/files/0DveDDlStv649OqMh14d)

### [**Mec Fit**](/dante-6.3-help-documentation/introduction-2/mec-fit.md)

For the **Mec Fit** utility, instead of **Fitting Type**, the utility offers **Phase Composition** and **Processing Method** as the two options.

![](/files/gKCeww9GojwJCeR5AHxB)

#### Phase Composition

* Used to select the phases to be fitted for
* **Austenite, Ferrite, Pearlite, Bainite, and Martensite**

#### Processing Method

**Plot Input Parameters**

* Plots the plastic parameters located in the Parameters section with the elastic values in the Properties section to the experimental data

**Fit Using Random Search**

* Random search method based on the number of iterations defined by the user (**NLoop**)

**Plot for Single Point**

* Plot a single stress/strain curve based on the inputs defined in the Conditions menu
* Inputs required include **Max Strain, Strain Rate, Temperature, and Carbon Level**

**Plot for Strain Rate Range**

* Plots an array of stress/strain curves based on a range of strain rates defined in the Conditions menu
* Inputs required include **Max Strain, Temperature, and Carbon Level**

**Plot for Temperature Range**

* Plots an array of stress/strain curves based on a range of temperature defined in the Conditions menu
* Inputs required are **Max Strain, Strain Rate, and Carbon Level**

**Plot for Carbon Range**

* Plots an array of stress/strain curves based on a range of carbon defined in the Conditions menu
* Inputs required include **Max Strain, Strain Rate, and Temperature**

### [**TTT Fit**](/dante-6.3-help-documentation/introduction-2/ttt-fit.md)

The **TTT Fit** utility fits TTT data for the DANTE phase kinetic parameters

![](/files/uV0bkIgetPg1JiwIYEB9)

**Phase Type**

* The phase types include **Bainite, Pearlite, Ferrite, Ferrite + Pearlite**


---

# 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://dante-solutions-inc.gitbook.io/dante-6.3-help-documentation/introduction-2/general/fitting-type.md?ask=<question>&goal=<endgoal>
```

`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.