1. Quick Start Guide SITES SOFTWARE APPLICATION SEMINAR
__________________________
SITES
INTEGRATED DEVELOPMENT ENVIRONMENT
for
WATER RESOURCE SITE ANALYSIS 1

2. Objectives Getting Started Software Architecture Data Organization
Installation
Software Architecture
Input Interface
Build Interface
Output (View) Interface
Data Organization
Projects and Files
Input/Output
Additional Features
The objective of this session is explain where to get Sites, how to install Sites, and how to use Sites efficiently. The software architecture consists of three parts, an input interface to facilitate the creation of control files describing the watershed and structures to be analyzed, a build interface to check the integrity of the control file and invoke the Sites simulation to perform the analysis, and an output interface to view the output and compare results. Control files are organized together in project folders. Finally, the session will close with a few additional features that enhance Sites.

3. Objectives Getting Started Software Architecture Data Organization
Installation
Software Architecture
Input Interface
Build Interface
Output (View) Interface
Data Organization
Projects and Files
Input/Output
Additional Features
The first step to install the application.

4.
From our web site, usda.damsafety.info, follow the link to SITES Water Resource Site Analysis Software.

5. This will take you to the SITES page within a collection of NRCS Hydraulic and Hydrology Tools. Simply click DOWNLOAD NOW.

6. And a list of download links will be shown
And a list of download links will be shown. Click on SITES 2005 under the Download List, and Save the setup executable on your local machine.

7. Sites 2005 User’s Manual
Users can also download the SITES 2005 User’s Manual from the same Download List. The User’s Manual includes Appendix A which more or less covers the same information we will be discussing here.

8. After saving SITES2005. Setup
After saving SITES2005.Setup.exe, double-click on the file to start application installation.

9. Download and Install Sites 2005.1.3
Run Sites2005.Setup.exe
- InstallShieldTM Installation Set
Follow instructions from the InstallShield Installation Set.

10. Note that the application is installed to C:\Program Files\USDA\SITES\ by default. The user is free to select a different installation location.

11. After installation, click on Finish to complete installation.

12. Sites Program Group
To execute the application, click on Programs + Engineering Applications + SITES + SITES

13. Objectives Getting Started Software Architecture Data Organization
Installation
Software Architecture
Input Interface
Build Interface
Output (View) Interface
Data Organization
Projects and Files
Input/Output
Additional Features
The application software architecture consists of three interfaces.

14. Software Architecture
Sites
(Sites2005.exe)
Input Interface
Build Interface
View Interface
The input interface is used to create input control files using a standard File Menu and Input Interface Screens, the Build Interface is invoked using the Build Menu, and the View Menu is used to view a summary of output and view graphical and text output.

15. Create a New Project or Open an existing project.
The first step is to create a new project or open an existing project.

16. A project can be created inside an existing folder
A project can be created inside an existing folder. However, new projects cannot be nested or created with the same name as an existing folder. Here we are creating a new project called TurkeyCreek in the Sites Projects folder. The Sites Project folder could have been created using Windows Explorer.

17. Sites 2005.1.3 Quick Start Objectives
Getting Started
Installation
Software Architecture
Input Interface
Build Interface
Output (View) Interface
Data Organization
Projects and Files
Input/Output
Additional Features
Sites data is stored in a project folder.

18. Data Organization C:\Sites Projects\TurkeyCreek
For now, all we have is a project folder called TurkeyCreek.

19. And later, select the Project from the History List to open a recently used project.
When a user exits from a project, the project is added to a HISTORY LIST. Recently used projects can be opened by simply clicking on the HISTORY LIST. Up to the 5 most recently used projects will be listed.

20. Create a New File.
After creating a project, the next step is to create a new input file for a given simulation run.

21. Click on Continue - to enter data for the new file (run).
Click on Continue to enter data for the new run.

22. Fill in the required global data.
Specify global properties for the run.

23. Click on the element icons to build the watershed schematic for the run.
Then, construct a logical watershed schematic consisting of icons for STRUCTURES (STR), SUBWATERSHEDS (WSD), REACHES (RCH), and JUNCTION POINTS (JCT).

24. Data Organization Project Run Summary Table Structure (STR) Watershed1
Run
Summary
Table
0..n
0..n
0..n
0..n 1
The top-level data abstraction is a project which identifies a directory (folder) used to hold a collection of related runs. Each run is associated with an input (control) file and numerous output files. The input file is passed as input to the simulator (damsite.exe) and the simulator generates numerous output files. Some of those files are parsed by the IDE to generate additional output (*.out) and hydrograph (*.phy) files for each element. A given run is comprised of any number of hydrologic elements, including Structures, Subwatersheds, Reaches, and Junction (Bifurcation) Points. In addition, relationships between those elements is represented using a tree called as Watershed Schematic. All runs within a project that have been built (simulated) are listed in the Summary Table. From the Summary Table, related runs can be compared, and output graphs and text can be displayed for each run.
Structure
(STR)
Watershed
(WSD)
Reach
(RCH)
Junction
(JCT)
Watershed
Schematic

25. Example: Sites in Series
Here is an example: The Work Plan Map shows sites (structures) in series.
Note the solid arrow to lower site. This is the lower or design series site.
The other arrows are to upper sites or upstream sites. These are considered built for the design of the downstream or lower site.

26. The plan map of the previous slide is converted to a schematic showing the elements in the watershed. Each of the upstream elements is considered a feature of the watershed influencing the inflow to the downstream site. The downstream site is the one to be designed or analyzed.

27. How are elements processed?
Elements are processed from upstream to downstream using a postorder traversal; e.g., an element is processed only after all upstream elements have been processed.
Intermediate results are stored on a stack; the last set of hydrographs placed on the stack is the first set to be removed (LIFO).
How many elements can be pushed onto the stack? 100
You may wonder how these elements are processed internally. In general, elements are processed from upstream to downstream, and from left to right using what is called a postorder traversal of the tree.
A stack can be thought of as a bottle, and the last element put onto the stack is the first element to be removed from the stack.
The IDE only allows up to 100 elements to be added to a watershed schematic.

28. This diagram shows the traversal on the watershed schematic
This diagram shows the traversal on the watershed schematic. As you pass each element for the second time (post order) and you go down (traverse) on the right-hand side of each element it will be processed in the simulation.

29. Key Point Elements are processed from upstream to downstream.
The key point is that the interface will generate the model and commands necessary to take care of the series routing.
Elements are processed from upstream to downstream.
The key point is that the IDE will automatically generate the ADDMOV and SAVMOV commands required for series routing.

30. Create Watershed Schematic
If we just have a simple site, the schematic looks like this with ONE STRUCTURE.
Click on the STR icon on the toolbar to add a single structure.

31. We can click on the icon in the workspace, then click on the REACH icon on the tool bar to add a reach upstream.
Highlight the STR icon on the workspace, and then click on the RCH icon on the toolbar to add a reach upstream of the structure.

32. As shown here.

33. We can also add elements downstream if we accidentally forget to put one in.
By default, elements are added upstream of the selected element, but they can also be added downstream of the selected element by clicking on Options + Add Elements Downstream.

34. To edit the data describing an element in the schematic, or to enter data in a new element, the edit element command on the edit menu is used.
Select Edit + Edit Element to edit the selected hydrologic element denoting a single structure.

35. double click on the element icon, or
right click on the element icon to bring up a drop-down menu and select Edit Element.
The edit function for the element may also be accessed by a double click of the left mouse button or by a right click. Note that other information that may also be accessed through the right click menu. This will be of primary value for accessing information related to complex watersheds following execution of the computational routine through the build command – for example if we want to see output hydrographs at different points in the watershed.

36. This is the Watershed Information Screen.
Screen Level Help is available on every screen to assist the user in entering the required information.
The interface will guide the user through the input screens in a logical sequence for data entry, and help is available for each input field. The Other SESSIONS will cover the meanings of these fields.

37. The data is only stored in memory until it is Saved!
After entering the required information, select File + Save As… to save the data to a *.d2c file.
The data is only stored in memory until it is Saved!
After all required data has been entered, return to the home screen (through the schematic screen) to save the data to a file in the project using the save as command from the file menu. NOTE: The environment is file based: the data must be saved before using the build command to perform the computations.

38. Give the file a name. By default an extension of D2C is used.

39. Data Organization C:\Sites Projects\TurkeyCreek Demo.d2c
Once a file is saved, then a control file is stored in the project directory; e.g., Demo.d2c.

40. Software Architecture
Sites
(Sites2005.exe)
View Interface
Input Interface
Build Interface
Once a file is created using the Input Interface, it can be checked and processed using the Build Interface.
Integrity Checker
(IntCheck.exe)
Sites Simulator
(DamSite.exe)

41. The Check File command on the Build menu is used to do a first check of the entered data. This check will identify errors that will prevent the computations from being successful and to identify unusual combinations of data that may indicate possible data entry errors. It is not possible to check all possible problems at this level, so passing of this data check does not guarantee that the data has been entered correctly and will provide valid output.

42. Integrity Checker Sites 2005.1.3 Check File Error Table containing
(Sites2005.exe)
Check File
Demo.d2c
Demo.err
Error Table containing
a list of all errors
Message Box containing message "No Errors Found"
Input Interface
Build Interface
The Integrity Checker takes the d2c file as input and generates an error file. If the error file is empty, there are no errors or warnings to report.
Integrity Checker
(IntCheck.exe)

44. Build Interface Sites 2005.1.3 Build File Input Interface
(Sites2005.exe)
Build File
Input Interface
Build Interface
Sites Simulator
(DamSite.exe)
Demo.d2c
Demo.out
Demo.drg
Demo.dhy
Demo.dg2
The Build File command causes the Sites Simulator to be invoked to route the hydrographs and simulate erosion on auxiliary spillway of the design structure. Several files will be created as a result of a run.

45. Software Architecture
Sites
(Sites2005.exe)
View Summary Table
Input Interface
Build Interface
View Interface
From the top-level interface, a user can perform the basic operations on Input, Processing (Build), and Output (View) by using the corresponding menu options. To view the output, select View + Summary Table.

46. After selecting the run of interest, click on View Graphs or View Text to view detailed output for the run.

47. View Graphs
Several different graphs are available. Each graph can be copied to the clipboard or saved as a bitmap.

48. Summary of Steps Required to Get Started 1. Create a New Project
2. Create a New File
a. Click on Continue
b. Specify Global Watershed Data
c. Develop Watershed Schematic
d. Input data for each element (structure)
3. Save input file (*.d2c)
4. Check and build input file
5. View Summary Table and results
In summary, the steps to get started are: create a project, create a file (run), save the file, check and build the file, view results.

49. Download Example Data Package
From the web, several different sample data sets are available.

50. Import Example Files
Here are some examples that are described in the Sites User’s Manual.

51. Rebuild All
After downloading, you can build all of the files in a project folder at once.

52. Summary Graphs Sites 2005.1.3 View Summary Table View Interface
(Sites2005.exe)
View Summary Table
View Interface
Here we just have two files in the folder.

53. Summary Graph Selections
Then, compare the two runs using View + Summary Graphs. Select the variables to be used for the x and y axes.

54. And plot the results.

55. Another Example: Demo Project
Here is a slightly more interesting comparison with seven files.

56. Note that by changing the AS Width from 60 to 70 feet, we greatly increase the AS Integrity Distance – that is, how far the headcut is from the top of crest.

57. Additional Features
Data can be easily shared with other applications, using copy + paste.
The Sites Control File data can be modified directly.
User preferences can be changed: colors, backgrounds, font sizes, etc.
Output hydrographs are generated for each element in the Watershed Schematic.
Sites Control File format: SAVMOV and ADDMOV Commands
Sites has some additional features to make the application more user friendly.

