eQUEST logic statements

3 posts / 0 new
Last post

Greetings,

I have not had any real experience using logic statements in eQUEST and
am wondering if there is anyone out there proficient in using such
techniques in their model developments. I have seen the 'User-Defined
Default Expression' option where logic commands can be entered, but have
not been able to figure out good uses for this tool. I have seen how it
can be useful in making building parameters interdependent, but this is
often not needed in the model I construct.

I would appreciate it if someone could share a good document (or
information otherwise) that would have some examples with applicable
language for the user-defined default expression.

Related to this, is it possible to systematically change certain defined
values (LPD, infiltration, etc...) by a factor to create new defined
values?

Thanks in advance,
Mike Smith

Mike Smith's picture
Offline
Joined: 2011-10-02
Reputation: 0

Mike-

I've done various things using with logic statements in eQuest but usually
find that they create more problems then they solve. Simple logic
statements work fine but when I create long statements they seem to get cut
off and corrupt my .inp file. Does anyone else share this opinion? I'm
curious to see if complex logic statements can be incorporated without
errors. For example, I've created scripts that pull Occupancy, Heat Gain,
LPD, and EPD values based on the schedules assigned to the spaces. They
usually work first time but once I re-open my model it becomes corrupted. I
think this has something to do with DOE2/eQuest only being able to read a
certain amount of characters per line. Any thoughts?

Steve Mignogna

Steve Mignogna's picture
Offline
Joined: 2011-09-30
Reputation: 0

Steve,

Yes, you can only use 80 characters on a DOE2 BDL line. You'll either
need to break up your logic conditions or try using shorter variable
names.

Scott Horowitz

Horowitz, Scott2's picture
Joined: 2011-10-02
Reputation: 0