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

[Joe Huang]

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
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140326/82b0b6de/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 43155 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140326/82b0b6de/attachment-0002.png>