SWMMVis  6.0.0-alpha.4
Qt6/C++ GIS-based graphical user interface for the SWMMVis engine (6.0.0-alpha.4)
Loading...
Searching...
No Matches
mesh2daquifermodel.h File Reference
#include <QAbstractTableModel>
#include <QList>
#include <QString>
#include <openswmm/engine/openswmm_engine.h>
Include dependency graph for mesh2daquifermodel.h:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

class  openswmmvis::ui::Mesh2DAquiferModel
 The [2D_AQUIFER] rows: scope, the five positional columns, and the law/closure selections. More...
 
class  openswmmvis::ui::Mesh2DAquiferNodeModel
 The [2D_AQUIFER_NODE] beds: which 1D node exchanges with which cell, through what conductance. More...
 

Namespaces

namespace  openswmmvis
 
namespace  openswmmvis::ui
 

Detailed Description

Author
Caleb Buahin caleb.nosp@m..bua.nosp@m.hin@g.nosp@m.mail.nosp@m..com
Date
2026
License\n GPL-3.0-or-later

GG2 / GG3 (2026-09-07) — MVC models for the two-zone groundwater kernel's authoring rows: [2D_AQUIFER] and [2D_AQUIFER_NODE].

The engine is the single source of truth. load() reads the rows through swmm_gw2d_row_* / swmm_gw2d_node_*, edits are staged here, and commit() writes the difference back. Staging rather than writing through matters for one reason worth stating: these rows seed the kernel at initialize, so the C API refuses them mid-run. A model that wrote through would fail silently on half a table; a model that stages can tell the user up front that the run has to be reset.

Values are in the PROJECT's units throughout — the same numbers the .inp carries and the same numbers the API takes. The dialog labels the columns from UnitSystem; nothing converts, so what the user types is what the file holds. (Converting in the GUI is how a saved model stops matching what was on screen.)