Revision history [back]

This is a whitespace problem. The process I used to debug was to run your unmethours.imf file through energyplus via the CLI energyplus -m -d out/ unmethours.imf (you can use EP-Launch too). The -m flag is used to tell E+ to run EPMacro prior to simulation. Anyways, you will find an eplusout.epidf that is the result of running the EPMacro over the IMF. That one indeed had an empty peak flow rate.

Turns out that #eval[0.0000067517*1] is NOT understood, but #eval[ 0.0000067517 * 1 ] is. So will #eval[0.0000067517 * 1]. Bottom line: the space around the arithmetic operator is mandatory.

Old:

WaterUse:Equipment,
  Level0:Bedroom Water Outlet,    ! - Component name
  ,                               ! - End use sub-category
  #eval[0.0000067517*1],        ! - Peak flow rate (m3/s)
  Hotel_EnsuiteBed_Occ,           ! - Flow rate fraction schedule
  Domestic hot water setpoint temperature: Always 55.00,  ! - Target temperature schedule
  ,                               ! - Hot water supply temperature schedule
  ,                               ! - Cold water supply temperature schedule
  ,                               ! - Zone name
  Off 24/7,                       ! - Sensible fraction schedule
  Off 24/7;                       ! - Latent fraction schedule

New:

WaterUse:Equipment,
  Level0:Bedroom Water Outlet,    ! - Component name
  ,                               ! - End use sub-category
  #eval[0.0000067517 * 1],        ! - Peak flow rate (m3/s)
  Hotel_EnsuiteBed_Occ,           ! - Flow rate fraction schedule
  Domestic hot water setpoint temperature: Always 55.00,  ! - Target temperature schedule
  ,                               ! - Hot water supply temperature schedule
  ,                               ! - Cold water supply temperature schedule
  ,                               ! - Zone name
  Off 24/7,                       ! - Sensible fraction schedule
  Off 24/7;                       ! - Latent fraction schedule