 | 1 | initial version |
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?
| | 2 | retagged |
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?
| | 3 | retagged |
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?
