Sun path from Ecotect vs Ladybug

Hi,

I’ll continue the tread here as a discussion and not as a comment. I’ve found some issues that maybe a discussion is more appropriate.

I was curious about the original question and Mostapha’s reply. So i decided to check this more thoroughly.

Started comparing the solar vectors LB calculates against DIVA’s, for Tel Aviv EPW, 10 am. There are differences, even meaningful ones (5-6 degrees in the azimuth, 2-3 degrees for altitude). Then i calculated by myself the numbers and even consulted a couple of websites (NOAA & ESRL and pveducation). The differences with LB remain about the same.

Since my calculations are consistent with those of the websites and Diva’s, and even with those of Ecotect (yes, i have the numbers) i started to thing what could be the problem (it is not daylight savings!!). I’ve found that the input time in LB is, probably, the Solar Time and the others is the local time (or civil time … your clock).

After i use the Solartime as input for receiving the azimuth/altitude the results are more consistent with those of LB (for this specific example, instead of giving 10 i gave 9:38).

I don’t know if LB calculations take into account the Equation of Time, or earth declination, but i think the formula should be revised.

Also the input time is a matter of discussion. People (me) always thing about Time as the one you see in your clock (civil) and not the one according to sun position. As you can see the differences can be very significant.

I’m attaching my checking file, using Tel Aviv EPW at 10 am, for your convenience i concentrated the numbers in excel.

Hope this helps to make this (important) point clear. Sorry for the length.

-A.

SunpathCompare-LB-Diva.gh (66.5 KB)
SunpathCompare-LB-Diva.xlsx (8.85 KB)

Hi Abraham,

Thank you so much for checking this. I’m using Radiance’s sunpath equations and based on my understanding the difference should always be less than a degree. I’ll check this issue in more details this weekend and let everybody know the result.

Best,

Mostapha

Hi again Abraham,

I checked the sunpath and the difference, as you mentioned, is the difference between solar time and local time. As you can see in the image below if you provide longitude and time zone the difference between the result of Ladybug and your results is less then a degree.

Your point about how people input the hour is fair. One option is to remove latitude, longitude, and timeZone inputs from the component and have the weather file as the input so the correction will be always applied. The only concern is in some cases you may want to draw the sunPath for locations that you don’t have the weather file but you have the lat, lng, and time zone. Maybe we can have two sunpath components?

The other option is to add a component to convert solar time <-> local time and then use the solar time as the input. It might be confusing though.

Thanks again and let me know what do you think.

Best,

Mostapha

Hi Mostapha,

I see that now the azimuth difference is a bit more than 1 degree (1.1 to 1.3). The altitude is quite close.

What to do (i think):

First, what NOT to do: 2 sunpaths. It will be quite confusing.

Agree that the conversion Local <–> Solar may be confusing. But sometimes user may want to use each of them(SunlightHours vs Radiation, for instance). I would only add an explanation in the Help of the relevant components about the meaning of using Solar vs Local.

What may lead to the confusion is that the ImportEPW component has only Latitude output. For Local time you need both Longitude and TimeZone. It is a bit of unconvenient to look for these, and then sometimes user may “forget” or miss to input one/both of them into the Sunpath component (as seems to be the case with Stefania … and me ).

The DecomposeLocationData component has the 3 outputs and then the correction works. But this component is not included in the released version (v0.0.35). If so, it will difficult to users to catch what to do (input manually the Longitude and TZ).

So i think the things to do are:

Hope this helps.

-A.

Hi Abraham,

Location input is a great idea. You can either take it from importEPW or create it yourself. Pretty cool! I think I’ll apply it this weekend.

And yes, let’s make a component for local versus solar time. Sounds useful.

Thanks,

Mostapha

Done except the solarTime component. Will work on it later this week…

Looks good!!

-A.

Hi Mostapha,

Any news on this front?

Thanks,

-A.

Hi Mostapha,

Thanks for the hard work. I am trying to do sun hours with ladybug. I also noticed some differences in the results, comparing different sources. I read all the comments in this discussion and saw some new components being used. I have version.0.0.35, therefore, missing the new components from february/july. Are these components already available? If yes, where can I download them?

Thanks a lot,

Alejandra C

Hi Alejandra,

You can download the decompose location component from here and then you should be good to go for sunlight hours study.

Let me know if you need anything else.

Mostapha

Sent you an email!

Hi Mostapha,

Thanks a lot for the quick response. I will try it whenever grasshopper wants to cooperate with me a bit more. ;). I am having problems with GH whenever I try to open it. Very few times it opens inmediately,sometimes it opens, but takes ages and some time it doesnt open at all. I have the version 0.9.0056 (may 16). Can you give me a hint? Is is the version? Any suggestions are appreciated.

Best,

Alejandra

They released a new version last week (090061 i believe) that is supposed to solve this issue.

-A.