<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (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: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:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 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";}
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";}
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";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
--></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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">The practical rule here is exterior surfaces will only be generated along the lines that make up the building footprint, and only where the zone lines match up.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I suggest a best practice to ALWAYS lock vertices wherever you have the option. Don’t intentionally play within tolerances – they exist, but in my experience there’s much more headaches/heartaches down that
path than simply getting it done exactly right the first go around.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">As you and others have found, intentionally or by accident, the wizards have a limited resolution for defining vertices, to the second decimal place. While this normally isn’t an issue, this can occasionally
cause issues if you are defining perimeter zones along a non-orthogonal footprint line, which doesn’t have vertices to lock to. Locking to endpoints from your CAD reference can (not always) in that scenario not line up sufficiently with the footprint perimeter.
Solution here is to define additional vertices for the building footprint along such facades.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Also, when you do lock to a CAD endpoint, you might notice on zooming waaaay in that your vertex/lines might not appear perfectly in-sync against the reference. I think this is a limitation of the UI and related
to that 2-decimal “resolution,” but generally if you only appear off by a pixel or so you can rest assured things are in fact lined up. Critical thing is to ensure your footprint and zone vertices are locked together.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">~Nick<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><img width="119" height="37" id="_x0000_i1028" src="cid:image001.jpg@01CDD15F.099488C0" alt="cid:489575314@22072009-0ABB"></span><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E">NICK CATON, P.E.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900">SENIOR ENGINEER<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">Smith & Boucher Engineers</span><span style="font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">25501 west valley parkway, suite 200<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">olathe, ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">direct 913.344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">fax 913.345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span style="font-size:10.0pt">www.smithboucher.com</span></a></span><u><span style="font-size:10.0pt;color:blue">
</span></u><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> equest-users-bounces@lists.onebuilding.org [mailto:equest-users-bounces@lists.onebuilding.org]
<b>On Behalf Of </b>Jonathan Bowser<br>
<b>Sent:</b> Monday, December 03, 2012 1:22 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] eQUEST Wizard Zone Segments<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for the response, Nick. I never thought about the relationship between doors and windows as children of the exterior surface. That’s a good way to think of it.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">However, I still have some confusion as so when there is an exterior surface. From my tinkering around in the wizard, I’ve noticed various tolerances that seem to come into play with whether or not there will
be an exterior surface to place doors and windows. For example, if the edge of a zone is parallel with an exterior wall and within .45’ of that same exterior wall, then there is an exterior surface there. However, if the zone segment isn’t parallel with
the exterior wall but is within about 5 degrees of being parallel, then different distance tolerances come into play – and when this happens, the exterior surface follows the zone rather than the exterior wall.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I’m generating PD2 files outside of eQUEST, I’m trying to figure out what these “rules” are (hopefully without a huge amount of trial and error) so that I can better guarantee that the generated PD2 file provides
legitimate inputs.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">-- Jon<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><strong><span style="font-family:"Arial Narrow","sans-serif";color:black">Jonathan Bowser, MCPD</span></strong><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">Senior Software Engineer</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">Beck Technology
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">1807 Ross Avenue, Suite 500</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">Dallas, TX 75201
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">(214) 303-6815</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif""><a href="http://www.beck-technology.com/">www.beck-technology.com</a></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><strong><span style="font-family:"Arial Narrow","sans-serif";color:silver">Innovation in All Dimensions</span></strong><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:9.0pt;font-family:"Arial Narrow","sans-serif";color:green">Please consider the environment before printing this e-mail
</span><span style="color:blue"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><strong><span style="color:blue"> </span>
</strong><span style="color:blue"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:9.0pt;font-family:"Arial Narrow","sans-serif";color:black">This e-mail may be privileged and confidential. If you are not the intended recipient, please delete from all computers.</span><span style="color:blue"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Nick Caton [<a href="mailto:ncaton@smithboucher.com">mailto:ncaton@smithboucher.com</a>]
<br>
<b>Sent:</b> Friday, November 30, 2012 8:51 AM<br>
<b>To:</b> Jonathan Bowser; <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> RE: eQUEST Wizard Zone Segments<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Window & Door placements for eQuest wizards are limited to
<u>exterior</u> surfaces. This kind of makes sense when you consider in the world of eQuest, windows and doors exist only as “child” components of exterior surfaces – a means of heat transfer to/from the exterior environment.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The segment shared by both zones is automatically interpreted as an
<u>interior</u> surface (partition) and so is not one of the options for window placement.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If wish to model interior partitions containing or composed of glass, you will want to consider modifying interior constructions.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you have<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><img border="0" width="119" height="37" id="_x0000_i1025" src="cid:image001.jpg@01CDD15F.099488C0" alt="cid:489575314@22072009-0ABB"></span><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-family:"Stylus BT","sans-serif";color:#2D4D5E"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt;font-family:"Stylus BT","sans-serif";color:#2D4D5E">NICK CATON, P.E.<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900">SENIOR ENGINEER<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">Smith & Boucher Engineers</span><span style="font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">25501 west valley parkway, suite 200<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">olathe, ks 66061<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">direct 913.344.0036<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">fax 913.345.0617<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="www.smithboucher.com" title="blocked::www.smithboucher.com"><span style="font-size:10.0pt">www.smithboucher.com</span></a></span><u><span style="font-size:10.0pt;color:blue">
</span></u><span style="color:#1F497D"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:equest-users-bounces@lists.onebuilding.org">equest-users-bounces@lists.onebuilding.org</a> [<a href="mailto:equest-users-bounces@lists.onebuilding.org">mailto:equest-users-bounces@lists.onebuilding.org</a>]
<b>On Behalf Of </b>Jonathan Bowser<br>
<b>Sent:</b> Thursday, November 29, 2012 10:09 AM<br>
<b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> [Equest-users] eQUEST Wizard Zone Segments<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Is anyone familiar with the rules that govern what segments of a zone will be available in the wizard for placing windows?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As a simple example, assume I have the following footprint definition (8 vertices with 8 sketched segments) and zone footprint (4 vertices with 4 sketched segments)…<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img border="0" width="165" height="177" id="Picture_x0020_1" src="cid:image002.jpg@01CDD15F.099488C0"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Later in the wizard, for custom windows placement, this information is translated into 5 segments where windows can be placed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><img border="0" width="143" height="194" id="Picture_x0020_2" src="cid:image003.jpg@01CDD15F.099488C0"><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you look at the corresponding PD2 file, the zone has actually has more than the 4 segments even though it still only has 4 vertices.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">CustomZone "Custom Zone 1" <o:p></o:p></p>
<p class="MsoNormal"> NumVerts = 4<o:p></o:p></p>
<p class="MsoNormal"> X[1] = 0<o:p></o:p></p>
<p class="MsoNormal"> X[2] = 111.8<o:p></o:p></p>
<p class="MsoNormal"> X[3] = 111.8<o:p></o:p></p>
<p class="MsoNormal"> X[4] = 0<o:p></o:p></p>
<p class="MsoNormal"> Y[1] = 0<o:p></o:p></p>
<p class="MsoNormal"> Y[2] = 0<o:p></o:p></p>
<p class="MsoNormal"> Y[3] = 111.8<o:p></o:p></p>
<p class="MsoNormal"> Y[4] = 111.8<o:p></o:p></p>
<p class="MsoNormal"> ..<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">FacetWiz "Facet-0-4" <o:p></o:p></p>
<p class="MsoNormal"> ParentZoneIdx = 0<o:p></o:p></p>
<p class="MsoNormal"> SegmentNumber = 5<o:p></o:p></p>
<p class="MsoNormal"> ..<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In this particular scenario, it’s fairly straight forward to see how eQUEST determines the segments of the zone. However, the rules don’t appear to be super straight forward. There are angular tolerances involved, depending on what the
zone spans, it segments different, etc. Is anyone familiar with how this is done?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- Jon<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><strong><span style="font-family:"Arial Narrow","sans-serif";color:black">Jonathan Bowser, MCPD</span></strong><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">Senior Software Engineer</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">Beck Technology
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">1807 Ross Avenue, Suite 500</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">Dallas, TX 75201
</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif"">(214) 303-6815</span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-family:"Arial Narrow","sans-serif""><a href="http://www.beck-technology.com/">www.beck-technology.com</a></span><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"> <o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><strong><span style="font-family:"Arial Narrow","sans-serif";color:silver">Innovation in All Dimensions</span></strong><o:p></o:p></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:9.0pt;font-family:"Arial Narrow","sans-serif";color:green">Please consider the environment before printing this e-mail
</span><span style="color:blue"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><strong><span style="color:blue"> </span>
</strong><span style="color:blue"><o:p></o:p></span></p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="font-size:9.0pt;font-family:"Arial Narrow","sans-serif";color:black">This e-mail may be privileged and confidential. If you are not the intended recipient, please delete from all computers.</span><span style="color:blue"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif""><o:p> </o:p></span></p>
</div>
</body>
</html>