Appendix G - Rotation

2 posts / 0 new
Last post

Hey all,

So I'm trying to figure out exactly how to get eQuest to give an average
energy usage for the building in its four different orientations for the
Appendix G requirements. I did some searching, only to find other people
griping that there is no built in feature for this (however the
developers may be working on an Appendix G compliance add-in?), but I
still don't want to do it manually. I've played with the parametric
functions and this is what I've figured so far - any input on what's
going on here is much appreciated.

First, I created my model and baseline. I then took the baseline which
was oriented in the same direction as the proposed building, and added
four parametric runs called "orientation all", "orientation EW",
"orientation N" and "orientation S". Under "orientation all", I created
four parametric components called west east north and south. Under
"orientation EW" I created east and west and under "orientation n" I
just created a parametric component called north (same for its south
counterpart). Each of these components I categorized as follows (as you
can see in the attached screenshot called parametric runs.jpg - although
it doesn't include the S version):

* Type: BDL Command

* Component type: Building Parameters

* Keywords: Azimuth Index: NA Value: X (where X is 0-north,
90-East, 180-south, 270-West; the front of my building is oriented
towards the north in the proposed case)

I ran that, and got the results (screenshot parametric results.jpg).
After all this I then went back into the wizard mode and switched the
orientation of the building from north to south and ran just that one
run. The result was the exact same as the parametric result labeled
"orientation S". "orientation N" was also the same result which
indicates to me that it's not an average, but a best case scenario for
all its components. "orientation EW" makes sense because the front of
the building has the most glass, so orienting it towards the east or
west would increase the solar gain. However, my guess is that if I did
both east and west separately, one would match what EW got, and the
other would be less efficient.

I'm not sure where to go from here. Has anybody been successful in
getting eQuest to give an average, or are we stuck "doing it by hand"?
Any comments or suggestions would be appreciated.

Eric O'Neill

Eric O'Neill's picture
Joined: 2011-09-30
Reputation: 0


My understanding of the parametric runs in eQuest is that if you specify
multiple parametric components that change the same parameter (as you've
done with changing the azimuth parameter four times in your "orientation
all" run) the program will spit out the results for the last entry only.
In other words it ignores the first three entries. So, if the order of
your parametric components is as you listed them when describing
"orientation all" ...

"...I created four parametric components called west east north and

Then I would expect the results to match that for "orientation S" since
south is the last component. This is confirmed in your JPEG. Likewise
for your run "orientation EW", if your components are listed in the
order "east, west" I would expect it to match the results for a west

The parametric run simply systematically assigns the values associated
with each component then performs a single simulation. Unfortunately I
don't know of a way to do this averaging of multiple simulations

Most of my modeling purposes have been for LEED and the LEED Submittal
Template requires result data for each individual orientation anyways so
I have not found the need for automatic averaging ability. I generally
perform a baseline simulation then create three parametric runs
(90,180,270) and let the LEED template average them out. I suppose an
automated averaging would be handy for interim simulations as a
quick-reference tool.

Anyways, hope that helps.


Dan Russell, EIT

Dan Russell's picture
Joined: 2011-09-30
Reputation: 0