Why is Site:WaterMainsTemperature Correlation from Weather File locked on one temperature for all times and locations?
I'm trying to use a Site:WaterMainsTemperature object to get a Correlation Site Water Mains Temperature output variable. Because I want my model to be flexible across sites, I set the Calculation field to CorrelationFromWeatherFile. When I run a test, however, I see that the output is locked at 3.33 degC. This value appears for every timestep and for disparate locations; Phoenix and Chicago TMY3 files return the same value, 3.33 degC. I even tried Chicago TMY2 in case it was some sort of epw file version issue, but still it returned 3.33 degC.
If I switch to the Correlation method and throw in some input values, I see the water mains temperature vary as expected, with a different temperature each day and different temperatures between sites.
The HTML table gives me a possible hint; the numbers it apparently calculates from the weather file are very small and again are the same value for Phoenix and Chicago.
I haven't found any other questions about this except for this question regarding OpenStudio not having Correlation from Weather, but I'm working directly with EnergyPlus IDF editor, not OpenStudio.
Has anyone else had this issue? Is it a bug or am I just missing an object input somewhere to make this work correctly?
Comments
@nigusse I think you added this to EnergyPlus. Any idea?
I've had this issue, too! No way to tell e+ to use the following object to inform the cold water supply temperature at source-side inlet node for water heater within plant loop: Site:WaterMainsTemperature, CorrelationFromWeatherFile; Within the WaterHeater:Stratified section (9.5.0), the following is indicated: Field: Cold Water Supply Temperature Schedule Name ... If blank, water temperatures are calculated as above. This field is for stand-alone operation only. If there are node connections, this field is not used. I can find no indication of how to assign to source-side node.