[Equest-users] DOE2 Input File Universal?

[Brian Fountain]

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.

 

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Joe
Chappell
Sent: Thursday, January 30, 2014 11:20 AM
To: 'equest-users at lists.onebuilding.org'
Subject: [Equest-users] DOE2 Input File Universal?

 

Hello,

 

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?

 

Thanks in advance for your feedback.

 

Kind regards,

Joe

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140130/a71d2349/attachment-0002.htm>