english:

 

 

                                 

 

     The following convention is used for identifying the different types of input parameters.  Parameters corresponding to secondary keywords which should be input "as is" are listed on the tables with all capital letters and are underlined. Other parameter names are given with an initial capital letter and are not input "as is."  In all cases, the parameter names are intended to be descriptive of the input variable being represented, and they often correspond to the Fortran variable names used in the model code.  Parentheses around a parameter indicate that the parameter is optional for that keyword.  The default that is taken when an optional parameter is left blank is explained in the discussion for that parameter.

                          TABLE B‑1

           DESCRIPTION OF CONTROL PATHWAY KEYWORDS

 

CO Keywords

    Type

Keyword Description

 

 

STARTING

    M ‑ N

Identifies the start of CONTROL pathway inputs

 

 

TITLEONE

    M ‑ N

First line of title for output

 

 

TITLETWO

    O ‑ N

Optional second line of title for output

 

 

MODELOPT

    M ‑ N

Job control and dispersion options

 

 

AVERTIME

    M ‑ N

Averaging time(s) to process

 

 

POLLUTID

    M ‑ N

Identifies type of pollutant being modeled

 

 

HALFLIFE

    O ‑ N1

Optional half life used for exponential decay

 

 

DCAYCOEF

    O ‑ N1

Optional decay coefficient

 

 

TERRHGTS

    O ‑ N

Specifies whether to assume flat terrain (default) or to allow use of receptors on elevated terrain

 

 

ELEVUNIT2

    O ‑ N

Defines input units for receptor elevations (defaults to meters)

 

 

FLAGPOLE

    O ‑ N

Specifies whether to accept receptor heights above local terrain (m) for use with flagpole receptors, and allows for a default flagpole height to be specified

 

 

RUNORNOT

    M ‑ N

Identifies whether to run model or process setup information only

 

 

EVENTFIL3

    O ‑ N

Specifies whether to generate an input file for EVENT model (Applies to ISCST Only)

 

 

SAVEFILE4

    O ‑ N

Option to store intermediate results for later restart of the model after user or system interrupt  (Applies to ISCST Only)

 

 

INITFILE4

    O ‑ N

Option to initialize model from file of intermediate results generated by SAVEFILE option  (Applies to ISCST Only)

 

 

MULTYEAR4

    O ‑ N

Option to process multiple years of meteorological data (one year per run) and accumulate high short term values across years (Applies to ISCST Only)

 

 

ERRORFIL

    O ‑ N

Option to generate detailed error listing file (error file is mandatory for CO RUNORNOT NOT case)

 

 

FINISHED

    M ‑ N

Identifies the end of CONTROL pathway inputs

 

 

Type:              M ‑ Mandatory

O - Optional

 

N - Non-Repeatable

R - Repeatable

 

 

1)

 

 

 

Either HALFLIFE or DCAYCOEF may be specified.  If both cards appear a warning message will be issued and the first value entered will be used in calculations.  Default assumes a half life of 4 hours for SO2 modeled in urban mode.

 

2)

 

 

The CO ELEVUNIT card is obsolescent with this version of the ISC models.  The new RE ELEVUNIT card should be used instead to specify elevation units for receptors.

 

3)

 

The EVENTFIL keyword controls whether or not to generate an input file for the ISCEV (EVENT) model.  The primary difference between ISCST and ISCEV processing is in the treatment of source group contributions.  The ISCST model treats the source groups independently, whereas the ISCEV model determines individual source contributions to particular events, such as the design concentrations determined from ISCST, or user‑specified events.  By specifying the EVENTFIL keyword, an input runstream file will be generated that can be used directly with the ISCEV model.  The events included in the generated ISCEV model input file are defined by the RECTABLE and MAXIFILE keywords on the OU pathway, and are placed in the EVent pathway.  If more than one output type (CONC, DEPOS, DDEP, and/or WDEP) is selected for the ISCST model, only events associated with the first output type, in the order stated above, are included in the EVENT model input file.

 

4)

 

The SAVEFILE and INITFILE keywords work together to implement the model's re‑start capabilities.  Since the MULTYEAR option utilizes the re‑start features in a special way to accumulate high short term values from year to year, it cannot be used together with the SAVEFILE or INITFILE keyword in the same model run.

 

                 


 

251 - 252 - 253 - 254 - 255 - 256 - 257 - 258 - 259 - 260 - 261 - 262 - 263 - 264 - 265 - 266 - 267 - 268 - 269 - 270 - 271 - 272 - 273 - 274 - 275 - 276 - 277 - 278 - 279 - 280 - 281 - 282 - 283 - 284 - 285 - 286 - 287 - 288 - 289 - 290 - 291 - 292 - 293 - 294 - 295 - 296 - 297 - 298 - 299 - 300

 

      Flag of Portugal 

 castellano:     italiano:     

 

 français:    português:  

 

deutsch:

 

 

 

deutsch: DIS CUS  DES  RAD

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