Ladybug_sunrise/sunset

grasshopper ladybug-legacy
21

Hey Chris,

At this point when I hear about addition of even more functionality to LB/HB I feel excited and always agree on it. However now that I’m trying to get a hang of HB I get frustrated by the sheer amount of components, they don’t even fit when I maximize the window unless I pull the tab all the way down XD.

All I want to say is that I think that at some moment in the future you guys will have to think about integration of multiple components in one and “prettyfication”, so the components are compact and nice looking (without all these underscores, dashes and spaces))

Don’t get me wrong, I love everything you do and understand that at this stage your (team) plugins are at pre-alpha state and need a lot of tuning and cleaning before they start to look something like native GH components.

Sometimes I’m itching to ask you guys:“Hey, what’s with all these blank inputs and outputs?” My guess, is a temporary system that you came up with or limitations of python (doubt), correct me on this one.

In conclusion, add as a new component and maybe integrate it in sunpath with boolean toggle for accuracy later. More is better but not too much XD

22

Hi Tim,

Thanks for posting this comment. Comments like this are much needed. I agree with your point about the extensive number of components in Honeybee and understand how frustrating it can be when you get started with them but at the same time that’s exactly what makes Honeybee as flexible as it is right now.

I’m borrowing a number of slides from Chris’s presentation where he uses the analogy of tool vs toolkit to describe how the vision behind Ladybug + Honeybee is different from other available tools. It’s the nature of the toolkit to have several options for the same problem:

At the same time, I totally agree with your comment that there is a great chance in improving the current “toolkit” by re-evaluating the components and re-structure and/or merge them together to make it more user friendly. We tried once to re-structure the components based on our understan… to address similar issues to what you mentioned but the instant feedback was pretty negative. As a result we reverted back to what we had in place.

Here is exactly where we need suggestions from you and other users. Please consider submitting issues for all the changes that you think can make Ladybug and Honeybee easier to learn and use. Now is the best time as we’re almost re-writing everything.

The underscores are there for a reason. They indicate which inputs are required, optional or required with a default value. Check number 4.

I’m not sure what do you refer to by blank inputs? Do you mean the separators? If that is the case then yes. That’s the limitation that we currently have to group inputs.

Back to the integration of new codes (such as this one) into older components it’s not as easy as it sounds mainly because of the way that the current components are developed. I’m doing my best to get this issue solved for the new development. Also once we have an API users can make their own customized components which will make it easier to keep the official components for Ladybug and Honeybee to essential components.

Mostapha

23

Haha, yeah, this is one way to describe it. Finished Chris’s HB tutorials, kinda got familiarized with the toolset but still have little idea what to do with it. Hopefully (hail!) Hydra will prove useful (pretty sure it will).

Here is exactly where we need suggestions from you and other users. Please consider submitting issues for all the changes that you think can make Ladybug and Honeybee easier to learn and use. Now is the best time as we’re almost re-writing everything.

I dug up my github account, last time I was confused by its application, but I guess it’s ok if I just post issues or comments (still a bit new to it, I’m not so savvy when it comes to social media XD).

The underscores are there for a reason. They indicate which inputs are required, optional or required with a default value.

Can proudly note that I knew that, maybe it is my problem, but I tend to find them ugly or abnormal, something you see in the code, behind the scenes.

I guess Python is case sensitive, but I think I’d express more sympathy to, let’s say all caps for MUSTS, upper case for Important and all lower for the rest.

Again, purely personal preference that, I guess, relies on the hierarchy of the letters (maybe it is something one naturally gets from learning alphabetic languages, because I really miss this feature here in China). Maybe italicize the words or bold them?

Again, just suggestions, I donno anything about Python but I do know that it is not that simple with the code unlike in the Word.

I’m not sure what do you refer to by blank inputs? Do you mean the separators? If that is the case then yes. That’s the limitation that we currently have to group inputs.

Yeah, I see. I wonder if David considered adding something like separators to GH components or ability to rearrange the position of inputs (would be my personal wish))), because so far he left an impression that he considered everything and couldn’t stick to all because of legitimate reasons XD.

Personally and I think many will agree, I would like to see fast and stable work first and “prettification” later. So can’t and don’t want to complain too much XD.

24

Hi Antonello,

Somehow I could not reply your latest post (with “LB sunrise_sunset.gh” attached).

The “isSunUpshit_” filter is awesome! I also like the idea of “IsSunUp” output. I am still a GH newbie, but why not using “IsSunUp” output to filter out your 8760hrs “sun vector” output and eventually feed LB “sun path”? You have all the necessary output to do such calculation.

I am also thinking, in addition to “isSunUpshit_”, an additional filter which could respect solar altitude will also be very helpful. What do you think? purely relying on a fixed hours before/after sunset/sunrise might be rigid.

Regards,

Cheney

25

Hi Cheney

Good news, I have also added the second filter, take a look here:

Now you can combine the two filters.

I have to do a couple of checks, however I think it is already good.

Best

Antonello

26

Hi Antonello,

Awesome! This is a great component and I’ve used it to define solar exposure volume successfully (by taking your output to modify epw weather file).

Hopefully in the near future this component can be directed to sunpath/analysisPeriod_ so that requested sunVectors could be exported.

Thanks for your great help!

Regards , Cheney

27

Hi Cheney,

You can find the last version of ladybug sunrise sunset with the conditional statement for the sun altitude in the updated version of LB.

You can update your LB version directly by using “Ladybug_Update Ladybug”.

Best
Antonello

28

This is awesome. Thank you, Antonello!

29

Hi,

Another nice tool and a good discussion as well!!!

I am sure that there are a lot of people out there, who utilize these wonderful tools in their studies.

Thank you guys all. Keep up the good work.

Best,

Mustafa