# 3.5.026

## INDEX

* [#inventory](#inventory "mention")
  * [#allow-users-to-input-init-end-nodes-in-arc-forms-when-they-are-null](#allow-users-to-input-init-end-nodes-in-arc-forms-when-they-are-null "mention")
  * [#check-redundant-values-for-elevation-fields-ud](#check-redundant-values-for-elevation-fields-ud "mention")
  * [#allow-hyperlinks-in-custom-form-to-be-editable](#allow-hyperlinks-in-custom-form-to-be-editable "mention")
  * [#manage-static-pressure-automatically](#manage-static-pressure-automatically "mention")
  * [#new-default-value-for-ymax-on-ud](#new-default-value-for-ymax-on-ud "mention")
  * [#new-default-value-for-users-to-search-municipality](#new-default-value-for-users-to-search-municipality "mention")
* [#om](#om "mention")
  * [#recalculate-mincut-when-execute-start-process](#recalculate-mincut-when-execute-start-process "mention")
  * [#new-columns-on-node-and-connec-mincut-result](#new-columns-on-node-and-connec-mincut-result "mention")
* [#epa](#epa "mention")
  * [#1d-2d-coupled-model-in-combination-with-swmm-iber](#1d-2d-coupled-model-in-combination-with-swmm-iber "mention")
  * [#enhance-valve-management-for-ws-go2epa-exportation](#enhance-valve-management-for-ws-go2epa-exportation "mention")
  * [#enable-work-with-crm-values-also-on-nodes-netwjoin](#enable-work-with-crm-values-also-on-nodes-netwjoin "mention")
  * [#improvements-on-dscenario-manager](#improvements-on-dscenario-manager "mention")
  * [#new-system-parameter-to-update-inventory-tables-when-change-epa-values](#new-system-parameter-to-update-inventory-tables-when-change-epa-values "mention")

## INVENTORY

### <mark style="color:blue;">Allow users to input init/end nodes in arc forms when they are NULL</mark>

When somehow the value of **node\_1 or node\_2 on arcs is NULL**, users are now capable of just **write** down the node\_id in the custom form widget and the arc will be reconnected to such node and topology recovered.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FjoKZY7zRliKb6kV1gZbh%2Fimage.png?alt=media\&token=8afc39d8-84d4-4a28-973d-ab42bf185492)

### <mark style="color:blue;">Check redundant values for elevation fields (UD)</mark>

There are **three main columns** on UD schemas to manage **elevation data**:

* ***top\_elev***
* ***ymax***
* ***elevation***

Even they are all editable, it's mandatory to **only fill two of them**, otherwise values will be **redundant**. In this version this redundancy begin to be controlled, in two steps:

#### System variable to control values on forms

A new variable ***edit\_check\_redundance\_y\_topelev\_elev*** have been added to ***config\_param\_system*** table. If true, node and arc forms will show a <mark style="color:red;">**warning**</mark> message every time a redundant value appears (it will also show warning for existing values even the form is not in editing mode).

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FpRf6KTcIRJZpagaXZ0qe%2Fimage.png?alt=media\&token=adf7bcd2-e6ee-489b-a484-dd9c06546986)

#### New parameter on check project

A new parameter related to redundant values have been added to **check project** (and OM check data). Every time these processes are executed **redundant values will be checked**, returning if there are some or not.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2F1JgzZpQt4lGUR48JvRLA%2Fimage.png?alt=media\&token=ae8739c9-7a29-4726-baf3-f997c65fc4d7)

### <mark style="color:blue;">Allow hyperlinks in custom form to be editable</mark>

In this version, widgets configured as **hyperlinks** in element's custom form are editable. This is only possible when **form is in edition**, otherwise, the hyperlink will work as always, redirecting to the URL on click.

This propery **isn't configured by default**. To allow the hyperlink edition, ***config\_form\_fields*** table must be properly configured: column *'iseditable'* must be TRUE for the desired formname and columnname.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2Fq4tFxTFuz7ivm0nwvsbj%2Fimage.png?alt=media\&token=9b50f13f-400d-4aa2-94ce-3b749775ad2c)

### <mark style="color:blue;">Manage static pressure automatically</mark>

When **inserting a new node or connec**, the value for **static pressure** will be automatically calculated. This will only happen when:

* **Elevation** value of the element is already filled or user fill it before Accept.
* **Presszone** related to the element is filled and its *'head'* field on presszone table has value.

The **result** value of static pressure is: *presszone.head - elevation.*

This value will always be **recalculated when presszone** of the element **change**.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FzVfGIGFKBFEPWYsWO0kh%2Fimage.png?alt=media\&token=e1dfa4f2-c995-46c2-bac0-f4ea360a9fbd)

### <mark style="color:blue;">New default value for ymax on UD</mark>

A new default value is now available on **Configuration tool of Giswater** to manage a default value for ***ymax*** on nodes. This value will appear automatically on node forms when inserting a new one. As always, this value is manually modificable inside the form.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2F9bUsbKMFkstUgzydPVad%2Fimage.png?alt=media\&token=c6f937fd-3856-4e69-aa4d-79a36535ca0b)

### <mark style="color:blue;">New default value for users to search municipality</mark>

To search in the **Address tab**, now is possible to set a **default value** for the first widget, **Municipality**. This can be useful on networks distributed within many different municipalities, because some users may need to search always in the same municipality and they can configure this value to be already defined.

It needs to be set on the **Configuration tool of Giswater**, in the Basic first tab.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FJvatqNIOaXFUIY21t0Lc%2Fimage.png?alt=media\&token=218cb864-18c5-4c64-938d-47370be69099)

## OM

### <mark style="color:blue;">Recalculate mincut when execute start process</mark>

Now is possible to enable the **automatic recalculation of a mincut** when click the **Start process button**.&#x20;

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2Fy6FtiXZr5JiEuui8UiQn%2Fimage.png?alt=media\&token=ef82e479-f5e6-4f30-aa56-6b3c4dc7bd81)

The **resulting mincut could be different** if the affected network have suffered changes from the moment that mincut was planified. For example:

* Some valves have been closed
* Some arcs have been changed
* Some connecs have been added or removed

This recalculation is **not enabled by default**. To use it, ***redoOnStart*** variable from **Mincut settings** on Configuration tool of Giswater needs to be set ***'true'***. It's also possible to configure the **number of past days** from the mincut planification to execute this automatic recalculation or not.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2F4jc2vCDtjIid80n7d66t%2Fimage.png?alt=media\&token=37034c9a-d105-461f-9b72-80173ee31ecd)

### <mark style="color:blue;">New columns on node and connec mincut result</mark>

Two columns have been added on node and connec **mincut result views**, to provide some additional information when a mincut is calculated. These columns are:

* Mincut result node: <mark style="color:blue;">**node\_type**</mark> (type of node affected by the mincut).
* Mincut result connec: <mark style="color:blue;">**customer\_code**</mark> (code used to relate connecs to other DB).

## EPA

### <mark style="color:blue;">**1D/2D coupled model in combination with SWMM-IBER**</mark>

This feature have been developed according the agreement of Giswater Association with BarcelonaTech University in order to connect Giswater-SWMM with IBER enabling a real drainage coupled model 1D/2D. The goal is to generate a gully CSV file at th same time as the INP file is generated. This CSV file contains all the information that IBER needs to work with 1D/2D coupled model.

Many improvement have been done in this release to work with the 1D/2D coupled model. It is possible to emphasize:

* New parameters have been added on gis-side for gullies as well as groove dimensions or grate\_location.
* New two epa-type objects have been defined on epa-side: gully and netgully with all parameteres that IBER needs to work with 1D/2D coupled model as well as outlet\_type, method, a,b weir\_cd o orifice\_cd.
* New widget on go2epa options dialog have been create in order to control this exportation `network geometgry generator` with two options (1D-SWMM / 1D-2D SWMM-IBER)

In case of the new object epa\_type: gullies, only will be exported on the csv file used by IBER to load gully. SWMM file will not have it.&#x20;

In case of the new object epa\_type: netgullies, as well as it will be exported as JUNCTION on inp file, will be also exported on the CSV file as another gully.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FBQ3T4wQICVwkHDfBZ0Fm%2Fimage.png?alt=media\&token=d17fafb8-6814-4e79-bffe-0080c4719cd0)

### <mark style="color:blue;">Enhance valve management for ws go2epa exportation</mark>

The valve management on ws inp export files have been simplified. In fact, widget have disappeared. The status on gis-side acts as primary status (only open or closed) and the status of epa-side acts as secondary status which it means that when the gis-side is open the status of valve will be the status defined on epa-tables.&#x20;

At the same time the mincut\_result strategy have been removed from this side and have been added on the dscenario manager as well as one scenario more.

### <mark style="color:blue;">Enable work with CRM values also on nodes (netwjoin)</mark>

Until now, CRM values could only be related to connec features. In this version, the possibility to establish CRM values related to a Netwjoin -a specific kind of node which acts like a connec but breaking the network- have been enabled.&#x20;

Netwjoin table has customer\_code column, which will relate this node to hydrometer values and so is possible to create Dscenario demands using both connecs and netwjoins.

### <mark style="color:blue;">Improvements on Dscenario manager</mark>

Among some bug fix, some improvements have been done on the dscenario manager button. It is possible to emphasize:

* New button in dscenario to add layers to ToC easily. By click on this button, new layer will appear on ToC in order to make easy the massive edition of rows by using the native attribute table editor of QGIS.
* Enable dscenario strategy for controls and rules. On this version it is possible to create also scenarios for controls and rules, enabling new borders on the dscenario strategy.
* New actions and buttons. Duplicate scenario button and create dscenario valve from mincut action have been added on this version.

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FUQeTPY3uIb55bYKUAciY%2Fimage.png?alt=media\&token=8cdccf02-5f08-432e-abe7-631d91e8bb91)

### <mark style="color:blue;">New system parameter to update inventory tables when change EPA values</mark>

A new parameter have been added to system configuration. It's goal is to **automatically update values on inventory** tables whenever values are **changed on epa tables** (inp).

To use it, ***status*** on parameter **EPA auto update inventory tables** on the Configuration tool of Giswater must be ***'true'***. Then, it's also mandatory to configure the SQL query which will be executed if changes are made in the different available ***sourceTables***. For example (the alias on the query are mandatory):

{% tabs %}
{% tab title="inp\_tank" %}
`UPDATE man_tank t SET hmax=maxlevel FROM inp_tank s`
{% endtab %}

{% tab title="inp\_valve" %}
`UPDATE man_valve t SET pression_exit=pressure FROM inp_valve s`
{% endtab %}

{% tab title="inp\_pump" %}
`UPDATE man_pump t SET power=powerFROM inp_pump s`
{% endtab %}
{% endtabs %}

{% hint style="info" %}
It's important to know that columns from both tables are deeply related, which just happen in some cases.
{% endhint %}

![](https://78444640-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3OfYgdaTSD51CRsy2UO6%2Fuploads%2FssN8xIAIyJuKfpgB7MgR%2Fimage.png?alt=media\&token=8767e2ff-d7b7-43cb-b8c6-897ddd83df71)
