Set up a simple sun path to look at Noon for every Month on the 15th.
1 hour, 1 day, 12 months
Ends up giving a range of 335 hours when it should be giving only 12. Not sure what’s going on here.
Set up a simple sun path to look at Noon for every Month on the 15th.
1 hour, 1 day, 12 months
Ends up giving a range of 335 hours when it should be giving only 12. Not sure what’s going on here.
Sorry for the very late response here, @cflynn29 and @Erikbeeren .
I was busy over the last month getting a lot of things together for the stable release. I’ll confirm that there is no bug here and this is just how the date range of Analysis Periods have been designed throughout the plugin. The dates are interpreted as exact continuous dates from one to another and the hour range is interpreted as something to be applied every day within that range.
In a lot of cases, this continuous date range is what people want. For example, I couldn’t imagine the confusion if we took the “typical hot/cold weeks” from Stat files and they happened to start and end in different months. You’d get these bits and pieces of each month that add up to more than one week.
But this behavior obviously does not cover all cases. If you want to get HOYs for the following conditions:
… the correct component to use is the LB Calculate HOY component and you would use it like so: