Hours of emission

[iporras]

I am running HYSPLIT model in dispersion mode and I am wondering if it is possible to set the "hours of emission" less than an hour (e.g. 2 minutes, 10 minutes, etc...) and how I should manage the Setup Run / Pollutant Emission menu.

Thanks in advance,

Ignasi

[barbara.stunder]

Yes the "Hours of emission" can be less than 1 hour. It is entered as a fraction, e.g. 10 minutes would be 0.1667 h. You can confirm this after the run by looking at the MESSAGE file for 'emissions started' and 'emissions terminated'.

[ariel.stein]

Alternatively you could use an EMITIMES file to set your emissions.

Advanced / File Edit / 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.
1 Record 1 - Identification record describing the emission cycle header record
2 Record 2 - Identification record describing a location emission data record
3 Record 3 - First emission cycle header record
4 Record 4 - First emission data record in the first emission cycle


Emission Cycle Header Record: {YYYY} {MM} {DD} {HH} {hhhh} {#rec}
1 {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.
2 {hhhh} - Duration in hours that this emission cycle is valid.
3 {#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}
1 {YYYY} {MM} {DD} {HH} {mm} - Emission start time at this location
2 {HHmm} - Release duration in hours and minutes (no space).
3 {Lat} {Lon} {Hgt} - Position and height of the release.
4 {Rate} - Emission rate in mass units per hour.
5 {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).
6 {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.

[iporras]

I am entering the "hours of emission" as a fraction (p.e. 0.08333 for 5 minutes emission) and the MESSAGE file doesn't contain any kind of pollutant concentration:
NOTICE main: Initial time step (min) 1
NOTICE main: 1 61039601 0 0.0000000
NOTICE main: 1 61039602 0 0.0000000
NOTICE main: 1 61039603 0 0.0000000
NOTICE main: 1 61039604 0 0.0000000
NOTICE main: 1 61039605 0 0.0000000

The CONTROL file contains the next data:

2016 1 21 14 40
1
46.16050 16.28910 10
4
0
15660
1
/HYSPLIT_v4/runs/bcn-tgn-1km/d03/2016012000/
WRFDATA.ARL
1
As
3.6e+15
0.1667
00 00 00 00 00
1
41.16050 1.28910
0.006 0.006
1.8 1.8
./
cdump
2
0 16
00 00 00 00 00
00 00 00 00 00
00 1 00
1
1.0000 5.7760 1.0
0.0000 0.0000 0.0000 0.0000 0
0 0.00008 0.00008
0.0
0.000001

Do you know where could be the problem?

Thanks in advance.

[ariel.stein]

Can you please provide the MESSAGE file?

[iporras]

For sure:

MESSAGE.txt

MESSAGE file

(15.41 KiB) Downloaded 281 times

[ariel.stein]

I think you are running an older version of the code where the minute start time was not corrected.
Please replace the following part of the CONTROL file:

As
3.6e+15
0.1667
00 00 00 00 00

with

As
3.6e+15
0.1667
16 01 21 14 40

[iporras]

Dear Ariel,

Thank you very much for your help. The last suggested modification in the CONTROL file works perfectly (adding date information).

Kind regards,
Ignasi

[iporras]

Hello again,

I am trying to run HYSPLIT model using EMITIMES file with the next configuration:

YYYY MM DD HH DURATION(hhhh) #RECORDS
YYYY MM DD HH MM DURATION(hhmm) LAT LON HGT(m) RATE(/h) AREA(m2) HEAT(w)
2016 01 28 15 0001 2
2016 01 28 15 00 0010 41.14950 1.25900 10 1000 0.0 0.0
2016 01 28 15 00 0010 41.15950 1.26900 10 1000 0.0 0.0

MESSAGE file doesn't show any concentration value. On the other hand, HYSPLT runs if the emission duration is more than 10 min. The next EMITIMES configuration works:

YYYY MM DD HH DURATION(hhhh) #RECORDS
YYYY MM DD HH MM DURATION(hhmm) LAT LON HGT(m) RATE(/h) AREA(m2) HEAT(w)
2016 01 28 15 0001 2
2016 01 28 15 00 0011 41.14950 1.25900 10 1000 0.0 0.0
2016 01 28 15 00 0011 41.15950 1.26900 10 1000 0.0 0.0

Which is the problem with emission duration values are less than 11 min?
Thanks in advance.

[ariel.stein]

Please send me your MESSAGE files