> For the complete documentation index, see [llms.txt](https://docs.ladybug.tools/hb-energy-primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ladybug.tools/hb-energy-primer/components/6_result/normalize_by_floor_area.md).

# Normalize by Floor Area

![](/files/-MihpgHGq8tKxUf1jQ9O)

![](/files/-MihpgHHWDagdOrRoYZG) - [\[source code\]](https://github.com/ladybug-tools/honeybee-grasshopper-energy/blob/master/honeybee_grasshopper_energy/src//HB%20Normalize%20by%20Floor%20Area.py)

Normalize Zone-level data collections from an energy simulation by the by the floor area of the corresponding honeybee Rooms.

## Inputs

* **data \[Required]**

  A list of HourlyContinuousCollections of the same data type, which will be normalized by room floor area. Data collections can be of any class (eg. MonthlyCollection, DailyCollection) but they should originate from an energy simulation sql (with header metadata that has 'Zone' or 'System' keys). These keys will be used to match the data in the collections to the input rooms.&#x20;
* **model \[Required]**

  An array of honeybee Rooms or a honeybee Model, which will be matched to the data collections. The length of these Rooms does not have to match the data collections and this object will only output collections for rooms that are found to be matching.&#x20;

## Outputs

* **total\_data**

  The total results normalized by the floor area of all connected rooms. This accounts for the fact that some rooms have more floor area (or have a multiplier) and therefore get a greater weighting.&#x20;
* **room\_data**

  The results normalized by the floor area of each individual room.&#x20;


---

# 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://docs.ladybug.tools/hb-energy-primer/components/6_result/normalize_by_floor_area.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.
