Mincut basics - Giswater/giswater_dbmodel GitHub Wiki

GOALS:

Know the basic concepts to configure as a minimum for a mincut to work. Also answer some common questions about errors that may occur.

DESCRIPTION:

Installation

  • It is necessary to have the 'pgrouting' EXTENSION installed.

Pre-configuration

  • MACRO-EXPLOITATION – as there is the possibility that the networks of two municipalities are linked, when a mincut is done it takes into account the macro-exploitation to which the section planned to cut belongs. For this reason it is very important that each macro-exploitation, except those with interconnected networks, have its own macro-exploitation. For the exceptions, the different interconnected macro-exploitation must be part of the same macro-exploitation so that the mincut is able to cut the network in several exploitations if necessary.

  • EXPLOITATIONS AND DEPOSITS - Fill the table ‘anl_mincut_inlet_x_exploitation’. Here the nodes of each exploitation that serve as 'inlets' (usually deposits or catchments) must be configured.

  • VALVE TYPES – In the ‘anl_mincut_selector_valve’ table, the different types of valve must be configured which the mincut must take into account. To be selected from the existing valve types in the 'node_type' table.

  • RETENTION VALVES - In the 'anl_mincut_checkvalve' table it is possible to optionally configure retention valves that only allow water to pass in one direction. To establish this direction of water, the id of the section to which the water circulates must be reported in the column ‘to_arc’.

Inventory

  • The elements of the network (arc / node) must have a value for state_type and only those that will be taken into account for the mincut which have is_operative = TRUE (in the value_state_type table).
  • Have the topology in order. All sections must have value for node_1 and node_2.
  • Valves cannot have NULL values for closed and broken fields.

FAQS:

I click on a section and it says that it has been found. What can happen?

This section is being displayed on the screen but it has a state_type with is_operative=_FALSE_. This can happen with sections with status IN SERVICE or PLANNED.

I have done a mincut and it has extra-exploitations problems. What can happen?

Verify that the 'anl_mincut_inlet_x_exploitation' table is properly configured. It is possible that a exploitation does not have a water inlet (inlet) configured and is supplied by inlets from other exploitations.

I have done a mincut and it stops midway with a visually incorrect result. What can happen?

There is topological inconsistency. Check the node1 and node2 of the sections where the mincut stops. It may also occur because the valve types are incorrectly configured in the 'anl_mincut_selector_valve' table and a value needs to be added.

Why doesn’t a mincut ignore specific values?

Check that the closed and broken fields have values for this valve.

I have made a mincut that should affect a network section in the planned state and it does not go well. What can happen?

The planned alternatives topology is complex. It may happen that, due to the error of the planning user, there is a duplicate node (in different states) that disconnects the network even though it appears visually correct. You have to check that: in the cut zone we are only viewing an alternative of the psector or that the arc-node topology and the state topology are correct.

How does to_arc work act and which are the configuration differences related to mapzones and go2epa?

Unfortunately the configuration is not unified for now. That is why the following table details depending on the analysis process that is needed where the configuration must be carried out: