Revision history [back]

LEED asks you how many warnings you have, and you'll have to provide a supplemental narrative describing the warning messages and why they do not adversely affect the results of the energy model.

Without looking at your idf file, I'm not sure what's causing this specific error. Nevertheless, a few things to mention:

• I wouldn't necessarily be worried if it doesn't converge for only one timestep.
• I would try running the simulation will a smaller time step, say 6 per hour instead of 1. If your model is complex and you're afraid of computing time, try for just January

• It seems that while the supply inlet temperatures are indeed oscillating, they are not wild. Here's one extract:

  * ~~~ * Node named VAV2-37 SUPPLY INLET shows oscillating temperatures across iterations with a repeated value of 15.419107

  * ~~~ * Node named VAV2-37 SUPPLY INLET temperature [C] iteration history trace (most recent first): 15.419107,15.416305,15.426937,15.419107,15.416305,15.426937,15.419107,15.416305,15.426937,15.419107,

That being said, did you mean to have some apparently in cooling mode and others in heating mode? (You have 24 VAVs delivering air below 13°C/55°F, 21 VAVs delivering over 24/75°F, and 6 VAVs around 16°F/61°F)

• Something useful is to request an output at "Detailed" (= HVAC variable timesteps) reporting frequency of the supply inlet temperatures, and then plot it to see what's going on (I suggest using SQLite output and using the ResultsViewer from Openstudio)

• If after all of the above you're not satisfied, try the helpdesk.

LEED asks you how many warnings you have, and you'll have to provide a supplemental narrative describing the warning messages and why they do not adversely affect the results of the energy model.

Without looking at your idf file, I'm not sure what's causing this specific error. Nevertheless, a few things to mention:

• I wouldn't necessarily be worried if it doesn't converge for only one timestep.
• I would try running the simulation will with a smaller time step, say 6 per hour instead of 1. If your model is complex and you're afraid of computing time, try for just January

• It seems that while the supply inlet temperatures are indeed oscillating, they are not wild. Here's one extract:

  * ~~~ * Node named VAV2-37 SUPPLY INLET shows oscillating temperatures across iterations with a repeated value of 15.419107

  * ~~~ * Node named VAV2-37 SUPPLY INLET temperature [C] iteration history trace (most recent first): 15.419107,15.416305,15.426937,15.419107,15.416305,15.426937,15.419107,15.416305,15.426937,15.419107,

That being said, did you mean to have some apparently in cooling mode and others in heating mode? (You have 24 VAVs delivering air below 13°C/55°F, 21 VAVs delivering over 24/75°F, and 6 VAVs around 16°F/61°F)

• Something useful is to request an output at "Detailed" (= HVAC variable timesteps) reporting frequency of the supply inlet temperatures, and then plot it to see what's going on (I suggest using SQLite output and using the ResultsViewer from Openstudio)

• Check what convergence tolerances you're using for your VAVs (I think default is 0.001°C)

• If after all of the above you're not satisfied, try the helpdesk.