I was wondering if it’s possible to have is_leap_year as an input for the LB Analysis Period in the component, with the option to toggle it on or off via a button.
When you see features like this that are fully supported in the SDK but not exposed on an official component, it’s because we thought that exposing it might make the components more complex and therefore make it harder for new users to understand and get started with the components. For advanced users like yourself, you can always just open up a GHPython component and edit the AnalysisPeriod object to be for a leap year if you needed to.
Granted, I understand it can get annoying if you find yourself constantly having to make GHPython components. If this is what is going on, then I concede that adding one more input to the component isn’t really going to overwhelm and new user. So we can add it.
But I’m just trying to explain why every feature of the Ladybug Tools SDK isn’t exposed on a Grasshopper component since that would be pretty overwhelming for new users.
Since I have not heard from anyone yet about the leap year being a consistent pain point, I’m thinking to address this topic by just posting an example GHPython component that takes an analysis period as input and spits out one that is a leap year. Rather than making a change to the official component.
I’ll try to do this tomorrow unless I hear otherwise that it would be really appreciated to make the official change.