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:
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.
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.
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?
There ave been many request/questions on the forum regarding how to render only a group of hours (night hours, or otherwise) without taking those in between.
The HOY input can be a good way to implement. I think we can do it, and if it works smoothly i don’t think Mostapha or Chris will oppose.
The title for such cases should say something like “output for user selected hours”, or something similar, since with the HOY input i can give random hours. It will be difficult to write in the title all of those.
Hey gang! Just checking in to see if there has been any progress on integrating this into the Ladybug tools. Also, I assume these methods only work for Velocities and Directions, and I would not be able to add temperature to the scenario and have it be successful. Is that correct? We are trying to figure out the best times of day for natural and night ventilation of our building, but need data during time frames that occur after hours, like from 6:00 pm to 6:00 am. I was wondering if there’s a way to run two data collections, one from 6 pm to 12 pm, then run one from 12 pm to 6 am and somehow combine the data into a coherent single wind rose? I am a very new user and have almost no idea what I’m doing or saying lol