<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Chris,</p>
<p>My intention was not to recommend using macros instead of
expressions in eQUEST/DOE-2.2, but suggesting that if macros and
expressions share the same syntax, then the DOE-2.1E manual would
be a good place for documentation of the (common) syntax. <br>
</p>
<p>I've used DOE-2 macros extensively ever since they were developed
in the early 1980's, and in fact I can't imagine how to manage
parametric simulations without them. One thing I've noticed
repeatedly has been that people who are unfamiliar with macros,
especially those unfamiliar with DOE-2, tend to underestimate what
macros can do. For example, I remember a meeting at DOE in the
early 2000's where someone from another National Lab dismissed
macros as simply doing "sequential substitution". However, macros
(and presumably expressions as well) can import data from external
files, do arithmetic operations including trigonometry and
exponentials, as well as Boolean operations. <br>
</p>
<p>In fact, I got so worked up talking about this (kudos to Monty
Python's killer rabbit scene in "Search for the Holy Grail"
<a class="moz-txt-link-freetext" href="https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=monty%20pythom%20holy%20grail%20rabbit%20scene">https://www.google.com/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=monty%20pythom%20holy%20grail%20rabbit%20scene</a>
:-) ) that I decided to cut out the section on macros from the
2.1E Supplement and have attached it with this post.</p>
<p>Joe<br>
</p>
<pre class="moz-signature" cols="90">Joe Huang
White Box Technologies, Inc.
346 Rheem Blvd., Suite 205A
Moraga CA 94556
<a class="moz-txt-link-abbreviated" href="mailto:yjhuang@whiteboxtechnologies.com">yjhuang@whiteboxtechnologies.com</a>
<a class="moz-txt-link-freetext" href="http://weather.whiteboxtechnologies.com">http://weather.whiteboxtechnologies.com</a> for simulation-ready weather data
(o) (925)388-0265
(c) (510)928-2683
"building energy simulations at your fingertips"
</pre>
<div class="moz-cite-prefix">On 9/1/2016 5:32 AM, Chris Jones wrote:<br>
</div>
<blockquote
cite="mid:BL2PR02MB2004EC5C7443DDBF7F095A6599E20@BL2PR02MB2004.namprd02.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 14 (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: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:12.0pt;
font-family:"Times New Roman","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;}
p
{mso-style-priority:99;
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";
color:black;}
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;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">eQUEST
does use DOE-2 macros with the same syntax as DOE2.1e if you
edit the .inp file directly. The frustrating thing is that
eQUEST evaluates the macros when you reopen the project and
strips out the macro definitions leaving the resultant
value. So it is useless if you hope to use macros for
parametric runs in the eQUEST interface – at least in the
tests I have carried out. You can use parametric expressions
but the statements become much longer and, in my opinion,
harder to use but that’s likely because I am so used to the
macro language.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D">Christopher
Jones, P. Eng.<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D">Rowan
Williams Davies & Irwin Inc.</span></b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D"><br>
<i>Consulting Engineers & Scientists</i><br>
901 King Street West, Suite 400, Toronto, Ontario, M5V 3H5<br>
<b>T:</b> (519) 823-1311 ext 2052 <o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D">M:</span></b><span
style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1F497D">
(416) 697-0056
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";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
[<a class="moz-txt-link-freetext" href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Joe Huang via Equest-users<br>
<b>Sent:</b> Wednesday, August 31, 2016 10:33 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> Re: [Equest-users] DOE 2 Expressions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>People on the eQUEST/DOE-2.2 Development Team can correct me
if I'm wrong, but IF DOE-2 expressions use the same syntax as
DOE-2 macros, those are well-explained in the DOE-2
Supplement, Version 2.1E, by Winkelmann et al. 1993,
LBL-34947, Lawrence Berkeley National Laboratory, Berkeley CA
pp. 1.42-1.77 . You should be able to find a PDF version of
this document on the Web, since it's included in the DOE-2.1E
release, but if not, let me know and I'll see whether I could
put my PDF version online somewhere.<o:p></o:p></p>
<p>Joe<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 205A<o:p></o:p></pre>
<pre>Moraga CA 94556<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:yjhuang@whiteboxtechnologies.com">yjhuang@whiteboxtechnologies.com</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" 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>
<div>
<p class="MsoNormal">On 2016/8/31 15:42, Saif A via
Equest-users wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi guys, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">is there any materials (Books,
websites, examples) to learn DOE 2 expressions beside
the "Overview of DOE-2.2". <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Saif<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><br>
<br>
<br>
<o:p></o:p></p>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Equest-users mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" 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 moz-do-not-send="true" href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div style="font-size:7pt;">
<hr>
RWDI - One of Canada's 50 Best Managed Companies - This
communication is intended for the sole use of the party to whom
it was addressed and may contain information that is privileged
and/or confidential. Any other distribution, copying or
disclosure is strictly prohibited. If you received this email in
error, please notify us immediately by replying to this email
and delete the message without retaining any hard or electronic
copies of same. Outgoing emails are scanned for viruses, but no
warranty is made to their absence in this email or attachments.
If you require any information supplied by RWDI in a different
format to facilitate accessibility, contact the sender of the
email, email <a class="moz-txt-link-abbreviated" href="mailto:solutions@rwdi.com">solutions@rwdi.com</a> or call +1.519.823.1311.
<hr>
</div>
</blockquote>
<br>
</body>
</html>