Difference between HB Annual Loads and HB Model to OSM

Hi everyone,
I’m new to Grasshopper and Honeybee.

I’m currently running a façade energy simulation, and my goal is to determine the best geometry to reduce a building’s energy consumption. To do this, I’m analyzing the cooling and heating outputs from EnergyPlus.

I’ve run the simulation using both HB Annual Loads and HB Model to OSM, with exactly the same simulation parameters in both components, but I’m getting very different results. Can someone please enlighten me?

Here are my results summarized in a table:

This is a bit frustrating because, depending on which component I use, the optimized façade consumes either more or less energy than the reference façade.

Here is my Grasshopper file and a picture of it :

Somehow I cannot put my grasshopper file bc I’m new so here is a drive where my grasshopper file is :
https://drive.google.com/drive/folders/1j3-lZ8j9874mxbIEqDcGoPYP2NVTVwyQ?usp=drive_link

Here is also a picture of the parameters I have used for the simulation :

You should compare both IDF files with WinMerge and see what changes. Alternatively you can also use EPCompare.

Some time ago I had this similar issue. I think the HB Annual loads don’t take into account latent loads, you have to specify it. (I’m talking from memory, I might be wrong)

Before anything, I suggest you check a few things about yur odel:

  1. Scale: Seems to be you built it in cm instead of meters [as should be].
  2. There are no windows at all.
  3. The are open areas on the facade [open air]

I’m not sure these issues explain or correct the results, but seems to be fair to start with a “correct” built model.

-A.

Hi everyone, and thank you all for your answers.
I had a busy week, so it took me a bit of time to reply. Here’s an update:

Thanks again for your answers

@Kim_Phan here is a post that may answer your question Energy balance difference using Annual load and HB model to osm method
best
-trevor

Hi @TrevorFedyna, and thanks for the post redirection.

I read the post and it made me realize that some parts of my façade were being counted as floor surfaces because I am working with unusual façade geometries. The green areas in the picture below were considered floor because they were very flat, which ended up affecting the floor_area and therefore the area normalized energy outputs.
So be careful when designing an unconventional façade !

Aside from this, I still have a difference between HB Model to OSM and HB Annual Load, even though my model is really simple, it’s basically just a shoebox. So the rest of the post doesn’t solve my issue because I only have one room, so I don’t have the exlude_floor_area or multiplier issue. I think the difference comes from the way they each interpret the design days data.

@Kim_Phan, I am commenting a year later, so I hope that you resolved it already.
Otherwise, I had the same issue and after some trial errors, I found why the outputs HB Annual Loads is different to the HB Model to OSM.

  1. Timestep per Hour: The Annual Loads component uses a default of 1 timestep per hour. In contrast, the Model to OSM component defaults to a finer 6 timesteps per hour.
  2. Solar Distribution Calculations: The Annual Loads component uses a simpler FullExterior solar distribution method, while the Model to OSM component uses the more detailed FullExteriorWithReflections by default.
  3. Load Type: The ‘Annual Loads’ component calculate Sensible only whereas the ‘Model to OSM’ component’ calculates All as default.

See attached screenshot of inputs. You should have similar annual cooling load kWh/m2 with these changes, assuming your model is simple enough with similar normalised areas.

With regards to sizing with the difference between HB Peak Loads component vs HB Read HVAC Sizing component, no idea why they are different. From another thread in another post, it seems that the latter component does not consider solar load in the sizing, which is strange.