Problem: Yearly average sun vector / hour

Hello everyone,

I'm trying to get the average yearly sunVector for a hour a month.

e.g. the average monthly sunVector at 13:00 for 2015 is x °,
sadly i'm not getting the data sorted the way i want it. Becouse

i can't use the partition tool since for diffrent days there are

diffrent amounts of hours of sun. eg 1 januari from 8:00 to 16:00

and 1 februari from 8:00 to 18:00. Wich is making the information

in the list very hard to handle.

So can anyone help me find the average yearly sunvector for every hour

for each month

for example

avg sunvector for the whole of januari
1:00, avg sunvector (the avareages of all sunvectors at 1:00 in januari)
2:00 , avg sunvector
3:00 , avg sunvector
untill
24:00, sunvector temp
avg for the whole of februari
1:00, avg sunvector
2:00 , avg sunvector (the avareages of all sunvectors at 2:00 in februari)
3:00 , avg sunvector
untill
24:00, avg sunvector

and this for every month of the year.

I want to be able to optimize a surface wich is divided into multiple meshes (so for each part of the surface i want to relate it's normal to the vector of the sun). I'm not so much interested in the visualisations. I hope this is atleast abit understandable.

ps: this question is atleast abit simular to my previous question on wich i got some really good help, wich i'm very gratefull for.

Thanks in advance!

Included: gh file + the epw file i'm using

Attachments:

NLD_Amsterdam.062400_IWEC.epw, 1.5 MB
LADYBUG AVG monthly,hourly data,solar vector.gh, 364 KB

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Abraham Yezioro on December 9, 2015 at 8:08am

You should look at this discussion.

-A.

Permalink Reply by Mostapha Sadeghipour Roudsari on December 9, 2015 at 8:43am

This discussion should also help for separating data.

Permalink Reply by Leland Curtis on December 9, 2015 at 8:17am

I think you might be making the problem more complicated than it needs to be. You could simply take the 15th of each month. Even in February, this vector would be very close to the "average." In any case, the average vector may imply a false sense of accuracy. Optimizing to an average vector means you are optimizing to a vector that is between 0 and 15 days off from the real condition. In a way, that benchmark is arbitrary. Might as well choose a vector that is easy gather.

Permalink Reply by byron mardas on December 9, 2015 at 9:21am

My first thought was close to what Leland Curtis suggested. In any case if for some reason you want to continue with your approach, I tried to make a simple file to help your task.

I hope it is not too messy inside.

Let me know if it worked.

Attachments: