<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: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 15 (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:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Franklin Gothic Medium";
panose-1:2 11 6 3 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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.Normal, li.Normal, div.Normal
{mso-style-name:"\[Normal\]";
margin:0in;
margin-bottom:.0001pt;
text-autospace:none;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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="1027" />
</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="WordSection1">
<p class="MsoNormal">Follow-up questions:<o:p></o:p></p>
<p class="MsoNormal">If you specify the OUTPUT-MIN and OUTPUT-MAX will eQuest still through the CAUTION?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you specify DIAGNOSTIC WARNINGS .. will eQuest still through the CAUTION?
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Also where do you specify the DIAGNOSTIC keyword in the eQuest interface? I sometimes find it useful to specify DIAGNOSTIC DEFAULTS to see what hidden defaults might be leading to the results I am seeing. I know I can go through the BDLKEY.OUT
and BDLDFT.DAT files to check the defaults but I don’t always find what DIAGNOSTIC DEFAULTS prints in the .bdl file.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Christopher R Jones, P.Eng.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">T+ 1 416-644-0252<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><img width="60" height="29" style="width:.625in;height:.302in" id="_x0031_cc2331b-d8c3-424e-81de-2b17716d444e.png_x003f_ver_x003d_1495657656000" src="cid:image002.png@01D50CA9.7DF12660"><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Equest-users [mailto:equest-users-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Bishop, Bill via Equest-users<br>
<b>Sent:</b> Friday, May 17, 2019 11:33 AM<br>
<b>To:</b> 'Phil Jordan' <phil.jordan@clearesult.com><br>
<b>Cc:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] Performance Curves - independent variable boundaries<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Phil,<o:p></o:p></p>
<p class="MsoNormal">Good question! When a performance curve uses Raw Data Points (INPUT-TYPE = DATA), the coefficients for the curve are generated based on the data points and can be seen in the eQUEST Basic Specifications tab for the Performance Curve Properties.
(You can generate the coefficients yourself mathematically, by using the LINEST Excel function for example.) Outputs for the curve will be determined even if the inputs (independent variable values) are outside the range of the raw data points. For example,
a PLR of 0.2 and dT of 25F gives an EIR multiplier of 0.14 in the example curve below. The outputs could even be nonsensical if the simulation used garbage inputs. (An output of -0.2 using inputs of -1,-1.) I don’t think there is a keyword that restricts the
input variable values, but the OUTPUT-MIN and OUTPUT-MAX fix the output at those values rather than letting it go outside of those boundaries. Additionally, chillers have the MIN-RATIO keyword which defines the load for which the chiller will cycle on and
off.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">~Bill<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Franklin Gothic Medium",sans-serif;color:black">William Bishop, PE, BEMP, BEAP, CEM, LEED AP<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Senior Energy Engineer<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:3.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><!--[if gte vml 1]><v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="Picture_x0020_4" o:spid="_x0000_s1026" type="#_x0000_t75" alt="Pathfinder-EA-logo-2" style='position:absolute;margin-left:0;margin-top:63.6pt;width:68.45pt;height:43.9pt;z-index:-251658752;visibility:visible;mso-wrap-style:square;mso-width-percent:0;mso-height-percent:0;mso-wrap-distance-left:9pt;mso-wrap-distance-top:0;mso-wrap-distance-right:9pt;mso-wrap-distance-bottom:0;mso-position-horizontal:left;mso-position-horizontal-relative:text;mso-position-vertical:absolute;mso-position-vertical-relative:text;mso-width-percent:0;mso-height-percent:0;mso-width-relative:page;mso-height-relative:page'>
<v:imagedata src="cid:image006.jpg@01D50CA9.51C6D850" o:title="Pathfinder-EA-logo-2" />
<w:wrap type="through"/>
</v:shape><![endif]--><![if !vml]><img width="91" height="59" style="width:.9479in;height:.6145in" src="cid:image004.jpg@01D50CA9.7DF12660" align="left" hspace="12" alt="Pathfinder-EA-logo-2" v:shapes="Picture_x0020_4"><![endif]><b><i><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#002060">T:
(585) 698-1956</span><span style="color:#002060"> </span></i></b><span style="color:#1F497D"> </span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">F: (585) 325-6005<o:p></o:p></span></p>
<p class="MsoNormal"><a href="mailto:wbishop@pathfinder-ea.com"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">bbishop@pathfinder-ea.com</span></a><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"> </span><a href="http://www.pathfinder-ea.com/"><span style="font-size:9.0pt;font-family:"Arial",sans-serif">www.pathfinder-ea.com</span></a><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">134 South Fitzhugh Street<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#1F497D">Rochester, NY 14608
<img border="0" width="26" height="23" style="width:.2708in;height:.2395in" id="Picture_x0020_1" src="cid:image008.png@01D50CA9.51C6D850"> </span><i><span style="font-size:7.0pt;font-family:"Verdana",sans-serif;color:#00B0F0">Act on the climate crisis - the
Energy Innovation and Carbon Dividend Act</span></i><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Equest-users <<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>>
<b>On Behalf Of </b>Phil Jordan via Equest-users<br>
<b>Sent:</b> Thursday, May 16, 2019 7:54 PM<br>
<b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> [Equest-users] Performance Curves - independent variable boundaries<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">When a curve output exceeds the limits (min/max output, OUTPUT-MIN and OUTPUT-MAX keywords), eQUEST throws a CAUTION message in the SIM file, something like this:<o:p></o:p></p>
<p class="Normal"><span style="font-size:8.0pt;font-family:"Courier New"">**CAUTION**********************************************************************<o:p></o:p></span></p>
<p class="Normal"><span style="font-size:8.0pt;font-family:"Courier New""> In curve: Variable Speed Drive FPLR the dependent value<o:p></o:p></span></p>
<p class="Normal"><span style="font-size:8.0pt;font-family:"Courier New""> is exceeding the limits.<o:p></o:p></span></p>
<p class="Normal"><span style="font-size:8.0pt;font-family:"Courier New""> Value/Min/Max/First time: 1.004 0.100 1.000 7/21/ 8<o:p></o:p></span></p>
<p class="Normal"><span style="font-size:8.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="Normal"><span style="font-size:8.0pt;font-family:"Courier New""><o:p> </o:p></span></p>
<p class="MsoNormal">I’m curious, what happens when the input type for a performance curve is “Raw Data Points” and during the course of the simulation one of the independent variables is outside the range of the raw data points? For example, here’s a curve
from the library (BDLLIB.DAT) that’s defined via data points:<o:p></o:p></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New"">$LIBRARY-ENTRY SmFricW3VSD-EIR-fPLR&dT CURVE-FIT Sml Fric 3App -044d2 35<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New"">$ 70/140 ton, 3F approach evap & cond; R134a extended 460V 10F superheat -044d2 36<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New"">$ EIR = 0.182, 0.64 kW/ton, COP 5.5 -044d2 37<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> TYPE = BI-QUADRATIC-RATIO&DT INPUT-TYPE = DATA -044d2 38<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> IN-RATIO = ( 1.00, 0.75, 0.50, 0.25, $ PLR -044d2 39<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 1.00, 0.75, 0.50, 0.25, -044d2 40<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 1.00, 0.75, 0.50, 0.25, -044d2 41<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 1.00, 0.75, 0.50, 0.28 ) -044d2 42<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> IN-DT = ( 41.0, 41.0, 41.0, 41.0, $ ECT-CHW DT -044d2 43<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 31.0, 31.0, 31.0, 31.0, -044d2 44<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 26.0, 26.0, 26.0, 26.0, -044d2 45<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 46.0, 46.0, 46.0, 46.0 ) -044d2 46<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> OUTPUT = ( 1.00, 0.70, 0.46, 0.27, $ EIR ratio -044d2 47<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 1.00, 0.66, 0.39, 0.22, -044d2 48<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 1.00, 0.65, 0.38, 0.19, -044d2 49<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Courier New""> 1.00, 0.72, 0.50, 0.32 ) .. -044d2 50<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the data points, the minimum PLR boundary for the curve is 0.25 – what happens if during the simulation the PLR is 0.20? Does eQUEST use the curve output regardless (and is a CAUTION generated), or is the output at the minimum independent
variable used?<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"><o:p> </o:p></p>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Arial",sans-serif;color:#005E68">Phil Jordan</span></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
<br>
NOTICE: This communication and any attachments ("this message") may contain information which is privileged, confidential, proprietary or otherwise subject to restricted disclosure under applicable law. This message is for the sole use of the intended recipient(s).
Any unauthorized use, disclosure, viewing, copying, alteration, dissemination or distribution of, or reliance on, this message is strictly prohibited. If you have received this message in error, or you are not an authorized or intended recipient, please notify
the sender immediately by replying to this message, delete this message and all copies from your e-mail system and destroy any printed copies. You are receiving this communication because you are listed as a current WSP contact. Should you have any questions
regarding WSP's electronic communications policy, please consult our Anti-Spam Commitment at
<a href="http://www.wsp.com/casl">www.wsp.com/casl</a>. For any concern or if you believe you should not be receiving this message, please forward this message to
<a href="mailto:caslcompliance@wsp.com">caslcompliance@wsp.com</a> so that we can promptly address your request. Note that not all messages sent by WSP qualify as commercial electronic messages.
<br>
<br>
AVIS : Ce message, incluant tout fichier l'accompagnant (« le message »), peut contenir des renseignements ou de l'information privilégiés, confidentiels, propriétaires ou à divulgation restreinte en vertu de la loi. Ce message est destiné à l'usage exclusif
du/des destinataire(s) voulu(s). Toute utilisation non permise, divulgation, lecture, reproduction, modification, diffusion ou distribution est interdite. Si vous avez reçu ce message par erreur, ou que vous n'êtes pas un destinataire autorisé ou voulu, veuillez
en aviser l'expéditeur immédiatement et détruire le message et toute copie électronique ou imprimée. Vous recevez cette communication car vous faites partie des contacts de WSP. Si vous avez des questions concernant la politique de communications électroniques
de WSP, veuillez consulter notre Engagement anti-pourriel au <a href="http://www.wsp.com/lcap">
www.wsp.com/lcap</a>. Pour toute question ou si vous croyez que vous ne devriez pas recevoir ce message, prière de le transférer au
<a href="mailto:conformitelcap@wsp.com">conformitelcap@wsp.com</a> afin que nous puissions rapidement traiter votre demande. Notez que ce ne sont pas tous les messages transmis par WSP qui constituent des messages electroniques commerciaux.
<br>
</font><br>
<font face="Arial" color="WhiteSmoke" size="0.10"><br>
<br>
-LAEmHhHzdJzBlTWfa4Hgs7pbKl </font>
</body>
</html>