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

Revision history [back]

The warnings (not errors) you're getting are not unusual. A few basic schedules do get added when OpenStudio forward translates your model to EnergyPlus. You can check for these by comparing in.osm vs in.idf files under the run folder (using a text editor). Slightly annoying (we'd all like to see 0 warnings), yet usually not an issue.

Unless this has changed with the latest release, OpenStudio Application users cannot set ground temperatures (see here). That link provides a few suggestions to counter this limitation (including switching to KIVA), but you may be able to simply copy/paste something like the following directly in your OSM:

OS:Site:GroundTemperature:BuildingSurface,
  {f904478f-7d4c-4665-bc6f-f6798a5ea52f}, !- Handle
  13.02,                                  !- January Ground Temperature {C}
  12.94,                                  !- February Ground Temperature {C}
  12.92,                                  !- March Ground Temperature {C}
  18.03,                                  !- April Ground Temperature {C}
  22.41,                                  !- May Ground Temperature {C}
  26.33,                                  !- June Ground Temperature {C}
  26.64,                                  !- July Ground Temperature {C}
  25.84,                                  !- August Ground Temperature {C}
  23.47,                                  !- September Ground Temperature {C}
  18.98,                                  !- October Ground Temperature {C}
  13.86,                                  !- November Ground Temperature {C}
  13.19;                                  !- December Ground Temperature {C}

Adjust the temperatures based on your EPW.

It's usually discouraged to add OpenStudio objects with unique handles this way, but Site objects are pretty high up the model object hierarchy. Still, maybe safer to first try on a copy of the model.