<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=iso-8859-1">
<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:Batang;
panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
{font-family:Batang;
panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Cambria;
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:"\@Batang";
panose-1:2 3 6 0 0 1 1 1 1 1;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle20
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:220486421;
mso-list-type:hybrid;
mso-list-template-ids:1173228656 201916431 201916441 201916443 201916431 201916441 201916443 201916431 201916441 201916443;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</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 bgcolor=white lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>David,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>Glad to hear the improvement TRNYS 17 will bring over the previous
Version 16. In addition to features you mentioned, I think the following should
also be addressed by the development team:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><span
style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>Improved debugging. TRNSYS is “well known” for letting
users to guess what actually the error messages it displays mean. I started
using TRNSYS 15 and then converted to TRNSYS 16. I believe, TRNSYS 15 debugging
is better (read: straightforward) than TRNSYS 16.<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><span
style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>Direct translation of user defined TYPES / subroutine from
previous version 16 to 17. If this is not addressed, the users like me will
again get frustrated and spend a lot of time to transfer their project from
previous version to version 17. Creating the skeleton using “Export as
Fortran / C++ ….” is not enough. Using this skeleton, users still
spend a lot of time to copy paste the codes, checking the syntax and or defining
variables …<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><span
style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>You wrote: “</span><span style='font-family:"Cambria","serif";
color:black'>The user will probably have to adjust the way that they structure
information in TRNBuild”. I do not know whether this also means: we are
not able to actually run directly the previous TRNBUILD file in version 17?</span><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><span
style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-family:"Cambria","serif";
color:black'>Get rid of notorious “Error message 1000”</span><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
style='font-size:11.0pt;font-family:"Cambria","serif";color:black'><span
style='mso-list:Ignore'>5.<span style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>Optimised ordering of TRNSYS Simulation studio components without
the user needing to do manual ordering.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>I may have some more “wishes” later on, but for the
time being I encourage users like me to send their wishes for TRNSYS 17 in this
forum.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Cambria","serif";
color:black'>Thanks, Marcello, for reminding us about this.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'><o:p> </o:p></span></p>
</div>
<p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:black'>E Halawa</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p></o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'>From:</span></b><span lang=EN-US
style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>
David Bradley [mailto:bradley@tess-inc.com] <br>
<b>Sent:</b> Tuesday, 9 December 2008 3:20 AM<br>
<b>To:</b> Marcello Caciolo<br>
<b>Cc:</b> trnsys-users@cae.wisc.edu<br>
<b>Subject:</b> Re: [TRNSYS-users] Features of TRNSYS 17<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Marcello,<br>
You are correct that a new version is planned for release in summer
2009. The major new features of version 17 will center on the building model.
Specifically, TRNSYS will do a much better job of handling building self
shading and internal solar radiation distribution through the use of a
graphical preprocessor. The details are not yet fully worked out but in the
current testing, the user draws the building in Google SketchUp, then exports
it to TRNBuild through the use of a preprocessor). The user will probably have
to adjust the way that they structure information in TRNBuild. The use of the
preprocessor itself is quite straightforward and the structure of the TRNSYS
Studio will not change substantially. One important new feature there is planned
to be a two-tab view of the input file (*.dck and *.tpf). Another new feature
will be a very flexible component that will calculate energy transfer between a
building and the ground. There will be a number of other new features and
models as well but these three are the most significant developments.<br>
Kind regards,<br>
David<br>
<br>
<br>
Marcello Caciolo wrote: <o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>Hy!<br>
<br>
I’ve read in a previous message that a new release of TRNSYS is planned
for the next year. </span><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>I wonder if TRNSYS 17 will include
widespread changes in the interface and in the models with respect to the
present version or it will be just an “adjusted” version of it. Do
you have already defined which are the main new features?</span><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>Thank you!</span><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>Best regards,</span><o:p></o:p></p>
<p class=MsoNormal><span lang=EN-US>Marcello</span><o:p></o:p></p>
<pre>-- <o:p></o:p></pre><pre>--------------------------------------------------------------------------------<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>Marcello CACIOLO <o:p></o:p></pre><pre> <o:p></o:p></pre><pre>Ingénieur de Recherche <o:p></o:p></pre><pre>Centre Energétique et Procédés - Mines ParisTech<o:p></o:p></pre><pre>60, Bd Saint-Michel <o:p></o:p></pre><pre>75272 Paris Cedex 06 France <o:p></o:p></pre><pre>Tél : (33)1 40 51 94 21 Fax : (33)1 46 34 24 91 <o:p></o:p></pre><pre>E-mail: <a
href="mailto:marcello.caciolo@ensmp.fr">marcello.caciolo@ensmp.fr</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>--------------------------------------------------------------------------------<o:p></o:p></pre>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<pre><o:p> </o:p></pre><pre><o:p> </o:p></pre><pre> <o:p></o:p></pre><pre> <o:p></o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal>Scopri le top! <a href="http://livesearch.it.msn.com/"
target="_new">Quali sono le più cliccate della settimana?</a> <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>TRNSYS-users mailing list<o:p></o:p></pre><pre><a
href="mailto:TRNSYS-users@cae.wisc.edu">TRNSYS-users@cae.wisc.edu</a><o:p></o:p></pre><pre><a
href="https://www-old.cae.wisc.edu/mailman/listinfo/trnsys-users">https://www-old.cae.wisc.edu/mailman/listinfo/trnsys-users</a><o:p></o:p></pre><pre> <o:p></o:p></pre>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre><pre>***********************************************************************<o:p></o:p></pre><pre>Thermal Energy System Specialists (TESS), LLC <o:p></o:p></pre><pre>David BRADLEY 22 N. Carroll Street - Suite 370 <o:p></o:p></pre><pre>Partner Madison, WI 53703 <o:p></o:p></pre><pre> USA<o:p></o:p></pre><pre>P: +1.608.274.2577 <o:p></o:p></pre><pre>F: +1.608.278.1475<o:p></o:p></pre><pre>E-mail: <a
href="mailto:bradley@tess-inc.com">bradley@tess-inc.com</a> <o:p></o:p></pre><pre>Web Pages: <a
href="http://www.tess-inc.com">http://www.tess-inc.com</a> and <a
href="http://www.trnsys.com">http://www.trnsys.com</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>***********************************************************************<o:p></o:p></pre></div>
</body>
</html>