Simulation runtime bloats when Transmittance Schedule assigned to shading surface

asked 2017-04-19 09:36:55 -0600

Julien Marrec

29706 ●94 ●76 http://www.effibem.com/

updated 2017-04-20 07:08:05 -0600

__AmirRoth__

4436 ●5 ●17 http://bleedinggreenna...

I assigned a transmittance schedule that is simple (0.7 in summer, 0.175 for winter) to some (79) shading surfaces in my model, in order to account for one deciduous tree that is shading my building.

I experienced a much (much!) longer runtime: from 2 minutes to 34 minutes.

Naively I expected that the transmittance schedule would only be used as a multiplier and wasn't expecting this.

Is this normal? Are there workarounds to not bloat the simulation runtime?

answered 2017-04-19 09:52:36 -0600

Julien Marrec

29706 ●94 ●76 http://www.effibem.com/

updated 2017-04-20 02:04:01 -0600

The problem is that the Sky Diffuse Modeling Algorithm of ShadowCalculation is changed automatically by EnergyPlus.

** Warning ** GetShadowingInput: The shading transmittance for shading devices changes throughout the year. Choose DetailedSkyDiffuseModeling in the ShadowCalculation object to remove this warning.
 **   ~~~   ** Simulation has been reset to use DetailedSkyDiffuseModeling. Simulation continues.
 **   ~~~   ** Better accuracy may be gained by setting the Calculation Frequency to 1 in the ShadowCalculation object.

This happens in SolarShading.cc#L675.

There is a Github Issue that seems relevant here.

Shorten runtime?

I have set the Calculation Frequency to be 30 days (calc method set to AverageOverDaysInFrequency) instead of 7, runtime went down to 10 minutes.