<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Cheltenham;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1795102451;
mso-list-type:hybrid;
mso-list-template-ids:698365164 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Eric, <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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 </span><span style='color:#1F497D'>as you listed them when
describing “orientation all” …<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>“…I created four
parametric components called west east north and south.”<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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 orientation.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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 automatically. <o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>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.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Anyways, hope that helps.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks,</span><span
style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span style='font-size:14.0pt;font-family:Cheltenham;
color:#A0002F'> </span><span style='font-size:18.0pt;font-family:Cheltenham;
color:#A0002F'>Dan Russell, EIT <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:Cheltenham;
color:#A0002F'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:Cheltenham;
color:#A0002F'><img width=200 height=174 id="Picture_x0020_1"
src="cid:image001.jpg@01C90F46.FD32EBF0"
alt="cid:image001.jpg@01C840A4.E711B250"></span><span style='color:#1F497D'><o:p></o:p></span></p>
</div>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <b>On Behalf Of </b>Eric
O'Neill<br>
<b>Sent:</b> Friday, September 05, 2008 10:54 AM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] Appendix G - Rotation<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hey all,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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):<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>Type: BDL Command<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>Component type: Building Parameters<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span
style='font-family:Symbol'><span style='mso-list:Ignore'>·<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]>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)<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>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. <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i><span
style='font-size:12.0pt;font-family:"Garamond","serif";color:green'>Eric
O'Neill</span></i></b><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<br>
</span><span style='font-size:10.0pt;font-family:"Garamond","serif";color:gray'>Mechanical
Engineer</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<br>
</span><span style='font-size:10.0pt;font-family:"Garamond","serif";color:gray'>Energy
Division - Michaels Engineering</span><span style='font-size:12.0pt;font-family:
"Times New Roman","serif"'> <o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'>811 Monitor St. Ste 100</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <br>
</span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'>La Crosse, WI 54603</span><span style='font-size:12.0pt;font-family:
"Times New Roman","serif"'> <br>
</span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'>v: 608-785-1900 x521</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <br>
</span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'>f: 608-784-2270</span><span style='font-size:12.0pt;font-family:
"Times New Roman","serif"'> <br>
</span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'>elo@michaelsengineering.com</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'> <br>
</span><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:red'><a href="http://www.michaelsengineering.com">http://www.michaelsengineering.com</a></span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><o:p></o:p></p>
</div>
</body>
</html>