LadyBug Analysis Period Night Only

Replies to This Discussion

Permalink Reply by Devang Chauhan on December 13, 2016 at 12:02pm

Hi Filippo,

You can do the following;

Change the analysis period for Summer as per your climate.

-Devang

Permalink Reply by Filippo on December 14, 2016 at 1:17am

thank you Devang,

I tried the analysis period but looking at the results I saw that doing what you proposed the analised period is from midnght of june first to 8 am of septemper 31st..

what i need is analyse only the wind that blows at night during the summer period..

i don't want to calculate in the graph the wind blowing during the day when windows will be shut..

someone can help with it?

thanks!

filippo 

Permalink Reply by Chris Mackey on December 20, 2016 at 7:49pm

Filippo,

Devang's script is getting rid of all hours when the sun is not up (directNormalRadiation = 0.0) so he is showing you a wind rose for the summer night time.  If you need a wind rose for a specific analysis period at night, you can always use Julia T's awesome method here:

http://www.grasshopper3d.com/group/ladybug/forum/topic/show?id=2985...

You will probably want to create a list of domains over the whole summer to get all of the hours that you want.

-Chris

Permalink Reply by Abraham Yezioro on December 25, 2016 at 6:41am

Hi,

Just being curious, i tried to implement Julia's method (under Chris's suggestion), but i get, unfortunately an error with the windRose component.

I managed to select/extract the desired hours data. Plugged them into the windSpeed/Direction and then i get the following error:

Runtime error (IndexOutOfRangeException): index out of range: 2899
Traceback:
  line 198, in unpackPatternList, "<string>"
  line 568, in main, "<string>"
  line 1131, in script

From what i understand i can't input the data as a selected list. I also understand that the list must be annual.

In short, Devang method is fine, as long as you want the analysis for "dark" hours. But if i want a selected range of hours it fits less.

I can't see how to implement Julia's method.

I probably missed something here ...

Thanks,

-A.

Attachments:

• 04_WindAnalysis - NightHours.gh, 472 KB

Permalink Reply by Devang Chauhan on December 25, 2016 at 6:52am

Hi Abraham,

I will look into this one.

-Devang

Permalink Reply by Devang Chauhan on December 25, 2016 at 8:59am

Hi Abraham,

Your implementation of Julia's method as per Chris's suggestion is great. In the attached file, I propose we use the list of HOY you created instead of the typical analysis period. I have made some preliminary modifications to the component to do that. What I have done is a very temporary fix. I believe, we should think about building this capability to take such a list in this WindRose component.

-Devang

Attachments:

• 04_WindAnalysisNightHours_Edit.gh, 465 KB

Permalink Reply by Abraham Yezioro on December 25, 2016 at 12:01pm

Hi Devang,

Thanks for taking this one. Looking forward for the results.

I tried inputting the entwined data and the whole year analysis period, but the results were different than yours. So i decided to wait for your development instead of trying more things.

Best,

-A.

Permalink Reply by Chris Mackey on December 30, 2016 at 3:15pm

Abraham and Devang,

I had forgotten that the wind rose does not accept data without a Ladybug header on it (nor do any of the other annualHourlyData components).  For these cases, you are right that Julia T's method will not work.  I'll offer one very hacky script that will work for all of these cases:

I agree that it would be better to integrate this into the components somehow.  I could see you hourList input working well, Devang.  We'd just need several checks to make it compatible with the other inputs like the analysisPeriod.

-Chris

Permalink Reply by Chris Mackey on December 30, 2016 at 3:16pm

Forgot to upload the GH file

Attachments:

• 04_WindAnalysisNightHours_CWMEdit.gh, 441 KB

Permalink Reply by Abraham Yezioro on February 1, 2017 at 11:27am

Hi,

Just wanted to summarize the solutions. I'm proposing a new one.

The options are:

Devang's: Not flexible. Allows only to filter cases where radiation is 0. Doesn't allow free hours selection.

Chris's: Flexible. Allows any set of hours. Uses many GH components. The title doesn't show the real analysis period. Different results from Devang's.

Abraham's: Flexible. Allows any set of hours. Similar to Chris's, but i wrote a small code that cleans the undesired hours. Basically i set a flag for the desired hours of the year. So they can be mapped with the 3D Chart component. Same results as Chris's.

Don't know how to fix the title issue. Can be nice to have this solved. If any of you have ideas how to do it, will be great.

Maybe this can serve as a basis for a LB component, maybe the analysisPeriod?

-A.

Attachments:

• 04_WindAnalysis - NightHoursVersions.gh, 501 KB

Permalink Reply by Devang Chauhan on February 1, 2017 at 12:21pm

Hi Abraham,

Are you referring to the header for flag values? Did you check LB_Create Leader component?

-Devang

Permalink Reply by Abraham Yezioro on February 1, 2017 at 9:24pm

Hi Devang,

I suppose you refer to the LB_CreateHeader? If so, is not that. What i meant is that the title of the WindRose doesn't fit/correspond to the "real" analysis period intended.

-A.

• ‹ Previous
• 1
• 2
• Next ›
• Page