<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks for the answer, Matt.<br>
<br>
I see what you explain, but I don't see if it can apply to my
problem. For instance, if I continue with the type 16 example. My
question is : If the end-user wants to implement a variable number
of surfaces, how to implement that in a "user friendly" way.<br>
<br>
The way I see now is to use a default type 16 with a given numer of
surfaces, let's say ten. But if I don't want to see all inputs in
the GUI, I need to use check boxes that make appear inputs for the
"checked" surface. Is there a way to make it work the same way
cycles work in Trnsys, with a numer defining the right inputs
avalaible?<br>
<br>
Best regards<br>
<br>
Thibaut<br>
<br>
<br>
Le 07/12/2011 20:04, Matt Duffy a écrit :
<blockquote
cite="mid:1323284685.v2.mailanyonewebmail-331886@fuseweb2d"
type="cite">Dear Thibaut,<br>
<br>
I ran into a similar problem with this in TRNSED the other day: I
wanted to give the end-user the option of using one of two modes
for the Type16 radiation processor, and as it turns out these two
different modes had a different number of parameters or inputs.
Fortunately, I work with the Trnsys savvy, David Bradley, and he
contrived a solution. Implement both of the components in the
input file, then when the user selects either component (in your
case checks a box), it will turn on or off the appropriate outputs
of the appropriate component in an equation. Here is a simple
example.<br>
<br>
I have two different Type16 in the input file. In mode 1 is Unit 2
Type16, and in mode 2 is Unit 22 Type16. When the user selects the
mode 1, I set a variable to 1 (RM1=1) and set the other variable
to 0, (RM2=0). Then I simply make an equation for the output of
consideration that has both of the outputs from both of the
components with the variable's "swi tch" to enable or disable that
appropriate output.<br>
<br>
EQUATIONS 1<br>
QTotSurf=[2,7]*RM1+[22,7]*RM2<br>
<br>
<br>
<br>
Best regards, <br>
<br>
Matt Duffy <br>
<br>
<br>
<!--replyfwdwrap-->
<div style="background-image:
url(http://webmail.fusemail.com/de/r_bg_img.gif);
background-repeat: repeat-x; background-position: 50% top"><strong>-----
Original Message -----</strong><br>
<strong>From:</strong> "Thibaut VITTE"
<a class="moz-txt-link-rfc2396E" href="mailto:thibaut.vitte@h3c-energies.fr"><thibaut.vitte@h3c-energies.fr></a> <br>
<strong>Sent:</strong> Tue, December 6, 2011 12:15<br>
<strong>Subject:</strong> [TRNSYS-users] Trnsed and parameters
cycle<br>
<br>
<table cellspacing="5" width="100%">
<tbody>
<tr>
<td>
<div class="PrivateMsgDiv">
<pre>Dear Trnsys users,
I'm creating a trnsed application, and I need to define walls for a
simplified building. I'm having difficulties to program a cyle for
parameters. I've tried to use a model with a cycle implemented in the
tmf, but it does not work, and if I understand well how trnsed works, it
seems normal.
So I tried to make one using check box group that ask how many walls
need to be inputed. But it is not what we can call "user friendly" since
a numerical value would do the trick with a lot of space spared.
So my question is : Is it possible to take into account tmf cycles, or
is it possible to make it with a numerical value, or does anyone have a
good tip to share? I've looked into the applications I've found on the
web, but I did'nt found anything relevant. (If you have a good example
of an application using advanced trnsed possibilities that is avalaible,
even if it does'nt answer my question, I would be happy to have a look
!!! )
Many many thanks in advance.
Thibaut
_______________________________________________
TRNSYS-users mailing list
<a moz-do-not-send="true" href="javascript:bodyCreateMail('TRNSYS-users%40cae.wisc.edu')">TRNSYS-users@cae.wisc.edu</a>
<a moz-do-not-send="true" target="_blank" href="https://mailman.cae.wisc.edu/listinfo/trnsys-users">https://mailman.cae.wisc.edu/listinfo/trnsys-users</a>
</pre>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">
@page { size: 8.5in 11in; margin-top: 0.7874in; margin-bottom: 0.7874in; margin-left: 0.7874in; margin-right: 0.7874in }
table { border-collapse:collapse; border-spacing:0; empty-cells:show }
td, th { vertical-align:top; font-size:12pt;}
h1, h2, h3, h4, h5, h6 { clear:both }
ol, ul { margin:0; padding:0;}
li { list-style: none; margin:0; padding:0;}
li span.odfLiEnd { clear: both; line-height:0; width:0; height:0; margin:0; padding:0; }
span.footnodeNumber { padding-right:1em; }
* { margin:0; }
.fr1 { font-size:12pt; text-align:center; vertical-align:top; margin-left:0in; margin-right:0in; margin-top:0in; margin-bottom:0in; padding:0in; border-style:none; }
.P1 { font-size:12pt; margin-bottom:0in; margin-top:0in; font-family:Times New Roman; text-align:center ! important; }
.P10 { font-size:7.5pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#f79646; }
.P2 { font-size:9pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:center ! important; color:#e36c0a; font-style:italic; font-weight:bold; }
.P3 { font-size:9pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#e36c0a; font-weight:bold; }
.P4 { font-size:9pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#e36c0a; font-weight:bold; }
.P5 { font-size:7.5pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; color:#e36c0a; font-weight:bold; }
.P6 { font-size:7.5pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#3329b1; }
.P61 { font-size:8.5pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#3329b1; }
.P7 { font-size:7.5pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#3329b1; font-style:italic; }
.P8 { font-size:7.5pt; margin-bottom:0in; margin-top:0in; font-family:Tahoma, sans-serif; text-align:justify ! important; color:#3329b1; font-style:italic; }
.P9 { font-size:12pt; margin-bottom:0in; margin-top:0in; font-family:Times New Roman; text-align:justify ! important; }
.P91 { font-size:12pt; margin-bottom:0in; margin-top:0.05in; font-family:Times New Roman; text-align:justify ! important; }
.Standard { font-size:12pt; font-family:Times New Roman; }
.T1 { color:#f79646; }
.T2 { color:#f79646; font-family:Tahoma, sans-serif; font-size:7.5pt; }
.T3 { color:#3329b1; font-family:Tahoma, sans-serif; font-size:7.5pt; }
{ }
</style>
<table>
<tbody>
<tr>
<td>
<div class="P1">
<div style="height: 0.8543in;width: 2in;" id="graphics1"
class="fr1">
<p>
<img
src="cid:part1.04030906.02060507@h3c-energies.fr"></p>
<p class="P2">Le futur maîtrisé</p>
</div>
</div>
</td>
<td>
<br>
</td>
<td>
<p class="P3">Thibaut VITTE</p>
<p class="P61">Docteur - Ingénieur Energies</p>
<p class="P91"><span class="T2">Mail : </span><span
class="T3"><a class="moz-txt-link-abbreviated" href="mailto:thibaut.vitte@h3c-energies.fr">thibaut.vitte@h3c-energies.fr</a> </span>
</p>
<p class="P10">-----------------------------</p>
<p class="P4">H3C-énergies</p>
<p class="P6">35, chemin du vieux Chêne - 38240 MEYLAN</p>
<p class="P9"><span class="T2">Tél : </span><span
class="T3">04 76 41 88 66</span><span class="T1"> </span><span
class="T2">Fax : </span><span class="T3">04 76 41 28
94</span></p>
<p class="P5"><a class="moz-txt-link-abbreviated" href="http://www.h3c-energies.fr">www.h3c-energies.fr</a></p>
</td>
<td>
<br>
</td>
</tr>
</tbody>
</table>
<p class="P10">-----------------------------------------------------------------------------------</p>
<p class="P7">Afin de contribuer au respect de l'environnement,
merci de n'imprimer ce message qu'en cas de nécessité.</p>
<p class="P8">In order to respect the environment, please don't
print this e-mail unless you really need to.</p>
<p class="Standard">
</p>
</div>
</body>
</html>