<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 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: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:"AvantGarde Bk BT";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
h5
{mso-style-priority:9;
mso-style-link:"Heading 5 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
{mso-style-priority:99;
mso-style-link:"Body Text Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","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";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{mso-style-name:msochpdefault;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
span.balloontextchar0
{mso-style-name:balloontextchar;
font-family:"Tahoma","sans-serif";}
span.emailstyle19
{mso-style-name:emailstyle19;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.emailstyle20
{mso-style-name:emailstyle20;
font-family:"Calibri","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.Heading5Char
{mso-style-name:"Heading 5 Char";
mso-style-priority:9;
mso-style-link:"Heading 5";
font-weight:bold;}
span.BodyTextChar
{mso-style-name:"Body Text Char";
mso-style-priority:99;
mso-style-link:"Body Text";}
.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 lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>That was the only problem in my mind – I figured a try and see approach would get to the bottom of it. Scott is probably much more familiar with this than I am, but there are no problems referencing local keywords under the same parent from what I have seen. You can setup a function that defines the WIDTH keyword of a window as a function of the HEIGHT keyword of the same window without a problem. The issue I was worried about (and you are as well) would be using a local keyword as a reference when that keyword is determined by the program and not explicitly defined in the input file. <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'>It would probably take me at least a few hours of playing around with it to figure out if I can even reference the COOLING-CAPACITY keyword under the COOLING-EIR. <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:#1F497D'>Jeremy R. Poling, PE, LEED AP+BDC</span></b><span style='color:#1F497D'><br></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"'> Bishop, Bill [mailto:wbishop@pathfinder-ea.com] <br><b>Sent:</b> Wednesday, May 18, 2011 8:52 AM<br><b>To:</b> Jeremy Poling; Dahlstrom, Aaron; equest-users@lists.onebuilding.org<br><b>Cc:</b> Scott Criswell<br><b>Subject:</b> RE: [Equest-users] Appendix G Baseline Systems 1 and 2 efficiency<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='color:#1F497D'>Jeremy,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Can a child component (COOLING-EIR) reference the keyword value of another child component (COOLING-CAPACITY) of the same parent?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>In the case I’m describing, there is no keyword value for COOLING-CAPACITY, since it is calculated by the program, not entered. Is there any way to reference program output with a user input function?<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Bill<o:p></o:p></span></p><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"'> Jeremy Poling [mailto:Jeremy.Poling@transwestern.net] <br><b>Sent:</b> Tuesday, May 17, 2011 11:52 PM<br><b>To:</b> Dahlstrom, Aaron; Bishop, Bill; equest-users@lists.onebuilding.org<br><b>Subject:</b> RE: [Equest-users] Appendix G Baseline Systems 1 and 2 efficiency<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div id=idOWAReplyText54174><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:black'>Have you thought about using a "user input function" to define the EIR? I haven't used one this way yet, but there are a few examples out there in the help info. In theory, you could setup a logic statement that checks the capacity and uses the EIR value appropriate for that size system. I'd be willing to discuss the idea with you guys, but there'll be a certain amount of "if at first you don't succeed..." involved to figure out the right code to grab the system capacity.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I've been playing more with user input functions after seeing some examples of powerful ways they can remove some of the repetitive changes. For example, for single-zone systems, you could theoretically program eQuest to auto-calculate the OA based on ASHRAE 62.1 requirements and the zone area and population. You could probably do it for multi-zone systems also, but that gets into the complexity level of the ASHRAE 62.1 spreadsheet and it is probably less time to just do the calcs in the spreadsheet and input the results.</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p></div></div><div id=idSignature77069><div><div><div><p class=MsoNormal><b><span style='font-size:7.5pt;font-family:"Verdana","sans-serif";color:black'>Jeremy R. Poling, PE, LEED AP+BDC</span></b><span style='color:black'><o:p></o:p></span></p></div></div></div></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal style='margin-bottom:12.0pt'><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 on behalf of Dahlstrom, Aaron<br><b>Sent:</b> Tue 5/17/2011 10:31 PM<br><b>To:</b> Bishop, Bill; equest-users@lists.onebuilding.org<br><b>Subject:</b> Re: [Equest-users] Appendix G Baseline Systems 1 and 2 efficiency</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt'>Bill:</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Your procedure sounds very similar to ours.</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt'>Beyond the simple automation of a spreadsheet, and dual monitors to copy data from SIM to XLS quickly, we haven’t found any quicker ways to skin this cat.</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><div><p class=MsoNormal style='line-height:150%'><b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>Aaron Dahlstrom , PE, LEED® AP</span></b><o:p></o:p></p><p class=MsoNormal style='line-height:150%'><b><span style='font-family:"AvantGarde Bk BT";color:#17365D'>In P</span></b><b><span style='font-family:"AvantGarde Bk BT";color:#619428'>o</span></b><b><span style='font-family:"AvantGarde Bk BT";color:#17365D'>sse</span></b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'> – </span><span style='font-size:8.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>A subsidiary of</span><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'> </span><b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:#CC0000'>AKF</span></b><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>| 1500 Walnut Street, Suite 1414, Philadelphia, PA 19102 </span><o:p></o:p></p><p class=MsoNormal style='line-height:150%'><span style='font-size:9.0pt;line-height:150%;font-family:"Verdana","sans-serif";color:gray'>d: 215-282-6753| m: 267-507-5470| In Posse: 215-282-6800| AKF: 215-735-7290</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Verdana","sans-serif";color:gray'>e: ADahlstrom@in-posse.com | in posse web: <a href="http://www.in-posse.com/">www.in-posse.com</a> | akf web: <a href="http://www.akfgroup.com/">www.akfgroup.com</a></span><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> <o:p></o:p></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>Bishop, Bill<br><b>Sent:</b> Tuesday, May 17, 2011 3:43 PM<br><b>To:</b> equest-users@lists.onebuilding.org<br><b>Subject:</b> [Equest-users] Appendix G Baseline Systems 1 and 2 efficiency</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Appendix G Baseline Systems 1 (PTAC) and 2 (PTHP) have cooling efficiencies (and for PTHP, heating efficiencies) that vary with cooling capacity per Table 6.8.1D. Since each thermal block is modeled with its own system, you can end up modeling as many as 100 or more systems per project. For LEED projects (or other App. G models), I have been calculating and manually entering values for cooling EIR for every single system, based on capacities reported in the SV-A reports. I factor in the unique fan power (per G3.1.2.9) for each system and remove its contribution from the efficiency, since fan power is included in EER and needs to be separated per G3.1.2.1. Once you enter efficiency for each system, just about any change you make in the model changes the supply flow rate and/or system capacities, which means you need to redo all the efficiency calculations.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Does this method seem correct?<o:p></o:p></p><p class=MsoNormal>Has anyone figured out a way to automate this process? (And by “automate”, I don’t mean give it to the intern.)<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>Bill<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><img border=0 width=496 height=123 id="Picture_x0020_1" src="cid:image001.jpg@01CC1539.80E719D0" alt="Signature in jpg form"><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><br clear=all>This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail. E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with In Posse. <o:p></o:p></span></p></div></div></body></html>