Each event is defined by the two input cards EVENTPER and EVENTLOC, and these inputs are linked by the event name, which must be unique among the events being processed in a given run. There is no particular requirement for the order of cards on the EV pathway. Note that the location for the event may be specified by either Cartesian coordinates or by polar coordinates, however, the polar coordinates must be relative to an origin of (0,0).
3.7.1 Using Events Generated by the ISCST Model
Since the ISCEV (EVENT) model was designed to work in conjunction with the ISCST model, the ISCST model has an option (CO EVENTFIL described in Section 3.2.9) to generate an input file for the ISCEV model. When this option is used, the ISCST model copies relevant inputs from the ISCST runstream input file to the ISCEV model input file, and generates the inputs for the EVent pathway from the results of the modeling run. These events are the design concentrations identified by the OU RECTABLE keyword (see Section 184.108.40.206), such as the highest and high‑second‑high 24‑hour averages, etc., and any threshold violations identified by the OU MAXIFILE keyword (see Section 220.127.116.11). The inputs generated by the ISCST model correspond to the syntax described above for the EVENTPER and EVENTLOC keywords. The locations for events generated by the ISCST model are always provided as Cartesian coordinates.
To easily identify the events generated by the ISCST model, and to provide a mechanism for the ISCST model to manage the events generated from the model run, a naming convention is used for the EVNAME parameter. The following examples illustrate the event names used by the ISCST model:
H1H01001 ‑ High‑first‑high 1‑hour average for source group number 1
H2H24003 ‑ High‑second‑high 24‑hour average for source group number 3
TH030010 ‑ Threshold violation number 10 for 3‑hour averages
TH240019 ‑ Threshold violation number 19 for 24‑hour averages
The high value design concentrations are listed first in the ISCEV model input file, followed by the threshold violations (grouped by averaging period). To make it easier for the user to review the ISCEV model input file generated by the ISCST model, and determine which events are of most concern, the actual concentration or deposition value associated with the event is included as the last field on the EVENTPER card. This field is ignored by the ISCEV model, and is included only for informational purposes. The user should be aware that the same event may appear in the ISCEV model input file as both a design value and as a threshold violation, depending on the options selected and the actual results. Since the model processes the events by date sequence and outputs the results for each event as it is processed, the order of events in the output file will generally not follow the order of events in the input file, unless all of the events were generated by the MAXIFILE option.
201 - 202 - 203 - 204 - 205 - 206 - 207 - 208 - 209 - 210 - 211 - 212 - 213 - 214 - 215 - 216 - 217 - 218 - 219 - 220 - 221 - 222 - 223 - 224 - 225 - 226 - 227 - 228 - 229 - 230 - 231 - 232 - 233 - 234 - 235 - 236 - 237 - 238 - 239 - 240 - 241 - 242 - 243 - 244 - 245 - 246 - 247 - 248 - 249 - 250
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