A junction object stores only a single demand pattern (enough for Anytown and Hanoi).

Base subnetworks

With the term base subnetworks, I refer to those sets of nodes or links indicating problem-independent elements. For example:

• Demand nodes (list of junctions where demand >0)
• Reservoir (list of junctions where type is reservoir)
  etc...

element and all the classes derived from it return a reference to int instead of the value.

instead of throwing std::runtime_error everywhere, create some specific error classes to simplify the passing and having the messages more constant.
todo:

• [] epanet_retrieve_error(int errorcode, string id)
• []

The new library structure is not working anymore on the problem Hanoi.

The command

_results_.strings().insert("NAME",bevarmejo::wds::vars::variable<std::string>("unit", "test"));

can not build.

There is no copy constructor for EPANET projects, as the project is in C++. However, when using EPANET with C++ projects, it's a necessary feature to have copy constructors.

Both Node and Link classes contains pointers to the others for connecting purposes. However, through Node::links() I am getting the std::unordered_set<link*> this is ok as with set I can't modify the set (changing the pointers without using insert or remove) otherwise it would lose invariance. However, I could still modify the links to which it is pointing. Adding the const qualifier to the set would make the set unchangeable (i.e., no insert or remove anymore).
What I want is to return a std::unordered_set<const link*>, i.e., a set of pointers to constant objects, so that one could access them but not mess with them.
Still they remain destroyable... Requires thinking

I ran the optimization on the server and noticed that even with the largest diameters, the pressure deficit was still very high, which should not be the case. There must be some bug in the code.

For a series of subnetworks (e.g., nodes, reservoirs, pumps) I may have to extract a series of properties (e.g., head, pressure, flow) for a time series (t = [0, 1, ...]) and since each subnetwork has a series of elements the resulting combination is a std::vector<double>

Subnetworks are vectors of ids of the network with additional capabilities, e.g., comments.
In the future I may want to add a dynamic tracking of indexes, but let's see.

Write documentation for the build and run of the program for the use cases.

It should be hosted on GitHub and have a resemblance with Pagmo documentation. In the structure, not in the look.

EPANET prints stuff on the screen every time it is open, closed, created, or destructed, and does a simulation.

A settings file should pass all the information necessary. Thiw will be an XML file. The other type of data may have a different structure. It has to be decided.

When saving files, all the paths must exist; we have to deal with it automatically.

The calculation of the cost is wrong:

• Net Present Value has to be calculated for all the years' cash flow.
• Electricity cost is a yearly value, not daily

Several functions are useful for this class, especially since it is also inherited from patterns and hence demand and pump scheduling or similar.

• start time
• duration (end time - start time)
• has regular intervals ?
• values (i.e., a vector stripped of the time)