WHen the channel network is too dense dednm reports this in the dednm.log. it should look for this error and report it to the user
1 ***** BEGINNING PROGRAM DEDNM.
2 ***** BEGINNING INITIALIZATION AND INPUT OF CONTROL DATA FROM FILE DNMCNT.INP.
3 TOPAZ SOFTWARE : TOPAZ PARAMETERIZATION SOFTWARE SYSTEM
4 VERSION 3.12, AUGUST 1999
5 PROGRAM DEDNM : DIGITAL ELEVATION DRAINAGE NETWORK MODEL PROGRAM
6 VERSION 3.10, APRIL 1999
7 J. GARBRECHT, USDA-ARS, EL RENO, OKLAHOMA, USA.
8 L. MARTZ, UNIVERSITY OF SASKATCHEWAN, SASKATOON, CANADA.
9 DISCLAIMER
10 THIS PROGRAM AND ITS SUBROUTINES ARE ACCEPTED AND USED BY THE RECIPIENT UPON
11 THE EXPRESS UNDERSTANDING THAT THE DEVELOPERS MAKE NO WARRANTIES, EXPRESSED
12 OR IMPLIED, CONCERNING THE ACCURACY, COMPLETENESS, RELIABILITY OR
13 SUITABILITY FOR ANY ONE PURPOSE, AND THAT THE DEVELOPERS SHALL BE UNDER NO
14 LIABILITY TO ANY PERSON BY REASON OF ANY USE MADE THEREOF.
15 THE NUMBER OF ROWS OR COLUMNS IN THE AGGREGATED/RESAMPLED DEM, 1828 , IS LARGE.
16 DO YOU WISH TO CONTINUE? ENTER 1 TO CONTINUE,
17 OR 0 TO STOP PROGRAM EXECUTION.
18 TITLE OF THE CURRENT TOPAZ APPLICATION:
19 DATE: 23 AUGUST 1999 WEPP WEB INTERFACE DEDNM VERSION 3.1
20 APPLICATION FOR TESTING AND VERIFICATION WEPP WEB GIS; INPUT FILE
21 TESTING AND CALIBRATION.
22 ***** BEGINNING DEM INPUT AND DEM PRE-PROCESSING.
23 ***** BEGINNING DEPRESSION AND FLAT AREA TREATMENT.
24 ***** BEGINNING FLOW VECTOR, FLOW PATH AND DRAINAGE AREA COMPUTATIONS.
25 ***** BEGINNING CHANNEL NETWORK DEFINITION.
26 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
27 !!!!!!!!!!!!!! ERROR !!!!!!!!!!!!!!
28 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
29 SUBROUTINE PRUNE; MODULE DEDNM3 (M_DEDNM3.F90).
30 THE NUMBER OF GENERATED CHANNEL LINKS EXCEEDS THE AVAILABLE ARRAY SIZE
31 RESERVED FOR CHANNEL LINK PROPERTIES.
32 THE ARRAY SIZE VALUE ICHS IS NOT COMPUTED CORRECTLY.
33 ICHS = -27356
34 NEEDED ARRAY SIZE = 2
35 LOGIC ERROR. CONTACT PROGRAM DEVELOPERS.
36 STOP ABNORMAL PROGRAM TERMINATION. LOGIC ERROR. CHECK REPORT FILE.
WHen the channel network is too dense dednm reports this in the dednm.log. it should look for this error and report it to the user