> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/inputs-and-outputs/choose-the-input-layer-intentionally.md).

# Choose the input layer intentionally

| API                       | Reads                                             | Affected by earlier script output?               |
| ------------------------- | ------------------------------------------------- | ------------------------------------------------ |
| `get_ival(id)`            | physical input report                             | No                                               |
| `get_val(id)`             | current working/output value                      | Yes                                              |
| `get_lval(id)`            | final output value from the previous VM iteration | Yes—from the previous cycle, not the current one |
| `get_ipolar(stick, part)` | physical high-resolution polar input              | No                                               |
| `get_polar(stick, part)`  | current high-resolution polar value               | Yes                                              |

Raw reads are the safer default for independent features. Use current-value reads when one transformation is deliberately intended to build on another.

`get_lval` does not mean "last physical input." It returns the identifier's last outgoing value after the previous cycle's script processing. Writes made earlier in the current cycle do not change it, but writes from the prior cycle do.

{% code title="input-layer-comparison.gpc" %}

```cpp
int raw;
int working;

main {
    raw = get_ival(PS5_RX);
    set_val(PS5_RX, raw / 2);
    working = get_val(PS5_RX); // observes the half-strength value
}
```

{% endcode %}


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/inputs-and-outputs/choose-the-input-layer-intentionally.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.