> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/library-blocks-reference/signal-routing/data-type-converters.md).

# Data Type Converters

## Description

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-a3ac892fdb679b81282df0b18b03d479c17edfe5%2Fimage%20(491).png?alt=media" alt="" width="285"><figcaption></figcaption></figure>

The **Float to integer conversion** and **Integer to float conversion** blocks, located in the **Signal Routing** library, convert data types between float and integer.

**Float to integer conversion**: converts data type from float to integer.

**Integer to float conversion**: converts data type from integer to float.

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-675d1e6bee34acd893307f4ea113f00239ba61f2%2Fimage%20(492).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

These blocks have no parameters.

## Inputs

| Input                   | Description                |
| ----------------------- | -------------------------- |
| Float or integer signal | Input to conversion block. |

## Outputs

| Output                  | Description                       |
| ----------------------- | --------------------------------- |
| Integer or float signal | Output from the conversion block. |

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.


---

# 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.opal-rt.com/docs/hypersim/library-blocks-reference/signal-routing/data-type-converters.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.
