# HB bug - Incorrect start day when run period is specified

**URL:** <https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651>\
**Category:** honeybee\
**Tags:** energyplus, honeybee, analysis-period, idf\
**Created:** [November 27, 2025, 11:32am UTC](https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651 "2025-11-27T11:32:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MatteoMerli](https://discourse.ladybug.tools/user_avatar/discourse.ladybug.tools/matteomerli/32/31937_2.png) [@MatteoMerli](https://discourse.ladybug.tools/u/MatteoMerli)\
**Post date:** [November 27, 2025, 11:32am UTC](https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651/1 "2025-11-27T11:32:18Z")

</div>

When setting both _run\_period_ and _start\_dow_ in the HB Simulation Parameter, the latter isn’t written correctly into the IDF. It seems Honeybee assumes the Start Day refers to January, picks a reference year that matches that condition, and then shifts the Start Day based on that year. But EnergyPlus wants the Start Day of the selected Run Period, not of the year.

For example here I chose May as Run Period and Thursday as Start Day (as in 2025). In the IDF I get year 2009 and Start Day = Friday, because 1 May 2009 was a Friday (and 1 January 2009 was a Thursday). The simulation confirms the issue: it starts on Friday (occupied) then weekend (unoccupied), rather than starting on the Thursday.

 ![image](https://discourse.ladybug.tools/uploads/default/original/3X/5/a/5a8181b78c8269625f935e9dfdcd47b874b5e5f0.jpeg)

```auto
RunPeriod,
  Run Period 1, !- Name
  5, !- Begin Month
  1, !- Begin Day of Month
  2009, !- Begin Year
  5, !- End Month
  31, !- End Day of Month
  2009, !- End Year
  Friday, !- Day of Week for Start Day
  No, !- Use Weather File Holidays and Special Days
  No, !- Use Weather File Daylight Saving Period
  No, !- Apply Weekend Holiday Rule
  Yes, !- Use Weather File Rain Indicators
  Yes; !- Use Weather File Snow Indicators

```

 ![Capture](https://discourse.ladybug.tools/uploads/default/original/3X/9/d/9d79191c5cc529408228bf2c5a867579b41b2a86.jpeg)

It looks like a bug to me, but I’m not sure if it’s already fixed in a newer LBT version (I’m on 1.8).

---

<div class="post-metadata">

**Author:** ![bianca.fox](https://discourse.ladybug.tools/user_avatar/discourse.ladybug.tools/bianca.fox/32/40694_2.png) [@bianca.fox](https://discourse.ladybug.tools/u/bianca.fox)\
**Post date:** [April 15, 2026, 10:07am UTC](https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651/2 "2026-04-15T10:07:48Z")

</div>

Hello,

I just wanted to flag that EnergyPlus v25.1 seems to handle the run period differently than in previous versions.

Whereas previously the _start\_dow_ input in the HB simulation parameters would set the start day of the simulation, the most important parameter now appears to be the year. See the following warning message in the error file :

> **Warning** RunPeriod: object=RUN PERIOD 1, start weekday (THURSDAY) does not match the start year (2006), corrected to SUNDAY.

As a result, the start day specified in the `sim_par` component is no longer written to the IDF. Even if it is manually changed in the IDF, EnergyPlus will override it based on the selected year.

I recommend explicitly controlling the RunPeriod via an eppy script to assign the desired simulation year. The start day will then be automatically adjusted.

![image](https://discourse.ladybug.tools/uploads/default/original/3X/2/d/2dabf9e228d306f67615256f23c329b6eaa2493c.png)

 ![image2](https://discourse.ladybug.tools/uploads/default/original/3X/f/f/ffca3a70b7b1dd994bb610890aa1a74e63470da8.png)

@chris

---

<div class="post-metadata">

**Author:** ![chris](https://discourse.ladybug.tools/user_avatar/discourse.ladybug.tools/chris/32/10179_2.png) [@chris](https://discourse.ladybug.tools/u/chris)\
**Post date:** [April 17, 2026, 10:54pm UTC](https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651/3 "2026-04-17T22:54:12Z")

</div>

Thank you both for bringing this to my attention. It seems that I will have to make some changes to the source code and I’ll try to do this next week.

I’m sure that they have their reasons but, man, I wish the E+ developers would just leave the run period object alone. They keep making these big changes to address edge cases while the rest of us who are just trying to run simulations for a year or a part of a year have to suffer.

---

<div class="post-metadata">

**Author:** ![chris](https://discourse.ladybug.tools/user_avatar/discourse.ladybug.tools/chris/32/10179_2.png) [@chris](https://discourse.ladybug.tools/u/chris)\
**Post date:** [April 21, 2026, 4:00pm UTC](https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651/4 "2026-04-21T16:00:00Z")

</div>

@bianca.fox and @MatteoMerli ,

Thanks again for reporting this and looking into the root cause of the issue. I just merged a fix into the code base, which is now available via the [LB Versioner](https://docs.ladybug.tools/ladybug-primer/components/5_version/versioner):

> <https://github.com/ladybug-tools/honeybee-openstudio/pull/65>

Essentially, we work around the new limitation by looping over the last decade until we find a year where the start day of the run period matches the start day of the week. Or, in the case of a leap year, we loop over the last century.

I tested and this seems to produce the expected behavior in the E+ simulation.

Thanks again for bringing this up.

---

<div class="post-metadata">

**Author:** ![bianca.fox](https://discourse.ladybug.tools/user_avatar/discourse.ladybug.tools/bianca.fox/32/40694_2.png) [@bianca.fox](https://discourse.ladybug.tools/u/bianca.fox)\
**Post date:** [April 21, 2026, 5:40pm UTC](https://discourse.ladybug.tools/t/hb-bug-incorrect-start-day-when-run-period-is-specified/39651/5 "2026-04-21T17:40:25Z")

</div>

Amazing, thanks @chris  
We’ve tried running it both with and without a run period and it seems to work perfectly.
