Is it possible to define the runperiod for energyplus in hours, rather than in days, through python ?

answered 2018-06-12 01:32:46 -0500

updated 2018-06-12 01:32:56 -0500

You won't be able to stop in the middle of day out of the box, but that's not a problem, you can always truncate your output during post-processing if you want.

You don't need Python or whatever, but you just need a way to calculate the run period as you want it. You can do that manually, with excel, with python, etc.

eg: You want to run from january 1st, mignight to hour 1700. Ceiling(1700/24) = 71. January 1st offset by 71 days gives you March 13.

RunPeriod, 
  1700 hrs,  !- Name
  1,  !- Begin Month
  1,  !- Begin Day of Month
  3,  !- End Month
  13,  !- End Day of Month
  [...]

edit flag offensive delete link

Comments

Thanks a lot Julien! Actually I wanted to run a real-time simulation in which I get output every hour and based on that hour, I take a decision for the next hour. I might even have to go back by 1 hour, change schedules and run again. How will you suggest me to do that ?

niharkopal ( 2018-06-12 01:38:49 -0500 )edit

@Julien Marrec couldn't you just apply a schedule to Output:Variable for specific days/hours you want to store data in the SQL file.

@niharkopal can you update you question with additional details about the specific interaction you want. It may be possible directly in EnergyPlus, or through EMS.

David Goldwasser ( 2018-06-12 02:35:01 -0500 )edit

Yeah sure you can put a Schedule on the Output:Variable if you don't want it to be in the SQL file, but having 23 hours of extra data shouldn't be a huge deal.

@niharkopal: if want you want to do is simple, EMS might work. Otherwise you'd have to do cosimulation using the BCVTB for eg, but that's even more advanced.