**The Dam Catalog Reviewer**

**and**

**Estimating Tool**

**(DamCREST)**

**Database Configuration Version**

**User's Guide**

**August 11, 2004**

**NWS Office of Hydrologic Development**

Table of Content

***Overview*** [1](#__RefHeading___Toc74369105)

***Starting DamCREST application*** [3](#__RefHeading___Toc74369106)

***Starting DamCREST from the command line***
[3](#__RefHeading___Toc74369107)

***DamCREST modes*** [4](#__RefHeading___Toc74369108)

***1.* *Lookup mode*** [5](#__RefHeading___Toc74369109)

*Lookup Mode -- Search* [7](#__RefHeading___Toc74369110)

*Lookup Mode - Clear Search* [8](#__RefHeading___Toc74369111)

*Lookup Mode -- List All Dams* [9](#__RefHeading___Toc74369112)

*Lookup Mode - Create A New Dam* [10](#__RefHeading___Toc74369113)

*Lookup Mode - A Dam is Highlighted* [11](#__RefHeading___Toc74369114)

*Lookup Mode - Clone A Dam* [12](#__RefHeading___Toc74369115)

*Lookup Mode - Delete A Dam* [13](#__RefHeading___Toc74369116)

***2. Tabular DB Update mode*** [15](#__RefHeading___Toc74369117)

*Tabular DB Update mode - General Tab* [16](#__RefHeading___Toc74369118)

*Tabular DB Update mode - Construction Tab*
[18](#__RefHeading___Toc74369119)

*Tabular DB Update mode - Regulatory Tab*
[19](#__RefHeading___Toc74369120)

*Tabular DB Update mode - Downstream* [20](#__RefHeading___Toc74369121)

*Tabular DB Update mode - Cross-Sections*
[23](#__RefHeading___Toc74369122)

*Tabular DB Update mode - Input* [26](#__RefHeading___Toc74369123)

*Tabular DB Update mode -- Output* [29](#__RefHeading___Toc74369124)

***3. Output Manager mode*** [32](#__RefHeading___Toc74369125)

*Output Manager mode -- the "View Forecast Info" button is launched from
the Lookup mode* [37](#__RefHeading___Toc74369126)

*Output Manager mode -- the "Run SMPDBK Model" button is launched from
the Lookup mode* [41](#__RefHeading___Toc74369127)

*Output Manager mode -- the "Run SMPDBK" menu item is chosen under the
"Model" menu in the Model GUI* [44](#__RefHeading___Toc74369128)

***4. Model GUI mode*** [46](#__RefHeading___Toc74369129)

*Model GUI mode -The "Model Input Editor" window layout*
[47](#__RefHeading___Toc74369130)

*The "Model Input Editor -- Database Mode -- Editing DAMCAT Entry: \[dam
NIDID\]" window menu* [54](#__RefHeading___Toc74369131)

***Apps_defaults settings*** [57](#__RefHeading___Toc74369132)

***Resource file*** [58](#__RefHeading___Toc74369133)

***Initialization file .vimrc*** [58](#__RefHeading___Toc74369134)

***Appendix A. DamCat Database Specifications***
[59](#__RefHeading___Toc74369135)

***Figures***

Figure 1. \"DAMCAT - Search Tool\" window initial screen.
[5](#__RefHeading___Toc74369155)

Figure 2. \"DAMCAT - Search Tool\" window, the \"More\" button was
clicked to display more search options. [7](#__RefHeading___Toc74369156)

Figure 3. Button \"List All Dams\" was clicked. As a result of the query
all records are returned. [9](#__RefHeading___Toc74369157)

Figure 4. The \"Create New Dam\" button is clicked.
[10](#__RefHeading___Toc74369158)

Figure 5. A dam in the list of returned results is highlighted.
[11](#__RefHeading___Toc74369159)

Figure 6. A highlighted dam will be cloned - all information of the
highlighted dam will be copied to a newly created dam and saved in the
database. [12](#__RefHeading___Toc74369160)

Figure 7. If confirmation is received, the dam is deleted from the
database. [13](#__RefHeading___Toc74369161)

Figure 8. The \"DAMCAT - Search Tool\" will be updated after deleting a
highlighted dam - the deleted dam will be cleared from the dam list.
[14](#__RefHeading___Toc74369162)

Figure 9. The \"General\" tab is chosen in the \"DAMCAT - Dam View - Dam
NIDID\" window. [16](#__RefHeading___Toc74369163)

Figure 10. The user is prompted to confirm that a selected dam will be
deleted from the database. [17](#__RefHeading___Toc74369164)

Figure 11. The \"Construction\" tab is selected in the \"DAMCAT - Dam
View -- \[dam NIDID\]\" window. [18](#__RefHeading___Toc74369165)

Figure 12. The \"Regulatory\" tab is selected in the \"DAMCAT - Dam View
-- \[dam NIDID\]\" window. [19](#__RefHeading___Toc74369166)

Figure 13. The \"Downstream\" tab is selected in the "DAMCAT -- Dam View
-- \[dam NIDID\]" window. [20](#__RefHeading___Toc74369167)

Figure 14. The "New D/S Point" button is clicked when the "Downstream"
tab is selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.
[21](#__RefHeading___Toc74369168)

Figure 15. The user is prompted to confirm that a selected downstream
point will be deleted from the database.
[22](#__RefHeading___Toc74369169)

Figure 16. The "Cross Sections" tab is selected in the "DAMCAT -- Dam
View -- \[dam NIDID\]" window. [23](#__RefHeading___Toc74369170)

Figure 17. The "New XSection" button is clicked when the "Cross
Sections" tab is selected in the "DAMCAT -- Dam View -- \[dam NIDID\]"
window. [24](#__RefHeading___Toc74369171)

Figure 18. The user is prompted to confirm that a selected cross-section
pair will be deleted. from the database.
[25](#__RefHeading___Toc74369172)

Figure 19. The "Input" tab is selected in the "DAMCAT -- Dam View --
\[dam NIDID\]" window. [26](#__RefHeading___Toc74369173)

Figure 20. The "New Input" button is clicked when the "Input" tab is
selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.
[27](#__RefHeading___Toc74369174)

Figure 21. The user is prompted to confirm that a selected input entry
will be deleted from the database. [28](#__RefHeading___Toc74369175)

Figure 22. The "Output" tab is selected in the "DAMCAT -- Dam View --
\[dam NIDID\]" window. [29](#__RefHeading___Toc74369176)

Figure 23. The "New Output" button is clicked when the "Output" tab is
selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.
[30](#__RefHeading___Toc74369177)

Figure 24. The user is prompted to confirm that a selected output entry
will be deleted from the database. [31](#__RefHeading___Toc74369178)

Figure 25. The "Graphic" tab in the "Output Manager" window is selected.
[33](#__RefHeading___Toc74369179)

Figure 26. Output Data Table\" tab in the \"Output Manager\" window is
selected. [33](#__RefHeading___Toc74369180)

Figure 27. The \"Water Surface Profile Chart\" tab is selected in the
"Output Manager" window. [34](#__RefHeading___Toc74369181)

Figure 28. The \"Peak Discharge Profile Chart\" tab is selected in the
\"Output Manager\" window. [34](#__RefHeading___Toc74369182)

Figure 29. The \"Export to FLDVIEW\" tab in the \"Output Manager\"
window is selected. [35](#__RefHeading___Toc74369183)

Figure 30. The \"SMPDBK Output Text\" tab in the \"Output Manager\"
window is selected. [35](#__RefHeading___Toc74369184)

Figure 31. The \"Stored Forecast Text\" tab in the \"Output Manager\"
window is displayed. [36](#__RefHeading___Toc74369185)

Figure 32. The \"Warnings\" tab in the \"Output Manager\" window is
selected. [36](#__RefHeading___Toc74369186)

Figure 33. The previous model run results exist and displayed under the
\"Stored Forecast Text\" tab in the \"Output Manager\" window.
[37](#__RefHeading___Toc74369187)

Figure 34. The \"View Forecast Info\" button is launched, the output
results of the previous run is unavailable in the database.
[38](#__RefHeading___Toc74369188)

Figure 35. The "View Forecast Info" button is clicked, the output for
the dam is unavailable in the database, and some parameters should be
changed. [39](#__RefHeading___Toc74369189)

Figure 36. To save the changes, the "Update database" menu item under
the "Database" menu should be chosen. [39](#__RefHeading___Toc74369190)

Figure 37. To run the model, the user should chose the "Run SMPDBK" menu
item from the "Model" menu. [40](#__RefHeading___Toc74369191)

Figure 38. The \"Run SMPDBK Model\" button from the \"DAMCAT - Search
Tool\" is launched or the menu item \"Run SMPDBK\" is chosen from the
\"Model\" menu in the \"Model Input Editor\" window. The \"Graphic" tab
is opened by default. [41](#__RefHeading___Toc74369192)

Figure 39. The \"Output Manager - the most recent model run)\" tabbed
window is opened on the \"SMPDBK Output Text\". (Only the part of the
window is displayed). [42](#__RefHeading___Toc74369193)

Figure 40. The \"Warning\" message is displayed in the case when the
input parameters were changed for running the model. The "Run SMPDBK
Model" button is launched from the "DAMCAT -- Search Tool" window.
[43](#__RefHeading___Toc74369194)

Figure 41. The \"Warning\" message is displayed in the case when the
input parameters were changed for running the model. The "Run SMPDK"
button is chosen under the "Model" menu in the "Model Input Editor"
window. [44](#__RefHeading___Toc74369195)

Figure 42. The \"Model Input Editor\" window is displayed.
[46](#__RefHeading___Toc74369196)

Figure 43. Informational data about the dam is displayed.
[47](#__RefHeading___Toc74369197)

Figure 44. The scenario data from the SdbIn table is displayed.
[48](#__RefHeading___Toc74369198)

Figure 45. The \"Highlight me to append a new scenario\" option is
chosen to add a new scenario. [49](#__RefHeading___Toc74369199)

Figure 46. The error message is displayed if this source-scenario
combination already exists. [50](#__RefHeading___Toc74369200)

Figure 47. The downstream point data from the DownStream table is
displayed. [51](#__RefHeading___Toc74369201)

Figure 48. Cross-section pairs data taken from the SectionPair table is
displayed. It\'s associated with the highlighted in the \"Downstream
Point List\" downstream point. [52](#__RefHeading___Toc74369202)

Figure 49. When a new cross-section is created, the type is set to
\"M1 - Manual\", and can be changed for any selected from the \"Cross
Section Type\" combo box. [53](#__RefHeading___Toc74369203)

Figure 50. To save updated or newly inserted dam data to the database,
the user must click on the "Update Database" menu item under "Database"
menu. [54](#__RefHeading___Toc74369204)

Figure 51. The confirmation message dialog when the "Database -\>
"Update database" menu item is selected.
[54](#__RefHeading___Toc74369205)

Figure 52. The confirmation message dialog when the "Database -\>
"Close" menu item is selected. [55](#__RefHeading___Toc74369206)

Figure 53. The \"Edit -\> Edit Text File\" menu item is selected.
[55](#__RefHeading___Toc74369207)

Figure 54. The "Model -\> Run SMPDBK" menu item is selected.
[56](#__RefHeading___Toc74369208)

Figure 55. The user has option to view output of the model run saved to
the file. [56](#__RefHeading___Toc74369209)

***Overview***

[]{#__RefHeading___Toc74369105 .anchor}

The Dam Catalog Reviewer and Estimating Tool (DamCREST) is a Graphical
User Interface application available on both Linux and Windows operating
platforms.

Written primarily in Java, the application uses Java Database
Connectivity (JDBC) Protocols to access relational database structures,
enabling the application to run against virtually any database that has
an appropriate JDBC driver interface. The application has been
successfully tested using the Informix DBMS on Linux and the MySQL DBMS
on Windows, but can also run against flat file structures when
configured without a database.

Through the application's GUI, one can: explore output results of
previously run Dambreak models stored in the database; view parameters
used in Dambreak model run scenarios for each selected dam; generate new
Dambreak values by launching the HL Simplified Dambreak Model program
(written in FORTRAN); update any of the data stored in the database;
insert new dams into the Catalog or delete old dams from the Catalog.

The program initially was introduced as a MOTIF-based AWIPS (non-PC)
application; it was developed as the Catalogue of Dams with approximate
flood forecasting information -- DAMCAT. The Catalogue was a menu driven
package that allowed the user to search for a particular dam or a group
of dams by supplying one of the following: dam name, dam I.D. number,
river name, nearest downstream ton name, county name, or county FIPS
code.

One of the first enhancements made was to combine the program that
generated the Catalog of Dams (DAMCAT) with the Simplified Dambreak
Model (SMPDBK) to form one program -- a PC-based, non-AWIPS application.
This menu driven program contained all the capabilities of both programs
as well as the added capability of automatically updating a particular
dam using the SMPDBK option.

The next version of the DamCat application executes within the
AWIPS-supplied Netscape web browser using Tcl/Tk, GCI, and an Informix
relational database. The application provides a catalog (database) of
physical dam characteristics and dam break scenarios; includes intuitive
GUI to navigate the catalog; provides ability to run alternate dam break
model scenarios; creates and distributes dam break user products, and
gives the user possibility to update existing dam information and rerun
the model with new set of parameters.

More recently, due to advances in technology, the DamCREST application
is being upgraded to include improved I/O (read/write/editing
capabilities). For both NWS internal customers and non-NWS customers
using various platforms, the application fully integrates the Dam
Catalogue with the model creation software in an efficient Java program.
The software is a more meaningful and user-friendly application in terms
of the GUI interface, the database design, and the maintainability of
the code, developed for modern platforms (Java/LINUX or Java/Windows).
Certain new features, such as inserting a new dam into the catalog or
deleting an existing dam, were added. One or more scenarios, downstream
points, cross-section pairs, and cross-section types could be added to
an existing dam. The dam break scenario results will be stored to the
database.

To make sure that the DamCREST values are appropriate for each dam,
Weather Forecast Offices should review and account for variations in dam
geometry, local geographic topology and location of communities as well
as high value structures downstream of each dam. With this updated data,
offices have the ability to insure that the crest wave height and time
of travel for important downstream areas are representative and
effective.

***Starting DamCREST application***

[]{#__RefHeading___Toc74369106 .anchor}

To start the DamCREST (The Dam Catalog Reviewer and Estimating Tool)
application in the database configuration the user must have a suitable
Java DataBase Connectivity (JDBC) database and driver. The application
was designed and tested for an Informix database connection when the
application runs on the LINUX operating system or a MySQL database
connection when the application runs on the Windows operating system.

"DAMCAT - Search Tool" window is the first window to be displayed if the
tool is configured with DBMS. The "Search Results" list will display all
dams existing in the database if the "hasListAllDams" variable is set to
"true" in the "resources.txt" file. Otherwise, if the "hasListAllDams"
variable is set to "false", the "Search Results" list initially is
empty. The user has choice to click the "hasListAllDams" button to
display all dams existing in the database or to conduct search based on
a preferred criteria.

***Starting DamCREST from the command
line***[]{#__RefHeading___Toc74369107 .anchor}

The DamCREST application could take an argument from the command line.
The given argument is the NIDID of the particular dam. The user will be
directed to the "Output Manager" window, "Stored Forecast Text" tab GUI
display (see Figure 33) if the results of the previous run existing in
the database. If the previous run results do not exist in the database,
the program will run the model first and store the results in the
database (see Figure 34). If the set of input to the model parameters is
not fully presented or some of them are invalid, the user will be
provided through steps to fix it and run the model (see Figure 35).

***DamCREST modes***[]{#__RefHeading___Toc74369108 .anchor}

The DamCREST application has several modes:

1\. Lookup mode ("DAMCAT -- Search Tool" window) -- to search for a
subset of dams or a particular dam, or to display list of all dams.

2\. Tabular DB Update mode ("DAMCAT -- Dam View -- \[dam NIDID\] window)
-- to update database tables, to insert / delete new dams, new
downstream points, and new cross-sections. Any changes made can be saved
to the database.

3\. Output Manager mode ("Output Manager" window) from the Lookup mode
("DAMCAT -- Search Tool" window) -- to display output results of the
previous model run in graphical or textual form.

Output Manager mode ("Output Manager" window) from the Model GUI mode
("Model Input Editor -- Database Mode -- Editing DAMCAT Entry: \[dam
NIDID\] window) -- to display output results of the recent model run in
graphical or textual form.

4\. Model GUI mode ("Model Input Editor -- Database Mode -- Editing
DAMCAT Entry: \[dam NIDID\] window) -- to display all data used as input
to run model, taken from different database tables. The user can also
make updates of the database tables via this window.

***1.* *Lookup mode***[]{#__RefHeading___Toc74369109 .anchor}

"DAMCAT - Search Tool" window is the first window to be displayed if the
tool is configured with DBMS.

![](media/image1.png){width="6.493055555555555in"
height="4.535416666666666in"}

[]{#__RefHeading___Toc74369155 .anchor}Figure 1. \"DAMCAT - Search
Tool\" window initial screen.

When DamCREST application, database configuration is started, a "DAMCAT
-- Search Tool" window with a drop-down combo box, search text field,
buttons "More" and "Fewer", set of buttons "Search" "List All Dams",
"Clear Search Fields", "Create New Dam", "Clone A Dam" (greyed), "Delete
A Dam" (greyed), empty list of search results, set of buttons "View /
Edit Dam Information" (greyed), "View in Catalog" (greyed), "Run Model"
(greyed), "Print", and "Quit" will be displayed.

**Their functionality is as following:**

The drop-down combo box, search text field, buttons "More", Fewer", and
"Search" bring the ability to search for a particular dam or set of dams
by searching criteria.

When the "List All Dams" button is selected, the list of all dams in the
database is returned.

If the application is configured to list all dams at startup, the tool
will automatically search the database and display the results.

Search results are automatically listed in alphabetic order by Dam Name.
However, the user may click on any of the following column names -- "Dam
Name", "River Name", "County Name" or "NIDID" to change the alphabetic
order of the results list.

With click on the "Clear Search Fields" the search fields will be
cleared and a new search could

be conducted.

With click on the "Create New Dam" button a new dam is created, data
fields are empty or

defaults to 0.0.

When the "Clone A Dam" is clicked, a dam highlighted in the list of
returned result is cloned

(copied) with a new ID.

When the "Delete A Dam" is clicked, a highlighted dam will be deleted
from the database.

With click on the "Edit Dam Data" the user is navigated to the Tabular
mode, the "DAMCAT -- Dam View -- \[dam NIDID\] tabbed window, the
"General" tab is opened by default.

When the "View Forecast Info" button is clicked, the "Output Manager"
window is opened, and results of the last model run are displayed.

When the "Run SMPDBK Model" button is clicked, the "Model GUI" and
"Output Manager" windows are opened. The model is run, and results are
displayed in the "Output Manager" window. After closing the "Output
Manager", the user stays in the "Model GUI" window.

When the "Print" button is clicked, the "Search Results" table in the
"DAMCAT - Search Tool" window is sent to the printer.

When the "Quit" button is clicked, the application exits.

*Lookup Mode -- Search*[]{#__RefHeading___Toc74369110 .anchor}

![](media/image2.png){width="6.493055555555555in"
height="4.535416666666666in"}

[]{#__RefHeading___Toc74369156 .anchor}Figure 2. \"DAMCAT - Search
Tool\" window, the \"More\" button was clicked to display more search
options.

The "Search" button provides the ability to search for particular dam by
one (or a combination) of the following fields:

**Dam** - Official dam name, or the popular (Other Name) name

**River** - Name of the river

**County** - FIPS code of county in which dam is located

**NIDID** - National Inventory of Dams Identification Number

**HSA** - Hydrologic Service Area

> **RFC** - River Forecast Center

**DH** - Code indicating the potential hazard to the downstream area
resulting

from failure or misoperation of the dam, L=Low, S=Significant, H=High

**Volume** - Starting volume (acre-ft) of reservoir

**Longitude** - West longitude coordinate of dam

**Latitude** - North latitude coordinate of dam.

**To conduct customized search by criteria:**

1\) an appropriate field (or set of fields) should be chosen from one or
more combo boxes (to get

more combo boxes with search options the "More" button should be
clicked, and to get less

combo boxes on the screen the "Fewer" button should be clicked)

2\) choose "contains" and click on the "Search" button. A search result
will appear as a

returned list of dams under the label "Search Results -- \[number of
records\] results returned".

**Note:**

If the "equal" button is chosen, the exact name should be typed in the
text field.

In the case when the search was provided by NIDID, only one station will
appear.

If the search text fields were left empty, the list of all stations will
be displayed.

The following fields will be displayed in the list of returned results:
number of the record, name

of dam, river name, county name, and NIDID.

A search operation is conducted on the entry in the "Search" search text
field each time a category is selected, and the user hits return after
making an entry in search text field or clicks on the "Search" button.

*Lookup Mode - Clear Search*[]{#__RefHeading___Toc74369111 .anchor}

With click on the "Clear Search Fields" button, the search fields will
be cleared and a new search could be conducted.

*Lookup Mode -- List All Dams*[]{#__RefHeading___Toc74369112 .anchor}

To list all dams, the "List All Dams" button should be clicked.

The application may also be configured to display all the dams in the
database at startup. The "damcat.hasListAllDams" variable must be set to
"true" in the "resources.txt" or in the .Apps_defaults file.

![](media/image3.png){width="6.493055555555555in"
height="4.535416666666666in"}

[]{#__RefHeading___Toc74369157 .anchor}Figure 3. Button \"List All
Dams\" was clicked. As a result of the query all records are returned.

**Note:** snapshot on the Fig.3 presents only a part of a real window.

*Lookup Mode - Create A New Dam*[]{#__RefHeading___Toc74369113 .anchor}

When the \"Create a New Dam\" button is clicked, a dialog window prompts
the user to pick a state in the combo box where a new dam should be
created. A new NIDID is calculated by the program and has the format
"SS99nnn" where the first two characters (SS) is a state abbreviation
supplied by the user, next two characters (99) -- is the indication that
a new dam is created manually, and a number of this dam in the
particular state (nnn) is an integer number. With click "OK" in the
"Choose a State" dialog window, an empty record in the DamMaster and
DamFeatures table (except NIDID as a key) is added to the database. This
record could be updated, filled up with information, and saved.

![](media/image4.png){width="6.493055555555555in"
height="4.535416666666666in"}

[]{#__RefHeading___Toc74369158 .anchor}Figure 4. The \"Create New Dam\"
button is clicked.

*Lookup Mode - A Dam is Highlighted*[]{#__RefHeading___Toc74369114
.anchor}

When a particular dam in the list of returned records is highlighted,
all desensitized buttons:

"Clone A Dam", Delete A Dam", View / Edit Dam Information", "Prerun
Results", Run Model" are enabled.

![](media/image5.png){width="6.493055555555555in"
height="4.535416666666666in"}

[]{#__RefHeading___Toc74369159 .anchor}Figure 5. A dam in the list of
returned results is highlighted.

.

*Lookup Mode - Clone A Dam*[]{#__RefHeading___Toc74369115 .anchor}

When the "Clone A Dam" is clicked on the "DAMCAT -- Search Tool" window,
a highlighted in the list dam is cloned (copied) with a new ID where the
ID is created automatically in the "SS99nnn" format when the user
supplies the state. With click "OK" in the "Choose a State" dialog
window, a data set of a chosen dam is copied to the database with a new
NIDID. This record could be updated and saved.

> ![](media/image6.png){width="5.997916666666667in"
> height="4.189583333333333in"}

[]{#__RefHeading___Toc74369160 .anchor}Figure 6. A highlighted dam will
be cloned - all information of the highlighted dam will be copied to a
newly created dam and saved in the database.

*Lookup Mode - Delete A Dam*[]{#__RefHeading___Toc74369116 .anchor}

When the "Delete A Dam" is clicked in the "DAMCAT -- Search Tool"
window, the user will be prompted to confirm that a particular dam will
be deleted from the database.

After receiving confirmation the dam will be deleted from the database
and the "DAMCAT -- Search Tool" window will be updated.

![](media/image7.png){width="5.997916666666667in"
height="4.189583333333333in"}

[]{#__RefHeading___Toc74369161 .anchor}Figure 7. If confirmation is
received, the dam is deleted from the database.

![](media/image8.png){width="5.997916666666667in"
height="4.189583333333333in"}

[]{#__RefHeading___Toc74369162 .anchor}Figure 8. The \"DAMCAT - Search
Tool\" will be updated after deleting a highlighted dam - the deleted
dam will be cleared from the dam list.

***2. Tabular DB Update mode***[]{#__RefHeading___Toc74369117 .anchor}

When a particular dam is highlighted in the list of the returned
results, after

1\) double clicking on the selected row or

2\) single-clicking on the "Edit Dam Data" button when a row is
highlighted, the application navigates to the "DAMCAT -- Dam View"
screen in the Tabular mode.

**Note:** the Tabular Database Update mode section is intended for the
more advanced user, one who is very familiar not only with the hydrology
of the application but also with the database behind the application
interface. Because of this intention, the maximum amount of data is
exposed and available to the user in this section. It is best if the
user understands the scientific model itself and the relationship
between the data before changing/inserting/deleting data by way of these
screens.

**Note:**

The "updated" field is not editable. It is automatically set by the
DamCREST software to contain the current date/time when the database
table is modified.

**The Tabular DB Update mode window consists from:**

**1)** **Set of Tabs:**

General tab -- contains informational data of the dam

Construction tab -- contains technical information of the dam and
reservoir

Regulatory tab -- contains the owner, inspection, type of agency
information, etc.

Downstream tab -- contains data about downstream point

Cross Sections tab -- contains cross - section pair data

Input -- contains input data to the model

Output -- contains output data of the model run

**2) Set of Buttons:**

"New Dam" / "New D /S Point" / "New XSection" / "New Input" / "New
Output" button (name of the button is dynamically changed depending on
which tab is chosen) - to insert a new dam information, new downstream
point, new cross-section, new input, and new output to the database.

"View / Edit Failure Scenarios" -- to navigate to the Model GUI mode.

"Save Changes" -- to save made changes to the database.

"Delete" -- to delete a dam, a downstream point, a cross-section.

"Close" -- close the window.

*Tabular DB Update mode - General Tab*[]{#__RefHeading___Toc74369118
.anchor}

When the "Edit Dam Data" button in the "DAMCAT -- Search Tool" window
(Lookup mode) is clicked, the user is navigated to a new window "DAMCAT
-- Dam View - \[dam NIDID\]" (Tabular DB Update mode). This is the
tabbed window; information under the General tab contains such
informational data about the dam as its name, ID, location, latitude,
longitude, elevation, which topographical map was used, information
about the responsible RFC -- River Forecast Center and HAS -- Hydrologic
Service Area, updated, etc.

The General tab is opened by default. The "New Dam" button is disabled
because a new dam insertion cannot be initiated from this screen. The
"Save Changes" button is disabled initially, and becomes enabled after
typing in any of text fields. The displayed dam information is read from
the DamMaster and DamFeatures tables. If this is a newly created dam, a
window with blank or contain 0.00 text fields is displayed. The dam
information could be inserted / updated manually in any text field
except in the primary key "NIDID" and the field "Updated" which are
uneditable and greyed out.

![](media/image9.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369163 .anchor}Figure 9. The \"General\" tab is
chosen in the \"DAMCAT - Dam View - Dam NIDID\" window.

The dam could be deleted from this window. When the "Delete" button is
selected, the user is informed that by opting to delete the dam that all
information associated with the dam will be also deleted (cascading
delete). If confirmation is received, and the dam is deleted, the
"DAMCAT -- Search Tool" will be also updated - the dam will be deleted
from the list of the returned dams.

![](media/image10.png){width="5.997916666666667in"
height="4.683333333333334in"}

[]{#__RefHeading___Toc74369164 .anchor}Figure 10. The user is prompted
to confirm that a selected dam will be deleted from the database.

*Tabular DB Update mode - Construction
Tab*[]{#__RefHeading___Toc74369119 .anchor}

When the Construction tab is selected in the "DAMCAT -- Dam View - \[dam
NIDID\]" window, such technical information of the dam and reservoir as
dam type (earth, concrete, etc.), height of the dam, reservoir, storage
volume, dam length, maximal discharge, etc. is displayed. The "New Dam"
and "Delete" buttons are disabled because a new dam insertion or
deletion cannot be initiated from this screen. The "Save Changes" button
is disabled initially, and becomes enabled after typing in any of text
fields. The displayed dam information is read from the DamFeatures
table. If this is a newly created dam, a window with blank or contain
0.00 text fields is displayed.

![](media/image11.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369165 .anchor}Figure 11. The \"Construction\"
tab is selected in the \"DAMCAT - Dam View -- \[dam NIDID\]\" window.

*Tabular DB Update mode - Regulatory Tab*[]{#__RefHeading___Toc74369120
.anchor}

When the Regulatory tab is selected in the "DAMCAT -- Dam View - \[dam
NIDID\]" window, information about the owner, inspection, type of
agency, etc. is displayed. The "New Dam" and "Delete" buttons are
desensitized because a new dam insertion or deletion cannot be initiated
from this screen. The "Save Changes" button is desensitized initially,
and becomes enabled after typing in any of text fields. The displayed
dam information is read from the DamFeatures table. If this is a newly
created dam, a window with blank or contain 0.00 text fields is
displayed.

![](media/image12.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369166 .anchor}Figure 12. The \"Regulatory\" tab
is selected in the \"DAMCAT - Dam View -- \[dam NIDID\]\" window.

*Tabular DB Update mode - Downstream*[]{#__RefHeading___Toc74369121
.anchor}

When the Downstream tab is selected in the "DAMCAT -- Dam View - \[dam
NIDID\]" window, information about the downstream point such as
downstream point name, best cross-section type (type on which model
runs), distance from the dam to point of interest or town along the
routing reach, latitude and longitude of the downstream point, elevation
of the downstream point, flood flow, flood depth, off channel Manning's
N coefficient, comments and updated is displayed. Downstream points
information is mainly taken from the Downstream table, auxiliary table
-- DamMaster. Number of combinations is varying depending on number of
downstream points and variety of cross-section types.

![](media/image13.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369167 .anchor}Figure 13. The \"Downstream\" tab
is selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.

The downstream point information could be inserted / updated manually in
any text field except in the primary key field "D/S Point Name" and the
field "Updated" which are uneditable grayed out.

The "New D/S Point" button is enabled; a new downstream point could be
inserted for the existed dam. To insert a new downstream point, the user
must supply the second part of the primary key -- downstream point name
(when the first part of the primary key - NIDID, is already known). The
user will be prompted to fill up the downstream point name in the dialog
box, and click on the "OK" button to add a new downstream point to the
existing dam.

![](media/image14.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369168 .anchor}Figure 14. The "New D/S Point"
button is clicked when the "Downstream" tab is selected in the "DAMCAT
-- Dam View -- \[dam NIDID\]" window.

The "Save Changes" button is disabled initially, and becomes enabled
after updating any of text fields. The displayed downstream information
is read from the DownStream table. If this is a newly created downstream
point, a window with blank or contain 0.00 text fields is displayed.

The user can delete a downstream point of the selected dam. The user
will be prompted that the downstream point will be deleted. If the
confirmation is received, a downstream point with all information
associated with it, i.e., all cross-section pairs of this point, will be
also deleted (cascading delete).

![](media/image15.png){width="5.997916666666667in"
height="4.683333333333334in"}

[]{#__RefHeading___Toc74369169 .anchor}Figure 15. The user is prompted
to confirm that a selected downstream point will be deleted from the
database.

*Tabular DB Update mode - Cross-Sections*[]{#__RefHeading___Toc74369122
.anchor}

When the Cross-Sections tab is selected in the "DAMCAT -- Dam View -
\[dam NIDID\]" window, information about the cross-section pair such as
cross-section type, pair number, elevation, top width, inactive width,
Manning's N coefficient, updated is displayed. Cross-section pairs
information is taken from SectionPair table. Number of combinations is
varying depending on number of downstream points, number of
cross-section types, and number of pairs.

The cross-section pair could be inserted / updated manually in any text
field except in the primary key fields "D/S Point Name", "Cross Section
Type" and the field "Updated" which are uneditable and greyed out.

![](media/image16.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369170 .anchor}Figure 16. The "Cross Sections"
tab is selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.

The "New XSection" button is enabled; a new cross-section pair could be
added to the existed downstream point. To insert a new cross-section,
the user must supply the needed primary key fields -- downstream point
name, cross-section type, and pair number (when the first part of the
primary key - NIDID, is already known). The user will be prompted to
fill up the downstream point name, cross-section type, pair number in
the dialog box, and click on the "OK" button to add a new cross-section
pair to the existed downstream point.

![](media/image17.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369171 .anchor}Figure 17. The "New XSection"
button is clicked when the "Cross Sections" tab is selected in the
"DAMCAT -- Dam View -- \[dam NIDID\]" window.

The "Save Changes" button is disabled initially, and becomes enabled
after updating any of text fields. The displayed cross-section pairs
information is read from the SectionPair table. A newly created
cross-section pair will be displayed with blank or contain 0.00 text
fields.

The user can delete a cross-section pair or multiple cross-section pairs
of the selected downstream point. The user will be prompted that the
cross-section pair (or pairs) will be deleted. If the confirmation is
received, a cross-section pair (or pairs) will be deleted.

**Note**:

A cross-section is defined by a minimum of two pairs and for purposes of
running the model, the same number of pairs must exist for each
downstream point.

![](media/image18.png){width="5.997916666666667in"
height="4.683333333333334in"}

[]{#__RefHeading___Toc74369172 .anchor}Figure 18. The user is prompted
to confirm that a selected cross-section pair will be deleted. from the
database.

*Tabular DB Update mode - Input*[]{#__RefHeading___Toc74369123 .anchor}

When the Input tab is selected in the "DAMCAT -- Dam View - \[dam
NIDID\]" window, input data for the model such as source, scenario,
starting water surface, bottom of breach, starting volume, starting
surface area, time of failure, additional flow, final breach, dam type,
comments, updated is displayed. Input information is taken from the
SdbIn table. "Source" reflects type of office where the model is run;
"Scenario" defines type of the failure of the dam: "HF"- high fast, "HN"
-- high normal, "MF" -- medium fast, "MN" -- medium normal. On the
screen will be shown all possible source -- scenario combinations.
Number of cases will vary depending on how many source-scenario
combinations exist for the particular dam.

The source-scenario could be inserted / updated manually in any text
field except in the primary key fields "Source", "Scenario" and the
field "Updated" which are uneditable greyed out.

![](media/image19.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369173 .anchor}Figure 19. The "Input" tab is
selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.

The "New Input" button is enabled; a new source-scenario combination
could be added to the existed input. To insert a new source-scenario
combination, the user must supply the needed primary key fields --
source, scenario (when the first part of the primary key - NIDID, is
already known). The user will be prompted to fill up the source and
scenario in the dialog box, and click on the "OK" button to add a new
source-scenario combination to the existed input data.

![](media/image20.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369174 .anchor}Figure 20. The "New Input" button
is clicked when the "Input" tab is selected in the "DAMCAT -- Dam View
-- \[dam NIDID\]" window.

The "Save Changes" button is disabled initially, and becomes enabled
after updating any of text fields. The displayed input information is
read from the SdbIn table. A newly created source-scenario input entry
will be displayed with blank or contain 0.00 text fields.

The user can delete a selected source-scenario input entry. The user
will be prompted that the selected input entry will be deleted. If the
confirmation is received, it will be deleted.

![](media/image21.png){width="5.997916666666667in"
height="4.683333333333334in"}

[]{#__RefHeading___Toc74369175 .anchor}Figure 21. The user is prompted
to confirm that a selected input entry will be deleted from the
database.

*Tabular DB Update mode -- Output*[]{#__RefHeading___Toc74369124
.anchor}

When the Output tab is selected in the "DAMCAT -- Dam View - \[dam
NIDID\]" window, output from the model such as source, scenario,
downstream point name, slope, max flow, max elevation, time to max
elevation, time to flood, time to deflood, comments, updated is
displayed. Output information is taken from the SdbOut table. Number of
cases will vary depending on scenario, and number of downstream points.

The output entry could be inserted / updated manually in any text field
except in the primary key fields "Source", "D/S Point Name" and the
field "Updated" which are uneditable and greyed out.

**Note:** An output entry may be inserted only when the corresponding
input record, i.e. the source-scenario part of its key for a particular
dam, already exists in the input table. An exception to this is if the
source field to be inserted starts with the "#" character. In this case
the output table SdbOut will be updated, and the corresponding record
will be inserted into the input table SdbIn but the model will never run
to check such a record for consistency. Purpose of this feature is to
allow to store in the database "dirty" output entries in the database
running on which the model will produce errors.

![](media/image22.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369176 .anchor}Figure 22. The "Output" tab is
selected in the "DAMCAT -- Dam View -- \[dam NIDID\]" window.

The "New Output" button is enabled; a new output could be added to the
existed output. To insert a new output entry, the user must supply the
needed primary key fields -- source, scenario, and D/S Point Name (when
the first part of the primary key - NIDID, is already known). The user
will be prompted to fill up the source, scenario, and downstream name in
the dialog box, and click on the "OK" button to add a new output entry
to the existed output data.

![](media/image23.png){width="5.99375in" height="4.665972222222222in"}

[]{#__RefHeading___Toc74369177 .anchor}Figure 23. The "New Output"
button is clicked when the "Output" tab is selected in the "DAMCAT --
Dam View -- \[dam NIDID\]" window.

The "Save Changes" button is disabled initially, and becomes enabled
after updating any of text fields. The displayed input information is
read from the SdbOut table. A newly created output entry will be
displayed with blank or contain 0.00 text fields.

The user can delete a selected output entry. The user will be prompted
that the selected output entry will be deleted. If the confirmation is
received, it will be deleted.

![](media/image24.png){width="5.997916666666667in"
height="4.683333333333334in"}

[]{#__RefHeading___Toc74369178 .anchor}Figure 24. The user is prompted
to confirm that a selected output entry will be deleted from the
database.

***3. Output Manager mode***[]{#__RefHeading___Toc74369125 .anchor}

Model run output results are presented in the tabbed "Output Manager"
window ( Output Manager mode) under the following tabs: "Graphic",
"Output Data Table", "Water Surface Profile Chart", "Peak Discharge
Profile Chart", "Export to FLDVIEW", "SMPDBK Output Text", "Stored
Forecast Text" (if exists). Any GUI could be chosen with a click on the
correspondent tab.

The "Graphic" tab is opened by default when the button "Run SMPDBK
Model" is clicked in the "DAMCAT -- Search Tool" window or the menu item
"Run SMPDBK" under menu "Model" is chosen in the "Model GUI" window.

The "Stored Forecast Text" is displayed by default when the "View
Forecast Info" button is clicked in the "DAMCAT -- Search Tool" window.

The "Scenario" drop-down box contains set of the scenarios on which the
model ran. The chosen scenario run results are displayed on the screen.
The "High Fast" scenario model run results are displayed by default.

The "Distance:" combo box contains set of the downstream points (include
at dam point).

The model run results are displayed on the screen for the chosen
downstream point.

In the lower part of the "Output Manager" window the following buttons
are reside:

"View/Save/Print Output File", "Print Screen", and "Close".

The "View/Save/Print Output File" button is designed to work with the
"SMPDBK Output Text" and the "Stored Forecast Text" tabs only. When the
button is clicked, the text under any of these two tabs is sent to the
file, and could be opened in WordPad editor in Windows and in GVIM (VIM)
editor under Linux. The output file could be edited; content could be
saved in the same or newly created file. The output file cold be
printed, orientation of the paper is set to "Landscape" by default in
the ".vimrc" file.

When the "Print Screen" is clicked, the GUI snapshot under the chosen
tab is sent to print.

**Note:** There are differences in the print setup between Windows and
Linux operating systems when the "Print Screen" button is chosen.

In the Windows application the user should not worry about the printer
settings. The print options are set programmatically, no changes needed.

In the Linux application the user should set the proper print options
manually. The GUI under the "Graphics" and "Export to FLDVIEW" tabs must
be printed in "Portrait" paper orientation mode; all another settings
must be default.

To print the GUI snapshot under any another tab, the "Landscape" paper
orientation must be set. The left margin must be set to 0.0.

When the "Close" button is clicked, the window will be closed.

![](media/image25.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369179 .anchor}Figure 25. The "Graphic" tab in
the "Output Manager" window is selected.

![](media/image26.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369180 .anchor}Figure 26. Output Data Table\"
tab in the \"Output Manager\" window is selected.

![](media/image27.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369181 .anchor}Figure 27. The \"Water Surface
Profile Chart\" tab is selected in the "Output Manager" window.

![](media/image28.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369182 .anchor}Figure 28. The \"Peak Discharge
Profile Chart\" tab is selected in the \"Output Manager\" window.

![](media/image29.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369183 .anchor}Figure 29. The \"Export to
FLDVIEW\" tab in the \"Output Manager\" window is selected.

When the "Generate FLDVIEW Files" is clicked, the **.xy** and **.fcs**
input to FLDVIEW files will be generated.

![](media/image30.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369184 .anchor}Figure 30. The \"SMPDBK Output
Text\" tab in the \"Output Manager\" window is selected.

When the "SMPDBK Output Text" tab is selected, the results of the
FORTRAN (SMPDBK) model run will be displayed.

![](media/image31.png){width="5.990277777777778in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369185 .anchor}Figure 31. The \"Stored Forecast
Text\" tab in the \"Output Manager\" window is displayed.

When the "Stored Forecast Text" tab is selected, the results of the
previous model run stored in the database will be displayed.

![](media/image32.png){width="5.993055555555555in"
height="3.3555555555555556in"}

[]{#__RefHeading___Toc74369186 .anchor}Figure 32. The \"Warnings\" tab
in the \"Output Manager\" window is selected.

If the model produced any warning messages during a run, the additional
"Warnings" tab will be displayed.

*Output Manager mode -- the "View Forecast Info" button is launched from
the Lookup mode*[]{#__RefHeading___Toc74369126 .anchor}

The DamCREST application has the ability to quickly display the results
of model runs stored in the database. The user should highlight the
chosen dam in the list of the returned result ("DAMCAT -- Search Tool"
window) and select the "View Forecast Info" button in the "DAMCAT --
Search Tool" window.

**Several different cases possible:**

1\. The results of the previous model run exist. To display them on the
screen the "Prerun Output Text" tab in the "Output Manager" window will
be opened by default.

![](media/image33.png){width="5.993055555555555in"
height="3.3555555555555556in"}

[]{#__RefHeading___Toc74369187 .anchor}Figure 33. The previous model run
results exist and displayed under the \"Stored Forecast Text\" tab in
the \"Output Manager\" window.

2\. If output for the dam is unavailable in the database, the model will
run for the user automatically and the "Output Manager" window will be
opened.

![](media/image34.png){width="5.997916666666667in"
height="4.184027777777778in"}

[]{#__RefHeading___Toc74369188 .anchor}Figure 34. The \"View Forecast
Info\" button is launched, the output results of the previous run is
unavailable in the database.

3\. If the output does not exist in the database and/or there are some
fixes of the input parameters needed to run model, the user will be
provided through set of the user friendly prompts to indicate what needs
to be done to obtain the desired results. The messages on screen will
vary depending on which parameters should be inserted or changed to
provide to successful model run. To supply changes or to insert the
parameters, the "Model GUI" window will be opened.

![](media/image35.png){width="5.9944444444444445in"
height="4.092361111111111in"}

[]{#__RefHeading___Toc74369189 .anchor}Figure 35. The "View Forecast
Info" button is clicked, the output for the dam is unavailable in the
database, and some parameters should be changed.

![](media/image36.png){width="5.995833333333334in"
height="3.354861111111111in"}

[]{#__RefHeading___Toc74369190 .anchor}Figure 36. To save the changes,
the "Update database" menu item under the "Database" menu should be
chosen.

![](media/image37.png){width="5.995833333333334in"
height="3.354861111111111in"}

[]{#__RefHeading___Toc74369191 .anchor}Figure 37. To run the model, the
user should chose the "Run SMPDBK" menu item from the "Model" menu.

**Notes:**

1\. Needed updates could be also made in the Tabular DB Updates mode.

2\. The user can click on the "Run SMPDBK Model" button in the Lookup
mode to run the model.

*Output Manager mode -- the "Run SMPDBK Model" button is launched from
the Lookup mode*[]{#__RefHeading___Toc74369127 .anchor}

**Several different cases possible:**

1\) The input data set to the model is fully presented, data is valid.

The model will run. The "Output Manager -- (the most recent model run)"
tabbed window is opened, the "Graphic" tab with the graphic
representation of the model run results is displayed by default. In the
"Scenario" combo box the scenario on which the model ran is displayed.
The model run results are presented for the first downstream point by
default. This could be changed with choosing another parameter in the
"Distance" combo box in the lower part of the "Output Manager" window.

![](media/image38.png){width="5.996527777777778in"
height="3.361111111111111in"}

[]{#__RefHeading___Toc74369192 .anchor}Figure 38. The \"Run SMPDBK
Model\" button from the \"DAMCAT - Search Tool\" is launched or the menu
item \"Run SMPDBK\" is chosen from the \"Model\" menu in the \"Model
Input Editor\" window. The \"Graphic" tab is opened by default.

The output results of the model run in the textual form are presented
under the "SMPDBK Output Text" tab in the "Output Manager" window.

![](media/image39.png){width="5.997222222222222in"
height="3.363888888888889in"}

[]{#__RefHeading___Toc74369193 .anchor}Figure 39. The \"Output Manager -
the most recent model run)\" tabbed window is opened on the \"SMPDBK
Output Text\". (Only the part of the window is displayed).

The model runs from the "Model DAMCAT -- Search Tool" window where the
"Run SMPDBK Model" button is launched. The input data set to the model
is fully presented, but some input parameters was revised by the model
and changed. In this case the warning message is displayed on the
screen. To continue, the "OK" button should be clicked. The warning
message is displayed one per corresponding scenario. After running all
scenarios, the model run results will be displayed in the "Output
Manager -- most recent model run)" window, in analogy with the
previously described case.

![](media/image40.png){width="5.997916666666667in" height="4.18125in"}

[]{#__RefHeading___Toc74369194 .anchor}Figure 40. The \"Warning\"
message is displayed in the case when the input parameters were changed
for running the model. The "Run SMPDBK Model" button is launched from
the "DAMCAT -- Search Tool" window.

*Output Manager mode -- the "Run SMPDBK" menu item is chosen under the
"Model" menu in the Model GUI*[]{#__RefHeading___Toc74369128 .anchor}

When the "Run SMPDBK" menu item is chosen under the "Model" menu in the
"Model Input Editor" window, also the same several cases of the model
run exist:

1\) The model run successfully, and the output results of the model run
in the textual form are presented under the "SMPDBK Output Text" tab in
the "Output Manager" window.

2\) The model runs from the "Model Input Editor" window where the "Run
SMPDBK" menu item is chosen under the "Model" menu. The input data set
to the model is fully presented, but the input parameters are changed by
the model, the warning message will appear on the screen. To continue,
the "OK" button should be clicked. The warning message is displayed one
per corresponding scenario. After running all scenarios, the model run
results will be displayed in the "Output Manager -- most recent model
run)" window, in analogy with the previously described case.

![](media/image41.png){width="5.992361111111111in"
height="4.995138888888889in"}

[]{#__RefHeading___Toc74369195 .anchor}Figure 41. The \"Warning\"
message is displayed in the case when the input parameters were changed
for running the model. The "Run SMPDK" button is chosen under the
"Model" menu in the "Model Input Editor" window.

3\) The model cannot run because the input set of parameters is not
fully presented

and/or there are some fixes of the input parameters needed to run model,
the user will be provided through set of the user friendly prompts to
indicate what needs to be done to obtain the desired results. The
messages on screen will vary depending on which parameters should be
inserted or changed to provide to successful model run. To supply
changes or to insert the parameters, the "Model Input Editor" window
will be opened.

***4. Model GUI mode***[]{#__RefHeading___Toc74369129 .anchor}

The user can open the "Model Input Editor" window in several different
ways:

1\. Click on the "Edit Dam Data" button in the "DAMCAT - Search Tool"
window, then click on the "View/Edit Failure Scenarios" button in the
next opened "DAMCAT -- Dam View \[dam NIDID\]" window will navigate the
user to the "Model Input Editor" screen.

2\. Click on the "Run Model" button in the "DAMCAT - Search Tool"
window, the model will run, and the "Output Manager" window will be
opened. With click on the "Close" button to close the "Output Manager"
window, the user will be taken to the "Model Input Editor" window.

**Note:** If model cannot run because of insufficient data, first
approach should be used.

![](media/image42.png){width="5.992361111111111in"
height="4.997916666666667in"}

[]{#__RefHeading___Toc74369196 .anchor}Figure 42. The \"Model Input
Editor\" window is displayed.

*Model GUI mode -The "Model Input Editor" window
layout*[]{#__RefHeading___Toc74369130 .anchor}

The "Model Input Editor " window layout divided on four separate parts
which have hierarchical structure:

\- one dam could have several scenarios of the model run;

\- one dam has several downstream points (minimum two to run model);

\- one downstream point has several cross-section pairs (minimum two to
run model.

1\. In the upper left part is displayed informational data about dam,
taken from the DamMaster table. This part of the window has grey
background.

![](media/image43.png){width="4.0625in" height="1.5in"}

[]{#__RefHeading___Toc74369197 .anchor}Figure 43. Informational data
about the dam is displayed.

2\. In the lower left part is displayed data taken from SdbIn table.
This part of the window has pink background. The data displayed in the
fields is associated with the scenario highlighted in the "Scenario
List". The scenario in the combo box is changed to be in sync with
highlighted in the list scenario. The set of the data is brought for the
chosen scenario. The type of the dam could be changed as chosen from the
"Type of Dam" combo box. The user is able to choose a debug option for
the Simplified Dambreak model in the "SMPDBK Debug Option" combo box. By
default it is turned off. With the debug option turned on the debug
information will be displayed. When the debug option will be set on the
system level, more debug information will be displayed.

![](media/image44.png){width="4.072916666666667in"
height="5.145833333333333in"}

[]{#__RefHeading___Toc74369198 .anchor}Figure 44. The scenario data from
the SdbIn table is displayed.

The user can to add a new scenario to existing list of scenarios by
clicking on the "Highlight me to append a new scenario" option in the
"Scenario List" or hit "Insert" key on the keyboard. To delete
highlighted scenario the "Delete" key should be used.

![](media/image45.png){width="4.072916666666667in"
height="5.145833333333333in"}

[]{#__RefHeading___Toc74369199 .anchor}Figure 45. The \"Highlight me to
append a new scenario\" option is chosen to add a new scenario.

Initially the source and scenario is displayed as "Not Specified", all
text fields are zeroed, they must be updated manually.

The scenario could be picked from the "Scenario" combo box, and the
source typed in the "Source" text field.

**Note:** Data inserted into the text fields will be tested for
consistency. When attempting to run the model with inconsistent input
data, a proper error message will be displayed.

The test on uniqueness is provided. With attempt to insert the duplicate
source - scenario combination, the error message will be displayed.

![](media/image46.png){width="4.0625in" height="5.09375in"}

[]{#__RefHeading___Toc74369200 .anchor}Figure 46. The error message is
displayed if this source-scenario combination already exists.

3\. In the upper right part is displayed downstream points data taken
from the DownStream table. This part of the window has light blue
background. The dam could have several downstream points -- minimum two
to run model. The data displayed in the fields is associated with the
downstream point highlighted in the "Downstream Point List". The set of
the data is brought for the chosen downstream point. The "Best Section
Type" combo contains all cross-section types available for the
particular down-stream point. The "Best Section Type" means that the
model will run on this type and associated with it set of data. The user
can pick any of existed in the combo box option to run the model.

![](media/image47.png){width="3.84375in" height="3.3333333333333335in"}

[]{#__RefHeading___Toc74369201 .anchor}Figure 47. The downstream point
data from the DownStream table is displayed.

The user can add a new downstream point to existing list of downstream
points by clicking on the "Highlight me to append a new cross-section
location" option in the "Downstream Point List" or hit "Insert" key on
the keyboard. To delete highlighted downstream point the "Delete" key
should be used.

Initially the downstream point name is displayed as "Not Specified", all
text fields are zeroed, they must be updated manually. The "Best Section
Type" combo box is set to "M1" -- manual.

**Note:** Data inserted into the text fields will be tested for
consistency. When attempting to run the model with inconsistent
downstream point data, a proper error message will be displayed.

4\. In the lower right part is displayed cross-section data taken from
the SectionPair table. This part of the window has light green
background. The dam could have several cross-section pairs -- minimum
two to run model. The data displayed in the fields is associated with
the downstream point highlighted in the "Downstream Point List". The set
of the cross-section pairs data is brought for the chosen downstream
point.

**Note:**

If the cross-section part of the window is empty, the cross-section type
should be chosen in the "Cross-Section List". Cross-section data for the
highlighted downstream point will populate the lower right part of the
GUI. If another downstream point is selected from the "Downstream Point
List", then the user will select the cross-section type in the
"Cross-Section List" valid for the chosen downstream point, and the
cross-section data will be displayed for the associated downstream
point.

![](media/image48.png){width="3.7604166666666665in"
height="2.7916666666666665in"}

[]{#__RefHeading___Toc74369202 .anchor}Figure 48. Cross-section pairs
data taken from the SectionPair table is displayed. It\'s associated
with the highlighted in the \"Downstream Point List\" downstream point.

The user can add a new cross-section to existing list of cross-sections
by clicking on the "Highlight me to append a new set of elevations"
option in the "Cross Section List" or hit "Insert" key on the keyboard.
To delete highlighted cross-section the "Delete" key should be used.

Initially the cross-section type is displayed as "M1 - Manual", all
cross-section text fields are empty, they must be updated manually.

**Note:** Data inserted into the text fields will be tested for
consistency. When attempting to run the model with inconsistent
cross-section pairs data, a proper error message will be displayed.

![](media/image49.png){width="3.7604166666666665in"
height="2.7916666666666665in"}

[]{#__RefHeading___Toc74369203 .anchor}Figure 49. When a new
cross-section is created, the type is set to \"M1 - Manual\", and can be
changed for any selected from the \"Cross Section Type\" combo box.

*The "Model Input Editor -- Database Mode -- Editing DAMCAT Entry: \[dam
NIDID\]" window menu*[]{#__RefHeading___Toc74369131 .anchor}

**1. The user has an option to save all changes made in this GUI to the
database.**

![](media/image50.png){width="3.2916666666666665in"
height="1.6770833333333333in"}

[]{#__RefHeading___Toc74369204 .anchor}Figure 50. To save updated or
newly inserted dam data to the database, the user must click on the
"Update Database" menu item under "Database" menu.

When the "Update Database" item is chosen under the "Database" menu, the
confirmation message box is displayed. If the "Yes" button is selected,
data will be saved to the database.

![](media/image51.png){width="5.995138888888889in"
height="2.582638888888889in"}

[]{#__RefHeading___Toc74369205 .anchor}Figure 51. The confirmation
message dialog when the "Database -\> "Update database" menu item is
selected.

If the "Close" button was clicked without saving data, the following
confirmation message dialog will appear:

![](media/image52.png){width="5.995138888888889in"
height="2.582638888888889in"}

[]{#__RefHeading___Toc74369206 .anchor}Figure 52. The confirmation
message dialog when the "Database -\> "Close" menu item is selected.

**2. The user has an option to edit a text file.**

This option could be used when the forecast product is being created. An
editor is setup in the resources file. With click on the "Edit Text
File" item under "Edit" menu, the file manager is opened, and needed
directory and file could be chosen. Made changes could be saved to the
same or a new file.

![](media/image53.png){width="3.2708333333333335in"
height="1.6145833333333333in"}

[]{#__RefHeading___Toc74369207 .anchor}Figure 53. The \"Edit -\> Edit
Text File\" menu item is selected.

**3. The user has an option to run a simplified Dambreak model.**

When the "Run SMPDBK" is selected under "Model" menu is selected, the
model will run. If the dataset for a particular dam is full and data is
consistent, the user will be navigated to the "Output Manager" window
(Output mode). If data needs to be fixed or some parameters are absent,
the correspondent messages will be displayed to prompt the user what
should be changed for proper model run.

![](media/image54.png){width="3.2708333333333335in"
height="1.6145833333333333in"}

[]{#__RefHeading___Toc74369208 .anchor}Figure 54. The "Model -\> Run
SMPDBK" menu item is selected.

4\. The user has an option to retrieve output results from the previous
model run. The user could save output from the latest run into the file
and revise / change the results without running model. By default the
file should have .OUT extension and saved in the directory specified by
the \<dba.home\> value in the resources file or in the start script.

![](media/image55.png){width="5.999305555555556in"
height="3.826388888888889in"}

[]{#__RefHeading___Toc74369209 .anchor}Figure 55. The user has option to
view output of the model run saved to the file.

***.Apps_defaults settings***

**damcrest.db_enabled : true** -- indicates that the user has Damcat
database

**damcrest.hasListAllDams : true** - the "Search Results" list will
display all dams existing in the database if the "hasListAllDams" when
the application starts; set to "true" by default

**damcrest.editor : /usr/X11R6/bin/gvim** -- The DamCREST application
uses editor, the default is the gvim editor.

Optionally an editor can be set to KWrite or nedit editors. Depending on
chosen editor the **damcrest.editor** token needs to be set
correspondently:

**damcrest.editor : /usr/bin/kwrite --** for KWrite

or

**damcrest.editor : /usr/bin/X11/nedit --** for nedit.

**DBDRIVER, CONNECTION_STRING, RUNPATH** environmental variables are set
up in the start script.

**CONNECTION_STRING** - variable resolving connection to needed database
**DBDRIVER** - defines Informix driver are set in the start script

**RUNPATH** -- path to the directory where executable of the SMPDBK
could be found.

[]{#__RefHeading___Toc74369132 .anchor}

***Resource file***

The application looks for the resources.txt at starting point. If the
operating system is Windows, resources.txt file must be presented in the
"damcrest home" directory or the application will exit. Path to this
directory is resolved in the start script as the value of the
DAMCREST_HOME environmental variable. If the operating system is Linux,
the application will look for needed settings in the .Apps_defaults and
set_hydro_env files if "resources.txt" file could not be found.

**Resources.txt** contains following settings:

**damcrest.db_enabled**

**damcrest.hasListAllDams**

**damcrest.editor**

**DBDRIVER**

**CONNECTION_STRING**

**RUNPATH**

[]{#__RefHeading___Toc74369133 .anchor}

***Initialization file .vimrc***[]{#__RefHeading___Toc74369134 .anchor}

The .vimrc file is the resource file used for gvim editor
initialization. This file has to be placed in the ../local/data/damcrest
directory. The settings in this file customize the default
initialization of the gvim editor, printing options. More detailed
description of the vim editor features could be found in MAN VIM pages.

window it and run the model. raph 3 of the is not fully presented or
some of them are invalid, the user will be provided throug

***Appendix A. DamCat Database
Specifications***[]{#__RefHeading___Toc74369135 .anchor}

***Database***

DamCREST uses the AWIPS Informix Relational Database Management System
and is located in the Informix database as dc_ob5xxx, where xxx - the
office identifier. For example, the DamCREST database names are

dc_ob5tae - WFO Tallahassee Hydrologic Service Area

dc_ob5pbz - Pittsburgh Basin RFC

***DamCat database Tables and Fields***

The Relational structure for dc_ob5xxx is comprised of 7 tables:

**[Tables]{.underline}** [**Number of Fields** **Primary**]{.underline}
**[Key(s)]{.underline}**

dammaster 10 nidid

damfeatures 52 nidid

damreservoir 6 nidid, type, elevation

downstream 13 nidid, down_name

sdbin 13 nidid, src, scenario

sdbout 12 nidid, down_name, src, scenario

sectionpair 9 nidid, down_name, pair_num, xsec_type

These tables contain information on dam search fields, additional dam
physical data, down stream location and cross-section data, dam break
results at dam and downstream locations, and reservoir capacity. New
dams can be added to the catalog, existed dams could be deleted from the
catalog, the dam can be copied under a newly created nidid (cloned), and
dam data can be edited.

The DamCat database table and field listings contain the following
columns of information:

colname - field name used in the DamCat database

colno - the column number of the field

coltype - the data type applicable to the corresponding field

collength - column length of the corresponding field.

  --------------------------------------------------------------------------------------
  ***DamMaster***                                                          
  ------------------------ ------------- --------------- ----------------- -------------
  ***colname***            ***colno***   ***coltype***   ***collength***   ***nulls***

  *nidid*                  *1*           *Char*          *10*              *No*

  *dam_name*               *2*           *Char*          *65*              

  *county*                 *3*           *Char*          *30*              

  *river*                  *4*           *Char*          *30*              

  *downstream_hazard*      *5*           *Char*          *11*              

  *volume_dam*             *6*           *Float*         *8*               

  *hsa*                    *7*           *Char*          *3*               

  *rfc*                    *8*           *Char*          *5*               

  *longitude_dam*          *9*           *Float*         *8*               

  *latitude_dam*           *10*          *Float*         *8*               
  --------------------------------------------------------------------------------------

  --------------------------------------------------------------------------------------
  ***DamFeatures***                                                        
  ------------------------ ------------- --------------- ----------------- -------------
  ***colname***            ***colno***   ***coltype***   ***collength***   ***nulls***

  *nidid*                  *1*           *Char*          *10*              *No*

  *other_dam_name*         *2*           *Char*          *65*              

  *dam_former_name*        *3*           *Char*          *50*              

  *stateid*                *4*           *Char*          *20*              

  *section_t_r*            *5*           *Char*          *30*              

  *owner_name*             *6*           *Char*          *50*              

  *owner_type*             *7*           *Char*          *14*              

  *dam_designer*           *8*           *Char*          *65*              

  *private_on_federal*     *9*           *Char*          *6*               

  *dam_type*               *10*          *Char*          *6*               

  *core*                   *11*          *Char*          *6*               

  *foundation*             *12*          *Char*          *6*               

  *purposes*               *13*          *Char*          *8*               

  *year_completed*         *14*          *Char*          *20*              

  *year_modified*          *15*          *Char*          *20*              

  *emerg_action_plan*      *16*          *Char*          *3*               

  *inspection_date*        *17*          *Char*          *20*              

  *inspection_freq*        *18*          *Char*          *20*              

  *st_reg_dam*             *19*          *char*          *6*               

  *st_reg_agency*          *20*          *Char*          *30*              

  *spillway_type*          *21*          *Char*          *6*               

  *spillway_width*         *22*          *Float*         *8*               

  *outlet_gates*           *23*          *Char*          *6*               

  *number_locks*           *24*          *Float*         *8*               

  *length_locks*           *25*          *Float*         *8*               

  *width_locks*            *26*          *Float*         *8*               

  *fed_funding*            *27*          *Char*          *20*              

  *fed_design*             *28*          *Char*          *20*              

  *fed_construction*       *29*          *Char*          *20*              

  *fed_regulatory*         *30*          *Char*          *20*              

  *fed_inspection*         *31*          *Char*          *20*              

  *fed_operation*          *32*          *Char*          *20*              

  *fed_owner*              *33*          *Char*          *20*              

  *fed_other*              *34*          *Char*          *20*              

  *source_agency*          *35*          *Char*          *60*              

  *drainage_area*          *36*          *Float*         *8*               

  *topo_map*               *37*          *Char*          *22*              

  *return_flow_region*     *38*          *Integer*       *4*               

  *dam_length*             *39*          *Float*         *8*               

  *dam_height*             *40*          *Float*         *8*               

  *structural_height*      *41*          *Float*         *8*               

  *hydraulic_height*       *42*          *Float*         *8*               

  *nid_height*             *43*          *Float*         *8*               

  *max_discharge*          *44*          *Float*         *8*               

  *max_storage*            *45*          *Float*         *8*               

  *normal_storage*         *46*          *Float*         *8*               

  *nid_storage*            *47*          *Float*         *8*               

  *surface_area*           *48*          *Float*         *8*               

  *elev*                   *49*          *Float*         *8*               

  *prebreak_avail*         *50*          *Char*          *1*               

  *comments*               *51*          *Char*          *30*              

  *updated*                *52*          *Datetime*      *date/time*       
  --------------------------------------------------------------------------------------

  -----------------------------------------------------------------------------------
  ***DamReservoir***                                                   
  -------------------- ------------- --------------- ----------------- --------------
  ***colname***        ***colno***   ***coltype***   ***collength***   ***nulls***

  *nidid*              *1*           *Char*          *10*              *No*

  *type*               *2*           *Char*          *1*               *No*

  *elevation*          *3*           *Float*         *8*               *No*

  *stordis*            *4*           *Float*         *8*               

  *surface*            *5*           *Float*         *8*               

  *updated*            *6*           *Datetime*      *date/time*       
  -----------------------------------------------------------------------------------

  ------------------------------------------------------------------------------------
  ***Downstream***                                                      
  --------------------- ------------- --------------- ----------------- --------------
  ***colname***         ***colno***   ***coltype***   ***collength***   ***nulls***

  *nidid*               *1*           *Char*          *10*              *No*

  *down_name*           *2*           *Char*          *25*              *No*

  *longitude*           *3*           *Float*         *8*               

  *latitude*            *4*           *Float*         *8*               

  *elevation*           *5*           *Float*         *8*               

  *distance_from_dam*   *6*           *Float*         *8*               

  *flood_flow*          *7*           *Float*         *8*               

  *flood_depth*         *8*           *Float*         *8*               

  *flood_width*         *9*           *Float*         *8*               

  *mann_oc*             *10*          *Float*         *8*               

  *comments*            *11*          *Char*          *30*              

  *xsec_best_type*      *12*          *Char*          *2*               

  *updated*             *13*          *Datetime*      *date/time*       
  ------------------------------------------------------------------------------------

  -------------------------------------------------------------------------------
  ***SdbIn***                                                      
  --------------- -------------- --------------- ----------------- --------------
  ***colname***   ***colno***    ***coltype***   ***collength***   ***Nulls***

  *nidid*         *1*            *Char*          *10*              *No*

  *src*           *2*            *Char*          *3*               *No*

  *scenario*      *3*            *Char*          *2*               *No*

  *hde*           *4*            *Float*         *8*               

  *bme*           *5*            *Float*         *8*               

  *vol*           *6*            *Float*         *8*               

  *sa*            *7*            *Float*         *8*               

  *tfm*           *8*            *Float*         *8*               

  *qo*            *9*            *Float*         *8*               

  *bw*            *10*           *Float*         *8*               

  *idam*          *11*           *Integer*       *4*               

  *comments*      *12*           *Char*          *30*              

  *updated*       *13*           *Datetime*      *date/time*       
  -------------------------------------------------------------------------------

  ----------------------------------------------------------------------------------
  ***SdbOut***                                                        
  ------------------- ------------- --------------- ----------------- --------------
  ***colname***       ***colno***   ***coltype***   ***collength***   ***nulls***

  *nidid*             *1*           *Char*          *10*              *No*

  *src*               *2*           *Char*          *3*               *No*

  *scenario*          *3*           *Char*          *2*               *No*

  *down_name*         *4*           *Char*          *25*              *No*

  *slope*             *5*           *Float*         *8*               

  *max_flow*          *6*           *Float*         *8*               

  *max_depth*         *7*           *Float*         *8*               

  *time_max_depth*    *8*           *Float*         *8*               

  *time_flood*        *9*           *Float*         *8*               

  *time_deflood*      *10*          *Float*         *8*               

  *comments*          *11*          *Char*          *30*              

  *updated*           *12*          *Datetime*      *date/time*       
  ----------------------------------------------------------------------------------

  ----------------------------------------------------------------------------------
  ***SectionPair***                                                   
  ------------------- ------------- --------------- ----------------- --------------
  ***colname***       ***colno***   ***coltype***   ***collength***   ***nulls***

  *nidid*             *1*           *Char*          *10*              *No*

  *down_name*         *2*           *Char*          *25*              *No*

  *pair_num*          *3*           *Int*           *4*               *No*

  *xsec_type*         *4*           *Char*          *2*               *No*

  *elev*              *5*           *Float*         *8*               

  *tw*                *6*           *Float*         *8*               

  *mann_n*            *7*           *Float*         *8*               

  *inactive_width*    *8*           *Float*         *8*               

  *updated*           *9*           *Datetime*      *date/time*       
  ----------------------------------------------------------------------------------