Emission rate

Topics about the HYSPLIT dispersion model.

Emission rate

Postby tschonholz » August 29th, 2013, 2:39 pm

Is it possible to change emission rate with time or depending on a certain variable from an incoming model or should it remain constant in time during the whole run?
Thanks
Tamara.-
Tamara Schonholz
tschonholz
 
Posts: 19
Joined: May 8th, 2013, 11:42 am
Location: Argentina

Re: Emission rate

Postby ariel.stein » September 4th, 2013, 10:36 am

Below is the help file for the configuration of a time varying emission file for HYSPLIT

Advanced / Configuration Setup / Emissions File

This menu creates the optional EMITIMES file which is used to configure more complex point source emissions scenarios. In the standard model simulation, the CONTROL file can only be used to define one pollutant release cycle which applies equally to all source locations. Although multiple release cycles can be defined, they must all be at the same interval. Using the EMITIMES file to define the point source emissions, multiple release locations can each have their own emission characteristics, each with different pollutants, if desired. Furthermore, multiple emission cycles, at non-regular intervals can also be defined. By appropriately locating multiple sources in space and time, line- source as well as other non-regular emissions configurations can be created. In version 4.8 the format of this file has changed from previous HYSPLIT versions to such an extent that they are incompatible with each other. In all versions the file name is defined by the EFILE variable in the namelist configuration file created thorough the Advanced / Configuration menu tab.

The first menu tab defaults to the configuration for one source. If multiple sources are required, then enter the number in this menu. After pressing the Configure Locations button, another menu comes up to select the location number to configure. Pressing the location number button brings up the menu shown below. The GUI menu only supports the creation of a file for one pollutant for one emission cycle. If multiple pollutants are defined, or multiple cycles are required, then the file must be edited manually by duplicating the emission record at each location for all pollutants in the order they are defined in the CONTROL file. Each defined release location must be configured according to the following instructions. The point source emissions file must be located in the startup directory the name should always be in uppercase. The following is an example of the contents of EMITIMES file for one location. Multiple locations would have one line per location. The number of data records should equal the number of sources defined in the CONTROL file times the number of pollutants released.

The EMITIMES file may also be configured to construct a vertical line source by having two consecutive emission points defined at the same spatial location but each with different heights. Unlike the vertical line source definition through the CONTROL file, where the same emission rate is defined for all sources, here the emission rate may be varied through the column. For instance, if the source record N is at the same location as record N-1, the the emission rate defined for record N-1 will be used for all particles released in the column from N-1 to N. This means that the emission value given for the last record, in a series of records at the same location will not be used.

Record 1 - Identification record describing the emission cycle header record
Record 2 - Identification record describing a location emission data record
Record 3 - First emission cycle header record
Record 4 - First emission data record in the first emission cycle

Emission Cycle Header Record: {YYYY} {MM} {DD} {HH} {hhhh} {#rec}

{YYYY} {MM} {DD} {HH} - Starting time of the emission cycle, with each new emission cycle, all previous emission records are replaced with those in the new cycle.
{hhhh} - Duration in hours that this emission cycle is valid.
{#rec} - Number of emission records in this cycle (= # sources times # pollutants).

Emission Cycle Data Record: {YYYY} {MM} {DD} {HH} {mm} {HHmm} {Lat} {Lon} {Hgt} {Rate} {Area} {Heat}

{YYYY} {MM} {DD} {HH} {mm} - Emission start time at this location
{HHmm} - Release duration in hours and minutes (no space).
{Lat} {Lon} {Hgt} - Position and height of the release.
{Rate} - Emission rate in mass units per hour.
{Area} - Emission area in square meters. Zero is treated as a point source and non-zero values only apply to one of the horizontal distribution models (top-hat or Gaussian).
{Heat} - Heat released during the emission. Non-zero values result in a bouyancy plume rise calculation, replacing the previous height value.

The emisson cycle header record defines the valid time period for the subsequent data records. At the end of the header record time period {hhhh}, the model will attempt to read the next emission cycle header record. If no header record is found, then the EMITIMES emission processing is terminated and the model reverts to using the emission values defined in the CONTROL file. For instance, this means that if a short emission duration is defined in the data records, but the model simulation covers a longer period, the header record duration {hhhh} should be long enough to cover the entire simulation period. Unless it is indended to use both methods, the emission rate and duration in the CONTROL file should both be set to zero when using an EMITIMES file.

Special Case: Backward simulations

In the case of backward simulations, the cycle header record should point to the first (oldest) emission cycle and all subsequent emission cycles should be earlier in time. The emission start time within a cycle corresponds to a time such that the duration of emissions proceeds backward from that starting time. The internal backward flag has already been set from the negative run duration in the CONTROL file and therefore all time durations in the EMITIMES file should be expressed as positive numbers.
ariel.stein
 
Posts: 51
Joined: November 7th, 2012, 3:14 pm


Return to Dispersion Model

Who is online

Users browsing this forum: No registered users and 1 guest

cron