My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
FLOOD05059
CWCB
>
Floodplain Documents
>
Backfile
>
4001-5000
>
FLOOD05059
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/25/2010 6:48:07 PM
Creation date
10/5/2006 1:13:32 AM
Metadata
Fields
Template:
Floodplain Documents
County
Statewide
Community
Nationwide
Basin
Statewide
Title
WSP2 Computer Program
Date
5/1/1976
Prepared By
USDA Soil Conservation Service - Engineering Division
Floodplain - Doc Type
Educational/Technical/Reference Information
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
63
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
<br />Output <br /> <br />An 80/80 list of all input data is printed <br />first (see sample output on page 31). The <br />end of the input list is noted "END of 80/80 <br />LIST." This means that a COMPUTE card <br />has been encountered and computations <br />will follow. The standard output (valley sec- <br />tion and bridge rating tables) appears next. <br />Requested optional output (segment and <br />KD tables and rating curve plots) is inter- <br />mixed with the rating tables. Only one KD <br />table and rating curve plot is reproduced <br />in the sample. <br />The velocity under the total column in <br />the segment table is a weighted velocity. <br />It is the velocity that, when squared and <br />divided by 2g, yields the velocity head (see <br />step 3, Valley Section Analysis). Stated an- <br />other way, it is the average section velocity <br />adjusted (usually increased) for nonuni- <br />form velocity distribution within the valley <br />section. <br />Each output sheet has its own page iden- <br />tification. The standard output contains <br /> <br />Helpful Hints <br /> <br />Quite often it is necessary for someone <br />other than the person who prepares the <br />input to study the output. For a person un- <br />familiar with the data, it is much easier to <br />find specific pieces of information if a set <br />input pattern is followed. Therefore, the <br />pattern shown in the sample job is recom- <br />mended. The standard forms can aid in <br />coding input in this manner. <br />The sample job was put together as fol- <br />lows: The information on form SCS-ENG-16 <br />was put first. The complete reach and road <br />file was put next on a general input form. <br />The complete reach and road file should <br />be put here even if the section information <br />is split by LINK cards. This was followed by <br />the SECTION and BPR or CULV informa- <br /> <br />only the page number. The other sheets <br />contain the same number plus a letter iden- <br />tification. K for' KD table, P for plotted <br />rating table, and S for segment information <br />table. All output sheets pertaining to the <br />same cross section have the same page <br />number. The title part of the identification <br />is indicated by the input title cards. The <br />points on the plotted rating table are <br />labeled 0 for lowest cross section eleva- <br />tion, 1 to 9 for profiles 1 to 9, and A to F <br />for profiles 10 to 15. <br /> <br />The cost to run the sample job on <br />the USDA computer (IBM 370 model 168) <br />in Washington, D.C., was approximately <br />$17: 22 percent for reading data; 8 percent <br />for building the section tables of elevation <br />versus KD, Q'dt" etc.; 8 percent to bal- <br />ance energy between the valley sections; <br />1 percent to analyze the bridge; 33 percent <br />to analyze the culverts; and 28 percent to <br />print the output (Of which 1 percent was <br />for printing the rating curve plots). <br /> <br />tion in the upstream order of appearance <br />in the valley. The last information was <br />COMPUTE information followed by END- <br />JOB and ENDRUN cards. <br /> <br />WSP2 requires a large amount of input <br />data. The user should make every possible <br />check to eliminate errors. Use of the sort- <br />routine precludes WSP2 from checking for <br />correct station (x) values. Section 90963 in <br />the sample job is a good example of the <br />use of the sort-routine. After the section <br />was coded, it was noted that elevation at <br />the first end of the section was inadequate <br />The user coded a point at the end of the <br />section that WSP2 placed at the beginning <br />of the section. A warning message stating <br /> <br />11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.