Since this is a warning message, it would have appeared at the end of the message summary table in the output file, but it would not have halted processing of the data. The last item on the message line, "Hints," may include such information as the keyword or parameter name causing the error, the source ID, group ID or (as in this case) the network ID involved, or perhaps the date variable identifying when the message occurred during the processing of the meteorological data, such as an informational message identifying the occurrence of a calm wind.
For new users and for particularly complex applications, it is strongly recommended that the model first be run with the RUNORNOT keyword (on the CO pathway) set NOT to run. In this way, the user can determine if the model is being setup properly by the runstream file before committing the resources to perform a complete run. The user should make a point of examining any warning messages carefully to be sure that the model is operating as expected for their application, since these messages will not halt processing by the model. In most cases, the detailed messages will provide enough information for the user to determine the location and nature of any errors in the runstream setup file. If the intent of the message is not immediately clear, then the user should refer to the more detailed descriptions provided in Appendix E for the particular error code generated.
In deciphering the error and warning messages, the line number provided as part of the message may be particularly helpful in locating the error within the input file. However, if it is an error of omission that is caught by the error checking performed at the completion of inputs for a pathway, then the line number will correspond to the last record for that pathway. The user may need to examine all of the messages carefully before locating the error or errors, especially since a single occurrence of certain types of errors may lead to other error conditions being identified later in the input file which do not really constitute errors in themselves. An example of this is provided in Figure 2‑4, which shows some inputs for the SO pathway where the building dimension keywords have been typed incorrectly, and the associated list of error messages. Since continuation cards were being used for the building width inputs, and the keyword was entered incorrectly on the first line, the subsequent records were also taken by the model to be invalid keyword inputs. While the error messages are the same for these records, the message originates from a different part of the model (SUBROUTINE SOCARD) for the records with the blank keyword.
101 - 102 - 103 - 104 - 105 - 106 - 107 - 108 - 109 - 110 - 111 - 112 - 113 - 114 - 115 - 116 - 117 - 118 - 119 - 120 - 121 - 122 - 123 - 124 - 125 - 126 - 127 - 128 - 129 - 130 - 131 - 132 - 133 - 134 - 135 - 136 - 137 - 138 - 139 - 140 - 141 - 142 - 143 - 144 - 145 - 146 - 147 - 148 - 149 - 150
APLICACIONES castellano: DIS CUS DES RAD english: DIS CUS DES RAD
português: DIS CUS DES RAD italiano: DIS CUS DES RAD
français: DIS CUS DES RAD