[Equest-users] eQUEST Wizard Zone Segments

Nick Caton ncaton at smithboucher.com
Fri Nov 30 06:51:20 PST 2012


Window & Door placements for eQuest wizards are limited to exterior 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.

The segment shared by both zones is automatically  interpreted as an interior surface (partition) and so is not one of the options for window placement.

If wish to model interior partitions containing or composed of glass, you will want to consider modifying interior constructions.

If you have

[cid:489575314 at 22072009-0ABB]

NICK CATON, P.E.
SENIOR ENGINEER

Smith & Boucher Engineers
25501 west valley parkway, suite 200
olathe, ks 66061
direct 913.344.0036
fax 913.345.0617
www.smithboucher.com

From: equest-users-bounces at lists.onebuilding.org [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Jonathan Bowser
Sent: Thursday, November 29, 2012 10:09 AM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] eQUEST Wizard Zone Segments

Is anyone familiar with the rules that govern what segments of a zone will be available in the wizard for placing windows?

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)...

[cid:image002.jpg at 01CDCE40.48E44280]

Later in the wizard, for custom windows placement, this information is translated into 5 segments where windows can be placed.

[cid:image003.jpg at 01CDCE40.48E44280]

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.

CustomZone   "Custom Zone 1"
   NumVerts = 4
   X[1] = 0
   X[2] = 111.8
   X[3] = 111.8
   X[4] = 0
   Y[1] = 0
   Y[2] = 0
   Y[3] = 111.8
   Y[4] = 111.8
   ..

FacetWiz   "Facet-0-4"
   ParentZoneIdx = 0
   SegmentNumber = 5
   ..

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?

-- Jon



Jonathan Bowser, MCPD

Senior Software Engineer

Beck Technology

1807 Ross Avenue, Suite 500

Dallas, TX 75201

(214) 303-6815

www.beck-technology.com<http://www.beck-technology.com/>



Innovation in All Dimensions

Please consider the environment before printing this e-mail



This e-mail may be privileged and confidential. If you are not the intended recipient, please delete from all computers.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121130/f309b927/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1459 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121130/f309b927/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 2572 bytes
Desc: image002.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121130/f309b927/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3151 bytes
Desc: image003.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20121130/f309b927/attachment-0008.jpg>


More information about the Equest-users mailing list