epyt-flow 0.1.0__tar.gz

epyt_flow-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

epyt_flow-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 EPyT-Flow Developers
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

epyt_flow-0.1.0/MANIFEST.in

@@ -0,0 +1,13 @@
+include epyt_flow/VERSION
+recursive-include epyt_flow/EPANET *
+exclude .*
+exclude DEVELOPERS.md
+exclude REQUIREMENTS-DEV.txt
+exclude noxfile.py
+exclude Makefile
+exclude make.bat
+recursive-exclude examples/ *
+recursive-exclude paper/ *
+recursive-exclude docs/ *
+recursive-exclude tests/ *
+recursive-exclude .github/ *

epyt_flow-0.1.0/PKG-INFO

@@ -0,0 +1,139 @@
+Metadata-Version: 2.1
+Name: epyt-flow
+Version: 0.1.0
+Summary: EPyT-Flow -- EPANET Python Toolkit - Flow
+Author-email: André Artelt <aartelt@techfak.uni-bielefeld.de>, "Marios S. Kyriakou" <kiriakou.marios@ucy.ac.cy>, "Stelios G. Vrachimis" <vrachimis.stelios@ucy.ac.cy>
+License: MIT License
+Project-URL: Homepage, https://github.com/WaterFutures/EPyT-Flow
+Project-URL: Documentation, https://epytflow.readthedocs.io/en/latest/
+Project-URL: Repository, https://github.com/WaterFutures/EPyT-Flow.git
+Project-URL: Issues, https://github.com/WaterFutures/EPyT-Flow/issues
+Keywords: epanet,water,networks,hydraulics,quality,simulations
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: epyt>=1.1.3
+Requires-Dist: requests>=2.31.0
+Requires-Dist: scipy>=1.11.4
+Requires-Dist: u-msgpack-python>=2.8.0
+Requires-Dist: networkx>=3.2.1
+Requires-Dist: scikit-learn>=1.4.0
+Requires-Dist: tqdm>=4.66.2
+Requires-Dist: openpyxl>=3.1.2
+Requires-Dist: falcon>=3.1.3
+Requires-Dist: multiprocess>=0.70.16
+Requires-Dist: psutil
+
+# EPyT-Flow -- EPANET Python Toolkit - Flow
+
+EPyT-Flow is a Python package building on top of [EPyT](https://github.com/OpenWaterAnalytics/EPyT) 
+for providing easy access to water distribution network simulations.
+It aims to provide a high-level interface for the easy generation of hydraulic and water quality scenario data.
+However, it also provides access to low-level functions by [EPANET](https://github.com/USEPA/EPANET2.2) 
+and [EPANET-MSX](https://github.com/USEPA/EPANETMSX/).
+
+EPyT-Flow provides easy access to popular benchmark data sets for event detection and localization.
+Furthermore, it also provides an environment for developing and testing control algorithms.
+
+![](https://github.com/WaterFutures/EPyT-Flow/blob/main/docs/_static/net1_plot.png?raw=true)
+
+## Installation
+
+EPyT-Flow supports Python 3.9 - 3.12
+
+Note that [EPANET and EPANET-MSX sources](epyt_flow/EPANET/) are compiled and overrite the binaries
+shipped by EPyT IF EPyT-Flow is installed on a Linux system. By this we not only aim to achieve
+a better performance of the simulations but also avoid any compatibility problems of pre-compiled binaries.
+
+### PyPI
+
+```
+pip install epyt-flow
+```
+
+### Git
+Download or clone the repository:
+```
+git clone https://github.com/WaterFutures/EPyT-Flow.git
+cd EPyT-Flow
+```
+
+Install all requirements as listed in [REQUIREMENTS.txt](REQUIREMENTS.txt):
+```
+pip install -r REQUIREMENTS.txt
+```
+
+Install the toolbox:
+```
+pip install .
+```
+
+## Quick Example
+
+<a target="_blank" href="https://colab.research.google.com/github/WaterFutures/EPyT-Flow/blob/main/docs/examples/basic_usage.ipynb">
+<img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open In Colab"/>
+</a>
+
+```python
+from epyt_flow.data.benchmarks import load_leakdb_scenarios
+from epyt_flow.simulation import ScenarioSimulator
+from epyt_flow.utils import to_seconds
+
+
+if __name__ == "__main__":
+    # Load first Hanoi scenario from LeakDB
+    network_config, = load_leakdb_scenarios(scenarios_id=["1"], use_net1=False)
+
+    # Create scenario
+    with ScenarioSimulator(scenario_config=network_config) as sim:
+        # Set simulation duration to two days
+        sim.set_general_parameters(simulation_duration=to_seconds(days=2))
+
+        # Place pressure sensors at nodes "13", "16", "22", and "30"
+        sim.set_pressure_sensors(sensor_locations=["13", "16", "22", "30"])
+
+        # Place a flow sensor at link/pipe "1"
+        sim.set_flow_sensors(sensor_locations=["1"])
+
+        # Run entire simulation
+        scada_data = sim.run_simulation()
+
+        # Show sensor readings over the entire simulation
+        print(f"Pressure readings: {scada_data.get_data_pressures()}")
+        print(f"Flow readings: {scada_data.get_data_flows()}")
+```
+
+## Documentation
+
+Documentation is available on readthedocs: [https://epytflow.readthedocs.io/en/latest/](https://epytflow.readthedocs.io/en/latest/)
+
+## License
+
+MIT license -- see [LICENSE](LICENSE)
+
+## How to Cite?
+
+If you use this software, please cite it as follows:
+
+```
+@misc{github:epytflow,
+        author = {André Artelt, Marios S. Kyriakou, Stelios G. Vrachimis, Demetrios G. Eliades, Barbara Hammer, Marios M. Polycarpou},
+        title = {EPyT-Flow -- EPANET Python Toolkit - Flow},
+        year = {2024},
+        publisher = {GitHub},
+        journal = {GitHub repository},
+        howpublished = {\url{https://github.com/WaterFutures/EPyT-Flow}}
+    }
+```
+
+## How to Contribute?
+
+Contributions (e.g. creating issues, pull-requests, etc.) are welcome -- please make sure to read the [code of conduct](CODE_OF_CONDUCT.md) and follow the [developers' guidelines](DEVELOPERS.md).

epyt_flow-0.1.0/README.md

@@ -0,0 +1,105 @@
+# EPyT-Flow -- EPANET Python Toolkit - Flow
+
+EPyT-Flow is a Python package building on top of [EPyT](https://github.com/OpenWaterAnalytics/EPyT) 
+for providing easy access to water distribution network simulations.
+It aims to provide a high-level interface for the easy generation of hydraulic and water quality scenario data.
+However, it also provides access to low-level functions by [EPANET](https://github.com/USEPA/EPANET2.2) 
+and [EPANET-MSX](https://github.com/USEPA/EPANETMSX/).
+
+EPyT-Flow provides easy access to popular benchmark data sets for event detection and localization.
+Furthermore, it also provides an environment for developing and testing control algorithms.
+
+![](https://github.com/WaterFutures/EPyT-Flow/blob/main/docs/_static/net1_plot.png?raw=true)
+
+## Installation
+
+EPyT-Flow supports Python 3.9 - 3.12
+
+Note that [EPANET and EPANET-MSX sources](epyt_flow/EPANET/) are compiled and overrite the binaries
+shipped by EPyT IF EPyT-Flow is installed on a Linux system. By this we not only aim to achieve
+a better performance of the simulations but also avoid any compatibility problems of pre-compiled binaries.
+
+### PyPI
+
+```
+pip install epyt-flow
+```
+
+### Git
+Download or clone the repository:
+```
+git clone https://github.com/WaterFutures/EPyT-Flow.git
+cd EPyT-Flow
+```
+
+Install all requirements as listed in [REQUIREMENTS.txt](REQUIREMENTS.txt):
+```
+pip install -r REQUIREMENTS.txt
+```
+
+Install the toolbox:
+```
+pip install .
+```
+
+## Quick Example
+
+<a target="_blank" href="https://colab.research.google.com/github/WaterFutures/EPyT-Flow/blob/main/docs/examples/basic_usage.ipynb">
+<img src="https://colab.research.google.com/assets/colab-badge.svg" alt="Open In Colab"/>
+</a>
+
+```python
+from epyt_flow.data.benchmarks import load_leakdb_scenarios
+from epyt_flow.simulation import ScenarioSimulator
+from epyt_flow.utils import to_seconds
+
+
+if __name__ == "__main__":
+    # Load first Hanoi scenario from LeakDB
+    network_config, = load_leakdb_scenarios(scenarios_id=["1"], use_net1=False)
+
+    # Create scenario
+    with ScenarioSimulator(scenario_config=network_config) as sim:
+        # Set simulation duration to two days
+        sim.set_general_parameters(simulation_duration=to_seconds(days=2))
+
+        # Place pressure sensors at nodes "13", "16", "22", and "30"
+        sim.set_pressure_sensors(sensor_locations=["13", "16", "22", "30"])
+
+        # Place a flow sensor at link/pipe "1"
+        sim.set_flow_sensors(sensor_locations=["1"])
+
+        # Run entire simulation
+        scada_data = sim.run_simulation()
+
+        # Show sensor readings over the entire simulation
+        print(f"Pressure readings: {scada_data.get_data_pressures()}")
+        print(f"Flow readings: {scada_data.get_data_flows()}")
+```
+
+## Documentation
+
+Documentation is available on readthedocs: [https://epytflow.readthedocs.io/en/latest/](https://epytflow.readthedocs.io/en/latest/)
+
+## License
+
+MIT license -- see [LICENSE](LICENSE)
+
+## How to Cite?
+
+If you use this software, please cite it as follows:
+
+```
+@misc{github:epytflow,
+        author = {André Artelt, Marios S. Kyriakou, Stelios G. Vrachimis, Demetrios G. Eliades, Barbara Hammer, Marios M. Polycarpou},
+        title = {EPyT-Flow -- EPANET Python Toolkit - Flow},
+        year = {2024},
+        publisher = {GitHub},
+        journal = {GitHub repository},
+        howpublished = {\url{https://github.com/WaterFutures/EPyT-Flow}}
+    }
+```
+
+## How to Contribute?
+
+Contributions (e.g. creating issues, pull-requests, etc.) are welcome -- please make sure to read the [code of conduct](CODE_OF_CONDUCT.md) and follow the [developers' guidelines](DEVELOPERS.md).

epyt_flow-0.1.0/REQUIREMENTS.txt

@@ -0,0 +1,11 @@
+epyt>=1.1.3
+requests>=2.31.0
+scipy>=1.11.4
+u-msgpack-python>=2.8.0
+networkx>=3.2.1
+scikit-learn>=1.4.0
+tqdm>=4.66.2
+openpyxl>=3.1.2
+falcon>=3.1.3
+multiprocess>=0.70.16
+psutil

epyt_flow-0.1.0/epyt_flow/EPANET/EPANET/SRC_engines/AUTHORS

@@ -0,0 +1,28 @@
+# Authors ordered alphabetically
+
+Authors with Contributions in the Public Domain:
+
+Lewis Rossman <LRossman@cinci.rr.com>
+Michael Tryby <tryby.michael@epa.gov>
+
+Authors with Contributions Subject to Copyright (see LICENSE):
+
+Jinduan Chen <jinduan.uc@gmail.com>
+Maurizio Cingi <mrzcng2@gmail.com>
+Demetrios Eliades <eldemet@gmail.com>
+Will Furnass <will@thearete.co.uk>
+Milad Ghiami <milad-ghiami@users.noreply.github.com>
+Sam Hatchett <samhatchett@gmail.com>
+Abel Heinsbroek <mail@abelheinsbroek.nl>
+Mike Kane <muke195@gmail.com>
+Marios Kyriakou <mariosmsk@gmail.com>
+Steffen Macke <sdteffen@sdteffen.de>
+Angela Marchi <angela.marchi@adelaide.edu.au>
+Bryant McDonnell <bemcdonnell@gmail.com>
+Elad Salomons <selad@optiwater.com>
+Feng Shang <fshang>
+Yunier Soad <yunier.soad@gmail.com>
+Markus Sunela <markus.sunela@fluidit.fi>
+Tom Taxon <tntaxon@anl.gov>
+James Uber <jim@citilogics.com>
+Hyoungmin Woo <hyoungmin.woo@gmail.com>

epyt_flow-0.1.0/epyt_flow/EPANET/EPANET/SRC_engines/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2017 (see AUTHORS)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

epyt_flow-0.1.0/epyt_flow/EPANET/EPANET/SRC_engines/Readme_SRC_Engines.txt

@@ -0,0 +1,18 @@
+This folder archives the EPA/OWA and community collaboration source code files for the EPANET hydraulic and water quality engines for v2.2.0.
+
+It contains the source code for the EPANET 2.2 network hydraulic and water quality solver. 
+It is written in ANSI-compatible C and can be compiled into either a Windows Dynamic Link Library of functions
+or into a command-line executable.
+
+The DLL version of the solver (epanet2.dll) is used with
+the EPANET 2 user interface executable (epanet2w.exe) to
+form a complete Windows modeling package. It also serves
+as the function library for the EPANET Programmer's Toolkit,
+allowing developers to construct their own customized pipe
+network analysis applications.
+
+All the files except main.c are needed to build the DLL version of the solver.  
+The file main.c needs to be incudled for building a command-line executable. 
+Epanet2.def should be inculded as a module definition file
+for building the DLL that can be used in EPANET user inferface (epanet2w.exe).  
+

epyt_flow-0.1.0/epyt_flow/EPANET/EPANET/SRC_engines/enumstxt.h

@@ -0,0 +1,134 @@
+/*
+ *****************************************************************************
+ Project:      OWA EPANET
+ Version:      2.2
+ Module:       enumstxt.h
+ Description:  text strings for enumerated data types
+ Authors:      see AUTHORS
+ Copyright:    see AUTHORS
+ License:      see LICENSE
+ Last Updated: 06/20/2019
+ ******************************************************************************
+*/
+
+#ifndef ENUMSTXT_H
+#define ENUMSTXT_H
+#include "text.h"
+
+char *NodeTxt[]         = {t_JUNCTION,
+                           t_RESERVOIR,
+                           t_TANK}; 
+
+char *LinkTxt[]         = {w_CV, 
+                           w_PIPE,
+                           w_PUMP,
+                           w_PRV,
+                           w_PSV,
+                           w_PBV,
+                           w_FCV,
+                           w_TCV,
+                           w_GPV};
+
+char *StatTxt[]         = {t_XHEAD,
+                           t_TEMPCLOSED,
+                           t_CLOSED,
+                           t_OPEN,
+                           t_ACTIVE,
+                           t_XFLOW,
+                           t_XFCV,
+                           t_XPRESSURE,
+                           t_FILLING,
+                           t_EMPTYING,
+                           t_OVERFLOWING};
+
+char *FormTxt[]         = {w_HW,
+                           w_DW,
+                           w_CM};
+
+char *RptFormTxt[]      = {t_HW,
+                           t_DW,
+                           t_CM};
+
+char *RptFlowUnitsTxt[] = {u_CFS,
+                           u_GPM,
+                           u_MGD,
+                           u_IMGD,
+                           u_AFD,
+                           u_LPS,
+                           u_LPM,
+                           u_MLD,
+                           u_CMH,
+                           u_CMD};
+
+char *FlowUnitsTxt[]    = {w_CFS,
+                           w_GPM, 
+                           w_MGD,
+                           w_IMGD,
+                           w_AFD,
+                           w_LPS, 
+                           w_LPM, 
+                           w_MLD, 
+                           w_CMH,
+                           w_CMD};
+
+char *PressUnitsTxt[]   = {w_PSI,
+                           w_KPA,
+                           w_METERS};
+
+char *DemandModelTxt[] = { w_DDA,
+                           w_PDA,
+                           NULL };
+
+char *QualTxt[]         = {w_NONE,
+                           w_CHEM,
+                           w_AGE,
+                           w_TRACE};  
+
+
+char *SourceTxt[]       = {w_CONCEN,
+                           w_MASS,
+                           w_SETPOINT,
+                           w_FLOWPACED};
+
+char *ControlTxt[]      = {w_BELOW,
+                           w_ABOVE,
+                           w_TIME,
+                           w_CLOCKTIME};
+
+char *TstatTxt[]        = {w_NONE,
+                           w_AVG,
+                           w_MIN,
+                           w_MAX,
+                           w_RANGE};
+
+char *MixTxt[]          = {w_MIXED,
+                           w_2COMP,
+                           w_FIFO,
+                           w_LIFO, 
+                           NULL};
+
+char *RptFlagTxt[]      = {w_NO,
+                           w_YES,
+                           w_FULL};
+
+char *SectTxt[]         = {s_TITLE,     s_JUNCTIONS, s_RESERVOIRS,
+                           s_TANKS,     s_PIPES,     s_PUMPS,
+                           s_VALVES,    s_CONTROLS,  s_RULES,
+                           s_DEMANDS,   s_SOURCES,   s_EMITTERS,
+                           s_PATTERNS,  s_CURVES,    s_QUALITY,
+                           s_STATUS,    s_ROUGHNESS, s_ENERGY,
+                           s_REACTIONS, s_MIXING,    s_REPORT,
+                           s_TIMES,     s_OPTIONS,   s_COORDS,
+                           s_VERTICES,  s_LABELS,    s_BACKDROP,
+                           s_TAGS,      s_END,
+                           NULL};
+
+char *Fldname[]         = {t_ELEV,      t_DEMAND,    t_HEAD,
+                           t_PRESSURE,  t_QUALITY,   t_LENGTH,
+                           t_DIAM,      t_FLOW,      t_VELOCITY,
+                           t_HEADLOSS,  t_LINKQUAL,  t_LINKSTATUS,
+                           t_SETTING,   t_REACTRATE, t_FRICTION,
+                           "", "", "", "", "", "", NULL};
+
+
+#endif