CLIMATE BASED ANALYSIS \ ANNUAL ANALYSIS \ UDI-DA

Hi all,

I am trying to understand which is the logic behind some result we can have using Annual Analysis with Read Rad 1 component.

Annual analysis in honeybee is not done with climate data, it don't need skyfile as input but only the epw weather file (which have the informations of the location). Running the analysis and using Read Rad component I can calculate DA-UDI etc throught Daysim.

BUT reading about Daysim calculation method (http://daysim.ning.com/page/keyword-daylight-autonomy) on the official site I see that DA is obtained "considers all sky conditions throughout the year" and also the definition of DA (http://patternguide.advancedbuildings.net/using-this-guide/analysis...) explains that " a major innovation since in considers geographic location specific weather information on an annual basis".

Also this Paper by Mostapha (http://www.ibpsa.org/proceedings/bs2013/p_2499.pdf page 3133) explaine that "One component calculates typical outputs of an annual climate based daylighting analysis, such as Daylight Autonomy and Daylight Availability".

My questions are: Does Honeybee work using CLIMATE BASED data to calculate UDI-DA? How can it use climate data if it needs only epw weather file? If it doesn't use climate data, which kind of sky it use? Looking at DIVA the annual analysis is named "CLIMATE BASED ANALYSIS": which are the difference between Honeybee Annual Analysis and this last DIVA analysis.

Hoping someone can help me to understand which kinds of results we are getting from this incredible plug-in,

Kind Regards

David

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Leland Curtis on February 1, 2016 at 7:23am

David,

epw files include tmy3 weather data to approximate the local climate at every hour. DA is calculated by measuring how much each unique skypatch contributes to the test point. Once this matrix is computed, Daysim creates a series of unique hourly skies to match each hour in the analysis range. Each hour is based on the epw weather data, so the final result it is climate and location specific. You don't need to input the sky because Daysim creates them automatically. Honeybee and DIVA both use the DAYSIM/Radiance calc engines, so the computation should be identical.

Permalink Reply by David Maimone on February 1, 2016 at 8:31am

Hi Leland,

thanks for your explaination. I am starting to understand which the results mean. My doubts start watching the different kinds of skys, expecially seeing the Climate based sky for grid analysis. Mostapha explained that it can be used only for a specific time in the year because using that sky for a annual analysis means to run 8700 analysis, one for each hour of the year. So, if I understand well, using "readDSHourlyResults" and choosing the same HOY I used for grid analysis with Climate Based Sky, I should have the same result?

Thanks a lot for your time

David

Permalink Reply by Leland Curtis on February 1, 2016 at 9:04am

David,

Daysim DA calcs use Tregenza skies to simplify the calculation process. I think a standard Radiance render or grid point calc uses a smoother Perez sky or CIE standard sky type depending on what sky type you choose. See images below.

A Tregenza sky discretizes the skydome into 145 patches to simplify the calculation process. This skydome approximates the smoother Perez sky shown below. Both the Tregenza 145-patch sky and the Perez sky use climate data to create realistic skies that react to hourly solar and weather data. So there may be some differences between the two runs. Also, every unique run will have some error based on how the calc process works and what your presets are.