Ask help to RUN model directly by doe22

4 posts / 0 new
Last post

Hey everyone,

I am trying to run the model directly by doe22.

I have more then 10 models, and each inp file of them is larger then 2MB,
even opening the model in eQuest takes me several minutes. Always I need to
simulate all of them and this take me more then half an hour to sit just
before the monitor, click and wait. And now I realize that opening file in
doe22, actually not open - it just check and run the directly, is much
quick, and also it will be easier to write a little script to batch run all
of them by only one click.

After I unzip the file downloaded from the official website with the code,
read the instrument - they run doe22 by a windows batch file, not like
other modern execute file, which can send the parameters easily and
clearly. There are several limitation in the way they provide, and the most
important are:

- file path length no`more then 64
- file path cannot contain space
- weather file location is fixed

I have read the content inside the batch which they provide, but not clear
(I am not that good at this coding staff). And I haven't found any other
documents to give more help.

Does anyone here know more about this? Like the user manual for doe22, or
examples, anything may be helpfull.

Thanks a lot!

Best regards,

Grammy Jiang

Qingdao Create Future Environment Protection Technology Consultancy Co., Ltd

Room 6-11, Building B, International Innovation Park, Songling Road,
Laoshan District, Qingdao City, China

Grammy Jiang's picture
Offline
Joined: 2011-09-30
Reputation: 0

This topic comes up fairly frequently. Search the archives for ?command line?.

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

Chris Jones

crollinjones's picture
Offline
Joined: 2013-12-12
Reputation: 0

Hello Grammy,

I think you have a conceptual problem with your input file. Specifically, there should be no reason to have such a large input file...ever...

Without knowing anything about your simulation I can guess that you have too many zones, floors, and/or windows/walls, etc.

Therefore, I suggest you simplify your simulation down to a basic building that has the features that you're trying to evaluate, and cut out all the extra input lines that are not having an impact on your simulation. You can also use multipliers to get the intended result.

Unfortunately, there are not a lot of websites where you can go for advice on this...one that may help is the IBPSA USA web site that has a PPT file about a simulation overview. Also, in the original DOE-2 Newsletters there use to be advice about multipliers, etc., which may also be discussed in the EQUEST/DOE-2.2 website.

If you insist that you have to have all these lines of code, then you can cut the file into pieces, make multiple runs and glue the pieces back together again using the hourly files.

Hope this helps.

Jeff

8=! 8=) :=) 8=) ;=) 8=) 8=( 8=) 8=() 8=) 8=| 8=) :=') 8=) 8=?
Jeff S. Haberl, Ph.D.,P.E.inactive,FASHRAE,FIBPSA,......jhaberl at tamu.edu
Professor........................................................................Office Ph: 979-845-6507
Department of Architecture............................................Lab Ph:979-845-6065
Energy Systems Laboratory...........................................FAX: 979-862-2457
Texas A&M University...................................................77843-3581
College Station, Texas, USA, 77843.............................http://esl.tamu.edu
8=/ 8=) :=) 8=) ;=) 8=) 8=() 8=) :=) 8=) 8=! 8=) 8=? 8=) 8=0

Jeff Haberl2's picture
Offline
Joined: 2011-10-02
Reputation: 0

Hello, everyone here,

First of all, thanks for your kind reply!

To Jones, Chris,

I have searched the key word "site:www.gard.com command line", and the
search results are not that helpful. Would you give me more specific
details?

To Daniel Knapp,

You are right. The original *BDLLIB.DAT* file in "D22s48rr52h.zip" does not
contain the library used in eQuest, good news is that the *eQ_Lib.365.dat*
is provided at the same folder with *BDLLIB.DAT*. And it is easy to insert
the content of *eQ_Lib.365.dat* into to the bottom of *BDLLIB.DAT*, they
are all text format in fact.

I see you use the windows batch to run a lot of model in once time. One
more question, generally eQuest will generate **.hsr* file automatically,
but if running the model by doe22, there is no such **.hsr* file. I know
there will be a copy in **.SIM* file, but actually the report in **.SIM*
has a little difference with **.hsr*. Do you know how to generate this
**.hsr* file by doe22? This file is in csv format and easy to deal with a
lot of program language, it will be very helpful for me.
To Jeff Haberl,

Let me do some explanation about the size of model. This is a project for
LEED, and geometry is huge, I have used multiple floors for typical floors,
but it is still huge - this 2MB size inp file is only for one tower, and I
have two towers and one podium. I know the inp generated by eQuest wizard
mode contain some useless component, but I have no time to clear these
constructions, polygons, etc. Maybe one day I can write a little script to
do this.

Btw, I have opened source one little script written in python on Github, I
am fresh about Github, any help is welcome! The mainly function of this
script is to split the *.SIM into pieces as you want, default it will split
it into two part:

- hourly report
- none hourly report

As you know, if you have a large hourly report inside, it will take a long
time to open *.SIM file. Removing the hourly report part will reduce the
waiting time a lot. Here it is:

https://github.com/grammy-jiang/eQuest-Script

To Brian Fountain,

I have heard about this one, but never check it. I will check it, thanks
for you reminding!

Best regards,

Grammy Jiang

Qingdao Create Future Environment Protection Technology Consultancy Co., Ltd

Room 6-11, Building B, International Innovation Park, Songling Road,
Laoshan District, Qingdao City, China

Grammy Jiang's picture
Offline
Joined: 2011-09-30
Reputation: 0