Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question
1

Some questions about error about schedule

asked 1 year ago

ZRong's avatar

updated 1 year ago

holle everyone, I have just started learning Open Studio and encountered some problems while conducting simulations. The error report is presented below. May I ask what is the reason for this situation? How should it be modified?

Program Version,EnergyPlus, Version 23.1.0-87ed9199d4, YMD=2023.12.25 20:48,
************* Beginning Zone Sizing Calculations
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 07:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 07:45
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 08:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 08:45
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 09:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 17:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 17:45
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 18:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 18:45
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 19:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 1
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 12:45
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 2
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 13:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 2
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 13:45
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 2
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 14:15
**   ~~~   ** Other errors may result. Occurred in Day Schedule=SCHEDULE DAY 2
** Warning ** ProcessScheduleInput: DecodeHHMMField, Invalid "until" field value is not a multiple of the minutes for each timestep: 17:15
**   ~~~   ** Other errors may result. Occurred in Day ...
(more)
Preview: (hide)

1 Answer

Sort by » oldest newest most voted
2

answered 1 year ago

These warnings are raised (Line ~3458) when there is a mismatch between simulation timesteps and sub hourly schedule specifications. In your case, you may be running 6 timesteps per hour (i.e. each timestep == 10 minutes), while "day" schedule entries remain based on 15 minutes. The simplest is to modify the simulation timestep to e.g. 15 (or 5) minutes.

Preview: (hide)
link

Comments

Thank you very much for your explanation. I understand how to do it now

ZRong's avatar ZRong  ( 1 year ago )

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Training Workshops

Careers

Question Tools

Stats

Asked: 1 year ago

Seen: 164 times

Last updated: Dec 26 '23