<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: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:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
p.BalloonText, li.BalloonText, div.BalloonText
{mso-style-name:"Balloon Text";
mso-style-link:"Balloon Text Char";
margin:0cm;
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.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</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=FR link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Dear Michael,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I try to give you some answers from the point of view of our department of a large HVAC installation company, dedicated to energy efficiency. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>We have been developing our own components for three years.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>“At the moment, we think there are two drivers to move to TRNSYS. Firstly, we would be able to model systems where it is required to simulate transient behaviour..”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>TRNSYS has the potential to model transient behaviours, but take in mind that </span><span lang=EN-US style='color:#1F497D'>most of TRNSYS components are developed to be used for “quasi-steady” modeling<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>“Secondly, as TRNSYS has a modular structure, we feel there may be a reduction in time required to develop models. Since EES is fully equation-based, the mathematical equation-equivalent of complex and large systems can become quite extensive and tedious to develop. It seems TRNSYS would more readily enable the re-use of sub-models in various projects and therefore reduce time to develop and check models.”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>You are right : reusability of components (modularity) is one of the main strength of TRNSYS ! <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>However, consider that developing a new submodel (component) in TRNSYS demands more effort than its equivalent in an equation based solver (EES, for example, or Modelica, which could be a serious challenger of TRNSYS in your case). <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU>“The biggest question mark around TRNSYS is this: By researching the possibilities and available components, I am now 100% convinced we will need to develop our own component models for many of our system components and control systems. In essence, I don’t see this as a problem.”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>This is the typical situation of an industrial company, where we want to model systems basing on our knowledge, our data and our functional analysis.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>“</span><span lang=EN-AU>. However, after reading through the several manuals, working with the demo and reading the various threads on this mailing list, it seems we can expect a lot of trouble/problems when developing components. As one example, there seems to be no clear guidance on which Fortran compiler to use. Many people recommend an old compiler (Compaq Visual Fortran) which is no longer available. There seems to be no information which details how to develop new components with for example the latest Intel Visual Fortran Composer XE 2013..”<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Creating new components with the latest Intel Visual Fortran Composer XE 2013 is well documented in the last version of the programmer’s guide (chapters 7.5.5 and 7.5.6). Personally, I found no problem to create my first components. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Moreover, I think that Intel Visual Fortran is the suggested development suite for TRNSYS 17. By the way, distributed version of TrdDll, which is the core of the TRNSYS engine, is compiled using Intel Visual Fortran (even though I ignore the exact version used by the developer team). Compaq Visual Fortran is an old staff today, but it is used often because, looking a little, it can be found for free (but Visual Fortran is not expensive).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>“</span><span lang=EN-AU>Besides that, I can see many people struggling on these threads with errors that are seemingly impossible to correct of solve.<span style='color:#1F497D'>”<o:p></o:p></span></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I find that most of problems that are posted on this list derive from an insufficient knowledge of good programming practices in general, and of Fortran in particular. Fortran is not VBA : array limit checking is not automatic, division by zero is possible and debugging is more difficult than for an interpreted language (VBA). </span><span lang=EN-AU style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>“</span><span lang=EN-AU>Are these merely problems related to the Fortran programming itself?<span style='color:#1F497D'>”<o:p></o:p></span></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Not only Fortran but any powerful language, which should be used knowing what you do… </span><span lang=EN-AU style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>“</span><span lang=EN-AU> I may be wrong, but there seems to be not much technical support for people who are required to develop their own components.<span style='color:#1F497D'>”<o:p></o:p></span></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>This is a fact : TRNSYS is not a commercial suite, finding a competent technical support is not easy. However, in my experience, if you post clearly a technical question in an acceptable English, explaining your problem and what you want to do, there are always nice people answering your questions.</span><span lang=EN-AU style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>“</span><span lang=EN-AU>As you can see, we are struggling with the above issues. I would be delighted if people could share their thoughts on this and offer some advice.<span style='color:#1F497D'>”<o:p></o:p></span></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>My two cents...<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-AU style='color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-family:"Tahoma","sans-serif";color:#58595B'>Marcello Caciolo</span></b><span style='font-family:"Tahoma","sans-serif";color:#58595B'><br></span><span style='font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#58595B'>Responsable Outils et Méthodes d'Analyse Energétique</span><span style='font-family:"Tahoma","sans-serif";color:#58595B'><o:p></o:p></span></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'><img width=170 height=62 id="Image_x0020_1" src="cid:image002.jpg@01CEA3F7.2A9B6640" alt="cid:image003.jpg@01CD4E08.954D04D0"><br><b><br></b>Cellule Efficacité Energétique et Environnementale - Pôle Projets et Réalisations<br>46 Boulevard de la Prairie au Duc<br>BP 40119 - 44201 Nantes Cedex 02</span><span style='font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Tél.: +33 02 40 41 06 57</span><span style='font-size:9.0pt;font-family:"Tahoma","sans-serif";color:#1F497D'><br><a href="mailto:prenom.nom@aximaseitha-gdfsuez.com"><span style='color:blue'>marcello.caciolo@cofelyaxima-gdfsuez.com</span></a></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:Webdings;color:#339966'>P</span><span style='font-size:10.0pt;font-family:Webdings;color:#339966'> </span><b><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#339966'>Pensez à l'environnement avant d'imprimer ce message</span></b><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>