I'd love to have the annual hours [0-8760] as a single number instead of the percentages [0-100] in a daylight autonomy for the extra accuracy. I've been modelling an ASE for a LEED project and here we'd want to show how much of a surface has more than 250hours of direct sun annually. The easy way to do this is make a DA with "-ab 0" (0 bounces) and see how much of the occupied time it's being hit. If i have a schedule from 8-18 all days, this is 10 hours a day, or 3650 hours a year.

When my limit is 250hrs and the output is in percentages (and rounded to nearest whole percentage), this means that my threshold is 250/3650*100 = 6.8% . I am only including points that are up to 6%, because the points with 7% are actually exceeding the threshold. This means that my new threshold is 6/100*3650 = 219 hours instead of the original 250.

A workaround is to get the hourly values and count how many exceed a value and return that amount to each point. But this data management is huge and if one has 15000+ points, the data amount is 15000 x 8760 integers, let alone for one floor in my project which takes ages to process.

So the request is: if its not too difficult, output an actual number of hours instead of only a % of the working hours in the daylight autonomy. Or put one extra decimal on the percentage output. This being both in grasshopper and in Rhino

Best Mathias

Tags: Hours, LEED, LEEDv4, Number, of

Views: 179

Reply to This

Replies to This Discussion

Hi Mathias,

I'm not sure if you have to do this in Grasshopper, but DIVA-3.0 reports ASE (via the toolbar) in hours, so there are no rounding issues. You can run a sDA + ASE calculation, and then right-click the Metrics button to load the ASE data specifically.



Reply to Discussion


© 2020   Created by jeff niemasz.   Powered by

Badges  |  Report an Issue  |  Terms of Service