58. Sharing Data
All grid controls can have their data shared with other applications in a standard way.
Even hydrologic elements can be “imported” from an external file.
On any grid, users can copy and paste the data; e.g., to/from an Excel spreadsheet.

59. Sites Control File Data
The Sites Control File data can be modified directly – however, be careful .
Also, the run data in memory can be viewed and edited directly.
Remember the data is not saved until the user selects File + Save As, and saves the data to a file.
A good idea is to save the data to a file with a different name.

60. User Preferences
User preferences can be specified by selecting Options + Specify Colors, then double-click on the color to be changed. Graphs will be updated when reloaded.
Colors on all graphs can be changed based on a user preferences using the standard color update control by selecting Options + Specify Colors or by double-clicking on any graph.

61. Watershed Schematic: View Hydrograph
Right-click on element and click View Hydrographs

62. Sites Control File Format -- ADDMOV and SAVMOV Commands
Other commands are described in detail in the Sites User’s Guide.
As mentioned earlier, the watershed schematic is defined using ADDMOV and SAVMOV.

63. Example 5 6 B C 3 4 A B+C 2 D C B E A D 1 Stack E SITES 05/01/2000
SAVMOV
SAVMOV
SAVMOV
SAVMOV
SAVMOV
ADDMOV
ADDMOV
SAVMOV
SAVMOV
SAVMOV
ENDJOB 5 6 B C 3 4 A
B+C 2
Elements are processed starting with element 3. A set of null hydrographs is pushed onto the stack because there is no other input to element 3. These null hydrographs are popped off of the stack, and used as input to element 3. After simulating element 3, the output hydrographs (denoted A) are pushed onto the stack.
This routine continues until all elements have been processed.
The table on the right shows the SAVMOV/ADDMOV commands used to move the data to and from the stack. D C B
B+C E A D 1
A+B+C
Stack E

64. SAVMOV Command 21-25 41-50 The revised SAVMOV command uses:
columns and for hydrograph storage location numbers.
an Element Reference Number in columns 21-25, and
an Element Identifier in columns
For each element, the system allows for output of hydrographs to validate the simulation.
The SAVMOV command used by the computational routine is modified from its previous form to allow hydrograph storage locations of 0 to 101 (3 characters).
Two additional fields were also added for use by the IDE: an Element Reference Number (generated by the system) in columns 21-25, and an Element Identifier in columns extracted from the user input identification for the element.

65. Hydrograph Storage Location Numbers
The storage location “101” denotes the stack.
Commonly Used Commands:
SAVMOV push a set of “zero” null hydrographs onto the stack.
SAVMOV push a set of “output” hydrographs onto the stack.
SAVMOV or SAVMOV pop a set of hydrographs off of the stack.
This slide includes commonly used SAVMOV commands.

66. Example: basex.d2c Element ID Element Ref. #
Note that in SAVMOV x records, column 71 stores the Element Type. This is necessary to allow a user to only input the elements in a watershed schematic without adding any data for the element; e.g., only SAVMOV and ADDMOV commands.
If the next element downstream is a structure or subwatershed, then SAVMOV is used. For a reach, SAVMOV is used. For junction (bifurcation) points, ADDMOV x is used.
Going to a structure or subwatershed(1), or going to a reach (2)
Element Type is stored in column 71
(1 = STR, 2 = WSD, 3 = RCH, 4 = JCT)

67. Example: Watershed Schematic
Subwatershed: W2
Structure: 256B4
Bifurcation Point: J1
Here is an example that we will use: basex.d2c.
Reach: S2
Structure: 256B5

68. ADDMOV Command
The ADDMOV command uses columns for an optional Element Reference Number, and for Element ID, and 71 for Element Type.
The ADDMOV command tells the simulator to add the top two sets of hydrographs on the stack and store the result on the stack for routing; e.g., Push(Stack, Pop(Stack) + Pop(Stack)).
The ADDMOV command uses columns for an optional Element Reference Number.
The top two elements on the stack are removed, added together, and the result is pushed back onto the stack.

69. For More Information Refer to the Sites User’s Manual.
Check out the web site: