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

Importing complex schedules into designbuilder

asked 2020-05-07 07:58:09 -0600

mmatic17 gravatar image

updated 2020-05-09 11:11:02 -0600

Hello, I am working on calibrating a building model in DesignBuilder trough measured temperature data. I was wondering if I could import detailed sub-hourly occupant schedules, that I have been collecting for two months now, into DesingBuilder to increase calibration accuracy. Example of an occupancy schedule for one of the building zones:

Date; Time; Fractions

  • 1/4/2020; 12:00; 0.75
  • 1/4/2020; 12:15; 0.25
  • 1/4/2020; 12:30; 1.0
  • ...

These schedules vary drastically from day to day, and I cannot use Compact Schedules.

Thanks to your replies,

Matic

UPDATE:

@Aaron Boranian. Thank you for your response, I've attempted to import these schedules, following your instructions, but I seem to be missing something. When I run the simulation, DB returns the following error report:image description This is EMS code that I'm trying to run:

Schedule:File,
Office_Occ1,                                                          !- Name
Any Number,                                                           !- ScheduleType
C:\Program Files (x86)\DesignBuilder\EnergyPlus\loads_example.csv,    !- Name of File
2,                                                                    !- Column Number
1,                                                          !- Rows to Skip at Top
8760,                                                       !- Number of Hours of Data
Comma;                                                      !- Column Separator

EnergyManagementSystem:Actuator,
myOffice_Occ1_Override,                             ! Name
Office_Occ1,                                        !- Actuated Component Unique Name
Schedule:File,                                      ! Actuated Component Type
Schedule Value;                                     ! Actuated Component Control Type

Output:Variable,Office_Occ1,Schedule Value,Timestep;

and the schedule, that I am trying to overwrite: image description

Do you have any idea as to why this doesn't work? Thanks for your help.

edit retag flag offensive close merge delete

Comments

@mmatic17 why is it that you cannot use Compact Schedules?

Aaron Boranian gravatar image Aaron Boranian  ( 2020-05-07 08:36:01 -0600 )edit

Well, it is because in Compact schedules I can only define a schedule for typical days (Weekdays, Weekends, and so on), but what I am trying to do is have DesignBuilder read a two-month schedule with individual days, similar to creating and importing a custom epw. file.

mmatic17 gravatar image mmatic17  ( 2020-05-07 09:12:54 -0600 )edit

Ah, so you could do it, but it would just be really tedious. Got it. Does this post about including a partial IDF with a Schedule:File object referencing an external file of your schedule data in combination with EMS scripting answer your question?

Aaron Boranian gravatar image Aaron Boranian  ( 2020-05-07 10:09:02 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
2

answered 2020-05-11 03:44:22 -0600

Nishesh gravatar image

Hello,

Please try the following EMS Code in DB EMS, I have tried to configure it to your schedule name. You need to correct the file path. The intention is to use the external schedule file as sensor and then use the internal schedule as the actuator.

EnergyManagementSystem:Sensor,
   Office_Occ1_Ext,
   ExtOfficeOcc1,
   Schedule Value;

EnergyManagementSystem:Actuator,
   Schedule_Value_Office_Occ1,
   Office_Occ1,
   Schedule:Compact,
   Schedule Value;


Schedule:File,
  ExtOfficeOcc1,!- Name
  Any Number,!- ScheduleType
  C:\...\...\loads_example.csv,!- Name of File
  2,!- Column Number
  1,!- Rows to Skip at Top
  8760,!- Number of Hours of Data
  Comma;!- Column Separator


EnergyManagementSystem:ProgramCallingManager,
   Schedule change,
   BeginTimestepBeforePredictor,
   OfficeOcc1Prog;

EnergyManagementSystem:Program,
   OfficeOcc1Prog,
   ! add program code
  Set t = Office_Occ1_Ext,
  Set Schedule_Value_Office_Occ1 = t,
   ;

In this case you can also Simplify your schedule in DB, instead of the detailed one.

 Schedule:Compact,
    Office_Occ1,
    Any Number,
    Through: 12/31,
    For: AllDays,
    Until: 24:00,  0;
edit flag offensive delete link more

Comments

Thank you so much @Nishesh, for your detailed answer! Your code worked perfectly.

mmatic17 gravatar image mmatic17  ( 2020-05-18 13:52:49 -0600 )edit

Your Answer

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

Add Answer

 

Question Tools

1 follower

Stats

Asked: 2020-05-07 07:58:09 -0600

Seen: 272 times

Last updated: May 11 '20