<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<STYLE type=text/css>DIV {
MARGIN: 0px
}
</STYLE>
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2>Gidday </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2>We have run into issues like this before with Ecotect - to
the point where I now have a KISS (Keep it simple Stupid) lecture in
reserve for my students to review the difference between visual and mathematical
modelling</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2>Only guessing, because I have not encountered this specific
issue. But I suspect that this is also one of these visual logic vs
mathematical model issues. For example, we had students who have in the past
with a school gymnasium modelled some bleachers / upper level spectator area
using the same tools they modelled the general gym form. With the simple gym
form, the sound ray trace worked believably. With the extra seating area
modelleed so that it looked visually acceptable, the sound stayed inside the
bleacher/balcony form. What had happened was that a second zone
(bleacher) had been created inside the first (gym) zone and the
acoustic (mathematical) model just worked on the inner zone definition, no
matter where in the larger, outer zone the visuals showed the sound source to
have been placed. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2>I am imagining that there is a mathematical model (lumen
method?) linking your 'simple box' zone to the sky definition; adding
another 'roof' zone that appears visually 'above' the first 'simple box' zone
does not remove that mathematical link. You would need explicitly to change the
horizontal window definition to be some form of interzone device...
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2>At some point in these type of calc's you might
consider that the Ecotect quick calculation model has reached its limits and
then you would use it to export to a more capable modeller - the new Control
panel in Ecotect is a great way of running Radiance!?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=843411001-19102007><FONT face=Arial
color=#0000ff size=2>M</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<STYLE>
st1\:*{behavior:url(#ieooui) }
</STYLE>
<STYLE>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:1627421319 -2147483648 8 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;
text-underline:single;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-noshow:yes;
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:8.0pt;
font-family:Tahoma;
mso-fareast-font-family:"Times New Roman";}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</STYLE>
<DIV class=Section1>
<P class=MsoNormal>Michael
Donn
<BR>Associate Dean Research<BR>Director Centre for <?xml:namespace prefix = st1
ns = "urn:schemas-microsoft-com:office:smarttags" /><st1:PlaceType
w:st="on">Building</st1:PlaceType> <st1:PlaceName
w:st="on">Performance</st1:PlaceName> <st1:PlaceName
w:st="on">Research</st1:PlaceName><BR><st1:PlaceType
w:st="on">School</st1:PlaceType> of <st1:PlaceName
w:st="on">Architecture</st1:PlaceName><SPAN class=GramE>
</SPAN><BR><st1:PlaceName w:st="on">Victoria</st1:PlaceName> <st1:PlaceName
w:st="on">University</st1:PlaceName> <SPAN
style="mso-spacerun: yes"> </SPAN>+64 4 463 6221
work<BR><st1:address
style="BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"
tabIndex=0 w:st="on"><st1:Street w:st="on">PO Box</st1:Street>
600
+64</st1:address> 21 611 280 mobile<BR><st1:City
w:st="on">Wellington</st1:City>
<SPAN style="mso-spacerun: yes">
</SPAN>+64 4 463 6204 work fax<BR><st1:place w:st="on"><st1:country-region
w:st="on">New Zealand</st1:country-region></st1:place> <SPAN
style="mso-spacerun: yes">
</SPAN>+64 21 611 594 <SPAN class=SpellE>mobilefax</SPAN></P>
<P class=MsoNormal> </P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><A
href="http://www.vuw.ac.nz/architecture/staff/academics/michael-donn.aspx">http://www.vuw.ac.nz/architecture/staff/academics/michael-donn.aspx</A>
</SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">------------------------------------------------------------------------------------</SPAN></P></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> BLDG-SIM@gard.com
[mailto:BLDG-SIM@gard.com] <B>On Behalf Of </B>Adam Jackaway<BR><B>Sent:</B>
Friday, 19 October 2007 10:09 a.m.<BR><B>To:</B>
BLDG-SIM@gard.com<BR><B>Subject:</B> [BLDG-SIM] Ecotect
skylights<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV
style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">
<DIV>My students are working on skylighting designs for simple models in
Ecotect. They are starting with a simple box with no windows. They insert a
horizontal window into the ceiling plane. Illuminance calculations look
reasonable. They then insert a roof zone on top of the box, intending to
eventually make a 'lay-light' scheme. But before inserting any glazing into the
roof zone, they run the illuminance calcs to check the roof was inserted
properly - expecting to see no daylight in the lower box. Yet there is a low
level wash on the interior. </DIV>
<DIV> </DIV>
<DIV>Anyone run into this before? Any suggestions?</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV> </DIV>
<DIV>Adam</DIV></DIV><PRE>
==================
You received this e-mail because you are subscribed
to the BLDG-SIM@GARD.COM mailing list. To unsubscribe
from this mailing list send a blank message to
BLDG-SIM-UNSUBSCRIBE@GARD.COM
</PRE><PRE>
===========================
You received this e-mail because you are subscribed
to the BLDG-SIM@GARD.COM mailing list. To unsubscribe
from this mailing list send a blank message to
BLDG-SIM-UNSUBSCRIBE@GARD.COM
</PRE></BODY></HTML>