Using Local Weather Data for specified range with the Buildings Model in Modelica Buildings Library

[Shalom6624]

Hello, I am trying to run a simulation similar to the Buildings.ThermalZones.EnergyPlus_9_6_0.Examples.SingleFamilyHouse.AirHeating model in the Modelica Buildings Library. But I wanted to use my own weather data. I have generated my EPW weather file and converted to a .mos file and successfully run the simulation. However, on trying to rerun the simulation using just a month data, I got the error below:

13219200.000 AirHeating_testing_BEEL.building: Error from EnergyPlus: GetNextEnvironment: Runperiod [mm/dd] (Start=01/01,End=12/31) requested not within Data Period(s) from Weather File
13219200.000 AirHeating_testing_BEEL.building: Error from EnergyPlus: Weather Data Period (Start=06/01/,End=06/30/)
13219200.000 AirHeating_testing_BEEL.building: Fatal from EnergyPlus: GetNextEnvironment: Program terminates due to preceding condition.

Meanwhile, I separately ran the same one month weather file using the Buildings.BoundaryConditions.WeatherData.ReaderTMY3 and it worked successfully. I also specified the runperiod in my IDF file and tested it by running a standalone simulation with EnergyPlus and it also ran successfully. So, I am unclear what is meant by the error that Runperiod [mm/dd] (Start=01/01,End=12/31) requested not within Data Period(s) from Weather File considering that I already specified my runperiod in my IDF and confirmed that it works. WOuld gladly appreciate any help on how to fix this as the weather data I need for my work is 2024 data which I cannot get annual readings for at the moment. Thanks

[mwetter]

@Shalom6624 : In Spawn, the RunPeriod entry of the idf file is ignored.
Please make sure your weather file has the same structure as the original weather data file. If the problem persists, perhaps @kbenne has some insight as this error is triggered in the EnergyPlus source code.

[Shalom6624]

@Shalom6624 : In Spawn, the RunPeriod entry of the idf file is ignored. Please make sure your weather file has the same structure as the original weather data file. If the problem persists, perhaps @kbenne has some insight as this error is triggered in the EnergyPlus source code.

Dear Michael,

Thank you very much for your kind feedback. I have rechecked the .mos file to confirm by comparing with "C:\Users\Buildings 10.0.0\Resources\Data\BoundaryConditions\WeatherData\Validation\DecemberToJanuary.mos". Though by running mine with the ReaderTMY3 model, it ran successfully and also ran successfully in EnergyPlus, I noticed my .mos file started from 0.0 as shown below

While the DecemberToJanuary.mos started from the time seconds corresponding to the day of the year as shown below

So, I manually adjusted my start time to correspond to June 1st, 2024, 00:59, as well as 01:00 as shown below,

but this did not fix the issue and still gave same error from the Spawn simulation. It further caused the standalone simulation with ReaderTMY3 to fail.

[mwetter]

For Spawn, it looks like weather files must start at 0.
@kbenne : Can you confirm, and if so, is this a limitation that could be removed?