> 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/evaluation-and-reporting/golden-reports/cooling.md).

# Cooling

This page covers the source-specific heuristics and assumptions behind district cooling in the Golden Report.

## Abbreviations

* **AHU** — air handling unit

## What gets measured

District cooling is split into three buckets:

* **Cooling circuits**
* **Air handling units in cooling mode**
* **Other**

`Other` covers cooling uses outside those HVAC components.

## How energy is distributed across uses

A monthly `Other` amount is set aside first — either a figure you provide or the estimate described below.

The remaining cooling energy is split between:

* **Cooling circuits**
* **Air handling units**

The default split is **50% / 50%**.

If you have a better building-specific split, Myrspoven uses that instead.

### Other-cooling estimate

If you do not provide an `Other` figure, it is estimated as the average of the **two lowest district-cooling months**.

This assumes those months mostly reflect non-HVAC cooling use.

The estimate requires at least **8 months** of energy data.

If less data is available, `Other` defaults to **0**.

## What myCoreAI controls

The myCoreAI-controlled share is the cooling used by:

* **Cooling circuits**
* **Air handling units in cooling mode**

That total is then weighted by uptime for the period.

## Source-specific calculation details

Cooling calculations are done separately for each component type.

* **Cooling circuits** use hourly averages, then aggregate across relevant components and time stamps.
* **Air handling units** use hourly averages during cooling mode, then aggregate across relevant units and time stamps.

## Improving accuracy

Two inputs improve accuracy most:

* Your real **Other cooling** figure
* Your real **cooling-circuit / AHU split**

Share them with your Myrspoven representative to replace the defaults.


---

# 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/evaluation-and-reporting/golden-reports/cooling.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.