<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:"Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@Yu Gothic";
panose-1:2 11 4 0 0 0 0 0 0 0;}
/* 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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoPlainText">You've got this, and you've stumbled into a great question!
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The issue here, as you might imagine, is that this piece of your switch statement: #L(GLASS-TYPE") is not returning any of the text strings you are using for your cases ("GT1", "GT3", etc.). Let’s explore this.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This dummy model has 3 glass types defined:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="745" height="562" style="width:7.7604in;height:5.8541in" id="Picture_x0020_1" src="cid:image001.png@01D60DE5.622F7EC0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">What happens if I enter #L(GLASS-TYPE") in for something like the height input?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="798" height="604" style="width:8.3125in;height:6.2916in" id="Picture_x0020_2" src="cid:image002.png@01D60DE5.DFB289A0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hmm. What happens if I leave that expression in place but change the glass type?<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="756" height="563" style="width:7.875in;height:5.8645in" id="Picture_x0020_3" src="cid:image003.png@01D60DE5.DFB289A0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Neat! (please, hold your applause!!!)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">What we’re seeing here is that each glass type (and in fact, every component of your model) has a unque number mapped to it. This number is called the
<b>symbol index</b>.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Before going deeper, let’s apply this to a switch statement to confirm understanding (yep, this works as expected if you toggle the glass type dropdown):<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="943" height="587" style="width:9.8229in;height:6.1145in" id="Picture_x0020_15" src="cid:image010.png@01D60E37.C2905F80"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> This is frankly what most doe-2 defaults look like in my experience, but we can incrementally improve end-user readability by inserting some comments. These have no effect on the function of the expression, but I feel
it’s a good practice for leaving yourself/others a breadcrumb trail whenever a custom expression isn’t totally intuitive:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><img width="921" height="590" style="width:9.5937in;height:6.1458in" id="Picture_x0020_16" src="cid:image004.png@01D60E38.7A4136E0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><u>I think this is as close as I can get to your original intended form, using a switch statement</u>, but we aren’t machines and it would be *<b>nice</b>* to use strings per your query. We can (sorta) get there!
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The <b>symbol index</b> is a mysterious thing that even today I wonder at sometimes (I may not be qualified to teach this), but if you take away one thing from this post, know that the main trick to bridging the gap between “textual
inputs” and “index numbers of things” in your expressions is to use the <b>#SI()</b> or
<b>#SymbolIndex()</b> wrapper.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">An expression like this wil return the same integer (1971):<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="904" height="580" style="width:9.4166in;height:6.0416in" id="Picture_x0020_9" src="cid:image007.png@01D60DEA.D2397EA0"><o:p></o:p></p>
<p class="MsoPlainText">A lot is going on here. To unpack, let’s first take a look at a local example from the same input screen. Through the expression definition dialog, I can load up the doe-2 default expression that results in the default (green) “No”
input for the “Diffusing:” dropdown. Let’s take a look:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="934" height="576" style="width:9.7291in;height:6.0in" id="Picture_x0020_5" src="cid:image005.png@01D60DE7.E26CB5B0"><o:p></o:p></p>
<p class="MsoPlainText">This expression is looking to the selection made/defaulted for the locaql WINDOW-TYPE to determine whether to default to either “YES” or “NO” for the keyword “DIFFUSING-GLASS.” Notice this #SI wrapper is used in every place you’d normally/intuitively
name something with a string like “NO” or “YES.” In doe-2 reference manual terms, this pattern is described as follows:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="875" height="321" style="width:9.1145in;height:3.3437in" id="Picture_x0020_10" src="cid:image008.png@01D60DF4.7C04D0C0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">To help remember/understand this pattern of “string, command, keyword” let’s observe what the previous example input looks like in an INP file:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="429" height="238" style="width:4.4687in;height:2.4791in" id="Picture_x0020_7" src="cid:image006.png@01D60DE8.4824E6C0"><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The string is “NO”<o:p></o:p></p>
<p class="MsoPlainText">The command is a “WINDOW”<o:p></o:p></p>
<p class="MsoPlainText">The keyword is “DIFFUSING-GLASS”<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Note each of these is using quotation marks in the wokring examples illustrated. I forget those a lot, personally.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">So… armed with this knowledge, we can assemble an example/template resembling your actual request using if/then statements:<o:p></o:p></p>
<p class="MsoPlainText" style="margin-left:.5in"><img width="907" height="568" style="width:9.4479in;height:5.9166in" id="Picture_x0020_14" src="cid:image009.png@01D60E34.515AED10"><o:p></o:p></p>
<p class="MsoPlainText">Not as clean as a switch statement, but gets the job done. My preference would probably lie with using integers per the previous example, using comments to help my human brain interpret each case.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I don’t know if it’s possible to arrive at something quite like your original intent however, with textual representations of symbols like “GT1” used for the case arguments. While I have seen and used many cases of switch statements
based on C-ACTIVITY-DESC using 4-character string blocks for the case options, I think that might be a special snowflake exception to the rule in the help files: the thing following “case” should be an integer. Maybe I’m missing something on this front,
in which case I hope someone will take the time/effort to educate me/us!<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hope this is hepful!<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">~Nick<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">------------------------------------------------------<o:p></o:p></p>
<p class="MsoPlainText">Nick Caton, P.E., BEMP<o:p></o:p></p>
<p class="MsoPlainText"> Senior Energy Engineer<o:p></o:p></p>
<p class="MsoPlainText"> Energy and Sustainability Services<o:p></o:p></p>
<p class="MsoPlainText"> Schneider Electric <o:p></o:p></p>
<p class="MsoPlainText">D 913 . 564 . 6361<o:p></o:p></p>
<p class="MsoPlainText">M 785 . 410 . 3317<o:p></o:p></p>
<p class="MsoPlainText">E nicholas.caton@se.com<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: Equest-users <equest-users-bounces@lists.onebuilding.org> On Behalf Of Melissa Crowe via Equest-users<br>
Sent: Wednesday, April 8, 2020 4:05 PM<br>
To: equest-users@lists.onebuilding.org<br>
Subject: [Equest-users] User Expression Window Width, Height as Function of Glass-Type</p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">[External email: Use caution with links and attachments]<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">________________________________<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hi All<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Hoping this day find you all safe at home and healthy!<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Having a LEED review head-ache. I need to change the way eQuest evaluates the assembly U-value for the proposed building.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I have 12 window types with variations in glazing, dimensions and # of mullions. The way I see it now easiest to assign each window type as a "Glass-Type" and then do an expression for height, width and frame width for each type.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Is there a way to do Height as function of Glass-Type..... the following is not working for me.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">switch(#L("GLASS-TYPE"))<o:p></o:p></p>
<p class="MsoPlainText">case "GT1" : 12<o:p></o:p></p>
<p class="MsoPlainText">case "GT3" : 8<o:p></o:p></p>
<p class="MsoPlainText">case "GT4" : 4<o:p></o:p></p>
<p class="MsoPlainText">default : #@##!!<o:p></o:p></p>
<p class="MsoPlainText">ENDSWITCH<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The problem is that default : is required and all cases end up being the default.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Any Ideas?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thanks<o:p></o:p></p>
<p class="MsoPlainText">Melissa<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Melissa Crowe, LEED AP, BEMP<o:p></o:p></p>
<p class="MsoPlainText">Senior Mechanical/Energy Engineer<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">161 Worcester Road, Suite 305<o:p></o:p></p>
<p class="MsoPlainText">Framingham, MA 01701<o:p></o:p></p>
<p class="MsoPlainText">O: 508.647.9200 x1225<o:p></o:p></p>
<p class="MsoPlainText">C: 978.204.2559<o:p></o:p></p>
<p class="MsoPlainText">cmta.com<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">_______________________________________________<o:p></o:p></p>
<p class="MsoPlainText">Equest-users mailing list<o:p></o:p></p>
<p class="MsoPlainText"><a href="https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.onebuilding.org%2Flistinfo.cgi%2Fequest-users-onebuilding.org&data=02%7C01%7CNicholas.Caton%40se.com%7Cb8255f5cfca24ec6bd5408d7dc009174%7C6e51e1adc54b4b39b5980ffe9ae68fef%7C0%7C0%7C637219767309856918&sdata=GrXUIWWSp0Cf49X1YOWnCnUz6%2B6r4ziDqdZFcU0E5wQ%3D&reserved=0"><span style="color:windowtext;text-decoration:none">https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.onebuilding.org%2Flistinfo.cgi%2Fequest-users-onebuilding.org&data=02%7C01%7CNicholas.Caton%40se.com%7Cb8255f5cfca24ec6bd5408d7dc009174%7C6e51e1adc54b4b39b5980ffe9ae68fef%7C0%7C0%7C637219767309856918&sdata=GrXUIWWSp0Cf49X1YOWnCnUz6%2B6r4ziDqdZFcU0E5wQ%3D&reserved=0</span></a><o:p></o:p></p>
<p class="MsoPlainText">To unsubscribe from this mailing list send a blank message to
<a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG"><span style="color:windowtext;text-decoration:none">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">______________________________________________________________________<o:p></o:p></p>
<p class="MsoPlainText">This email has been scanned by the Symantec Email Security.cloud service.<o:p></o:p></p>
<p class="MsoPlainText">______________________________________________________________________<o:p></o:p></p>
</div>
</body>
</html>