<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Times New Roman, Times, serif"> You did have an error in
your electric rate but obviously if it is not now involved it probably
is not the main problem. That leaves the roof. If you have several
custom floors when you create them in the DD wizard they will all have
roofs. If they are stacked you will have embedded roofs if</font> you
have not gone in and removed them which you can't do in the DD wizard.
They will only effect floor to floor heat transfer and maybe eQuest
will give them a solar load I don't know. eQuest will run with them if
they are technically (geometrically) correct. The problem is you can't
see them in the 3D view if they are covered by other floors and easy
visual check to see if they are geometrically correct is not possible.
That will cause eQuest to crash. You may be able to cheat a little.
eQuest will show external surfaces in a red outline in the 3D view. If
this is may be your problem go to the building shell tab to one of the
floors and highlight the roof in tree pane. Switch to your 3D view and
hold your control key and with your left mouse held down rotate the 3D
model. It will switch to wire frame and the roof surface will be
highlighted in red. I can't remember how to turn on the wire frame
view but that is possible to do as well. Maybe someone monitoring this
will refresh my memory. I think you have a roof geometry problem and
geometry problems are a pain in the ass.<br>
The other thing I have noticed and I'm not sure quite why but if
there was an error and you have corrected it, the program may have not
actually accommodated the change yet. My guess is, the program runs in
a linear fashion start to finish. A change will probably get added to
the end of the program as a addition or change. When the program is
run again it is using the original file and then the additions, but the
error is still there and the program hits it first and crashes. I have
found when doing major changes it is best just to save the file, close
it and re-open it. eQuest will then reorder the file and it probably
won't crash if you did correct the error. Run a simulation and you
will get much better error messages as to what the problem is. I have
adjusted my trouble shooting technique to this method in the last few
weeks and have seen many errors disappear once the file is
reinitialized. It has saved many hours of banging my head on the wall.<br>
This is not specifically for you Aaron, just a general observation
(tangent). I have noticed a few guides in the last week or so to help
new comers but no one has mentioned reinitializing the project. It may
be an obscure point but I think it saved me about 30% of my hours on my
latest project. One of the biggest things with eQuest is to get it
running and keep it running as you build your model. Start simple,
initially, heat transfer surfaces are important, zones are important,
windows are not, schedules are not, utilities are not, constructions
are not, layers are not, HVAC systems and their zones are not.
Geometry is CRITICAL. eQuest will choke with a vertex error of .01,
Carol(e) is "anal on this point", lol, but she knows what she is
talking about. She and Pasha both agree and no doubt will add wisdom
if they have any pointers to add. I should add a plug for Nick as
well, another heavy hauler on this site with major experience beyond
his years. Start simple, get the box(es), and surfaces correct. Zones
initially can be artificial with the future HVAC system in mind <u>but
also</u> to assist with the geometry. Specifically, in dealing with
other floors and roofs. An un-named eQuest instructor will attest to
this, it is easier to manipulate your zoning to assist in your geometry
problems and put them together later to accommodate your HVAC model
than create the surfaces on the fly in detailed edit. Especially with
40 students watching! eQuest can be humbling even for experts. NEVER
get 30 hours in without testing and running it many times on the path.
Lots of saves, build your files as well as the model. The simulation
at this point is for confirmation your model is running and for error
messages. A tiny error in geometry will crash the file. There is no
point doing anything but the bare minimum until the geometry is
correct. It will crash your project with minimal error messages, maybe
none, eQuest will just freeze. Once the geometry is correct keep
adding to the complexity one step at a time, test and confirm, fix
errors, save, then the next step. I know it sounds plodding, it is.
Methodical is a much classier word. Efficient is more to the point. I
contract so when everything blows up I don't get paid. I eat the hours
for my mistakes. In the end it is all similar, whether it is the boss
pounding on the door or the client, the deadline has arrived, eQuest is
not cooperating and you are ready to toss the computer out the window,
your name is mud. Plodding is smart.<br>
Sorry for the digression Aaron, the Voodoo thread was interesting
and I didn't get to add my 2 cents worth. I was in a swamp with
alligators at the time. On the other hand I did learn a lesson about
reinitialization. You learn by doing and making mistakes. <br>
Bruce<br>
<br>
On 14/06/2010 06:43 PM, Dahlstrom, Aaron wrote:
<blockquote
cite="mid:22CE8791E7DE554FB00676D7248C6B55253E2613@AKFMAILPA.AKF-ENG.COM"
type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Verdana;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"AvantGarde Bk BT";
        panose-1:2 11 4 2 2 2 2 2 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";
        color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:windowtext;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1933053658;
        mso-list-type:hybrid;
        mso-list-template-ids:-1250801932 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-text:"%1\)";
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">Bruce
–
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">The
error shows
up when I attempt to “finish” the DD wizard.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">When
I look
through the PD2 file and the INP file in Notepad, neither have any
explicit errors
in them.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">The
PD2 file
does have -<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent: -0.25in;"><!--[if !supportLists]--><span
style="font-size: 12pt; color: windowtext;"><span style="">1)<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span><!--[endif]--><span
style="font-size: 12pt; color: windowtext;">RoofZoneErrorCode = 4<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent: -0.25in;"><!--[if !supportLists]--><span
style="font-size: 12pt; color: windowtext;"><span style="">2)<span
style="font-family: "Times New Roman"; font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-size-adjust: none; font-stretch: normal; -x-system-font: none;">
</span></span></span><!--[endif]--><span
style="font-size: 12pt; color: windowtext;">TOUPeriodErrSeas1 = " "<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">I
can get <b><i>into
</i></b>the wizard just fine, and all the data appears correct. The
problem is
that when I “finish” the program crashes.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">I
just
experimented with removing the TOU electric rate, and again, when I hit
“finish”
it crashes eQUEST with the error noted below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">Thanks
for
trying!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;">Any
other
suggestions?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 12pt; color: windowtext;"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">Aaron
Dahlstrom , PE, LEED® AP</span></b><span style="color: windowtext;"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="font-family: "AvantGarde Bk BT","sans-serif"; color: rgb(23, 54, 93);">In
P</span></b><b><span
style="font-family: "AvantGarde Bk BT","sans-serif"; color: rgb(97, 148, 40);">o</span></b><b><span
style="font-family: "AvantGarde Bk BT","sans-serif"; color: rgb(23, 54, 93);">sse</span></b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">
– </span><span
style="font-size: 8pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">A
subsidiary of</span><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">
</span><b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: rgb(204, 0, 0);">AKF</span></b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">|
1500 Walnut Street, Suite 1414, Philadelphia, PA 19102 </span><span
style="color: windowtext;"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height: 150%;"><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">d:
215-282-6753| m: 267-507-5470| In Posse: 215-282-6800| AKF:
215-735-7290</span><span style="color: windowtext;"><o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; font-family: "Verdana","sans-serif"; color: gray;">e:
<a class="moz-txt-link-abbreviated" href="mailto:ADahlstrom@in-posse.com">ADahlstrom@in-posse.com</a> | in
posse web: <a moz-do-not-send="true" href="http://www.in-posse.com/">www.in-posse.com</a>
| akf web: <a moz-do-not-send="true" href="http://www.akfgroup.com/">www.akfgroup.com</a></span><span
style="color: windowtext;"><o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; font-family: "Verdana","sans-serif"; color: gray;"> </span><span
style="color: windowtext;"><o:p></o:p></span></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; font-family: "Verdana","sans-serif"; color: gray;"> </span><span
style="color: windowtext;"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size: 9pt; font-family: "Times New Roman","serif"; color: gray;"> </span><span
style="font-size: 12pt; color: windowtext;"><o:p></o:p></span></p>
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
Bruce Easterbrook
[<a class="moz-txt-link-freetext" href="mailto:bruce5@bellnet.ca">mailto:bruce5@bellnet.ca</a>] <br>
<b>Sent:</b> Monday, June 14, 2010 5:21 PM<br>
<b>To:</b> Dahlstrom, Aaron<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> Re: [Equest-users] dd wizard - invalid argument<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It depends where you are in the process. If you
are
getting a detailed sim report it should open to the errors part of the
report. If you aren't that far open the project BDL or INP files with
notepad. They will list warnings and errors as they are processed.
The error will be at the end, there may be contributing errors before.
All it really does is tell you where it kicked out, but it does provide
clues.
When you run your simulation make sure the boxes are checked so it will
run
through errors and warnings. You get better hints this way.<br>
Bruce Easterbrook P.Eng.<br>
Abode Engineering<br>
<br>
On 14/06/2010 04:56 PM, Dahlstrom, Aaron wrote: <o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;">Folks:</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;">I have gotten the
following
error several times on the same project.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;">I have rebuilt
the file from
scratch already once, and I’m wondering if there is another way to fix
this error.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;">Any idea if there
are reports
or INIs that I can view / modify to find out where exactly this
“invalid
argument” is located?</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"><img
id="Picture_x0020_1" src="cid:part1.08030905.03010709@bellnet.ca"
border="0" height="159" width="313"></span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;">Thanks!</span><o:p></o:p></p>
<p class="MsoNormal"><span style="font-size: 12pt;"> </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">Aaron
Dahlstrom
, PE, LEED® AP</span></b><o:p></o:p></p>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="font-family: "AvantGarde Bk BT","sans-serif"; color: rgb(23, 54, 93);">In
P</span></b><b><span
style="font-family: "AvantGarde Bk BT","sans-serif"; color: rgb(97, 148, 40);">o</span></b><b><span
style="font-family: "AvantGarde Bk BT","sans-serif"; color: rgb(23, 54, 93);">sse</span></b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">
– </span><span
style="font-size: 8pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">A
subsidiary of</span><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">
</span><b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: rgb(204, 0, 0);">AKF</span></b><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">|
1500 Walnut Street, Suite
1414, Philadelphia, PA 19102 </span><o:p></o:p></p>
<p class="MsoNormal" style="line-height: 150%;"><span
style="font-size: 9pt; line-height: 150%; font-family: "Verdana","sans-serif"; color: gray;">d:
215-282-6753|
m: 267-507-5470| In Posse: 215-282-6800| AKF: 215-735-7290</span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 9pt; font-family: "Verdana","sans-serif"; color: gray;">e:
<a moz-do-not-send="true" href="mailto:ADahlstrom@in-posse.com">ADahlstrom@in-posse.com</a>
| in posse web: <a moz-do-not-send="true"
href="http://www.in-posse.com/">www.in-posse.com</a> | akf
web: <a moz-do-not-send="true" href="http://www.akfgroup.com/">www.akfgroup.com</a></span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 9pt; font-family: "Verdana","sans-serif"; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 9pt; font-family: "Verdana","sans-serif"; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 9pt; font-family: "Times New Roman","serif"; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size: 12pt; font-family: "Times New Roman","serif";"><br
clear="all">
This e-mail may contain information that is confidential, privileged or
otherwise protected from disclosure. If you are not an intended
recipient of
this e-mail, do not duplicate or redistribute it by any means. Please
delete it
and any attachments and notify the sender that you have received it in
error.
Unintended recipients are prohibited from taking action on the basis of
information in this e-mail. E-mail messages may contain computer
viruses or
other defects, may not be accurately replicated on other systems, or
may be
intercepted, deleted or interfered without the knowledge of the sender
or the
intended recipient. If you are not comfortable with the risks
associated with
e-mail messages, you may decide not to use e-mail to communicate with
In Posse.
<o:p></o:p></span></p>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>Equest-users mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true"
href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><o:p></o:p></pre>
<pre>To unsubscribe from this mailing list send a blank message to <a
moz-do-not-send="true"
href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
<br clear="all">
This e-mail may contain information that is confidential, privileged or
otherwise protected from disclosure. If you are not an intended
recipient of this e-mail, do not duplicate or redistribute it by any
means. Please delete it and any attachments and notify the sender that
you have received it in error. Unintended recipients are prohibited
from taking action on the basis of information in this e-mail. E-mail
messages may contain computer viruses or other defects, may not be
accurately replicated on other systems, or may be intercepted, deleted
or interfered without the knowledge of the sender or the intended
recipient. If you are not comfortable with the risks associated with
e-mail messages, you may decide not to use e-mail to communicate with
In Posse.
</blockquote>
</body>
</html>