<!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">I just came on it by chance
late one night. I had a few BDL errors that I fixed, tried to run the
sim and it wouldn't run it, said I still had the errors in the BDL
file. Totally frustrated I saved the file and went to bed. Got up and
opened it in the morning, eQuest </font>initialized the cad file, ran
through the BDL error free, I ran the sim and everything worked. As
for exactly why, I do not know for sure, everything else in my comments
was speculation. I have used the re-evaluate components, doesn't
always do much. Seems to depend on what you have been changing. I
think the program just starts from scratch and rebuilds the BDL file,
the line processing order is reset. When you open the program and a
project the program always processes (compiles?) a file, and I assume
creates a new BDL file. All the information is saved in the INP file,
which is processed to create the BDL file? But I have noticed that a
lot of errors which eQuest said I had, which I had worked on to
correct, do not disappear until you force the program to redo the
initial launch process. When I think of all the hours I have
previously spent trying to fix an error, probably fixed it and threw
the fix away and then got into even more obscure ideas for a fix. It
only seems to apply to certain errors as well. Some fixes will get the
simulation to run. It is hard to track it when I don't use eQuest
every day. Sometimes I will not use it for weeks. For the time it
takes I just close the program and reopen it, 8 errors go to 3, you do
the 3 restart, and away you go, no getting lead down the garden path by
a flag which might or might not reset. This is probably why working
right in the INP file is so effective, you are fixing the error right
at the point it happens, not having something added at the end by the
wizard? I do this as well but prefer to use the wizard interface as
much as I can. Older files are handy for this as well if you delete
something you later find out is important, just go back to the old INP
file, copy what you need and put it back in the newer file. This is
something I have noticed in the INP file, the order is very important.
You can fix some errors just by changing the line order. This also had
something to do with my speculation. I had changed an item, can't
remember what, the sim wouldn't run. The error referred to the change
I had just made, I went into the INP file and saw my change further
down, after the program was making the call for the information, I
grabbed the section, moved it up before the call and the simulation
ran. That is about all the light I can shed on the subject, just an
observation about an inconsistency.<br>
Bruce<br>
<br>
On 15/06/2010 11:18 AM, Nick Caton wrote:
<blockquote
cite="mid:FCEBC0C28321F7479789B25A13030F69012C0272@sandbinc2.sbi.smithboucher.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:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@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:"Stylus BT";
panose-1:2 14 4 2 2 2 6 2 3 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 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:12.0pt;
font-family:"Times New Roman","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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Bruce,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Your
“reinitialization breakthrough” has my eyebrows
at attention! I’ve previously dug to figure out what the “reevaluate
components” and various “reinit… ” options under the ‘Tools’
menu are supposed to do, and have until now come up empty-handed… <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Are
you saying these functions perform something of a “cleaning
duty”? If anyone can offer a complete explanation of these tools
(or point me to a help file / search term), that’d be one less thing on
my “huh?” list =).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Aaron,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Bruce
has already said most of what I’d contribute to your
situation – I might only add that I now make a conscious point to do a
bit of rounding (to the first decimal place) whenever I define vertical
(z)
coordinates and floor-to-floor heights for different shells. It can
really streamline things and make it easier to get the geometries right
on the
first go. Recently I’ve thrown together fairly complex geometries
for a 5-level, 5-shell school, and I found making a quick reference
riser in my
notepad margin for each floor’s z-coordinates streamlined the process
perfectly.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I’ll
be very curious to hear whether the “reinit”
or “reevaluate” options help your situation – if you do have
pitched roofs to model, I’ll share that I’ve had nothing but
inconsistent troubles in the past using the wizard-generated pitched
roofs –
If so, I might encourage you or anyone else to consider whether a
wizard-generated
flat roof, mildly edited later in detailed mode (adding tilt and/or
breaking
into 2 pieces), might give a fair thermal approximation.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Pasha
and Bruce are right – a lot of people in the
industry make energy modeling out to be unrealistically complex and
accurate –the
end-users (I’m raising my hand) are occasionally the worst culprit!
When
you go to the hardware store to buy a hammer, would you pay for a
gold-interlaced hammer with pretty tassels, matching fashionable
holster,
built-in compass, and aerodynamic spoilers? Not to hammer things
with...
You’d simply buy a hammer. With eQuest, and indeed any energy
modeling software, we’re tasked with building a tool (the model) to
ultimately
perform a simple task. If a nail ultimately gets driven into the wood
straight, only hammer-connoisseurs might ever care how complex of a
hammer put
it there.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">~Nick<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">PS:
If anyone actually owns a hammer like that – yes, I am
making fun of you =).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><img
id="Picture_x0020_1" src="cid:part1.08070805.07080801@bellnet.ca"
alt="cid:489575314@22072009-0ABB" height="37" width="119"></span><b><span
style="font-size: 11pt; font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size: 11pt; font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span
style="font-size: 11pt; font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);">NICK
CATON, E.I.T.</span></b><b><span
style="font-family: "Stylus BT","sans-serif"; color: rgb(45, 77, 94);"><o:p></o:p></span></b></p>
<p class="MsoNormal"><span
style="font-size: 7.5pt; font-family: "Calibri","sans-serif"; color: rgb(204, 153, 0);">PROJECT
ENGINEER</span><span style="font-size: 7.5pt; color: rgb(204, 153, 0);"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">25501
west valley parkway<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">olathe
ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">direct
913 344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">fax
913 345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><i><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: rgb(45, 77, 94);">Check
out our new web-site @ </span></i><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><a
moz-do-not-send="true" href="www.smithboucher.com"
title="blocked::www.smithboucher.com"><span style="font-size: 10pt;">www.smithboucher.com</span></a></span><u><span
style="font-size: 10pt; font-family: "Calibri","sans-serif"; color: blue;">
</span></u><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><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;">
<a class="moz-txt-link-abbreviated" href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a>
[<a class="moz-txt-link-freetext" href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Bruce
Easterbrook<br>
<b>Sent:</b> Tuesday, June 15, 2010 2:21 AM<br>
<b>To:</b> Pasha Korber-Gonzalez<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">Thanks Pasha, positive feedback is nice. I'm on
a roll
after a 60 hour project. Not big, but complex. As it is fresh in my
mind I have been able to share a few new tidbits I have learned off the
top of
my head. Unfortunately a few were learned the hard way, again. The
reinitialization about the BDL file seems to be major, to me anyway.
It
seems before I was chasing a few phantom errors which I had actually
fixed but
didn't realize were fixed. Leading me down a path to never never land
thinking my fix was no good. The current building had multiple
intersecting cottage roofs on top and multiple flat roofs on lower
levels. Didn't even go there, the model has all flat roofs. Thermo
wise it will be close. That is another thing for new users, your 3D
model
does not have to look like the architects pretty rendering. eQuest is
a
thermodynamic idealization. There are limits on how much your client
wants to pay to get to get a good mechanical system. Sorry architects,
but I do find it encouraging some of you are dabbling with eQuest.
Understanding the total project and systems is the key to a great
building and
maybe a little more appreciation when your project lands on my desk,
lol.
I'm also a Joe Lstiburek fan like Nick. Another point I would like to
make is about reality on the building site. When the plumbing
contractor
drops a drain from a toilet that got moved right where your main supply
duct
was supposed to go, the sheet metal contractor uses 4 short 90's to
avoid it,
worrying about your AHU ESP of 2.55 " WC or 2.6 " WC is crazy.
Real life HVAC is not accurate to .01, except the eQuest geometry.
Besides my up to date ASHRAE manuals my next most valued quick
reference is the
fifth edition of Fan Engineering by the Buffalo Forge Company,
copyright
1949. There are very few current HVAC applications not covered in this
manual and with a psych chart (included) and a slide rule you are in
the ball
park with most of todays systems at least as far as they actually get
installed. Buffalo Forge was Willis Carrier's first engineering job
after
graduating from Cornell (1901), in an "experimental department", the
future "father of the AC industry". I have been in one old
building with a cast BF fan system still running like the day it was
installed,
and the occupants still satisfied after 70? years. My point, we have
better tools, computers, eQuest, HAP, Trace, infinitely better control
systems
and sensors, hi-efficiency motors, etc, but the basic engineering is
many
decades old. We are still re-inventing the wheel with new twists to
deal with the current reality. Calculating to .0001 is still, in
reality,
irrelevant in HVAC. The key is to simplify the model so it reflects
the
building reality reasonably close, have the model flexible enough to be
able to
test different ideas, configurations and use your computing horsepower
to run
simulations to test the different hypotheses. The model is the key,
once
it is running reliably and accurately, a new scenario is a dozen or 2
key
strokes and a press of the sim button. The other defining reality is
how
much your customer wants to pay for this information, somewhere between
as
little as possible and not much, lol.<br>
Time to get some sleep!<br>
Bruce<br>
<br>
<br>
On 15/06/2010 12:10 AM, Pasha Korber-Gonzalez wrote: <o:p></o:p></p>
<div>
<p class="MsoNormal">Bruce-you've been comin' in pretty heavy
yourself on
this forum and I concur with your explanations & comments/advice to
Aaron
and other new users of eQuest. Put very well and sincere. Bruce
stated the reality of the need for accuracy & efficiency in setting
up any
energy model. After foolishly having faith in my eQuest files' ability
to
run smoothly from start to finish, I have adopted the "Save As"
approach for all of my project files, and like Bruce stated, "Never get
30
hours in without testing and running it many times on the path...the
simulation
at this point is for confirmation your model is running and [free of
errors.]"<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Aaron-you might want to send us your .pd2 &
.inp files
so we can see the error(s) you are experiencing. I think Bruce is on
the
right track that it might be an external surface. Do you have a
pitched
roof on your model?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;">Pasha<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On Mon, Jun 14, 2010 at 7:50 PM, Bruce
Easterbrook <<a moz-do-not-send="true"
href="mailto:bruce5@bellnet.ca">bruce5@bellnet.ca</a>> wrote:<o:p></o:p></p>
<div>
<p class="MsoNormal"> 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 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>
<span style="color: rgb(136, 136, 136);">Bruce</span> <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
<br>
On 14/06/2010 06:43 PM, Dahlstrom, Aaron wrote: <o:p></o:p></p>
<div>
<p class="MsoNormal" style=""><span style="color: windowtext;">Bruce
– </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;">The
error shows up when I attempt to
“finish” the DD wizard.</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;">When I
look through the PD2 file and the INP file in
Notepad, neither have any explicit errors in them.</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;">The
PD2 file does have -</span><o:p></o:p></p>
<p><span style="color: windowtext;">1)</span><span
style="font-size: 7pt; color: windowtext;"> </span><span
style="color: windowtext;">RoofZoneErrorCode = 4</span><o:p></o:p></p>
<p><span style="color: windowtext;">2)</span><span
style="font-size: 7pt; color: windowtext;"> </span><span
style="color: windowtext;">TOUPeriodErrSeas1 = " "</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="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.</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="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.</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;">Thanks
for trying!</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;">Any
other suggestions?</span><o:p></o:p></p>
<p class="MsoNormal" style=""><span style="color: windowtext;"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="font-size: 9pt; line-height: 150%; color: gray;">Aaron
Dahlstrom , PE, LEED® AP</span></b><o:p></o:p></p>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="color: rgb(23, 54, 93);">In P</span></b><b><span
style="color: rgb(97, 148, 40);">o</span></b><b><span
style="color: rgb(23, 54, 93);">sse</span></b><span
style="font-size: 9pt; line-height: 150%; color: gray;"> – </span><span
style="font-size: 8pt; line-height: 150%; color: gray;">A subsidiary of</span><span
style="font-size: 9pt; line-height: 150%; color: gray;"> </span><b><span
style="font-size: 9pt; line-height: 150%; color: rgb(204, 0, 0);">AKF</span></b><span
style="font-size: 9pt; line-height: 150%; 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%; 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" style=""><span
style="font-size: 9pt; color: gray;">e: <a moz-do-not-send="true"
href="mailto:ADahlstrom@in-posse.com" target="_blank">ADahlstrom@in-posse.com</a>
| in posse web: <a moz-do-not-send="true"
href="http://www.in-posse.com/" target="_blank">www.in-posse.com</a> |
akf web:
<a moz-do-not-send="true" href="http://www.akfgroup.com/"
target="_blank">www.akfgroup.com</a></span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; color: gray;"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; color: gray;"> </span><o:p></o:p></p>
<div>
<div
style="border-style: solid none none; border-color: -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal" style=""><b><span
style="font-size: 10pt; color: windowtext;">From:</span></b><span
style="font-size: 10pt; color: windowtext;"> Bruce Easterbrook [<a
moz-do-not-send="true" href="mailto:bruce5@bellnet.ca" target="_blank">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 moz-do-not-send="true"
href="mailto:equest-users@lists.onebuilding.org" target="_blank">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> Re: [Equest-users] dd wizard - invalid argument</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">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" style="">Folks:<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">I
have gotten the following error several times on the same project.<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">I
have rebuilt the file from scratch already once, and I’m wondering if
there is another way to fix this error.<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">Any
idea if there are reports or INIs that I can view / modify to find out
where
exactly this “invalid argument” is located?<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style=""><img id="_x0000_i1025"
src="cid:part2.02030707.07000304@bellnet.ca" border="0" height="159"
width="313"><o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="">Thanks!<o:p></o:p></p>
<p class="MsoNormal" style=""> <o:p></o:p></p>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="font-size: 9pt; line-height: 150%; color: gray;">Aaron
Dahlstrom , PE, LEED® AP</span></b><o:p></o:p></p>
<p class="MsoNormal" style="line-height: 150%;"><b><span
style="color: rgb(23, 54, 93);">In P</span></b><b><span
style="color: rgb(97, 148, 40);">o</span></b><b><span
style="color: rgb(23, 54, 93);">sse</span></b><span
style="font-size: 9pt; line-height: 150%; color: gray;"> – </span><span
style="font-size: 8pt; line-height: 150%; color: gray;">A subsidiary of</span><span
style="font-size: 9pt; line-height: 150%; color: gray;"> </span><b><span
style="font-size: 9pt; line-height: 150%; color: rgb(204, 0, 0);">AKF</span></b><span
style="font-size: 9pt; line-height: 150%; 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%; 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" style=""><span
style="font-size: 9pt; color: gray;">e: <a moz-do-not-send="true"
href="mailto:ADahlstrom@in-posse.com" target="_blank">ADahlstrom@in-posse.com</a>
| in posse web: <a moz-do-not-send="true"
href="http://www.in-posse.com/" target="_blank">www.in-posse.com</a> |
akf web:
<a moz-do-not-send="true" href="http://www.akfgroup.com/"
target="_blank">www.akfgroup.com</a></span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><span
style="font-size: 9pt; color: gray;"> </span><o:p></o:p></p>
<p class="MsoNormal" style=""><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></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"
target="_blank">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" target="_blank">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre>
<pre> <o:p></o:p></pre>
</div>
<p class="MsoNormal"><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></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><br>
_______________________________________________<br>
Equest-users mailing list<br>
<a moz-do-not-send="true"
href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"
target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>
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></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
</body>
</html>