<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 14 (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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
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";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{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";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</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 bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">I have a guess: maybe the reason your altitude edits aren’t sticking has something to do with the green input fields & purple text – that tells me you’re using one of the energy compliance options (LEED/California/etc).
Those options result in a myriad of user interface quirks. <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">Try saving a separate copy of your project, then setting the code compliance version to “- none - ” (this is typical for every LEED project I’ve submitted)<o:p></o:p></span></p>
<p class="MsoNormal"><img width="851" height="422" id="Picture_x0020_2" src="cid:image003.png@01CF4FD5.D60B0AF0"><span style="color:#1F497D"><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">As to documentation, I’ve never included the eQuest generated LEED spreadsheet before, so it may help to know it’s not a requirement/expectation if it isn’t populating correctly. Simulation enduse output in
my experience is typically documented through either the graphical reports and/or the PS-F reports (the latter only, of late). You’re already “hand-entering” each of the enduses for each model/orientation anyway in the LEED templates – no good reason to
do it more when a reviewer can check against the typical output reports for errors.<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">~Nick<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><img width="119" height="37" id="Picture_x0020_1" src="cid:image001.jpg@01CF4FD5.47C25460" alt="cid:489575314@22072009-0ABB"></span><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E">NICK CATON, P.E.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900">SENIOR ENGINEER<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">Smith & Boucher Engineers</span><span style="font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">25501 west valley parkway, suite 200<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">olathe, ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">direct 913.344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">fax 913.345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span style="font-size:10.0pt">www.smithboucher.com</span></a></span><u><span style="font-size:10.0pt;color:blue">
</span></u><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";color:windowtext">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Joe Huang<br>
<b>Sent:</b> Thursday, April 03, 2014 10:20 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] How to Change Altitude and Unpopulated LEED Comparision Report<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I don't know about eQUEST, because my experience is only with the DOE-2 engine that lies behind it, so you should take what I say with a grain of salt.<br>
<br>
In DOE-2, the altitude of the building can be either read from the weather file, or input separately by the user. The altitude that's shown on the screen below seems to be taken from the weather file, which may be why you can't change it. Check to see if
that's true, and if so, check if there's a way for a user input of altitude that overrides what's on the weather file. It is possible to change the elevation on the weather file, but since it's a binary (not an ASCII) file, you have to use a couple of utility
programs to convert to text and then back to binary. However, I'm leery of large arbitrary changes in altitude, like from 3,000 ft in El Paso down to sea level, as you suggest, because the weather data would not be right at all. Why can't you just change
the weather file to that of an appropriate sea level location? <br>
<br>
Joe<br>
<br>
<o:p></o:p></p>
<pre>Joe Huang<o:p></o:p></pre>
<pre>White Box Technologies, Inc.<o:p></o:p></pre>
<pre>346 Rheem Blvd., Suite 108D<o:p></o:p></pre>
<pre>Moraga CA 94556<o:p></o:p></pre>
<pre><a href="mailto:yjhuang@whiteboxtechnologies.com">yjhuang@whiteboxtechnologies.com</a><o:p></o:p></pre>
<pre><a href="http://weather.whiteboxtechnologies.com">http://weather.whiteboxtechnologies.com</a> for simulation-ready weather data<o:p></o:p></pre>
<pre>(o) (925)388-0265<o:p></o:p></pre>
<pre>(c) (510)928-2683<o:p></o:p></pre>
<pre>"building energy simulations at your fingertips"<o:p></o:p></pre>
<p class="MsoNormal"><br>
On 4/3/2014 10:04 AM, Jay B. Dyer wrote: <o:p></o:p></p>
<p class="MsoNormal">Ladies and Gentlemen of the eQuest user community,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I’m stuck. It’s one of those days where I’ve been ginning through this model so long that my mind is blank. I’m hoping someone here has a quick answer.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ISSUE #1</b><o:p></o:p></p>
<p class="MsoNormal">Thinking back, the past 20 LEED models or so have been at sea level, lol. Now we’re of in Texas somewhere, and we are not able to edit the red altitude field below, so we adjust for the 1.16 altitude factor eQuest placed on our airflows
by lowering in our scheduled airflow. Now when comparing to a LEED baseline model, the factor reappears and we would like to eQuest to calculate those airflows, so the analysis is skewed. Our LEED model is reporting higher airflow due to the altitude correction
factor. Now we are back to changing the altitude to 0—but how? It allows us to type something in but doesn’t change the number? Editing the weather bin file isn’t easy either as it’s ASCII, and I’d have to research an editor and format.<o:p></o:p></p>
<p class="MsoNormal"><img border="0" width="576" height="432" id="_x0000_i1025" src="cid:image002.png@01CF4FD5.47C25460"><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ISSUE #2</b><o:p></o:p></p>
<p class="MsoNormal">My LEED report shows annual energy use but all 0’s in the energy breakdown and other normally populated items. This is a VRV job and only the DOAS is scheduled for airflow. Will 0’s for fan operation make the whatever results the LEED
comparison uses blank? The LEED report isn’t mining results, but other detailed reporting is OK. I’d hate to hand populate the sheet.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">The Excel sheet it spits out is attached.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Thanks for the assistance, <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Jay Dyer<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>James B. Dyer, P.E., LEED AP O+M, CEM</b><o:p></o:p></p>
<p class="MsoNormal"><b>Senior Mechanical Engineer</b><o:p></o:p></p>
<p class="MsoNormal"><b><span style="font-size:14.0pt;color:#632423">IC Thomasson Associates, Inc.</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt">622 Vassar St</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt">Orlando, FL 32804</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt">407.420.9924 – Direct</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt">321.287.1701 – Mobile</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt"><a href="http://www.icthomasson.com/">www.icthomasson.com</a></span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Equest-users mailing list<o:p></o:p></pre>
<pre><a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><o:p></o:p></pre>
<pre>To unsubscribe from this mailing list send a blank message to <a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre>
</div>
</body>
</html>