Laserfiche WebLink
<br />Output Error <br />Messages <br /> <br />The following explanations of error mes- <br />sages should help you determine the exact <br />cause of a particular problem. <br /> <br />ABUTMENT TYPE IS BLANK. DEFAULT IS <br />A. <br /> <br />The BPR abutment type should be A or B. <br />The program assumes an A if this field is <br />left blank. <br /> <br />BLANK IS NOT ALLOWED IN FIELD NUM- <br />BER XX. <br /> <br />Certain data fields cannot be left blank. If <br />zero is intended, the zero must be included <br />and punched in the card. This is because <br />certain types of data must be present for <br />the program to be run. The absence of data <br />would indicate an oversight or an error. <br /> <br />BRIDGE 'HEADWATER BELOW CRITICAL <br />DEPTH ON APPROACH SECTION. HEAD- <br />WATER PRESUMED AT CRITICAL. <br /> <br />The depth of water at the upstream face of <br />the bridge (bridge headwater elevation) is <br />less than critical depth at the same loca- <br />tion. This occurs if the bridge opening and <br />exit section have much more discharge <br />capacity than the approach section related <br />to the same depth. <br /> <br />CARD OUT OF SEQUENCE-FATAL. <br /> <br />The program expected a girder card or a <br />CULV2 card. <br /> <br />CROSS SECTION NAMED XXXXX WAS <br />NOT IN THE FILE, OR JOB DELETED. <br /> <br />In attempting to update the reach file, one <br />of the cross sections named in the From <br />XSEC or To XSEC was not in the file. These <br />cross sections must have been included in <br />the old reach file prior to an update. <br /> <br />CROSS SECTION XXXXX DOES NOT <br />HAVE A SEGMENT NUMBER XX. <br /> <br />Segments must be numbered consecutive- <br />ly. For example, if segments are numbered <br />1, 2, 4, and 5, WSP2 lists segment 3 as <br />missing. <br /> <br />CROSS SECTION XXXXX DOES NOT <br />HAVE SEGMENT FILE. <br /> <br />WSP2 found no segment file for the named <br />cross section. It could be that the section <br />is to be a bridge. If so, then bridge data are <br />also missing. <br /> <br />CROSS SECTION XXXXX HAS TWO SEG- <br />MENTS NUMBER XX. <br /> <br />In trying to set up the segments for this <br />cross section, the program found two seg- <br />ments with the same number; the first seg- <br />ment found with this number is used, and <br />the other is disregarded. <br /> <br />CROSS SECTION XXXXX WAS NOT IN <br />THE FILE. <br /> <br />The named cross section was not in the <br />section file. The cross section either was <br />not entered or an error was made in punch- <br />ing the name. <br /> <br />DATA POINTS REORDERED BY PRO- <br />GRAM ACCORDING TO X VALUES, OR <br />DUPLICATE X POINTS NOT CHANGED. <br /> <br />This means that the sort-routine was used <br />to put station (x) values in order of increas- <br />ing magnitude. <br /> <br />ERROR-THIS STARTING DATA NOT YET <br />COMPUTED. <br /> <br />The starting elevations were to have been <br />computed and retained. However, the re- <br />quired cross section has not been used in <br />any previous COMPUTES. <br /> <br />13 <br />