Revision history [back]

Too long for a comment.

I don't think see anything wrong with your geometry. Neither does the App:

Enable Geometry Diagnostics, and check all Diagnostic Tools. No reported issues. Try this out:

• make a copy of your .osm
• add a new thermal zone ("Thermal Zone 5")
• link "Space South" to "Thermal Zone 5", i.e. one space per thermal zone

Check the run/eplusout.err file. The "Warning .. CalculateZoneVolume" message no longer appears.

I encountered this a while back. I hesitate to qualify this as a bug at this moment, as I haven't taken a deep dive yet. This would be an SDK bug, not an App bug. In a nutshell, the interzone surface pair:

• "Surface 10" (Space South)
• "Surface 18" (Space Middle)

... should have been forward translated as an InternalMass object in the generated IDF, as suggested here. This no longer seems to work as before, maybe linked to EnergyPlus' "new" space concept introduced a few years ago.

What I end up doing is either:

• keep a single space for each thermal zone
• use an API-based script to combine spaces into one

I may be missing something obvious - would love to hear from other users.

Too long for a comment.

I don't think see anything wrong with your geometry. Neither does the App:

Enable Geometry Diagnostics, and check all Diagnostic Tools. No reported issues. Try this out:

• make a copy of your .osm
• add a new thermal zone ("Thermal Zone 5")
• link "Space South" to "Thermal Zone 5", i.e. one space per thermal zone

Check the run/eplusout.err file. The "Warning .. CalculateZoneVolume" message no longer appears.

I encountered this a while back. I hesitate to qualify this as a bug at this moment, as I haven't taken a deep dive yet. This would be an SDK bug, not an App bug. In a nutshell, the interzone interzone surface pair:

• "Surface 10" (Space South)
• "Surface 18" (Space Middle)

... should have been forward translated as an InternalMass object in the generated IDF, as suggested here. This no longer seems to work as before, maybe linked to EnergyPlus' "new" new space concept introduced a few years ago.

What I end up doing is either:

• keep a single space for each thermal zone
• use an API-based script to combine spaces into one

I may be missing something obvious - would love to hear from other users.

Too long for a comment.

I don't see anything wrong with your geometry. Neither does the App:

Enable Geometry Diagnostics, and check all Diagnostic Tools. No reported issues. Try this out:

• make a copy of your .osm
• add a new thermal zone ("Thermal Zone 5")
• link "Space South" to "Thermal Zone 5", i.e. one space per thermal zone

Check the run/eplusout.err file. The "Warning .. CalculateZoneVolume" message no longer appears.

I encountered this a while back. I hesitate to qualify this as a bug at this moment, as I haven't taken a deep dive yet. This would be an SDK bug, not an App bug. In a nutshell, the interzone surface pair:

• "Surface 10" (Space South)
• "Surface 18" (Space Middle)

... should have been forward translated as an InternalMass object in the generated IDF, as suggested here. This no longer seems to work as before, maybe linked to EnergyPlus' new space concept introduced a few years ago.

What I end up doing is either:

• keep a single space for each thermal zonezone (as illustrated above)
• use an API-based script to combine spaces into one

I may be missing something obvious - would love to hear from other users.

Too long for a comment.

I don't see anything wrong with your geometry. Neither does the App:

Enable Geometry Diagnostics, and check all Diagnostic Tools. No reported issues. Try this out:

• make a copy of your .osm
• add a new thermal zone ("Thermal Zone 5")
• link "Space South" to "Thermal Zone 5", i.e. one space per thermal zone

Check the run/eplusout.err file. The "Warning .. CalculateZoneVolume" message no longer appears.

I encountered this a while back. I hesitate to qualify this as a bug at this moment, as I haven't taken a deep dive yet. This would be an SDK bug, not an App bug. In a nutshell, the interzone surface pair:

• "Surface 10" (Space South)
• "Surface 18" (Space Middle)

... should have been forward translated as an InternalMass object in the generated IDF, as suggested here. This no longer seems to work as before, maybe linked to EnergyPlus' new space concept introduced a few years ago.

What I end up doing is either:

• keep a single space for each thermal zone (as illustrated above)
• use an API-based script to combine spaces into one

I don't know how to combine spaces into one using the App. I may be missing something obvious - would love to hear from other users.others.