<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)">
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Arial Black";
panose-1:2 11 10 4 2 1 2 2 2 4;}
/* 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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
-->
</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 lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>Hello,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I was almost sure that eQUEST/DOE-2.2 had a built-in control
mode to reset the tower-leaving condenser-water setpoint relative to outdoor
wet-bulb temperature. After puzzling over why I couldn’t find it in the
GUI, I eventually realized that I was thinking of EnergyPro/DOE-2.1e. This
is a fairly common control strategy for open towers, so I was wondering why
this feature disappeared between DOE-2 releases and what others are doing to
simulate this control mode using eQUEST.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Of course, COOL-SETPT-CTRL = OA-RESET is based on dry-bulb.
So you could assume a constant wet-bulb depression and use a SUPPLY-LO greater
than SUPPLY-HI (this is allowed, right?), but this is very crude.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I guess you could use COOL-SETPT-CTRL = SCHEDULED, parse the
hourly wet-bulb temps out of the weather file, add the tower design approach to
everything, and dump those values into a COOL-SETPT-SCH (hopefully using a perl
script or something). However, SCHEDULEs are limited to 12
WEEK-SCHEDULEs, so it’s not really possible to define a schedule of 8760 arbitrary
values. But even if you could, it seems to me that there’s a reason the
weather file has hourly wet-bulb data in it, and one of them is to avoid having
to do stuff like this… <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I had thought of using user expressions, but I think eQUEST
evaluates these when it generates the BDL, so they wouldn’t be evaluated during
the simulation for each hour. I’m pretty sure there’s no user variable
for current outdoor wet-bulb temp anyway, because this isn’t something that can
be evaluated ahead of time. Is this something that can be done with DOE-2
subroutines/functions (I haven’t played with those yet)? Something like:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>MAGIC-EXPRESSION = OA-WB-T + DESIGN-APPROACH ..<o:p></o:p></p>
<p class=MsoNormal>TWR-SETPT-SCH = SCHEDULE THRU DEC 31 (ALL) (1,24)
(MAGIC-EXPRESSION) ..<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The idea is that MAGIC-EXPRESSION would be evaluated every
time DOE-2 references the value of TWR-SETPT-SCH for the current hour.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Should I put this on the list of ECMs where I have to tell
people that I can’t really model that, or is there hope after all?<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal>Jeff<b><span style='font-size:8.0pt;font-family:"Verdana","sans-serif";
color:#135351'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:8.0pt;font-family:"Verdana","sans-serif";color:#135351'>Jeff
Saretsky</span></b><b><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#135351'><br>
</span></b><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";
color:#B2550C'>Energy Modeler<br>
</span><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";
color:#B2550C'>___________________________<br>
</span><span style='font-size:10.5pt;font-family:"Arial Black","sans-serif";
color:#135351'>RUMSEY</span><span style='font-size:13.5pt;font-family:"Arial Black","sans-serif";
color:#135351'><br>
</span><span style='font-size:6.0pt;font-family:"Tahoma","sans-serif";
color:#B2550C'>E N G I N E E R S<br>
</span><span style='font-size:7.0pt;font-family:"Verdana","sans-serif";
color:#B2550C'>Energy Efficient Design <br>
99 Linden Street<br>
Oakland CA 94607<br>
510 663 2070 x238<br>
fax 510 663 2080<br>
<a href="mailto:jsaretsky@rumseyengineers.com">jsaretsky@rumseyengineers.com</a><br>
</span><u><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";
color:#B2550C'><a href="http://www.rumseyengineers.com/"><span
style='font-size:7.0pt;color:#B2550C'>www.rumseyengineers.com</span></a></span></u><span
style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#B2550C'><br>
___________________________</span><b><span style='font-size:7.0pt;font-family:
"Verdana","sans-serif";color:#135351'><o:p></o:p></span></b></p>
</div>
</body>
</html>