Calculating LEED ASE


I have a request that many others may enjoy in HoneyBee.

I’ve been trying to create a module to calculate LEEDv4 ASE without luck.

It was very inspired by the readAnnualResultsI block.

I want it to look at results from an annualDaylightSimulation made with 0 bounces on several rooms.

Currently I can use the readAnnualResultsI with a DAIllumThreshold value of >1000 lux but output is in integer percentage-number instead of absolute yearly hours (i can multiply with 8760/100, but then rounding has been done).

Also it does not give me a shading schedule which should be activated/deactivated for hours with more or less than 2% of the points with >1000lux.

It should output the amount annual hours above 1000 lux for each point in the same tree structure as the input points. (i have a tree with one list per simulated room)

Ideally it would also output a list of 8760 (or length of whatever input schedule is used) true/false for values, each hour, or freshly generated schedule files (one for each list of inputted points).

Currently i do this statistics with regular GH components on every hourly values, but with, lets say, 1000 analysis points, and 8760 hours (8,760,000 float values), grasshopper starts stalling.

I was hoping it was possible through scripting, as this way (like the readAnnualResultsI) it does not slow down the GH UI once finished running.

My method is currently to use these freshly generated schedules do extract values from two different daylightAutonomies in order to create a sDA, which is needed for the LEEDv4 simulation. Currently my workflow works, but only on around 200-500 points, while some of our floor plans require more than 5000.

Hope my request makes sense - and let me know if you need any inputs. Hopefully we can make a fast way of implementing new LEED required simulations.


Mathias Sønderskov


Hi Mathias,

We have been working on adding this functionality to Honeybee for a while. You can read about it here , here, here and if you are familiar with rcontrib in Radiance, here.

There are essentially two aspects to implementing ASE:

  1. First, as you pointed out has to do with performance and being able to analyze larger number of illuminance grid points than currently possible.

  2. Second, which is probably more critical and the main bottleneck as far as implementation goes, has to do with the accuracy of Daysim. Just making the current Daysim engine work with ASE will result in erroneous simulations as Daysim overestimates the size of the sun (as compared to reality) by several orders of magnitude.

The implementation of ASE that we are working on currently will address both of the above issues. It should hopefully be available in this library: sometime next month and will get ported over to Honeybee inside grasshopper after that.



May I ask if LEED v.4 report is now available for Honeybee now?




Does anyone have any updates about this? I appreciate any inputs :slight_smile:



Hi Ladan,

As you are probably aware, the element of LEED v.4 daylight calculations that has been missing in Honeybee is the possibility to calculate ASE. I had mentioned a couple of months ago that we were working on implementing that script. Most of the development has already been finished and we are currently testing the scripts inside Grasshopper. We will probably have an official announcement from Mostapha and Chris sometime early next year.

This development has been so long in the making because we had to rewrite a significant part of the back-end code.


That is great news! thanks for the update, I am looking forward to this new feature in HB.


Hi Sarith,

Can I ask how is your grasshopper recipe going which can provide the algorithm for ASE calculation? Has it been officially released?