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

Revision history [back]

As you mention, the Load Profile object wants an hourly load schedule [in W], a peak flow rate, and an hourly normalized flow rate schedule [0-1]. Positive values for the load indicate a heating load, and negative values indicate a cooling load. The flow rate schedule is a fractional schedule of the design flow rate entered. It's possible to pull hourly flow rates from the original model and use them in the profile schedule, however I have found greater success (and less headache) using the hourly load schedule to create a normalized hourly flow schedule by calculating the flow rate from the hourly load assuming a constant delta-T.

Unfortunately OpenStudio does not support the Schedule:File object that is native in EnergyPlus, so the only way to create a custom 8760 hourly schedule in OpenStudio is to create one manually in the interface (grueling) or use a measure to create one automatically.

The post HERE contains the syntax needed to execute this as a ruby script. I used this just the other day to build a measure that will create a custom hourly OpenStudio schedule from the values in a CSV excel file. It's not pretty but it does create a custom 'Fixed Interval' schedule with the interval set to hourly and unique values for each hour.

If you are savvy enough to turn the snippets from the post above into a measure, I would suggest trying that. If not, I may be able to share the measure I created but buyer beware (it's a little rough around the edges for external use).

As you mention, the Load Profile LoadProfile:Plant object wants an hourly load schedule [in W], a peak flow rate, and an hourly normalized flow rate schedule [0-1]. Positive values for the load indicate a heating load, and negative values indicate a cooling load. The flow rate schedule is a fractional schedule of the design flow rate entered. It's possible to pull hourly flow rates from the original model and use them in the profile schedule, however I have found greater success (and less headache) using the hourly load schedule to create a normalized hourly flow schedule by calculating the flow rate from the hourly load assuming a constant delta-T.

Unfortunately OpenStudio does not support the Schedule:File object that is native in EnergyPlus, so the only way to create a custom 8760 hourly schedule in OpenStudio is to create one manually in the interface (grueling) or use a measure to create one automatically.

The post HERE contains the syntax needed to execute this as a ruby script. I used this just the other day to build a measure that will create a custom hourly OpenStudio schedule from the values in a CSV excel file. It's not pretty but it does create a custom 'Fixed Interval' schedule with the interval set to hourly and unique values for each hour.

If you are savvy enough to turn the snippets from the post above into a measure, I would suggest trying that. If not, I may be able to share the measure I created but buyer beware (it's a little rough around the edges for external use).

As you mention, the LoadProfile:Plant object wants an hourly load schedule [in W], a peak flow rate, and an hourly normalized flow rate schedule [0-1]. Positive values for the load indicate a heating load, and negative values indicate a cooling load. The flow rate schedule is a fractional schedule of the design flow rate entered. It's possible to pull hourly flow rates from the original model and use them in the profile schedule, however I have found greater success (and less headache) using the hourly load schedule to create a normalized hourly flow schedule by calculating the flow rate from the hourly load assuming a constant delta-T.

Unfortunately OpenStudio does not support the Schedule:File object that is native in EnergyPlus, so the only way to create a custom 8760 hourly schedule in OpenStudio is to create one manually in the interface (grueling) or use a measure to create one automatically.

The post HERE contains the syntax needed to execute this as a ruby script. I used repurposed this just the other day to build a measure that will create a custom hourly OpenStudio schedule from the values in a CSV excel file. It's not pretty but it does create a custom 'Fixed Interval' schedule with the interval set to hourly and unique values for each hour.

If you are savvy enough to turn the snippets from the post above into a measure, I would suggest trying that. If not, I may be able to share the measure I created but buyer beware (it's a little rough around the edges for external use).