> For the complete documentation index, see [llms.txt](https://docs.myrspoven.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myrspoven.com/how-the-ai-saves-energy/mixed-circuit-control.md).

# Mixed circuit control

A mixed circuit feeds both another downstream heating or cooling circuit *and* at least one air handling unit (AHU). Because the same circuit serves two loads with different temperature requirements, myCoreAI applies a dedicated control strategy so neither side is starved.

## Qualification

myCoreAI treats a circuit as mixed when all three conditions hold:

1. A **reference formula** is defined for the circuit — a reference held in the circuit's metadata that couples it to the other systems it feeds.
2. A **supply curve** exists for that reference — the baseline temperature curve against outdoor conditions.
3. **Component connections** link the reference to at least one downstream heating or cooling circuit *and* at least one downstream AHU.

Otherwise the circuit is controlled as a regular (non-mixed) circuit.

## Supply temperature

myCoreAI combines its optimization target with the baseline value from the supply curve so the most demanding downstream consumer is always covered:

| Circuit type | Supply temperature                                        |
| ------------ | --------------------------------------------------------- |
| Heating      | **Maximum** of optimizer target and supply curve baseline |
| Cooling      | **Minimum** of optimizer target and supply curve baseline |

This prevents the AHU side from being undersupplied when the radiator side could be lowered further, and vice versa.

## Fallback

If the supply curve is missing or returns a non-numeric value at the current outdoor temperature, myCoreAI logs a warning and uses the optimizer value directly, without the baseline floor or ceiling.

## Identification

Mixed circuits are tagged by Myrspoven in BackOffice during onboarding.


---

# 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://docs.myrspoven.com/how-the-ai-saves-energy/mixed-circuit-control.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.
