<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 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:"Century Gothic";
panose-1:2 11 5 2 2 2 2 2 2 4;}
@font-face
{font-family:Mistral;}
/* 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;}
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";}
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;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";
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="4098" />
</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=Section1>
<p class=MsoNormal><span style='color:#1F497D'>I would suggest side-to-side
over stacked.<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 position via coordinates,
and can get the adjacent planes to be in the same locations, eQuest recognize
the coincident planes and automate a number of things for you. You cannot
do this via stacking shells on top of each other.<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’d suggest reviewing some
specifics regarding how you go about positioning your shells from this mailing list
discussion. I can’t seem to find it in the archive to link to, but
Scott Criswell outlined some pointers pretty helpful to the task at hand.
I’ve copied the discussion down below for your review =). <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’d also suggest
bookmarking this archive search page if you haven’t already – you’ll
find more information regarding shell placement if you find further trouble
getting your shells to line up just right: <a
href="http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/">http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/</a><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_i1031" src="cid:image001.jpg@01CAC137.F5C39C80"
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-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><b><span style='font-size:12.0pt;
font-family:"Stylus BT","sans-serif";color:#2D4D5E'><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</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<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><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><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>Alex Krickx<br>
<b>Sent:</b> Thursday, March 11, 2010 4:11 PM<br>
<b>To:</b> Amandeep Singh; equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] How to model a bldg with different roof
levels?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>It might be easier to make the
two shells stacked instead of side-by-side. That way, you can specify that the
top shell is open to below and by zoning the bottom shell properly, you can
make the part with the high ceiling open to above. Just a thought.<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'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Alex Krickx<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:#262F13'>Alex Krickx<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:gray'>Building Energy
Specialist<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:8.0pt;color:#1F497D'><img border=0
width=121 height=42 id="_x0000_i1025" src="cid:image002.jpg@01CAC137.F5C39C80"
alt="email_sig"></span><span style='color:#1F497D'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>1250 Elko Dr,
Sunnyvale, CA 94089<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:#1F497D'>(t) 408.541.8124<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:9.0pt;color:gray'><o:p> </o:p></span></p>
<p class=MsoNormal><b><i><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:#1F497D'>Warning:</span></i></b><i><span style='font-size:7.5pt;
font-family:"Arial","sans-serif";color:#1F497D'> The information contained
in this e-mail may be privileged attorney-client communications or attorney
work product and/or proprietary and confidential. If the reader of this
message is not the intended recipient then you have received it in error and
any review, distribution or copying of this message is prohibited and you are
to notify us immediately by reply e-mail and delete the original message
immediately.</span></i><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><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>Amandeep
Singh<br>
<b>Sent:</b> Thursday, March 11, 2010 1:58 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] How to model a bldg with different roof levels?<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hello everyone,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I was trying to model a bldg with 50% area at 25 feet high
and remaining area at 10 feet. How can I specify different heights in the
footprint of this bldg. in eQUEST? I tried to draw in DD Wizard. First I drew
a footprint with 25-foot height, then I tied to create a new shell with 10-foot
height. I wasn’t able to put two shells together. Also, I didn’t
know how to change exterior walls to interior. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Any help would be appreciated .<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Regards,<o:p></o:p></p>
<p class=MsoNormal>Aman <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<table class=MsoNormalTable border=0 cellpadding=0 width=596 style='width:447.0pt'>
<tr style='height:96.0pt'>
<td width=277 valign=top style='width:207.75pt;padding:1.5pt 1.5pt 1.5pt 1.5pt;
height:96.0pt'>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif";
color:#1F497D'><img border=0 width=267 height=68 id="_x0000_i1030"
src="cid:image003.jpg@01CAC137.F5C39C80"
alt="http://www.energycenter.org/uploads/CCSE-email-logo.jpg"></span><span
style='font-size:12.0pt'><o:p></o:p></span></p>
</td>
<td width=305 valign=top style='width:228.75pt;padding:1.5pt 1.5pt 1.5pt 1.5pt;
height:96.0pt'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Amandeep Singh</span></b><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>
Energy Engineer</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>8690 Balboa Ave,
Suite 100<br>
San Diego, CA 92123-1502<br>
858.634.4729 <span style='color:#666666'>phone</span><br>
858.244.1178<span style='color:#666666'> fax</span><br>
<a href="http://www.energycenter.org/"><span style='color:black'>www.energycenter.org</span></a><span
style='color:#666666'> web</span><o:p></o:p></span></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'><o:p> </o:p></span></p>
</td>
</tr>
</table>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<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"'> Scott Criswell
[mailto:scott.a.criswell@gmail.com] <br>
<b>Sent:</b> Monday, November 23, 2009 12:49 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Cc:</b> Nick Caton; Smith, Aaron Matthew<br>
<b>Subject:</b> Re: [Equest-users] Roof monitor "Open to Below"<o:p></o:p></span></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Just wanted to clarify something that could possibly be
mis-understood from Nick's post below, when he states "eQuest will
recognize two planes are on top of each other and default each to be adiabatic
or partially adiabatic".<br>
Also please note that what Nick stated is by no means incorrect - I just felt
compelled to clarify some details here that are not broadly understood.<br>
<br>
Two important points on this topic:<br>
(1) The recognition of coincident walls works only for vertical walls
(side-by-side shells), NOT horizontal walls (shells stacked on top of each
other). When shells in the wizard are placed side-by-side, then eQUEST
can detect this wall coincidence and when generating the detailed building
model will utilize interior, adiabatic walls wherever the shells are
adjoining. However, there is no such roof/floor wall coincidence
intelligence for wizard shells stacked on top of each other. IN these
cases the user should make sure that the Ground Floor construction of the upper
shell is set to "Over Conditioned Space (adiabatic)" and the Roof
Construction is set to "No Exterior Exposure (adiabatic)".<br>
<br>
(2) This vertical wall coincidence checking mechanism lies within the wizard
database and defaulting mechanism and is used to populate the detailed (DOE-2)
model in such a way as to ensure proper model of side-by-side shells. No
such vertical wall coincidence checking exists when creating (the equivalent
of) side-by-side shells in the detailed interface. When creating such
walls in the detailed interface, the user must indicate wall exposure by
creating either exterior or interior (adiabatic or thermally conductive) walls.<br>
<br>
Lastly - our team would like to thank Nick (and many others as well) for his
contributions to this and the Bldg-Sim e-mail lists. His detailed and
accurate explanations are very beneficial to the eQUEST & building
simulation community at large.<br>
<br>
- Scott<br>
<br>
<br>
Nick Caton wrote: <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Happy to help – I’ll
point out further that the important thing when modeling varying roof heights /
monitors using the “cutting method” (and that is a term I just made
up so don’t search for that explicitly), to save yourself some time, is
to match vertices when defining the separate shells. In doing so, eQuest
will recognize two planes are on top of each other and default each to be
adiabatic or partially adiabatic. </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>This is good because on one
level you won’t accidentally end up with a lot more exterior wall than
you should have. On a further level, it will save you some time later in
identifying which walls need to be tied to adjacent zones (the adiabatic walls
will stand out in spreadsheet view), if you decide you want to more accurately
account for thermal behavior between the monitor zone(s) and the surroundings
by defining “Next to Space…”.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Also, flattery will get you
nowhere, but thanks for the model compliment ;).</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers!</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>~Nick</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'><img border=0 width=119
height=37 id="Picture_x0020_26" src="cid:image001.jpg@01CAC137.F5C39C80"
alt="cid:489575314@22072009-0ABB"></span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><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><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<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"'> Smith, Aaron
Matthew [<a href="mailto:SMITHA11@rpi.edu">mailto:SMITHA11@rpi.edu</a>] <br>
<b>Sent:</b> Thursday, November 19, 2009 10:48 AM<br>
<b>To:</b> Nick Caton; <a href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> RE: [Equest-users] Roof monitor "Open to Below"</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks Nick, this looks exactly
like what I want to accomplish. I will look up the “cutting lines”
strategy and see if I can implement it.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Also thank you for sharing the
images of your nice looking model.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Cheers,</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Aaron</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<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> Thursday, November 19, 2009 11:33 AM<br>
<b>To:</b> Smith, Aaron Matthew; <a
href="mailto:equest-users@lists.onebuilding.org">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> RE: [Equest-users] Roof monitor "Open to Below"</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>I think you’ve identified
the root of your problem – I’m unsure that there’s any way to
get light in one shell to transmit to another.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Attached and below is an example
of a project with a lot of roof monitors that does successfully measure and
account for daylighting in those spaces. A picture speaks a
thousand words, so see if this matches what you were thinking to
accomplish. </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Each monitor is a single zone
and shell (i.e. no plenum zone). Sensors are located either on the floor
or at a desk height, as appropriate to the space usage. Creating the
shell that “wraps” around the monitors is done by using
“cutting lines” in the footprint/zoning pattern – you can
read up on that strategy by searching the archives for how courtyards are
modeled. </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>I’ll point out, in terms
of accuracy, I have the impression that eQuest’s daylight sensors do not
accurately realize the full amount of light that should be encountered with
light shelves, light tubes, or other means of interreflected daylight, based on
my comparative daylight analyses using AGI32 (which I’ve learned to use accurately
for daylight modeling). The DOE2 help files I think also allude to this
– It’s something to keep in mind if you have a lot of monitor
overhangs, again as with the example below.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>~Nick</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'><br>
</span><span style='color:#1F497D'><img border=0 width=1245 height=712
id="Picture_x0020_2" src="cid:image004.png@01CAC139.5F3117F0"
alt="cid:image002.png@01CA690D.AFE25EE0"></span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'><img border=0 width=119
height=37 id="Picture_x0020_1" src="cid:image001.jpg@01CAC137.F5C39C80"
alt="cid:489575314@22072009-0ABB"></span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-family:"Stylus BT","sans-serif";
color:#2D4D5E'>NICK CATON, E.I.T.</span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:7.5pt;color:#CC9900'>PROJECT ENGINEER</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>25501 west
valley parkway</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>olathe ks 66061</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>direct 913
344.0036</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;color:#2D4D5E'>fax 913 345.0617</span><o:p></o:p></p>
<p class=MsoNormal><i><span style='font-size:10.0pt;color:#2D4D5E'>Check out
our new web-site @ </span></i><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><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<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>Smith, Aaron Matthew<br>
<b>Sent:</b> Thursday, November 19, 2009 9:42 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] Roof monitor "Open to Below"</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Hello E-quest group,<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>I am working on ways to implement Equest in my workflow for
the purpose of daylighting design evaluation, and I am having trouble
implementing a roof monitor. I have read the help files that describe the
limitations of Equest to perform daylighting calculations, but I have also seen
that some people have been able to implement multilevel atriums and I have seen
one application of a roof monitor. Anyways I want to give it a go before I
start programming in Daylight Factors. <o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Attached is an example building I would like to be able to
evaluate. My evaluation goal is to put a light meter on the bottom zone under
the monitor and see what results pop out in the detailed daylighting summary
reports (LS-G, LS-J, ect.) I would like to compare Equest results to the
results of other software/calculations/measurements I am investigating, however
it seems that no light from the roof monitor is making it to the bottom zone.<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>The bottom shell is all one zone and the top is all one
zone. I have found that it is necessary that the bottom zone have windows or
else no daylighting dialog screen shows up in the DD wizard, and that means no
light meter. At first I tried to make the top zone “open to below”
and then in the detailed edit mode moved the light meter under the monitor, but
the results do not indicate any light is making it from the roof monitor to the
bottom zone.<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>I was hoping some of you might have some suggestions to help
implement this roof monitor setup.<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal>Aaron<o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:18.0pt;font-family:Mistral'>Aaron Smith</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>Sr.
Research Specialist</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'><a
href="mailto:smitha11@rpi.edu">smitha11@rpi.edu</a></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>Lighting
Research Center</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>21
Union Street</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>Troy,
NY 12180</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>p.
518.687.7167</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Century Gothic","sans-serif"'>f.
518.687.7120</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<pre><o:p> </o:p></pre><pre style='text-align:center'>
<hr size=4 width="90%" align=center>
</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
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
href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><o:p></o:p></pre><pre> <o:p></o:p></pre>
<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 class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>