<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
The other thing to keep in mind is that even after you've converted
the input file to DOE-2.2, you will have to run it with DOE-2.2 in
batch mode, not through the eQUEST interface. <br>
<br>
Joe<br>
<pre class="moz-signature" cols="90">Joe Huang
White Box Technologies, Inc.
346 Rheem Blvd., Suite 108D
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>
<br>
On 1/30/2014 9:38 AM, Paul Riemer wrote:
<blockquote
cite="mid:057EF46662FE994F8119F0A903BCD0F802C692970178@eml1.dunham.corp"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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.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";}
span.EmailStyle19
{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: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Joe,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">Brian is right on. To add a bit, most of the
proprietary tools use 2.1e which allows user defined
functions. This gives them flexibility to write work around
code for things like heat recovery, VRF, etc. DOE 2.2 and
EQUEST do not allow user defined functions. I expect how
you proceed will come down to whether or not the existing
model truly relies on the their functions. You don’t sound
like you own the tool. If you do or are willing to buy it,
I would tell the tool developer where you are and where you
want to get to. I expect you will end up buying their tool
or starting over in eQUEST.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style=""><b><span style="font-size: 9pt;
font-family: "Verdana","sans-serif";
color: rgb(95, 87, 79);">Paul Riemer, PE, LEED AP BD+C</span></b><span
style="font-size: 9pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-family:
"Verdana","sans-serif"; color:
rgb(192, 0, 0);">DUNHAM</span></b><span
style="font-size: 11pt; font-family:
"Verdana","sans-serif"; color:
rgb(192, 0, 0);"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>
[<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>Brian Fountain<br>
<b>Sent:</b> Thursday, January 30, 2014 10:52 AM<br>
<b>To:</b> 'Joe Chappell'<br>
<b>Cc:</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] DOE2 Input File
Universal?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style=""><span lang="EN-CA">The key to
your question is what version of DOE-2 the ‘proprietory
tool’ is generating the simulation input for. If it is
DOE-2.2 then you should be able to import the .inp file
into eQUEST. It is more likely however that the other
software is generating a DOE-2.1 input file. There are
instructions in the eQUEST/DOE-2.2 documentation about how
to convert a DOE-2.1e input file to DOE-2.2 but it is
“non-trivial”. The structure of the plant keywords
completely changed as did the schedules and many other
keywords have small changes. The way to tell the version
of DOE-2 you are looking at is to look at the .sim output
file. The version will be in the corner of each report in
the .sim file.<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style=""><b><span lang="EN-CA">From:</span></b><span
lang="EN-CA">
<a class="moz-txt-link-abbreviated" href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>
[<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 Chappell<br>
<b>Sent:</b> Thursday, January 30, 2014 11:20 AM<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> [Equest-users] DOE2 Input File
Universal?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style=""><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA">Hello,<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA">I am
wondering if a DOE-2 input file is universally accepted by
all front-end softwares that utilize the DOE-2 simulation
engine, specifically eQuest. The specific example I’m
encountering is a DOE-2 model developed in a proprietary
software tool. The model needs to be further developed
and evaluated. If I have the input file that was used in
the proprietary model, am I able to import that same input
file into eQuest for further model development and
evaluation of energy conservation measures. If so, are
there significant hurdles in this process that make it
particularly burdensome?<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA">Thanks in
advance for your feedback.<o:p></o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal" style=""><b><span lang="EN-CA">Joe</span></b><span
lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal" style=""><span lang="EN-CA"><o:p> </o:p></span></p>
</div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Equest-users mailing list
<a class="moz-txt-link-freetext" href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a>
To unsubscribe from this mailing list send a blank message to <a class="moz-txt-link-abbreviated" href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a>
</pre>
</blockquote>
</body>
</html>