[Equest-users] Weird error, possibly model size? - ANSWER

[James Hansen]

Once again the members of this list have been invaluable!

 

Thanks Susan, Jeff and Scott for having the right answer (a minor line
code add to the pd2 file).

 

See Scott's email below.  It worked perfectly:

 

---------- Forwarded message ----------
From: Scott Criswell <scott.criswell at doe2.com>
Date: Thu, Jan 28, 2010 at 4:52 PM
Subject: Re: [Equest-users] Utility Rate Errors
To: Susan F <modelsenergy at gmail.com>

You have run up against a hard-coded limit on BDL default expression
dependency lists.
The following is a message I sent to another user after investigating
and dealing w/ a similar issue they encountered.  Given that the error
doesn't occur until you are processing the utility rates, you probably
can get away w/ implementing #1 below - unless you have more complexity
yet to add to your project.
---------------
You exceeded a more hard-coded limit in this project - one having to do
with BDL's default expression mechanism.  BDL allows for just under
1,000,000 expression dependency lists (each keeps track of all
dependencies that a single BDL expression references), but this didn't
cut it for your project.
I was however able to change a couple of things to squeeze the project
in under the wire.

(1)  I added the following line immediately before the trailing '..' of
the Project component definition in the project's PD2 file:
   DetailedModelEdits = 1
   ProjTreeType = ( 1, 1, 1, 1, 1, 1 )
   ProjTreeID = ( 10240000, 10081500, 10280021, 10640002, 10480018, 
                  10280020 )
   ProjTreeLabel = ( "...", "...", "...", "...", "...", "..." )
   MaxExpDeps = 10
   ..
What the MaxExpDeps property does is specify the maximum number of
separate global parameter and local & parent keyword references each
expression in the model is able to specify.  The default is 12, which is
pretty excessive.  By lowering this to 10, we increase the maximum
number of exp dep lists from 924K -> 1M.  But of course, your project
required even MORE.

(2)  I then went into <eQ Data>\DOE-2\BDLDft.dat (modified version
attached) and blasted all "C-" keyword default expressions, which are
only needed for models utilizing the Title-24 (or soon to be LEED
baseline generation) analysis capabilities.  By doing this, we help to
minimize the number of default expressions (also counted in the overall
limit).  Not sure exactly what the # of exp dep lists was after this
change, but it seemed to work.  The model now loads w/ no errors and
simulates.

If you have much/any complexity to still add to the project, one or more
of the following changes will likely be required:
- BDL source code mods to increase the limit of exp dep lists,
- removal of some fraction of the expressions contained in your INP
file, and/or
- the addition of Set-Default statements in your INP file that replace
additional BDL default expressions with static values or symbolic
selections. 
-------------------------------------------------

Hope this helps.

- Scott

From: Susan F [mailto:modelsenergy at gmail.com] 
Sent: Friday, May 14, 2010 3:25 PM
To: James Hansen
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Weird error, possibly model size?

 

Yes, I have had this problem and it is related to the size.  I will look
for the information I received about it and pass it along.  

On Fri, May 14, 2010 at 1:22 PM, James Hansen <JHANSEN at ghtltd.com>
wrote:

I've got a fairly big building model, and I'm getting the following
error.  Has anyone ever seen this "maximum number of expression
dependency" error?

 

It happens when loading up a specific System zone (the E28 North Perim
Zn (B.N48) everytime, and then causes weird things to occur in
everything defined AFTER that error.

 

I checked the input file, and nothing is different with that particular
zone.

 

If I delete the system associated with that zone, assign the zone to
another system, then the error happens on the NEXT component defined
(the next system).  To me it seems like it might be a size limitation in
eQuest.

 

I can't send out the .inp file, but was wondering if anyone has seen
this?

 

Could it be the fact that the model is so big?  115k lines of code when
this happens.

 

Thanks in advance!

 

Error! Filename not specified.

________________________________

The information contained in this communication is confidential, may be
privileged, and is intended only for the use of the addressee.  It is
the property of GHT Limited.  Unauthorized use, disclosure or copying of
this communication or any part thereof is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify me immediately by return e-mail or by e-mail to ght at ghtltd.com
<mailto:ght at ghtltd.com> , and destroy this communication and all copies
thereof, including all attachments.  Thank you.


_______________________________________________
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

 


The information contained in this communication is confidential, may be privileged, and is intended only for the use of the addressee.  It is the property of GHT Limited.  Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful.  If you have received this communication in error, please notify me immediately by return e-mail or by e-mail to ght at ghtltd.com, and destroy this communication and all copies thereof, including all attachments.  Thank you.



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