<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)">
<style>
<!--
/* Font Definitions */
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Times;
panose-1:2 2 6 3 5 4 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;}
@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="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=Section1>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Hi Taylor,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>I would recommend looking into the free program SPOT (Sensor Placement
Optimization Tool) which can create eQuest lighting schedules based on yearly
daylight availability and dimming that occurs with optimized sensor placement.
In order to get the Daysim .csv output into the current version of eQuest, you’d
have to parse the data into the correct eQuest .inp format, and wouldn’t
have the benefit of results based on sensor type and location. The only
issue with SPOT is that I believe you have to have Excel 2004 (not 2007) for it
to work.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'>Rosie<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<div>
<table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0
style='border-collapse:collapse'>
<tr>
<td width=590 valign=top style='width:6.15in;padding:0in 2.15pt 0in 0in'>
<p class=MsoNormal><b><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:#6A747C'>Roselin Osser, LEED AP</span></b><span style='color:blue'><o:p></o:p></span></p>
</td>
</tr>
<tr style='height:.2in'>
<td width=590 valign=top style='width:6.15in;padding:0in 2.15pt 0in 0in;
height:.2in'>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:#6A747C'>Green Integration Group</span><span style='color:blue'><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width=590 valign=top style='width:6.15in;padding:0in 2.15pt 0in 0in'>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:#6A747C'>R.G. Vanderweil Engineers, LLP</span><span style='color:blue'><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td width=590 valign=top style='width:6.15in;padding:0in 2.15pt 0in 0in'>
<p class=MsoNormal><span style='font-size:9.0pt;font-family:"Arial","sans-serif";
color:#6A747C'>T 617.956.4461 | F 617.423.7401 </span><span style='color:
blue'><o:p></o:p></span></p>
</td>
</tr>
</table>
</div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:blue'><o:p> </o:p></span></p>
<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>Taylor
Sharpe<br>
<b>Sent:</b> Sunday, April 18, 2010 10:31 PM<br>
<b>To:</b> equest-users@lists.onebuilding.org<br>
<b>Subject:</b> Re: [Equest-users] DAYSim and eQuest<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:13.5pt;
font-family:Times'>Otto,</span></span><b><span style='font-size:13.5pt;
font-family:Times'><o:p></o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:13.5pt;
font-family:Times'>I am able to complete a project in DAYSim, getting output
information in .csv format, as well as the basic .html output for daylight
factor, UDI etc. How am I able to integrate DAYSim data into eQuest? </span></span><b><span
style='font-size:13.5pt;font-family:Times'><o:p></o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:Times'><o:p> </o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:13.5pt;
font-family:Times'>You mentioned populating a schedule with the data...I'm not
sure how to go about doing this.</span></span><b><span style='font-size:13.5pt;
font-family:Times'><o:p></o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:Times'><o:p> </o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:13.5pt;
font-family:Times'>Regards,</span></span><b><span style='font-size:13.5pt;
font-family:Times'><o:p></o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><span class=apple-style-span><span style='font-size:13.5pt;
font-family:Times'>-Taylor Sharpe</span></span><b><span style='font-size:13.5pt;
font-family:Times'><o:p></o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:Times'><o:p> </o:p></span></b></p>
</div>
<div>
<p class=MsoNormal><b><span style='font-size:13.5pt;font-family:Times'><o:p> </o:p></span></b></p>
</div>
<p class=MsoNormal><span class=apple-style-span><b><span style='font-size:13.5pt;
font-family:Times'>Otto Schwieterman</span></b></span><span
class=apple-style-span><span style='font-size:13.5pt;font-family:Times'><a
href="mailto:equest-users%40lists.onebuilding.org?Subject=Re%3A%20%5BEquest-users%5D%20How%20does%20eQuest%20know%0A%09initialFootcandlesforDaylighting%20Calc%3F&In-Reply-To=%3C81CD81BB0AC1FF41B8F014BA7512A740041DD08B%4000mail.ad.fhai.org%3E"
title="[Equest-users] How does eQuest know initialFootcandlesforDaylighting Calc?">oschwieterman
at fhai.com</a></span></span><span style='font-size:13.5pt;font-family:Times'><br>
<span class=apple-style-span><i>Fri Jan 8 06:23:43 PST 2010</i></span></span><o:p></o:p></p>
<div><pre><o:p> </o:p></pre><pre>Here is an alternate method to eQUEST's daylighting strategies:<o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>><i>From my experience (and training from Marlin Addison), I believe that </i>eQUEST does not model daylighting with much accuracy. I believe that the best method to handle daylighting is to run models on independent software (DAYSIM is free) and insert the results into lighting schedules. My general practice with lighting schedules is to force 100% of the lights to be on when the room is occupied and during the sameoccupied times, create a new schedule that shows the fraction of lights on from the DAYSIM output. <o:p></o:p></pre><pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre>This method gives the modeler more control and flexibility with the model and daylighting strategies. Many times we have 3 rows of lights in a classroom and we typically force the row furthest from the window always on when occupied so the minimum percentage of lights on during daylighting is 33% (1/3). <o:p></o:p></pre></div>
</div>
</body>
</html>