Problem with leap year (2024) simulation data export – February 29th missing

[Daniela Silva]

When extracting simulation results in PV*SOL using measured load diagrams from 2024, the exported files are identified as belonging to 2024, but February 29th is not included.

As a result, when moving from February 28th to March 1st, there is a jump of two weekdays instead of one, causing a temporal misalignment in the exported data.

Is there a way to work around this issue so that the exported results remain time-consistent?

[hotline_oh]

Dear Daniela Silva,

Thank you for your inquiry.

The software always simulates a "standard year," which consists of 365 days. Therefore, 366 days are not required for the load profile. When importing a load profile from a leap year, it is automatically shortened by one day.

If you absolutely want the leap year's annual value to appear, you can overwrite the annual electricity demand accordingly in the Load Profiles/Individual Appliances window after importing. However, this isn't entirely accurate, because it would then be distributed over 365 days instead of 366.

[Daniela Silva]

I think you didn't understand my question. The pvsol is skipping 1 day of the week, for example in 2024, the 29th was a Thursday, so when the data is exported, the 28th (Wednesday) goes directly to March 1st (Friday). This interferes with all days from March 1st onwards, placing the weekends on Fridays and Saturdays. Is there any way around this?

[hotline_oh]

Dear Daniela Silva,

Thank you for your inquiry.

While the software doesn't output simulation results per weekday (only per day, per month, or per year), we understand that excluding February 29th can be detrimental. A workaround would be to remove the December 31st load profile data and import the load profile for 365 days of 2024 (from Monday, January 1st to Monday, December 30th). However, since the software expects 366 days for 2024, select January 1st, 2018, as the start date; this year runs from Monday, January 1st to Monday, December 31st.

[Daniela Silva]

Hello,

This cannot be done.

Below is an image showing an error with pvsol.

How can we solve this?

[hotline_oh]

Dear Daniela Silva,

Thank you for your inquiry.

As mentioned previously, select January 1, 2018 as the start date; the year runs from Monday, January 1, to Monday, December 31:

[Daniela Silva]

Hello,

So we have to eliminate December 31st, right?

2018 has 365 days and 2024 has 366..

[hotline_oh]

Dear Daniela Silva,

Thank you for your inquiry.

Yes, that's correct.

On 10/21/2025 at 11:08 AM, hotline_oh said:

While the software doesn't output simulation results per weekday (only per day, per month, or per year), we understand that excluding February 29th can be detrimental. A workaround would be to remove the December 31st load profile data and import the load profile for 365 days of 2024 (from Monday, January 1st to Monday, December 30th). However, since the software expects 366 days for 2024, select January 1st, 2018, as the start date; this year runs from Monday, January 1st to Monday, December 31st.