<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Thanks, Jon and Monika. Does the "known: boundary" type of node not count as a boundary node? I specified its ambient temerpature and pressure as 20C and 0 Pa, repsectively. Both unknown [zonal] nodes have connections to this node.<br><br>Liam<br><br><br><br>> From: jon@esru.strath.ac.uk<br>> To: obrien_liam@hotmail.com; esp-r@lists.strath.ac.uk<br>> Date: Fri, 10 Jul 2009 08:14:27 +0100<br>> Subject: [esp-r] Re: Problem with airflow network<br>> <br>> <br>> It is essential that there be at least one connection to a boundary node. The<br>> solver really needs this rule to be followed.<br>> <br>> For more information on defining air flow networks there is a chapter in the<br>> current version of the ESP-r Cookbook (ESRU web page -> software downloads -> esp-r<br>> -> beginners guide<br>> <br>> -Jon Hand<br>> ________________________________________<br>> From: esp-r-bounces@lists.strath.ac.uk [esp-r-bounces@lists.strath.ac.uk] On Behalf Of Liam O'Brien [obrien_liam@hotmail.com]<br>> Sent: 09 July 2009 20:24<br>> To: esp-r@lists.strath.ac.uk<br>> Subject: [esp-r] Problem with airflow network<br>> <br>> Hello everyone,<br>> <br>> I'm setting up a fairly rudimentary airflow network, in which two zone air nodes exchange air with a third node that is intended to mix the air and send it back to the nodes. A fixed volume rate component moves the air. The "mixing" node was assigned to known boundary conditions of P=0 Pa, T=20C. However, after several tries, I continue to get the following message for each timestep:<br>> <br>> Please check (in the following order) that:<br>> - each node has some flow path to a boundary pressure and<br>> - iteration convergence control is not too strict.<br>> Day 2 Month 1 Hour 24.000: 100 iterations; flows solution failed<br>> <br>> I assume the first issue is triggering the message. I would have thought that having the mixing node at known conditions would alleviate this error.<br>> <br>> Any thoughts? (I realize this could be accomplished in the operations file, but I want something more sophisticated eventually.)<br>> <br>> The afn file is below.<br>> <br>> Thanks very much!<br>> <br>> Liam O'Brien<br>> <br>> ----------------<br>> <br>> 3 1 4 1.000 (nodes, components, connections, wind reduction)<br>> Node Fld. Type Height Temperature Data_1 Data_2<br>> south 1 0 2.5000 20.000 0.0000 250.01<br>> north 1 0 2.5000 20.000 0.0000 250.01<br>> Mixing 1 2 20.000 0.0000 0.0000 2.0000<br>> Component Type C+ L+ Description<br>> Circulation 30 2 0 Constant vol. flow rate component m = rho.a<br>> 1. 0.200000003<br>> +Node dHght -Node dHght via Component<br>> south 8.750 Mixing -8.750 Circulation<br>> north 8.750 Mixing -8.750 Circulation<br>> Mixing -8.750 south 8.750 Circulation<br>> Mixing -8.750 north 8.750 Circulation<br>> <br>> ________________________________<br>> Windows Live helps you keep up with all your friends, in one place.<http://go.microsoft.com/?linkid=9660824><br>> <br>> _______________________________________________<br>> esp-r mailing list<br>> esp-r@lists.strath.ac.uk<br>> http://lists.strath.ac.uk/mailman/listinfo/esp-r<br><br /><hr />Windows Live helps you keep up with all your friends, <a href='http://go.microsoft.com/?linkid=9660824' target='_new'>in one place.</a></body>
</html>