> 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/startcompile2_144217709.md).

# StartCompile2

<table data-header-hidden><thead><tr><th width="199.77783203125"></th><th></th></tr></thead><tbody><tr><td><strong>Group</strong></td><td>Model Preparation</td></tr><tr><td><strong>Description</strong></td><td><p>Start the compilation steps, which separate the subsystems, generate the code and compile each subsystem.</p><p>This function enables you to specify:</p><ul><li>options by subsystem</li><li>option in the array will be read, and this option will be applied to each subsystem</li><li>If you want to compile all subsystems with the same options, you must specify only one subsystem with an empty string for the subsystem<br>name. Example: RtlabApi.StartCompile2( ( (““,options), ) )</li></ul><p>Compilation continues after this function has returned with a return code of EOK. You must call DisplayInformation to get the compilation results and the compilation termination status. You may call AbortCompile during the operation to stop the model's compilation. You must call RegisterDisplay to register to receive status and compilation messages.</p></td></tr><tr><td><strong>Required Control</strong></td><td>System Control</td></tr><tr><td><strong>Usage</strong></td><td>subsystemInfo1 = (subsystemName1, subsystemOptions1) subsystemInfo2 = (subsystemName2, subsystemOptions2) .... compilationInfo = ( subsystemInfo1, subsystemInfo2, ...)<strong>RtlabApi.StartCompile2</strong> (compilationInfo)</td></tr><tr><td><strong>Input</strong></td><td><p><strong>subsystemName:</strong> Subsystem name.</p><p><strong>subsystemOptions:</strong> Indicates which step of the compilation is to be completed. See OP_COMPILATION_DEFINE.</p></td></tr><tr><td><strong>Output</strong></td><td>None</td></tr><tr><td><strong>Exception</strong></td><td><p><strong>EOK:</strong> Command successfully issued (See Description for more information).</p><p><strong>OP_API_ESEPARATION</strong>: Error while separating the model's subsystems.</p><p><strong>OP_API_ECODE_GENERATION:</strong> Error while generating code for the subsystems.</p><p><strong>EPERM:</strong> System control was not granted to this client.</p><p><strong>EBUSY:</strong> Model executables already loaded.</p><p><strong>EBADF:</strong> Model not specified by previous Connect or OpenProject.</p><p><strong>EIO:</strong> Error sending the request or receiving the reply.</p><p><strong>OP_API_ENO_PRODUCT:</strong> No license for RT-LAB and RT-LABx.</p><p><strong>OP_API_ENO_DEVELOP_LICENSE:</strong> No development license available.</p><p><strong>OP_API_ENO_TARGET_LICENSE:</strong> No license for the selected target.</p></td></tr><tr><td><strong>Examples</strong></td><td>None</td></tr><tr><td><strong>Related Items</strong></td><td>AbortCompile, DisplayInformation, OP_COMPILATION_DEFINE.</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/startcompile2_144217709.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.
