<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.34">
<TITLE>RE: [esp-r] Re: The position of low-e coating in double glass.</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hi Jon,</FONT>
<BR><FONT SIZE=2>generally, I agree with you. However, in hectic times, ESP-r is a bit too around the corner at places, here. I do not exactly remember where, but emissivity is / can be entered at more than one place - only one of which is relevant - in connection with constructions / materials (maybe true only for transparent materials). </FONT></P>
<P><FONT SIZE=2>What I do certainly remember (and what we hopefully wrote to you at some point and what has been fixed in the mean time?) is that the QA report *did not* correctly report the emissivity values actually used. We hat quite a mixup due to this at the time.</FONT></P>
<P><FONT SIZE=2>And, my suggestion was to *check* what values are being used in the .con file. Not necessarily edit them (because of what you write).</FONT></P>
<P><FONT SIZE=2>Regards,</FONT>
<BR><FONT SIZE=2>Achim</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>Mit freundlichen Grüssen / Best regards</FONT>
<BR><FONT SIZE=2> </FONT>
<BR><FONT SIZE=2>Achim Geissler</FONT>
<BR><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Jon Hand (clcv10) [<A HREF="mailto:jon@esru.strath.ac.uk">mailto:jon@esru.strath.ac.uk</A>]</FONT>
<BR><FONT SIZE=2>> Sent: Monday, December 11, 2006 6:45 PM</FONT>
<BR><FONT SIZE=2>> To: Ery Djunaedy</FONT>
<BR><FONT SIZE=2>> Cc: Geissler Achim; esp-r@lists.strath.ac.uk; 안빈낙도</FONT>
<BR><FONT SIZE=2>> Subject: Re: [esp-r] Re: The position of low-e coating in double glass.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> A reminder about changing emissivity....</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> There has been some discussion about editing zone construction</FONT>
<BR><FONT SIZE=2>> files. This is not a good idea in terms of QA (because the changes can</FONT>
<BR><FONT SIZE=2>> be easily lost and some subtle errors can creep in when people</FONT>
<BR><FONT SIZE=2>> manually edit files).</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The best way of doing it is to use the materials database and get a</FONT>
<BR><FONT SIZE=2>> copy of the standard materials database into your model (there is</FONT>
<BR><FONT SIZE=2>> an option in the project manager to do this) and then find a material</FONT>
<BR><FONT SIZE=2>> that is similar to what you want an make a copy of it and change the</FONT>
<BR><FONT SIZE=2>> surface properties as necessary as well as changing the documentation</FONT>
<BR><FONT SIZE=2>> of the material to reflect what you changed and what the original</FONT>
<BR><FONT SIZE=2>> was.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Then in your construction database use the new material and the</FONT>
<BR><FONT SIZE=2>> altered surface properties will be imported into your model files.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Again - it is not a good idea to manually edit the zone files!</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> -ESRU</FONT>
</P>
</BODY>
</HTML>