Menu
▾
▴
cwsnet-users — Help for the CWSNet end users
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(3) |
Oct
(3) |
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
(3) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: André W. <wss...@gm...> - 2013-01-04 17:31:29
|
Thanks for the response Michelle! Do you plan on implementing this constant energy pump? 2013/1/4 Michele Guidolin <M.G...@ex...> > > Also, I sent you guys an email last year about some changes I had to do in > order to compile CWS under C++ Builder, but soon after we had to put our > project on hold and just resumed it recently. I'm trying to separate all > the changes and will be sending it soon. > > |
|
From: Michele G. <M.G...@ex...> - 2013-01-04 13:47:44
|
Hi André On 04/01/13 11:44, André William wrote: > Hi, > > I got an error while trying to load an INP file into CWSNet that contained > pumps with the keyword POWER. Is this limitation intentional or am I doing > something wrong? The sample INP file is attached. > > Error msg: Pump type not implemented (missing HEAD token) > File: EpanetInput.cpp > Line: 3329 I'm sorry but constant energy pumps, which are created using POWER token in EPANET2, are not implemented in CWSNet. This is why this particular input file is giving you an error. > > Also, I sent you guys an email last year about some changes I had to do in > order to compile CWS under C++ Builder, but soon after we had to put our > project on hold and just resumed it recently. I'm trying to separate all > the changes and will be sending it soon. > > Thanks in advance! > André > Thanks André, I'm looking forward to implement these changes. Regards. Michele |
|
From: André W. <wss...@gm...> - 2013-01-04 11:44:41
|
Hi, I got an error while trying to load an INP file into CWSNet that contained pumps with the keyword POWER. Is this limitation intentional or am I doing something wrong? The sample INP file is attached. Error msg: Pump type not implemented (missing HEAD token) File: EpanetInput.cpp Line: 3329 Also, I sent you guys an email last year about some changes I had to do in order to compile CWS under C++ Builder, but soon after we had to put our project on hold and just resumed it recently. I'm trying to separate all the changes and will be sending it soon. Thanks in advance! André |
|
From: Michele G. <M.G...@ex...> - 2012-04-16 16:02:42
|
Hi William, unfortunately at the moment there are no plans to add a water quality modelling to CWSNet. This might be change in the future. If you want to add a WQ modelling into CWSNet by yourself, we will be more than happy to help you on it. Regards. Michele On 16/04/12 16:06, William Furnass wrote: > Hi, > > Any plans to introduce a Langrangian transport component into CWSNet? > If so, is it the intention to eventually allow for MSX-like > multi-species WQ modelling? > > Cheers, > |
|
From: William F. <wi...@th...> - 2012-04-16 15:06:31
|
Hi, Any plans to introduce a Langrangian transport component into CWSNet? If so, is it the intention to eventually allow for MSX-like multi-species WQ modelling? Cheers, -- Will Furnass Doctoral Student Pennine Water Group Department of Civil and Structural Engineering University of Sheffield Phone: +44 (0)114 22 25768 |
|
From: André W. <wss...@gm...> - 2012-02-10 18:15:07
|
Thanks Michelle. Since I have no previous experience with CMake, I wasn't able to make it work with Borland makefiles. I was able, however, to compile CWSNet under C++ Builder granted some tweaks were necessary. Would these modifications be of any interest for you? Thanks again! 2012/2/10 Michele Guidolin <M.G...@ex...>: > Dear André, > > sorry for the late answer. > > In CWSNet, we use CMake (http://www.cmake.org/cmake/resources/software.html) > to compile the code. > > In CMake, it is possible to create a building project for various compiler > and environment. For example GCC in Linux > (http://sourceforge.net/apps/trac/cwsnet/wiki/DevelopmentInLinux) or > Visual Studio in Windows > (http://sourceforge.net/apps/trac/cwsnet/wiki/DevelopmentInWindows). > > This two options are the only one that we tested. Unfortunately, we never > tested compiling CWSNet using Borland Builder since we don't have access to > this compiler. > > However, in CMake it is possible to crate a Borland Makefile by choosing > this option as generator: > http://www.cmake.org/cmake/help/cmake2.6docs.html#gen:BorlandMakefiles > > Please Let us know if you are able to compile CWSNet using Borland Compiler. > If it is not the case, please let us know any eventual compiling error. > > Hope this help. > Michele. > > > On 07/02/12 11:23, André William wrote: >> >> Hi! >> >> I'm currently developing with Epanet and OOTEN but I would really like >> to migrate to CWSNet. >> What would be the easiest way for me to import/convert/compile CWS >> under Borland/Embarcadero's C++ Builder, assuming it is possible? >> I tried converting both the static and shared libraries with the >> implib and coff2omf utilities, but they couldn't produce a working >> version. >> >> Thanks in advance! >> André William >> >> >> ------------------------------------------------------------------------------ >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-d2d >> _______________________________________________ >> CWSNet-users mailing list >> CWS...@li... >> https://lists.sourceforge.net/lists/listinfo/cwsnet-users |
|
From: Michele G. <M.G...@ex...> - 2012-02-10 10:18:16
|
Dear André, sorry for the late answer. In CWSNet, we use CMake (http://www.cmake.org/cmake/resources/software.html) to compile the code. In CMake, it is possible to create a building project for various compiler and environment. For example GCC in Linux (http://sourceforge.net/apps/trac/cwsnet/wiki/DevelopmentInLinux) or Visual Studio in Windows (http://sourceforge.net/apps/trac/cwsnet/wiki/DevelopmentInWindows). This two options are the only one that we tested. Unfortunately, we never tested compiling CWSNet using Borland Builder since we don't have access to this compiler. However, in CMake it is possible to crate a Borland Makefile by choosing this option as generator: http://www.cmake.org/cmake/help/cmake2.6docs.html#gen:BorlandMakefiles Please Let us know if you are able to compile CWSNet using Borland Compiler. If it is not the case, please let us know any eventual compiling error. Hope this help. Michele. On 07/02/12 11:23, André William wrote: > Hi! > > I'm currently developing with Epanet and OOTEN but I would really like > to migrate to CWSNet. > What would be the easiest way for me to import/convert/compile CWS > under Borland/Embarcadero's C++ Builder, assuming it is possible? > I tried converting both the static and shared libraries with the > implib and coff2omf utilities, but they couldn't produce a working > version. > > Thanks in advance! > André William > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > CWSNet-users mailing list > CWS...@li... > https://lists.sourceforge.net/lists/listinfo/cwsnet-users |
|
From: André W. <wss...@gm...> - 2012-02-07 11:23:55
|
Hi! I'm currently developing with Epanet and OOTEN but I would really like to migrate to CWSNet. What would be the easiest way for me to import/convert/compile CWS under Borland/Embarcadero's C++ Builder, assuming it is possible? I tried converting both the static and shared libraries with the implib and coff2omf utilities, but they couldn't produce a working version. Thanks in advance! André William |
|
From: Sam H. <sam...@gm...> - 2011-08-15 17:30:09
|
Michele: That's wonderful news. I'm glad to hear that the rumors were greatly exaggerated. Can you say if you have chosen CUDA or OpenCL for the GP/GPU portion? I'm also curious about the capability to save .inp files (for a read/modify/write workflow) and export hydraulic results (in a familiar binary file format, for instance). And I'm sure many folks will wonder about water quality simulation. Many thanks! sam On Aug 15, 2011, at 7:01 AM, Michele Guidolin wrote: > Dear All, > > the project is still alive. > > Me and Pavel are still working on it. The main difference is that we have been both assigned to new projects. Thus, we don't have as much time as before to improve CWSNet. > > We are hoping to have version 1.0.3 released as soon as possible. > This new version fixes some bugs, has a better internal structure of the code, and add some new features. Some of the new features are SIMD instructions and GPGPU which improve the solver performance. > > Furthermore, I'm trying to optimise the internal structure of CWSNet in order to speed up the computation. This will be version 1.1.0. > > As always, if you have any suggestion about any new features that you would like to see implemented, just send an email to us. > > > Regards. > Michele > > On 14/08/11 01:45, Sam Hatchett wrote: >> Hello. >> >> I'm wondering about the status of the CWSnet project, and the fate of Michele and Pavel; the last message on this mailing list was about 9 months ago. I have no idea how many people like me are still listening for news, but I would be grateful for a brief mention of status and direction. >> >> Thanks, >> sam hatchett >> >> >> >> ------------------------------------------------------------------------------ >> FREE DOWNLOAD - uberSVN with Social Coding for Subversion. >> Subversion made easy with a complete admin console. Easy >> to use, easy to manage, easy to install, easy to extend. >> Get a Free download of the new open ALM Subversion platform now. >> http://p.sf.net/sfu/wandisco-dev2dev >> _______________________________________________ >> CWSNet-users mailing list >> CWS...@li... >> https://lists.sourceforge.net/lists/listinfo/cwsnet-users |
|
From: Michele G. <M.G...@ex...> - 2011-08-15 11:01:19
|
Dear All, the project is still alive. Me and Pavel are still working on it. The main difference is that we have been both assigned to new projects. Thus, we don't have as much time as before to improve CWSNet. We are hoping to have version 1.0.3 released as soon as possible. This new version fixes some bugs, has a better internal structure of the code, and add some new features. Some of the new features are SIMD instructions and GPGPU which improve the solver performance. Furthermore, I'm trying to optimise the internal structure of CWSNet in order to speed up the computation. This will be version 1.1.0. As always, if you have any suggestion about any new features that you would like to see implemented, just send an email to us. Regards. Michele On 14/08/11 01:45, Sam Hatchett wrote: > Hello. > > I'm wondering about the status of the CWSnet project, and the fate of Michele and Pavel; the last message on this mailing list was about 9 months ago. I have no idea how many people like me are still listening for news, but I would be grateful for a brief mention of status and direction. > > Thanks, > sam hatchett > > > > ------------------------------------------------------------------------------ > FREE DOWNLOAD - uberSVN with Social Coding for Subversion. > Subversion made easy with a complete admin console. Easy > to use, easy to manage, easy to install, easy to extend. > Get a Free download of the new open ALM Subversion platform now. > http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > CWSNet-users mailing list > CWS...@li... > https://lists.sourceforge.net/lists/listinfo/cwsnet-users |
|
From: Benninger F. <fre...@la...> - 2011-08-14 20:42:01
|
Hello, We also expect a lot from this project. But now we continue to use the extension Epanet2 with MSX (Multi-Species eXtension) Salutations F.Benninger > -----Message d'origine----- > De : Sam Hatchett [mailto:sam...@gm...] > Envoyé : dimanche 14 août 2011 02:46 > À : cws...@li... > Objet : [CWSNet-users] project status? > > Hello. > > I'm wondering about the status of the CWSnet project, and the fate of > Michele and Pavel; the last message on this mailing list was about 9 > months ago. I have no idea how many people like me are still listening > for news, but I would be grateful for a brief mention of status and > direction. > > Thanks, > sam hatchett > > > > ----------------------------------------------------------------------- > ------- > FREE DOWNLOAD - uberSVN with Social Coding for Subversion. > Subversion made easy with a complete admin console. Easy > to use, easy to manage, easy to install, easy to extend. > Get a Free download of the new open ALM Subversion platform now. > http://p.sf.net/sfu/wandisco-dev2dev > _______________________________________________ > CWSNet-users mailing list > CWS...@li... > https://lists.sourceforge.net/lists/listinfo/cwsnet-users |
|
From: Sam H. <sam...@gm...> - 2011-08-14 00:45:42
|
Hello. I'm wondering about the status of the CWSnet project, and the fate of Michele and Pavel; the last message on this mailing list was about 9 months ago. I have no idea how many people like me are still listening for news, but I would be grateful for a brief mention of status and direction. Thanks, sam hatchett |
|
From: Michele G. <M.G...@ex...> - 2010-11-10 12:58:57
|
The second patch version of CWSNet library has been made available to general public, see https://sourceforge.net/projects/cwsnet/files/ The main change in this version of CWSNet is the creation of a common interface for Connectivity classes. The objects with this common interface are used to found the eventual nodes and links that are not connected to a source node. The demand driven and pressure driven solvers now produce new messages which indicate when various nodes and links are disconnected from any source nodes. The messages produced are slightly different from the one in EPANET2, since it is considered that water cannot flow against the pumping direction of a pump. The minor updates for this version are: * Added the code that read [COORDINATES] and [VERTICES] sections from an EPANET2 input file * The hydraulic_solver demo now accepts various command line arguments which can change the behaviour of the hydraulic simulation and the respective output report. * Few bug fixes in the demand driven hydraulic solver. Please see the release notes or the NEWS file in the source package for further details. Please see the link http://cwsnet.sourceforge.net/docs-1.0/html/index.html for the last API documentation. |
|
From: Sam H. <sam...@gm...> - 2010-10-13 17:07:11
|
Pavel:
Thanks for taking time to explain all of this so clearly. I agree that it is "magic" - a very nice and elegant solution, and it works like a charm. I agree that this information needs to be made available on the wiki -- if I can be of any help in writing that portion, please just say so!
sam
On Oct 8, 2010, at 8:03 PM, Pavel Burovskiy wrote:
> Hi Sam,
>
> This is one of those key points which are too obvious when you are a developer. Thanks for spotting this, we will make a wiki page about. At the time, there are several solutions depending on what you are doing.
>
> Before going into details: I would strongly discourage you from using dynamic_cast, string comparison or switch control structure inside the loop (because all these is computationally slow).
>
> First, if you need iterating through all nodes of type CWS::Tank, you may retrieve a container of tanks via network->characteristics()->tanks(). Same applies to retrieving containers of CWS::Reservoir, CWS::Pump and CWS::Valve. If you need iterating through nodes or links of any other type, you need to use visitor pattern. This point is crucial for the whole CWSNet design.
>
> The scheme is the following. You are iterating through the container of elements of different type (up to inheritance) and for each element you have a call like {(*iterator)->accept(specific_action_visitor);}, where specific_action_visitor is the class derived from CWS::Visitor or CWS::ConstVisitor. Every child of these two classes should have overloaded methods visit(...) where "..." stands for the pointer to each type of hydraulic elements. Then, every call mentioned above results in execution of method specific_action_visitor->visit(...) corresponding to the type of element to which (*iterator) points to.
>
> This magic is actually simple: if network node container consists of one CWS::Tank and one CWS::Junction, you will perform two iterations through the container; at the first iteration, specific_action_visitor->visit(CWS::Tank *) is executed; at the second iteration, specific_action_visitor->visit(CWS::Junction *) is executed. Very similar to the switch statement, but differently implemented.
>
> For the example I would suggest to look into the code of HYD::DD::InspectSourceNode class (src/impl/hyd/dd/InspectSourceNode.hpp file) and scroll down to line 163. The HYD:DD::HydraulicSteadyState class calls HYD::DD::InspectSourceNode iterating through all network nodes, and what happens? Nothing for every node of type CWS::Junction. The outflow is computed for every node of type CWS::Reservoir, CWS::CylindricalTank and CWS::VolumeCurveTank, and for nodes of the last two types protected method checkTankTimeStep(...) is called.
>
> Hope this helps,
>
> Pavel Burovskiy.
>
>> Greetings. I'm having a blast going through the CWSnet code! I hope everyone else is, too.
>>
>> Quick (hopefully easy) question that I could not find an answer to in the online wiki or api docs:
>>
>> When iterating through the network nodes container, it's not very clear how to determine the type of node returned, other than calling CWS::Node::typeName() and testing the string returned against, for instance, "Tank". It looks like the base code uses a series of tests like {dynamic_cast<CWS::Tank*>(someNode) != 0} to determine the node type, but this seems just as kludgey as string comparison and makes using a switch control structure impossible.
>>
>> Surely there is an elegant solution?
>>
>> Thanks for your thoughts!
>>
>> sam hatchett
>> _______________________________________________
>> CWSNet-users mailing list
>> CWS...@li...
>> https://lists.sourceforge.net/lists/listinfo/cwsnet-users
>
|
|
From: Pavel B. <P.B...@ex...> - 2010-10-09 00:03:41
|
Hi Sam,
This is one of those key points which are too obvious when you are a
developer. Thanks for spotting this, we will make a wiki page about. At
the time, there are several solutions depending on what you are doing.
Before going into details: I would strongly discourage you from using
dynamic_cast, string comparison or switch control structure inside the
loop (because all these is computationally slow).
First, if you need iterating through all nodes of type CWS::Tank, you
may retrieve a container of tanks via
network->characteristics()->tanks(). Same applies to retrieving
containers of CWS::Reservoir, CWS::Pump and CWS::Valve. If you need
iterating through nodes or links of any other type, you need to use
visitor pattern. This point is crucial for the whole CWSNet design.
The scheme is the following. You are iterating through the container of
elements of different type (up to inheritance) and for each element you
have a call like {(*iterator)->accept(specific_action_visitor);}, where
specific_action_visitor is the class derived from CWS::Visitor or
CWS::ConstVisitor. Every child of these two classes should have
overloaded methods visit(...) where "..." stands for the pointer to each
type of hydraulic elements. Then, every call mentioned above results in
execution of method specific_action_visitor->visit(...) corresponding to
the type of element to which (*iterator) points to.
This magic is actually simple: if network node container consists of one
CWS::Tank and one CWS::Junction, you will perform two iterations through
the container; at the first iteration,
specific_action_visitor->visit(CWS::Tank *) is executed; at the second
iteration, specific_action_visitor->visit(CWS::Junction *) is executed.
Very similar to the switch statement, but differently implemented.
For the example I would suggest to look into the code of
HYD::DD::InspectSourceNode class (src/impl/hyd/dd/InspectSourceNode.hpp
file) and scroll down to line 163. The HYD:DD::HydraulicSteadyState
class calls HYD::DD::InspectSourceNode iterating through all network
nodes, and what happens? Nothing for every node of type CWS::Junction.
The outflow is computed for every node of type CWS::Reservoir,
CWS::CylindricalTank and CWS::VolumeCurveTank, and for nodes of the last
two types protected method checkTankTimeStep(...) is called.
Hope this helps,
Pavel Burovskiy.
> Greetings. I'm having a blast going through the CWSnet code! I hope everyone else is, too.
>
> Quick (hopefully easy) question that I could not find an answer to in the online wiki or api docs:
>
> When iterating through the network nodes container, it's not very clear how to determine the type of node returned, other than calling CWS::Node::typeName() and testing the string returned against, for instance, "Tank". It looks like the base code uses a series of tests like {dynamic_cast<CWS::Tank*>(someNode) != 0} to determine the node type, but this seems just as kludgey as string comparison and makes using a switch control structure impossible.
>
> Surely there is an elegant solution?
>
> Thanks for your thoughts!
>
> sam hatchett
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
> Spend less time writing and rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> CWSNet-users mailing list
> CWS...@li...
> https://lists.sourceforge.net/lists/listinfo/cwsnet-users
|
|
From: Sam H. <sam...@gm...> - 2010-10-08 19:19:14
|
Greetings. I'm having a blast going through the CWSnet code! I hope everyone else is, too.
Quick (hopefully easy) question that I could not find an answer to in the online wiki or api docs:
When iterating through the network nodes container, it's not very clear how to determine the type of node returned, other than calling CWS::Node::typeName() and testing the string returned against, for instance, "Tank". It looks like the base code uses a series of tests like {dynamic_cast<CWS::Tank*>(someNode) != 0} to determine the node type, but this seems just as kludgey as string comparison and makes using a switch control structure impossible.
Surely there is an elegant solution?
Thanks for your thoughts!
sam hatchett
|
|
From: Michele G. <M.G...@ex...> - 2010-09-22 12:09:35
|
Dear Kobus, the binary packages (named: Windows-x86-Relase, Windows-x86-Debug, Linux-i686-Release, Linux-i686-Debug) contain only the pre-compiled library (static and shared) and the header files in order to use the library. The source packages (named: Source) contains all the source code of the library. Thus, it contains the header files, the cpp source files and all the other files (CMake, inputs examples, etc). The source packages should contains all the files of the library, if this is not the case please let us know. In fact by using Cmake, it is possible to recompile and create your own binary packages from the file in the source packages. Furthermore, we are using the sourceforge public subversion repository for the source code, see https://sourceforge.net/scm/?type=svn&group_id=339916 From this repository, you can download the current version of the software with the day by day development. About user guide or helps, it is possible to find the documentation in the main sourceforge web-site of the project, see: http://cwsnet.sourceforge.net/ In this web site, we have a wiki system with the documentation on how to compile and use the library, and some information about the internals of the code. Furthermore, we have a tickets system that you can use if you find any bugs or if you want to promote any new feature. Any suggestions or problems that you find in the code or documentation is more than welcome. Regards. Michele. Kobus van Zyl wrote: > I noticed that very few source (cpp) files are provided with the CWSNet > library, and mostly only the header (hpp) files. Am I missing something, or > do you intend to keep the source files hidden? > > > > I have not been able to find any user guide or help file on the Sourceforge > site. Where will I be able to obtain this? > > > > Thanks in advance > > Kobus van Zyl > > > > > > > > > ### > UNIVERSITY OF CAPE TOWN > > This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 4500. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity. > > ### > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > CWSNet-users mailing list > CWS...@li... > https://lists.sourceforge.net/lists/listinfo/cwsnet-users |
|
From: Kobus v. Z. <kob...@uc...> - 2010-09-22 11:45:05
|
I noticed that very few source (cpp) files are provided with the CWSNet library, and mostly only the header (hpp) files. Am I missing something, or do you intend to keep the source files hidden? I have not been able to find any user guide or help file on the Sourceforge site. Where will I be able to obtain this? Thanks in advance Kobus van Zyl ### UNIVERSITY OF CAPE TOWN This e-mail is subject to the UCT ICT policies and e-mail disclaimer published on our website at http://www.uct.ac.za/about/policies/emaildisclaimer/ or obtainable from +27 21 650 4500. This e-mail is intended only for the person(s) to whom it is addressed. If the e-mail has reached you in error, please notify the author. If you are not the intended recipient of the e-mail you may not use, disclose, copy, redirect or print the content. If this e-mail is not related to the business of UCT it is sent by the sender in the sender's individual capacity. ### |
|
From: Michele G. <M.G...@ex...> - 2010-09-15 15:47:48
|
The first patch version of CWSNet library has been made available to general public, see https://sourceforge.net/projects/cwsnet/files/ This version provides minor update to the previous version: * Several bugs are fixed in the demand driven hydraulic solver, mainly in the management of control valves. * The PD_EMIT hydraulic solver, which introduces emitter-type pressure-demand dependency, is now in working (beta) stage. Please see the release notes or the NEWS file in the source package for further details. |
|
From: Michele G. <M.G...@ex...> - 2010-08-06 15:11:45
|
This is another test to see if Pasha receive any email. |
|
From: Michele G. <M.G...@ex...> - 2010-08-06 15:04:32
|
This is another test to see if Pasha receive this. |
|
From: Michele G. <M.G...@ex...> - 2010-08-06 09:19:41
|
Another mailing list test |
|
From: Michele G. <M.G...@ex...> - 2010-08-06 09:06:57
|
This is another test |
1 message has been excluded from this view by a project administrator.
