[Equest-users] Run Equest file in command line DOE2

Jones, Christopher cjones at halsall.com
Wed Mar 26 06:22:14 PDT 2014


I use the DOE22.bat file that comes with the installation.  At the top of that batch file you see: set doedir=C:\doe22.  Change that to the location of your installation.  In my case it is: set doedir=I:\doe2h2 (I have multiple versions of DOE22 that correspond to the different eQuest versions).

Then I change my environment so that that directory is in the PATH.  That way I can change to the directory containing the .inp file at the DOS prompt run DOE22 from there.  That way I keep projects in separate directories.

The other thing required is to make sure the .lib files from the DOE22 installation contain the definitions from the eQuest libraries.  I do this by copying the entire eQ_Lib.dat into the DOE22 usrlib.dat file.

Christopher Jones, P.Eng.
Tel: 416.644.4226 * Toll Free: 1.888.425.7255 x 527

From: equest-users-bounces at lists.onebuilding.org [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Joe Huang
Sent: Wednesday, March 26, 2014 4:03 AM
To: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Run Equest file in command line DOE2

You have no idea the pleasure your post brings to an old hacker like me, since that's  how I still use DOE-2, including even DOE-2.2, i.e., by command line batch scripts.  My recommendation to you is to be familiar with MS-DOS commands and then walk through the run22.bat script to see what it does step-by-step.  Keep in mind that all the "smarts" are in this batch file (run22.bat) that tells the computer to do this, and then do that.

Setting up a DOE-2 run is really very straightforward (at least to me).  The program needs an input file called INPUT.TMP, a weather file called WEATHR.TMP, and several utility or library files (BDLLIB.TMP - library file, BDLKEY.TMP - keyword file, HDRFIL.TMP - hourly report file data,  etc.).  Note that these files are all temporary (*.TMP), so the common procedure is to copy them from their permanent file names, e.g., *.inp,*.bin, *.dat, etc.

DOE-2 then runs doebdl, which is an input processor program, and then runs doesim, which is the actual simulation program. Both produces output files, called OUTPUT (natch), that are typically concatenated and then renamed as [input file name].out, or in the case of DOE-2.2, they're kept separate as  *.bdl and *.sim.  Once the simulation has been completed, the temporary files are typically deleted.

If you're looking at the run22.bat supplied with eQUEST, you'll notice that it contains some "bells and whistles" , like creating a subdirectory with the input file name, change to it, and then doing the simulations there.  Such embellishments are not necessary, and I like to keep my scripts simple and direct so I don't have to debug them, but to each his/her own.

>From the looks of the screen dump you've provided, the script is having trouble finding the needed utility and library files.  One surefire way to fix that is to give the full path, rather than the relative path, for the permanent copies of these files.

Good luck and I hope you can get it to work.

Joe
Joe Huang
White Box Technologies, Inc.
346 Rheem Blvd., Suite 108D
Moraga CA 94556
yjhuang at whiteboxtechnologies.com<mailto:yjhuang at whiteboxtechnologies.com>
http://weather.whiteboxtechnologies.com for simulation-ready weather data
http://www.whiteboxtechnologies.com
(o) (925)388-0265
(c) (510)928-2683
"building energy simulations at your fingertips"



On 3/25/2014 1:47 PM, Ben Brannon wrote:
Hello,

I have an equest file that I would like to be able to run from the command line.  I have plenty of Equest experience, but never DOE2 from the command line.  I have been able to find the general syntax: c:\...\run22 exe ModelFile WeatherFile, but it seems like there are some library differences between equest and pure DOE2 that I am not sure how to deal with.

This is what I am seeing from a default Equest project I was trying to get to run:

[cid:image001.png at 01CF23F5.FCA53980]

Ben


____________________________________________________________
Electronic mail messages entering and leaving Arup  business
systems are scanned for acceptability of content and viruses




_______________________________________________

Equest-users mailing list

http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org

To unsubscribe from this mailing list send  a blank message to EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG<mailto:EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG>


______________________________________________________________________
NOTICE: This communication and any attachments ("this message") may contain confidential information for the sole use of the intended recipient(s). Any unauthorized use, disclosure, viewing, copying, alteration, dissemination or distribution of, or reliance on this message is strictly prohibited. If you have received this message in error, or you are not an authorized recipient, please notify the sender immediately by replying to this message, delete this message and all copies from your e-mail system and destroy any printed copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140326/ea28e1ff/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 43155 bytes
Desc: image001.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140326/ea28e1ff/attachment-0002.png>


More information about the Equest-users mailing list