[Equest-users] Strange errors in file- HELP!
Patrick J. O'Leary, Jr.
poleary1969 at gmail.com
Fri Jul 9 11:48:03 PDT 2010
one thing you can do is make changes to the .pd2 and .inp files using
notepad once you've figured out what you need to change. for example,
if your EL3 East Perim Plnm (G.E6) was referenced but is no longer
defined, you have a plenum space that belonged to a space that changed
names during a zoning change. look at the .inp file line number, find
out which space the EL3 East Perim Plnm (G.E6) is supposed to correlate
to and change the name accordingly - in the .inp file. once these
references are corrected the simulation should run fine.
you're probably looking at changing EL3 East Perim Plnm (G.E6) to
whatever the new space name is (checking what comes before line 14898
can put you in the right direction on finding the correct name to change to.
and when you have a working simulation always backup your .pd2 (wizard
mode) and/or .inp (detailed mode) files even if you just copy them in
the same directory.
*ERROR****************************************************************************************
*ERROR*****EL3 East Perim Plnm (G.E6) was referenced on line 14898 but never
defined.
*ERROR****************************************************************************************
*ERROR*****EL3 West Perim Spc (G.W4) was referenced on line 15237 but never
defined.
*ERROR****************************************************************************************
*ERROR*****EL3 WNW Perim Plnm (G.WNW7) was referenced on line 15377 but
never
defined.
On 7/9/10 11:23 AM, Carol Gardner wrote:
> Hmm. Well I'm not sure I understand exactly what you are asking, but
> here are my recommendations. Finish what you need to do in DDWizard
> and get out of it. I wouldn't even try to make the changes you are
> trying to make while in the Wizard.
>
> Don't fear DD edit. You can do things in it just as easily as in the
> Wizard, and if you get stuck we'll help. Like I said earlier, the
> easiest way to see what and where the error is, is to open up the .bdl
> and .inp files. That might be even scarier to you than DD edit, and
> that's okay, you should be scared. You can mess up in a hurry but with
> careful work you won't.
>
> Take a deep breath and get out of the Wizard!!
>
> Cheers,
> Carol
>
> On Fri, Jul 9, 2010 at 11:11 AM, Paul Brooks <equestpaul at yahoo.com
> <mailto:equestpaul at yahoo.com>> wrote:
>
> Carol, Dave, and Mtt:
> Thank you for the replies. I did look in the BDL file, but did
> not realize I had to update the inp.
> That being said, am I safe in assuming that, if I stay in the
> DDwizard (not quite ready to leave yet), every time i add
> information and compile, I will have the same error. The root
> cause of the error is in the interface, correct? If that is the
> case, then the reality is it just cannot be fixed unless i change
> the inp file after compiling?
> Thank you again!
>
>
> ------------------------------------------------------------------------
> *From:* Carol Gardner <cmg750 at gmail.com <mailto:cmg750 at gmail.com>>
> *To:* Paul Brooks <equestpaul at yahoo.com <mailto:equestpaul at yahoo.com>>
> *Cc:* eQuest user forum <equest-users at lists.onebuilding.org
> <mailto:equest-users at lists.onebuilding.org>>
> *Sent:* Fri, July 9, 2010 1:32:58 PM
> *Subject:* Re: [Equest-users] Strange errors in file- HELP!
>
> Hi Paul,
>
> Here's my strategy when this happens to me. I open the *.inp* file
> and the *.bd*l file in Word. I then use the Edit, Find feature and
> search on ERROR in the *.bdl* file. When I find the line that the
> error is occurring in I then fix it in the *.inp* file. Repeat
> until all errors gone. You probably have an existing space that
> shared an interior wall with your now deleted space and is trying
> to reference it using" NEXT-TO". Be sure to fix the error in the
> *.inp* file not the .bdl file, which I have done a few times. This
> is one example of why it is good to familiarize yourself with the
> Building Descriptive Language (BDL): you can make these sorts of
> fixes much easier in your input deck using than trying to figure
> it out in DD edit. Just be sure not to delete any delimiters (..)
>
> Let me know how you do..
>
> Carol
>
> On Fri, Jul 9, 2010 at 8:33 AM, Paul Brooks <equestpaul at yahoo.com
> <mailto:equestpaul at yahoo.com>> wrote:
>
> I am modeling an addition to an existing building. I
> originally did the shell/zoning using just the original
> building. I then, after saving a back up copy of the base
> building, i went back to the shell and zone drawing screens in
> the DD wizard and expanded the shell to account for the
> addition, and then went into the zone creation and adjusted my
> zones. I was sure to follow the rules about matching
> verticies, etc.
> Now i am getting errors concerning the zone and plenum. It
> appears that the program is still seeing plenums and walls
> that are now non-existent. The program says that plenums are
> being referenced but are not defined (see error message below).
> Anyone got any ideas on how to clear this?
>
> *ERROR****************************************************************************************
>
> *ERROR*****EL3 East Perim Plnm (G.E6) was referenced on line
> 14898 but never
>
> defined.
>
> *ERROR****************************************************************************************
>
> *ERROR*****EL3 West Perim Spc (G.W4) was referenced on line
> 15237 but never
>
> defined.
>
> *ERROR****************************************************************************************
>
> *ERROR*****EL3 WNW Perim Plnm (G.WNW7) was referenced on line
> 15377 but never
>
> defined.
>
> **************************************** 5 ERRORS
>
> **************************************** 2 WARNINGS
>
> **************************************** 103 CAUTIONS
>
> *20195* COMPUTE ..
>
> *20196* STOP ..
>
> **************************************** 5 ABORT-LEVEL
> DIAGNOSTICS
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100709/02e4b08e/attachment-0001.htm>
More information about the Equest-users
mailing list