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

# Filter Room Result

![](/files/ea64HDvgNc1jWLp646Xp)

![](/files/q9SrFkTaFVZlPWeqwUyl) - [\[source code\]](https://github.com/ladybug-tools/honeybee-grasshopper-energy/blob/master/honeybee_grasshopper_energy/src//HB%20Filter%20Room%20Result.py)

Filter data collections of energy simulation results using a list of Rooms to which the simulations relate.

This can be used in combination with components like "HB Rooms by Attribute" to get simulation resutls for subset of rooms (eg. all of the offices).

### Inputs

* **data \[Required]**

A list of data collections output from an energy simulation, which will be filtered based on the input \_rooms. 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.

* **rooms \[Required]**

Honeybee Rooms, which will be matched with the input \_data. This can also be an enitre Model.

* **norm**

Boolean to note whether results should be normalized by the Room floor area if the data type of the data\_colections supports it. (Default: False)

* **merge\_zn**

Boolean to note whether the output data should include one data collection per room with the output aligned with input rooms (False) OR duplicate data collections for rooms belonging to the same zone should be merged (True). (Default: False).

### Outputs

* **data**

The input \_data filtered by the connected \_rooms (and optionally normalized by the floor area of each individual room).


---

# 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/filter_room_result.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.