My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Point Flow Analysis Software for the Lower South Platte River
CWCB
>
Water Supply Protection
>
DayForward
>
5001-6000
>
Point Flow Analysis Software for the Lower South Platte River
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2013 5:04:39 PM
Creation date
3/6/2013 3:09:49 PM
Metadata
Fields
Template:
Water Supply Protection
Description
User Guide: Point Flow Module & Querying & Charting Module
State
CO
Basin
South Platte
Water Division
1
Date
12/1/1994
Author
Northern Colorado Water Conservancy District
Title
User Guide for the Point Flow Analysis Software for the Lower South Platte River Kersey to Julesburg
Water Supply Pro - Doc Type
Report/Study
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
77
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Although Figure 3 shows the Q &CM querying only tables created by the PFM, if formatted <br />properly, the Q &CM can operate on tables created by other means. <br />The PFM consists of the Point Flow Software which acquires information through a user's <br />interface (screen/keyboard) and by accessing preconstructed tables (historical data). These <br />information components are illustrated, respectively, to the left and right of the Point Flow <br />Software component in Figure 3. The Point Flow Software is written in FoxPro database <br />language and operates within the FoxPro (for Windows) environment. <br />The only information the Point Flow Software requests from the user's interface is the beginning <br />and ending date of the period for which gains and flows are to be determined and the names of the <br />input and output tables. The bulk of the information necessary to perform the point flow <br />computations is stored within multiple tables. The upper most input table displayed in Figure 3, <br />entitled 'Control Table'. �ntains information specific to each structure within the river segment <br />and information charact� izing the fields within the Historical Data table(s). As Figure 3 shows, <br />multiple Historical Data tables can be included in the PFM. This allow users the ability to procure <br />data from multiple sources without having to incorporate the information into a single table. For <br />example, one Historical Data Table may contain only river diversion values, another Historical <br />Data Table may contain only values relating to inflowing streams, while a third Historical Data <br />Table comprises official river gauging values. <br />As noted above the only products from the PFM are two tables storing calculated subreach gains <br />and river channel flows (at points above and below each structure). The structural format and <br />field makeup of both the input tables (Control Table and Historical Table(s)) and the output tables <br />('Gains' Table and 'Flows' Table) are defined in subsequent sections. <br />The Q &CM consists of the Querying & Charting Software which relies on information supplied <br />directly by the user and from information stored in the 'Gains' and 'Flows' tables (output from the <br />PFM). The Querying and Charting Software is programmed in Visual BASIC and operated <br />within the Microsoft Excel (for Windows) environment. Charts (x -y graphs) and Summary Sheets <br />are the sole output of the Q &CM and can be directed to either a computer monitor or a printer. <br />The most logical operational scenario is to utilize the Point Flow Module only when data is <br />altered and /or appended to one or more of the Historical Data Tables. If no changes are expected <br />in any of the Historical Data Tables, the Point Flow Software need only be run one time to create <br />the 'Gains' and 'Flows' Tables (assuming that the entered 'beginning' and 'ending' date encompass <br />all dates wanting to be queried). Following the creation of the 'Gains' Table and 'Flows' Table the <br />Q &CM would be executed each 'querying' session. <br />12 ptflguid.wpd <br />
The URL can be used to link to this page
Your browser does not support the video tag.