> 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/rt-lab/automation-api-and-scripting/rt-lab-api/python-rtlab-api-reference/introduction-to-functions_143429297/setparametersbyname_143497513.md).

# SetParametersByName

<table data-header-hidden><thead><tr><th width="199.77777099609375"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Interaction, Parameters</td></tr><tr><td><strong>Description</strong></td><td>Change the value of one or more RT-LAB parameters using their path and name in the model.</td></tr><tr><td><strong>Required Control</strong></td><td>Parameter Control</td></tr><tr><td><strong>Usage</strong></td><td>parameterNames = (paramName1, paramName2, ...) parameterValues = (paramValue1, paramValue2, ...)<strong>RtlabApi.SetParametersByName</strong> (parameterNames, parameterValues)</td></tr><tr><td><strong>Input</strong></td><td><p><strong>parameterNames:</strong> Tuple of parameters’ path and name to set values.</p><p><strong>parameterValues:</strong> Tuple of parameters’ values to set.</p></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Exception</strong></td><td><p><strong>EOK:</strong> Success.</p><p>EPERM: Parameter control had not been granted to this client.</p><p><strong>EBADF</strong>: Model not specified by previous Connect or OpenProject.</p><p><strong>ENOEXEC:</strong> Model is not loaded.</p><p><strong>EINVAL:</strong> No parameter to set or invalid parameter id.</p><p><strong>E2BIG:</strong> Too many parameters or values to modify.</p><p><strong>ENOMEM:</strong> Memory allocation error.</p><p><strong>ENOENT:</strong> Cannot open parameter file or parameter name not found.</p><p><strong>EIO:</strong> Error sending the request or receiving the reply.</p><p><strong>OP_API_MODEL_IO_TIMEOUT:</strong> Timed out waiting for reply from model.</p><p><strong>OP_API_MODEL_IO_ERROR</strong>: Model is missing some or all processes or subsystems.</p></td></tr><tr><td><strong>Examples</strong></td><td>See example parameter1.</td></tr><tr><td><strong>Related Items</strong></td><td>GetParametersDescription, GetParameterControl, GetParametersByName.</td></tr><tr><td><strong>Modules</strong></td><td><strong>import RtlabApi</strong></td></tr></tbody></table>


---

# 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/rt-lab/automation-api-and-scripting/rt-lab-api/python-rtlab-api-reference/introduction-to-functions_143429297/setparametersbyname_143497513.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.
