<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 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Verdana;
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;}
/* 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.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";}
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";}
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-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:701245188;
mso-list-type:hybrid;
mso-list-template-ids:-989068512 -2107091736 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:"MS Mincho";
mso-bidi-font-family:"Times New Roman";}
@list l1
{mso-list-id:1074670533;
mso-list-type:hybrid;
mso-list-template-ids:-209401656 1052135226 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-start-at:2;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:"MS Mincho";
mso-bidi-font-family:"Times New Roman";}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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'>Umesh et al,<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 appreciate everyone’s
input/responses, both copied to this list and privately!<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 like to share my thoughts
with you all, in response to flood of useful advice I’m receiving =).<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'>First, I want to thank and
commend Umesh for bringing up something I should have made clear (as I have in
the past) – I don’t personally recommend that anybody should be
trying to use eQuest as a primary tool to determine daylighting illumination levels,
except expressly to check and fine-tune the modeled behavior. Rest
assured, I have rendered the daylighting behavior for this particular situation
many many times over from conceptual through final design stages =).<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'>eQuest is uniquely suited and
capable of determining the hourly energy behavior of a wide range of daylight
harvesting controls (with its own quirks), and through that can compare the
relative energy performance of a series of glazing/shading layouts and controls
combinations… very useful for certain situations, but one should
certainly concurrently be using photometric software fit to the task to
determine interreflected artificial and daylight behavior accurately enough to
make refined lighting & envelope system design decisions. <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'>Second, based on some
conflicting advice/experiences I’ve received, I’ve spent some
further time investigating my inquiry on my own and have some results to share:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>A photocell located
remotely from its parent space will still measure light. The amount measured
does not necessarily change as you move it to different zones or even outside
the building perimeter (literally outside).<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>If the parent space
has no exterior windows to get daylight from, it results in an error that stops
the simulation run.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-.25in;mso-list:l1 level1 lfo2'><![if !supportLists]><span
style='color:#1F497D'><span style='mso-list:Ignore'>-<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='color:#1F497D'>These behaviors
combined pretty much support the notion that photocells can only see light from
their parent space’s exterior windows, and consider relative orientation/distance
from the parent space’s window irrespective of whether they’re
actually in the space or not.<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 may have opened a can of worms
by revealing an underlying purpose of my original question – to model
open loop photocell controls. Allow me to caution and clarify: eQuest’s
daylighting functions are currently built on closed loop control schemes.
Modeling the hourly behavior of open loop controls is something I have been toying
with experimentally for awhile, and probably won’t ever recommend others
to try within the current version of eQuest, until I or others should work out
some major hurdles (this photocell placement workaround issue being one).
Paul Riemer has offered some ideas regarding a “dummy wall” of
sorts which has me a bit excited… =)<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'>Third, I’ve experimented
with a variety of things to get the second set of defined sensors to show up in
the LS-M reports, but to no avail… perhaps this is something to chalk up
as one of a multitude of things to get looked into for future eQuest updates *wink
wink… ;)*? If anyone has seen an LS-M report for a “Ref Pnt 2,”
I would be sincerely interested to examine your model, if I may, to figure out
what we’re doing differently!<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'>Thanks again to Umesh, Pasha,
Paul R. and others for your collective thoughts and insight!<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><br>
~Nick</span><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";
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_i1029" src="cid:image001.jpg@01CAD00D.66CE9F90"
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"'> Umesh Atre
[mailto:umesh@innovativedesign.net] <br>
<b>Sent:</b> Tuesday, March 30, 2010 11:15 AM<br>
<b>To:</b> Nick Caton; equest-users@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Equest-users] Daylight sensor placement question<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>Nick,</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>Reverting back to
your original email, if you are defining 2 sensors in reference to the
same space, as seen in your screenshot, </span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>you should
get daylighting contribution calculated at both sensors.</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>Which does not
mean that the calculated values will be accurate. Since the primary space is
your north zone, the 2nd sensor</span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>will only be
looking at the north exterior windows without any contribution
from the south or any openings on any intermediate </span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>interior walls.</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>I think you get
the LS-M for just the first reference point. LS-G and LV-L might be able
to provide averaged numbers though. If you do</span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>need the LS-M for
the other reference point, you could reverse number them, or define just
the sensor you want, and rerun the simulation.</span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>Per my
past trials with using daylighting in eQUEST, footcandle levels will be
calculated at reference points placed outside</span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>the primary space
to be daylit, or for that matter even if they are placed outside the building,
as long as the primary space has</span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>one window on an
exterior wall, and sensors are tied to this space. Outdoor sensors in this case
do not measure exterior </span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>illumination
though, which ideally would be in 1000's of footcandles. </span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>Even if you have
an interior wall (or more than 1 wall) separating 2 spaces, you will get
footcandle levels calculated at the other</span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>reference points.
Again, the condition seems to be that the sensors should be defined in
relation to a primary space which has</span><span style='font-size:10.0pt;
font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>to have an
exterior wall window opening. Since this does not reflect reality, I am
not sure how to approach this issue. I think all</span><span style='font-size:
10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>interior walls are
basically ignored for side-lighting calculations.</span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>This topic
has most probably been discussed here in the past, but
in short, the recommendation would be to use a separate daylighting </span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>program (which you
are trying to avoid using I gather) to independently calculate daylighting
levels in your spaces.</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <o:p></o:p></span></p>
</div>
<div>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p> </o:p></span></p>
</div>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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 [mailto:ncaton@smithboucher.com]
<br>
<b>Sent:</b> Tuesday, March 30, 2010 11:13 AM<br>
<b>To:</b> Umesh Atre; equest-users@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Equest-users] Daylight sensor placement question</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Umesh – you are
understanding the layout correctly =). <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 could apportion some fraction
of the classroom’s LPD to the corridor, and then locate a sensor in the
corridor to control that resulting fraction of lighting. This workaround
would be perfect, though it’s a bit of extra work that I’m unsure
is necessary… For all I know, these photocells are working
correctly, but I am not sure how to verify that since the appropriate LS-M
reports aren’t being generated!<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'>Ideally, I would like the energy
model to have the photocell in the corridor control a fraction of the lights in
the classroom – if only because it would be less work and match the true
design (open loop photocell controls). <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'>Regardless of whether this is
actually working, I’d really like to know whether photocells outside of
the controlled zone, irrespective of any relative window locations (or even
better, outside of the building perimeter) can correctly measure and report
daylight, accounting for specified building/site shades. I
understand this would be bending the current intent of the photocells as
defined in eQuest, as they’re intended to vary light levels based on
closed loop controls (measuring ambient+daylighting at the work surface in
question). This might help bridge a gap between syncing measured/modeled
daylight behavior to an energy model to accurately approximate open loop design
behavior.<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</span><o:p></o:p></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_i1026" src="cid:image001.jpg@01CAD00D.66CE9F90"
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"'> Umesh Atre
[mailto:umesh@innovativedesign.net] <br>
<b>Sent:</b> Tuesday, March 30, 2010 9:26 AM<br>
<b>To:</b> Nick Caton; equest-users@lists.onebuilding.org<br>
<b>Subject:</b> RE: [Equest-users] Daylight sensor placement question<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>If I may ask a
question:</span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>It looks like you
have the 2nd sensor located in a corridor the south side of
which is a glass wall. If I understand this correctly,</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>why would you not
define the sensor as part of that corridor zone instead of the north
zone? </span><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt;color:blue'>Maybe a section or
3d of this space would help.</span><span style='font-size:12.0pt;
font-family:"Times New Roman","serif"'><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>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <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>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> <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 class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><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>Nick
Caton<br>
<b>Sent:</b> Monday, March 29, 2010 11:58 AM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> [Equest-users] Daylight sensor placement question</span><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p></span></p>
<p class=MsoNormal>Hey all!<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Daylight sensor placement question (see highlighted space in
attached screengrab for an illustration):<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have a classroom with North and South daylight transition
windows, and a corresponding North and South daylighting “zone.”
The North side is easy – those windows are on the envelope wall, so
I’m sure the daylight is correctly being measured/modeled within the
space for the “North zone” sensor to pick up on.<o:p></o:p></p>
<p class=MsoNormal>The south windows however are in an internal wall, and on
the other side is a “glass box” corridor. Rather than pursue
the fuzzy route of trying to model daylight transitioning between zones
correctly (if anyone can fully digest the help file for INSIDE-VIS-REFL I would
really appreciate the layman’s explanation), I’ve taken the
“easy” route and located the daylight sensor in the corridor.
This happens to conveniently match the actual design location of the
photocell. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>My question has two parts:<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in'><span style='font-family:
Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman","serif"'>
</span>Can a zone’s daylight sensor be located in another zone and
measure light in a remote location? If so, are any extra steps necessary?<o:p></o:p></p>
<p class=MsoListParagraph style='text-indent:-.25in'><span style='font-family:
Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman","serif"'>
</span>I see my eQuest project is, on its own, generating an LS-M report for
each “Daylight Illuminance Ref Pnt 1.” What is the procedure
to generate the same reports for “Ref Pnt 2” where those
occur? <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>~Nick<o:p></o:p></p>
<p class=MsoNormal><img border=0 width=119 height=37 id="Picture_x0020_1"
src="cid:image001.jpg@01CAD00D.66CE9F90" alt="cid:489575314@22072009-0ABB"><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>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>