-
Notifications
You must be signed in to change notification settings - Fork 3
/
ch06_programs.xml
7706 lines (6451 loc) · 316 KB
/
ch06_programs.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
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
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
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
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
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="ch_programs">
<title>SMOKE Core Programs</title>
<section>
<title>Overview</title>
<para><xref linkend="fig_programs_core_programs" /> shows the SMOKE core programs and how they relate to each other. We define the core programs as those needed for the actual emissions processing; we exclude QA and utility programs such as <command>Smkreport</command> (these programs are discussed in <xref linkend="ch_quality_assurance" /> and <xref linkend="ch_utilities" />). The lines between the boxes represent one or more files passing between the programs, and show the dependencies among the programs. Note that we have omitted some redundant file dependencies to make the diagram easier to understand. Unless otherwise noted, the SMOKE core programs are applied for the anthropogenic source categories: area-, mobile-, and point-source processing (biogenic processing follows a separate path from the other source categories). When a program that applies to multiple source categories is used, it can be run for only one source category at a time, with the exception of <command>Smkmerge</command> and <command>Mrggrid</command>.</para>
<figure id="fig_programs_core_programs">
<title>SMOKE core programs</title>
<mediaobject>
<imageobject role="pdf">
<imagedata width="6.5in" fileref="images/programs/core_programs_pdf.jpg" />
</imageobject>
<imageobject role="html">
<imagedata fileref="images/programs/core_programs_html.jpg" />
</imageobject>
</mediaobject>
</figure>
<para>The <link linkend="sect_programs_smkinven"><command>Smkinven</command></link> program, at left in <xref linkend="fig_programs_core_programs" />, is responsible for importing the stationary area/non-point, nonroad, on-road mobile, and point source inventory emissions data. For mobile sources, <command>Smkinven</command> can also import activity data in the form of VMT and vehicle speed for use in generating emission factors. For point sources, <command>Smkinven</command> can also import day- and hour-specific data. The output from <command>Smkinven</command> is used as input to nearly every other core SMOKE program.</para>
<para>Also at left, the <link linkend="sect_programs_normbeis3"><command>Normbeis3</command></link> or <link linkend="sect_programs_normbeis4"><command>Normbeis4</command></link> program imports the gridded land use data and biogenic emissions factors, and creates gridded, normalized (time-independent) biogenic emissions.</para>
<para><link linkend="sect_programs_grdmat"><command>Grdmat</command></link> creates the gridding matrix for the anthropogenic source categories.</para>
<para><link linkend="sect_programs_temporal"><command>Temporal</command></link> program is used to create an hourly emissions file for the anthropogenic source categories. It can read in day-specific and hour-specific data, and merge this with estimated daily and hourly data created from the annual emissions data using temporal profiles.</para>
<para><link linkend="sect_programs_elevpoint"><command>Elevpoint</command></link> preprocesses the selected PinG and major point sources. <command>Elevpoint</command> is not used when no PinG or major point sources need to be defined. In this case, SMOKE can create elevated emissions for all point sources, so there is no need to specifically indicate the major point sources.</para>
<para><link linkend="sect_programs_laypoint"><command>Laypoint</command></link> computes the plume rise for all point sources based on the meteorology data.</para>
<para><link linkend="sect_programs_spcmat"><command>Spcmat</command></link> creates the speciation matrices (both mass and molar) for the anthropogenic source categories. It uses the user-selected chemical mechanism.</para>
<para><link linkend="sect_programs_cntlmat"><command>Cntlmat</command></link> creates the growth matrices, multiplicative control matrices, and reactivity control matrices for the anthropogenic source categories. This program is not used for base-year emissions without controls.</para>
<para><link linkend="sect_programs_grwinven"><command>Grwinven</command></link> is used to grow the emissions to past or future years using the growth matrix created by <command>Cntlmat</command> and the imported inventory data from <command>Smkinven</command>. It writes both SMOKE inventory format (I/O API NetCDF) and ORL format. The output from <command>Grwinven</command> is used in place of the original output from <command>Smkinven</command> when processing past or future years.</para>
<para><link linkend="sect_programs_tmpbeis3"><command>Tmpbeis3</command></link> or <link linkend="sect_programs_tmpbeis4"><command>Tmpbeis4</command></link> applies meteorology adjustments to the normalized emissions created by <command>Normbeis3</command> or <command>Normbeis4</command>. <command>Tmpbeis3</command> or <command>Tmpbeis4</command> also applies the speciation profiles needed for the user-selected chemical mechanism to create gridded, hourly, model-species biogenic emissions data for use in <command>Smkmerge</command> and <command>Mrggrid</command>. The <command>Normbeis3</command> and <command>Tmpbeis3</command> programs taken together are the equivalent of SMOKE-BEIS3, and <command>Normbeis4</command> and <command>Tmpbeis4</command> are SMOKE-BEIS4.</para>
<para><link linkend="sect_programs_smkmerge"><command>Smkmerge</command></link> is used to combine all emissions and matrices to create the gridded, hourly, model-species emissions needed for an AQM. It can merge for one source category at a time or all source categories at once, and it can read in the model-ready biogenic emissions to merge with the anthropogenic source categories. It can merge the matrices with the inventory data output from <command>Smkinven</command> or the hourly emissions from <command>Temporal</command>, and it can optionally merge the speciation, gridding, or control matrices, or any combination. It also writes state and county emissions totals.</para>
<para><link linkend="sect_programs_movesmrg"><command>Movesmrg</command></link> is only used for mobile sources to compute hourly emissions using the hourly VMT from <command>Temporal</command>, the MOVES emission rates lookup tables (i.e., RPD, RPH, RPV, RPP, RPS and RPHO), the gridded/averaged temperatures meteorology data and more. If VMT are not used, then the emissions from <command>Smkinven</command> are combined with the temporal factors, and the emission factors are not used at all.</para>
<para>In the remaining sections of this chapter, we provide detailed program descriptions, in alphabetic order.</para>
<para><link linkend="sect_programs_mrgelev"><command>Mrgelev</command></link> is used to combine ASCII elevated files created by <command>Smkmerge</command>. These files contain point-source data needed by AQMs including CAMx and UAM models.</para>
<para><link linkend="sect_programs_mrggrid"><command>Mrggrid</command></link> is used to combine gridded emission data files, which can be speciated or non-speciated, and hourly or time-independent. It can combine a 3-D point source file with any number of 2-D files from other source categories. This program is optional and provides a convenient way to merge model-ready output files outside of <command>Smkmerge</command>.</para>
<para><link linkend="sect_programs_mrgpt"><command>Mrgpt</command></link> is used to combine multiple point sources inline-mode hourly speciated emission data and ASCII elevated files created by <command>Smkmerge</command>. This program is optional and allows the users to process multiple point sources separately in inline mode through <command>Smkmerge</command> prior to merging them for CMAQ model.</para>
</section>
<section id="sect_programs_cntlmat">
<title><command>Cntlmat</command></title>
<section>
<title>Description</title>
<para><emphasis>Processing categories:</emphasis> area, mobile, point</para>
<para>The <command>Cntlmat</command> program uses control packets to create a growth matrix, and/or a multiplicative control matrix, and/or a reactivity control matrix. <command>Cntlmat</command> allows seven different control packet types: /MACT/, /CONTROL/, /EMS_CONTROL/, /CTG/, /ALLOWABLE/, /REACTIVITY/, and /PROJECTION/. The format of each packet type is given in <xref linkend="sect_input_gcntl" />.</para>
<itemizedlist>
<listitem>
<para>Growth matrix - This contains past- or future-year growth factors for all sources. <comment>If desired, <command>Cntlmat</command> can grow multiple inventory years to a single modeling year. The /PROJECTION/ packet contains the year for which the growth factors apply and contains both a <quote>to year</quote> and a <quote>from year</quote>. Using a series of these packets, inventory records from different years can be grown to a single year. <command>Cntlmat</command> supports multiple-year growth for area, mobile, and point sources.</comment></para>
</listitem>
<listitem>
<para>Multiplicative control matrix - This matrix contains the combination of various types ofcontrols typically used in emissions processing: CTG, MACT, RACT, control efficiency, rule effectiveness, rule penetration, allowable emissions, and caps. The logic used when applying this matrix is described below this bulleted list. </para>
</listitem>
<listitem>
<para>Reactivity matrix - This matrix contains the information needed for applying reactivity controls.</para>
</listitem>
</itemizedlist>
<section>
<title>Application Logic for the Multiplicative Control Matrix</title>
<para>The multiplicative matrix is built from entries in four packets: /MACT/, /CONTROL/ or /EMS_CONTROL/, /CTG/, and /ALLOWABLE/. The packets are applied in the following order:</para>
<itemizedlist>
<listitem>
<para>/MACT/</para>
</listitem>
<listitem>
<para>/CONTROL/ or /EMS_CONTROL/ (cannot use both at same time)</para>
</listitem>
<listitem>
<para>/CTG/</para>
</listitem>
<listitem>
<para>/ALLOWABLE/</para>
</listitem>
</itemizedlist>
<para>With the exception of the /CONTROL/ packet, all controls are always applied in addition to one another.</para>
<section>
<title>/MACT/ packet</title>
<para>The /MACT/ packet is designed to support the primary MACT controls needed for toxics processing. It is applied first, and uses the following logic. When a source is found that matches a /MACT/ packet entry (source matching is addressed in <xref linkend="sect_programs_cntlmat_source_match" />), <command>Cntlmat</command> first calculates a inventory efficiency value (Eff<subscript>inv</subscript>) for that source based on the control efficiency (C<subscript>eff</subscript>), rule effectiveness (R<subscript>eff</subscript>), and rule penetration (R<subscript>pen</subscript>) provided in the inventory:</para>
<para>Eff<subscript>inv</subscript> = C<subscript>eff</subscript> [inventory] x R<subscript>eff</subscript> [inventory] x R<subscript>pen</subscript> [inventory]</para>
<para>Next, a control factor is calculated for existing sources (Fac<subscript>exist</subscript>) using the control efficiency of existing sources (Eff<subscript>exist</subscript>) and fraction of new sources (Frac<subscript>new</subscript>) provided in the /MACT/ packet entry. If Eff<subscript>exist</subscript> > Eff<subscript>inv</subscript>, then Fac<subscript>exist</subscript> is calculated as:</para>
<para>Fac<subscript>exist</subscript> = (1 - Frac<subscript>new</subscript>) x ((1 - Eff<subscript>exist</subscript>) / (1 - Eff<subscript>inv</subscript>))</para>
<para>Otherwise,</para>
<para>Fac<subscript>exist</subscript> = (1 - Frac<subscript>new</subscript>)</para>
<para><command>Cntlmat</command> then calculates a control factor for new sources (Fac<subscript>new</subscript>) using the control efficiency of new sources (Eff<subscript>new</subscript>) provided in the /MACT/ packet. If Eff<subscript>new</subscript> > Eff<subscript>inv</subscript>, then</para>
<para>Fac<subscript>new</subscript> = Frac<subscript>new</subscript> x ((1 - Eff<subscript>new</subscript>) / (1 - Eff<subscript>inv</subscript>))</para>
<para>Otherwise,</para>
<para>Fac<subscript>new</subscript> = Frac<subscript>new</subscript></para>
<para>Finally, the new and existing source factors are summed to compute the final /MACT/ packet control factor (Fac<subscript>MACT</subscript>).</para>
<para>Fac<subscript>MACT</subscript> = Fac<subscript>exist</subscript> + Fac<subscript>new</subscript></para>
<para>The /MACT/ packet is designed to be used only for sources with MACT codes, currently nonpoint and point toxic sources.</para>
</section>
<section>
<title>/CONTROL/ packet</title>
<para>After processing the /MACT/ packet, the /CONTROL/ packet is applied using the following logic. Each entry in the /CONTROL/ packet can be identified as <quote>replacement</quote> or <quote>additive</quote>. If set to <quote>replace</quote>, the /CONTROL/ entry will be used to replace the controls from the /MACT/ packet or the base-year inventory controls; otherwise, the control will be applied in addition to the controls from the /MACT/ packet or the base-year inventory controls. When the controls are replaced, the default behaviour of <command>Cntlmat</command> is to back out the existing controls and apply the replacement controls. Usually, users want to do this only when the replacement controls are more stringent (i.e., a greater reduction) than the /MACT/ packet or base-year controls - so this is the default behaviour of <command>Cntlmat</command>. This default behaviour can be changed by setting the value of <envar>COMPARE_REPLACE_CONTROL</envar> to "N" in your run script. In this case, the replacement controls will be applied regardless of the existing controls from the base invetory or the /MACT/ packet, which could result in increased emissions. </para>
<para>When an <quote>additive</quote> entry is matched to a source, the /CONTROL/ packet factor (Fac<subscript>CONTROL</subscript>) the control packet information is applied in addition to the exitsing controls, which further reduce the remaining emissions.</para>
<para>For <quote>additive</quote> control packet entries, the control factors are calculated from the control efficiency, rule effectiveness, and rule penetration values provided in the /CONTROL/ packet entry as follows:</para>
<para>Fac<subscript>CONTROL</subscript> = (1 - C<subscript>eff</subscript> [packet] x R<subscript>eff</subscript> [packet] x R<subscript>pen</subscript> [packet])</para>
<para>A cumulative control factor Fac<subscript>result</subscript> is then calculated by multiplying Fac<subscript>Existing</subscript> x Fac<subscript>CONTROL</subscript>.</para>
<para>In the case of <quote>additive</quote> controls only, The overall reduction factor is then used to calculate an overall new control efficiency to be put in any resulting inventory files as: C<subscript>eff</subscript> [result] = 1 - Fac<subscript>result </subscript>. The final Rule Penetration and Rule Effectiveness values are then set to 100%.</para>
<para>For <quote>replacement</quote> entries, <command>Cntlmat</command> first <quote>backs out</quote> the existing controls provided in the inventory from the control values provided in the /CONTROL/ packet entry as follows:</para>
<para>D = (1 - C<subscript>eff</subscript> [inventory] x R<subscript>eff</subscript> [inventory] x R<subscript>pen</subscript> [inventory])</para>
<para>If D = 0.0, then the backout value, B, is equal to 0; otherwise, B = 1/D. Using this backout value, the /CONTROL/ factor is calculated as</para>
<para>Fac<subscript>CONTROL</subscript> = B x (1 - C<subscript>eff</subscript> [packet] x R<subscript>eff</subscript> [packet] x R<subscript>pen</subscript> [packet])</para>
<para>Unlike <quote>additive</quote> entries, the Fac<subscript>CONTROL</subscript> value for <quote>replacement</quote> entries replaces the factor calculated from the /MACT/ packet or base year inventory (if any). The /CONTROL/ packet can be applied to stationary area/nonpoint, nonroad, on-road mobile, and point sources. On-road mobile source inventories do not include control efficiency, rule effectiveness, or rule penetration fields. However, the /CONTROL/ packet can still be used to apply adjustment factors to mobile sources. In this case, B in the above formula will be 1 when computing factor Fac<subscript>CONTROL</subscript> that is applied to the emissions.</para>
</section>
<section>
<title>/CTG/ packet</title>
<para>The /CTG/ packet is processed next, as follows. The emission value (after application of /MACT/, /CONTROL/, and/or /EMS CONTROL/) is compared to the cutoff value specified as part of the /CTG/ packet record. If the emission value exceeds the cutoff value, then the control technology factor is applied to the emissions. If the resulting emissions value still exceeds the cutoff value, then either the MACT <emphasis>or</emphasis> the RACT factor is used. The MACT factor is used if it is defined (i.e., greater than zero); if it is not defined (less than or equal to zero), then the RACT factor is used. If neither the MACT nor RACT are defined, but the emissions are still greater than the cutoff, then the emissions are set to the cutoff value.</para>
</section>
<section>
<title>/ALLOWABLE/ packet</title>
<para>Finally, the /ALLOWABLE/ packet is processed. The entries in this packet override the /MACT/, /CONTROL/, /EMS CONTROL/, and /CTG/ packets. The way this packet is applied depends on whether or not the Cap and Replace values in the packet are defined (greater than zero).</para>
<itemizedlist>
<listitem>
<para>If the Cap value is defined, <command>Cntlmat</command> compares the inventory emissions value to the Cap value, and sets a control factor, using the following procedure: If both the Cap and Replace values are defined, this control factor is the Replace value divided by the original emissions value. If only the Cap value is defined, the factor is the Cap value divided by the original emissions value.</para>
</listitem>
<listitem>
<para>If the Cap value is not defined, then the factor is the Replace value divided by the original emissions value.</para>
</listitem>
<listitem>
<para>If neither the Cap nor Replace values are defined, the packet entry is invalid and is ignored.</para>
</listitem>
</itemizedlist>
</section>
</section>
<section id="sect_programs_cntlmat_source_match">
<title>Source Matching Hierarchy</title>
<para>To match each sources with the appropriate control packet entry, <command>Cntlmat</command> uses a hierarchy of source characteristics, trying to match each source to the most specific control packet entry. Note that not all combinations are applicable to all control packets (for example, there is no MACT code associated with the /PROJECTION/ packet). <quote>Left <emphasis>x</emphasis> of SCC</quote> refers to an 8- or 10-digit SCC with all digits except the first <emphasis>x</emphasis> set to 0. <quote>Left 2 of SIC code</quote> refers to a 4-digit SIC code with the third and fourth digits set to 0. The maximum field width in SMOKE and its input files for SCC is 20 characters as of SMOKE v4.0. The 8 or 10 digit SCC are still supported, but if the SCC is greater than 10 digits the SCC hierarchial approach will not be supported. The SIC may also be up to 20 characters in length, but if the SIC is larger than 4 characters then the hierarchial approach will not be used.</para>
<para>For point sources, the following hierarchy is used, in order of most specific to least specific. (NOTE: only for SCC less than or equal to 10 characters and SIC less than or equal to 4 characters) </para>
<orderedlist spacing="compact">
<listitem>
<para>Country/State/County code, plant ID, point ID, stack ID, segment ID, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID, stack ID, segment ID, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID, stack ID, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, MACT code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID, stack ID, segment ID, 8-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID, stack ID, segment ID</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID, stack ID</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, point ID</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, 8-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID, MACT code</para>
</listitem>
<listitem>
<para>Country/State/County code, plant ID</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, MACT code, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, MACT code, pollutant</para>
</listitem>
<listitem>
<para>MACT, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>MACT, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code, 8-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code</para>
</listitem>
<listitem>
<para>Country/State code, MACT code, 8-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State code, MACT code</para>
</listitem>
<listitem>
<para>MACT code, 8-digit SCC code</para>
</listitem>
<listitem>
<para>MACT code</para>
</listitem>
<listitem>
<para>Country/State/County code, 4-digit SIC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 2 of SIC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, 4-digit SIC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 2 of SIC code, pollutant</para>
</listitem>
<listitem>
<para>4-digit SIC code, pollutant</para>
</listitem>
<listitem>
<para>Left 2 of SIC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, 4-digit SIC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 2 of SIC code</para>
</listitem>
<listitem>
<para>Country/State code, 4-digit SIC code</para>
</listitem>
<listitem>
<para>Country/State code, left 2 of SIC code</para>
</listitem>
<listitem>
<para>4-digit SIC code</para>
</listitem>
<listitem>
<para>Left 2 of SIC code</para>
</listitem>
<listitem>
<para>Country/State/County code, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 6 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 3 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 1 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, 8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 6 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 3 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 1 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>8-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 6 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 3 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 1 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, 8-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 6 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 3 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 1 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, 8-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 6 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 3 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 1 of SCC code</para>
</listitem>
<listitem>
<para>8-digit SCC code</para>
</listitem>
<listitem>
<para>Left 6 of SCC code</para>
</listitem>
<listitem>
<para>Left 3 of SCC code</para>
</listitem>
<listitem>
<para>Left 1 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code</para>
</listitem>
<listitem>
<para>Country/State code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code</para>
</listitem>
<listitem>
<para>Pollutant</para>
</listitem>
</orderedlist>
<para>For nonpoint/stationary area sources, the following hierarchy is used. The maximum field width in SMOKE and its input files for SCC is 20 characters as of SMOKE v4.0. The 8 or 10 digit SCC are still supported, but if the SCC is greater than 10 digits the SCC hierarchial approach will not be supported. The SIC may also be up to 20 characters in length, but if the SIC is larger than 4 characters then the hierarchial approach will not be used. Nonpoint SCCs can have either 8 or 10 digits, which is why there are two separate SCC levels mentioned for each of the SCC-based assignments.(NOTE: hierarchial approach is only for SCC less than or equal to 10 characters and SIC less than or equal to 4 characters)</para>
<orderedlist spacing="compact">
<listitem>
<para>Country/State/County code, MACT code, 8- or 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, MACT code, 8- or 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, MACT code, pollutant</para>
</listitem>
<listitem>
<para>MACT code, 8- or 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>MACT code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code, 8- or 10-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, MACT code</para>
</listitem>
<listitem>
<para>Country/State code, MACT code, 8- or 10-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State code, MACT code</para>
</listitem>
<listitem>
<para>MACT code, 8- or 10-digit SCC code</para>
</listitem>
<listitem>
<para>MACT code</para>
</listitem>
<listitem>
<para>Country/State/County code, 4-digit SIC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 2 of SIC code, pollutant </para>
</listitem>
<listitem>
<para>Country/State code, 4-digit SIC code, pollutant </para>
</listitem>
<listitem>
<para>Country/State code, left 2 of SIC code, pollutant</para>
</listitem>
<listitem>
<para>4-digit SIC code, pollutant</para>
</listitem>
<listitem>
<para>Left 2 of SIC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, 4-digit SIC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 2 of SIC code</para>
</listitem>
<listitem>
<para>Country/State code, 4-digit SIC code</para>
</listitem>
<listitem>
<para>Country/State code, left 2 of SIC code</para>
</listitem>
<listitem>
<para>4-digit SIC code</para>
</listitem>
<listitem>
<para>Left 2 of SIC code</para>
</listitem>
<listitem>
<para>Country/State/County code, 8- or 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 6 or left 7 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 3 or left 4 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 1 or left 2 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, 8- or 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 6 or left 7 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 3 or left 4 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 1 or left 2 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>8- or 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 6 or left 7 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 3 or left 4 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 1 or left 2 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, 8- or 10-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 6 or left 7 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 3 or left 4 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 1 or left 2 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, 8- or 10-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 6 or left 7 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 3 or left 4 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 1 or left 2 of SCC code</para>
</listitem>
<listitem>
<para>8- or 10-digit SCC code</para>
</listitem>
<listitem>
<para>Left 6 or left 7 of SCC code</para>
</listitem>
<listitem>
<para>Left 3 or left 4 of SCC code</para>
</listitem>
<listitem>
<para>Left 1 or left 2 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code</para>
</listitem>
<listitem>
<para>Country/State code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code</para>
</listitem>
<listitem>
<para>Pollutant</para>
</listitem>
</orderedlist>
<para>On-road mobile and nonroad sources are matched to the control packet entries using the following hierarchy if the SCC length is less than 10 characters. As of SMOKE v4.0 the SCC character length may be up to 20 characters in length:(NOTE: this hierarchial approach is only for SCC less than or equal to 10 characters and SIC less than or equal to 4 characters)</para>
<orderedlist spacing="compact">
<listitem>
<para>Country/State/County code, 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 7 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 4 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, left 2 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, 10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 7 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 4 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code, left 2 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>10-digit SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 7 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 4 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Left 2 of SCC code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code, 10-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 7 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 4 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, left 2 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, 10-digit SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 7 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 4 of SCC code</para>
</listitem>
<listitem>
<para>Country/State code, left 2 of SCC code</para>
</listitem>
<listitem>
<para>10-digit SCC code</para>
</listitem>
<listitem>
<para>Left 7 of SCC code</para>
</listitem>
<listitem>
<para>Left 4 of SCC code</para>
</listitem>
<listitem>
<para>Left 2 of SCC code</para>
</listitem>
<listitem>
<para>Country/State/County code, pollutant</para>
</listitem>
<listitem>
<para>Country/State/County code</para>
</listitem>
<listitem>
<para>Country/State code, pollutant</para>
</listitem>
<listitem>
<para>Country/State code</para>
</listitem>
<listitem>
<para>Pollutant</para>
</listitem>
</orderedlist>
</section>
</section>
<section>
<title>Processing Order</title>
<para><command>Smkinven</command> must be executed before <command>Cntlmat</command>.</para>
<para><command>Cntlmat</command> must be executed before <command>Smkmerge</command>. <command>Cntlmat</command> also needs to be run prior to the <command>Grwinven</command> program, which requires at least one growth or control matrix to be run.</para>
<para><command>Cntlmat</command> is an optional program that needs to be run only when controlled emissions are needed for the AQM.</para>
</section>
<section>
<title>Files and Environment Variables</title>
<figure id="fig_programs_cntlmat">
<title><command>Cntlmat</command> input and output files</title>
<mediaobject>
<imageobject role="pdf">
<imagedata width="6.5in" fileref="images/programs/cntlmat_pdf.jpg" />
</imageobject>
<imageobject role="html">
<imagedata fileref="images/programs/cntlmat_html.jpg" />
</imageobject>
</mediaobject>
</figure>
<para><xref linkend="fig_programs_cntlmat" /> shows the input and output files for the <command>Cntlmat</command> program. The input files are the inventory file output from <command>Smkinven</command> (either <envar>AREA</envar>, <envar>MOBL</envar>, or <envar>PNTS</envar>), the control packets file (<envar>GCNTL</envar>), and the speciation profiles file (<envar>GSPRO</envar>) if there are reactivity controls (using the /REACTIVITY/ packet).</para>
<para>If the <envar>GCNTL</envar> file contains /MACT/, /CONTROL/ or /EMS_CONTROL/, /CTG/, and/or /ALLOWABLE/ packets, <command>Cntlmat</command> outputs a multiplicative control matrix file (<envar>ACMAT</envar>, <envar>MCMAT</envar>, or <envar>PCMAT</envar>), a report of multiplicative controls (<envar>ACREP</envar>, <envar>MCREP</envar>, or <envar>PCREP</envar>), and a report of all multiplicative controls applied to the inventory (<envar>ACSUMREP</envar>, <envar>MCSUMREP</envar>, or <envar>PCSUMREP</envar>). <command>Cntlmat</command> also outputs a warning file (<envar>ACTLWARN</envar>, <envar>MCTLWARN</envar>, or <envar>PCTLWARN</envar>) regardless of which packets are used.</para>
<para>If the <envar>GCNTL</envar> file contains a /PROJECTION/ packet, <command>Cntlmat</command> outputs a growth matrix file (<envar>APMAT</envar>, <envar>MPMAT</envar>, or <envar>PPMAT</envar>) and a growth report (<envar>APROJREP</envar>, <envar>MPROJREP</envar>, or <envar>PPROJREP</envar>).</para>
<para>If the <envar>GCNTL</envar> file contains a /REACTIVITY/ packet, <command>Cntlmat</command> outputs mole and mass-based reactivity matrix files (either <envar>ARMAT_L</envar> and <envar>ARMAT_S</envar>, <envar>MRMAT_L</envar> and <envar>MRMAT_S</envar>, or <envar>PRMAT_L</envar> and <envar>PRMAT_S</envar>), a reactivity matrix supplement file (<envar>ARSUP</envar>, <envar>MRSUP</envar>, or <envar>PRSUP</envar>), and a report of reactivity controls (<envar>AREACREP</envar>, <envar>MREACREP</envar>, or <envar>PREACREP</envar>). Finally, <command>Cntlmat</command> writes the <envar>LOGFILE</envar> detailing the program’s execution.</para>
<section>
<title>Input Files</title>
<informaltable>
<tgroup cols="3">
<colspec colwidth="20*" />
<colspec colwidth="18*" />
<colspec colwidth="62*" />
<thead>
<row>
<entry>File Name*</entry>
<entry>Format</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><envar>[AREA|MOBL|PNTS]</envar></entry>
<entry>SMOKE map</entry>
<entry>Intermediate inventory file produced by <command>Smkinven</command></entry>
</row>
<row>
<entry><envar>GCNTL</envar></entry>
<entry>ASCII</entry>
<entry>Control packets file</entry>
</row>
<row>
<entry><envar>GSPRO</envar> (optional)</entry>
<entry>ASCII</entry>
<entry>Speciation profiles file; only needed for reactivity controls</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>* As in <xref linkend="fig_programs_cntlmat" />, the notation <envar>[AREA|MOBL|PNTS]</envar> is used to indicate that only one of the three files is used for a given run.</para>
<para>The physical file name of the input file <envar>GCNTL</envar> file is typically overridden by the environment that is running <command>Cntlmat</command>. For example, when running SMOKE from scripts using the Assigns file, the projection factor inputs are available as the <envar>[A|M|P]PROJ</envar> files. So, for instance, the script must set <envar>GCNTL</envar> as <envar>APROJ</envar> (or area-source processing) after the Assigns file has been invoked by the script, but before the <command>Cntlmat</command> program is actually run.</para>
</section>
<section id="sect_programs_cntlmat_envar">
<title>Input Environment Variables</title>
<itemizedlist>
<listitem>
<para><envar>COMPARE_REPLACE_CONTROL:</envar> [default: Y]</para>
<para>Controls the way a replacement control is applied.</para>
<itemizedlist>
<listitem>
<para>Y: When set to Y, Cntlmat compares the overall percent reductions (CEFF * RPEN * REFF) from a replacement control in the CONTROL packet against existing percent reductions (either from the base inventory or from a just-applied /MACT/ packet). If the packet's reduction is more control (greater reduction) than the existing controls, then it is applied. Otherwise, it is not applied.</para>
</listitem>
<listitem>
<para>N: When set to N, Cntlmat applies replacement controls even if the control is less control than an existing control, which may result in an increase in emissions</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para><envar>FULLSCC_ONLY:</envar> [default: N]</para>
<para>Disables any sub-SCC cross-reference assignments that would otherwise be included in the cross-reference hierarchy. For example, the left-7, left-4, and left-2 levels of nonpoint and mobile SCCs would never be used. This is useful when zeros are a natural part of the SCC that the user does not want to assume are present for cross-reference hierarchy purposes. This option affects all Cntlmat input packets that use SCC assignments as part of their hierarchy.</para>
</listitem>
<listitem>
<para><envar>PROJECTION_YR_SPEC:</envar> [default: Y]</para>
<para>Sets whether or not entries in the /PROJECTION/ packet are in year-specific format.</para>
<itemizedlist>
<listitem>
<para>Y: Year-specific format in use</para>
</listitem>
<listitem>
<para>N: Year-specific format not in use</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para><envar>REACTIVITY_POL</envar>: [default: VOC]</para>
<para>Sets the pollutant name to use in computing the reactivity matrix.</para>
</listitem>
<listitem>
<para><envar>REPORT_DEFAULTS</envar>: [default: Y]</para>
<para>Defines whether or not the program reports when a source uses the default cross-reference.</para>
<itemizedlist>
<listitem>
<para>Y: List sources in the log file when they use default cross-reference</para>
</listitem>
<listitem>
<para>N: Do not list sources that use the default cross-reference</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para><envar>SMK_AVEDAY_YN</envar>: [default: N]</para>
<para>Indicates whether or not to read average day emissions instead of annual emissions from the inventory file.</para>
<itemizedlist>
<listitem>
<para>Y: Read average day emissions</para>
</listitem>
<listitem>
<para>N: Do not read average day emissions, use annual emissions instead</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para><envar>SMK_SOURCE</envar>: [default: blank]</para>
<para>Defines the type of sources to be processed. Valid values are</para>
<itemizedlist>
<listitem>
<para>A: Area processing</para>
</listitem>
<listitem>
<para>B: Biogenic processing</para>
</listitem>
<listitem>
<para>M: Mobile processing</para>
</listitem>
<listitem>
<para>P: Point processing</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para><envar>SMK_TMPDIR</envar>: [default: <quote>.</quote>]</para>
<para>Sets the path for writing the temporary files needed when processing the /ALLOWABLE/, /CONTROL/, /CTG/, /EMS_CONTROL/, /MACT/, and/or /PROJECTION/ packets (from the <envar>GCNTL</envar> file).</para>
</listitem>
<listitem>
<para><envar>SPEC_OUTPUT</envar>: [default: ALL]</para>
<para>Defines the types of speciation outputs to create.</para>
<itemizedlist>
<listitem>
<para>MASS: Output speciation matrix based on mass</para>
</listitem>
<listitem>
<para>MOLE: Output speciation matrix based on moles</para>
</listitem>
<listitem>
<para>ALL: Output both mass and mole speciation matrices</para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
<para><envar>XREF_SICOVERSCC</envar>: [default: Y]</para>
<para>Determines how to deal with packet entries that have both an SCC and SIC</para>
<itemizedlist>
<listitem>
<para>Y: Match sources by SIC before SCC</para>
</listitem>
<listitem>
<para>N: Match sources by SCC before SIC</para>
</listitem>
</itemizedlist>
</listitem>
</itemizedlist>
</section>
<section>
<title>Output Files</title>
<informaltable>
<tgroup cols="3">
<colspec colwidth="20*" />
<colspec colwidth="18*" />
<colspec colwidth="62*" />
<thead>
<row>
<entry>File Name*</entry>
<entry>Format</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><envar>[A|M|P]CMAT</envar></entry>
<entry>I/O API NetCDF</entry>
<entry>Multiplicative control matrix</entry>
</row>
<row>
<entry><envar>[A|M|P]CREP</envar></entry>
<entry>ASCII</entry>
<entry>Report of multiplicative controls applied to the inventory</entry>
</row>
<row>
<entry><envar>[A|M|P]CREP2</envar></entry>
<entry>ASCII</entry>
<entry>Detailed before-and-after report of application of the /CONTROL/ packet only, which includes any comments appended to the end of the /CONTROL/ packet entries. These comments can describe the controls being applied with each packet row. This report then includes the base and future overall percent reductions on a source-by-source basis, and includes the CONTROL packet line-specific comments.</entry>
</row>
<row>
<entry><envar>[A|M|P]CSUMREP</envar></entry>
<entry>ASCII</entry>
<entry>Report of all controls applied to the inventory, with all controls listed under each source</entry>
</row>
<row>
<entry><envar>[A|M|P]CTLWARN</envar></entry>
<entry>ASCII</entry>
<entry>List of warnings</entry>
</row>
<row>
<entry><envar>[A|M|P]PMAT</envar></entry>
<entry>I/O API NetCDF</entry>
<entry>Growth matrix</entry>
</row>
<row>
<entry><envar>[A|M|P]PROJREP</envar></entry>
<entry>ASCII</entry>
<entry>Report of growth factors applied to the inventory</entry>
</row>
<row>
<entry><envar>[A|M|P]REACREP</envar></entry>
<entry>ASCII</entry>
<entry>Report of reactivity controls applied to the inventory</entry>
</row>
<row>
<entry><envar>[A|M|P]RMAT_L</envar></entry>
<entry>I/O API NetCDF</entry>
<entry>Mole-based reactivity matrix</entry>
</row>
<row>
<entry><envar>[A|M|P]RMAT_S</envar></entry>
<entry>I/O API NetCDF</entry>
<entry>Mass-based reactivity matrix</entry>
</row>
<row>
<entry><envar>[A|M|P]RSUP</envar></entry>
<entry>ASCII</entry>
<entry>Reactivity matrix supplemental file</entry>
</row>
<row>
<entry><envar>LOGFILE</envar></entry>
<entry>ASCII</entry>
<entry>Log generated from executing <command>Cntlmat</command></entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>* As in <xref linkend="fig_programs_cntlmat" />, the notation <envar>[A|M|P]</envar> is used to indicate that only one of the three files is output for a given run.</para>
</section>
</section>
<!--
<section>
<title>Earlier Versions</title>
<para>The SMOKE prototype used separate programs for each type of source. These programs were CTLAMAT for area sources and CTLPMAT for point sources. A version of the control/growth program was not previously available for mobile sources.</para>
<para><command>Cntlmat</command> for SMOKE v1.2 did not have an operational reporting capability. The /MACT/ packet and updated /CONTROL/ and /PROJECTION/ packets were added in SMOKE v2.0.</para>
<para><command>Cntlmat</command> for SMOKE v2.3 supports passing through updated control efficiencies, rule penetrations, and rule effectiveness values to the output intermediate files. These can be subsequently used by Grwinven to include in the output SMOKE inventories created by that program.</para>
<para><command>Cntlmat</command> for SMOKE v2.3 now includes the COMPARE_REPLACE_CONTROL setting for controlling how Replacement controls are implemented (see above)<para>
<para><command>Cntlmat</command> for SMOKE v2.3 has added <envar>[A|M|P]CREP2</envar> report to provide more detailed reporting on controls actually applied to the inventory records.</envar>
</section>
-->
</section>
<section id="sect_programs_elevpoint">
<title><command>Elevpoint</command></title>
<section>
<title>Description</title>
<para><emphasis>Processing categories:</emphasis> point</para>
<para>The <command>Elevpoint</command> program is used to select elevated point sources and to prepare certain input files for special elevated source or PinG processing. <command>Elevpoint</command> selects the major point source (MPS) and major elevated point source emissions (MEPSE) records using a variety of criteria, such as stack parameters, emissions, and analytical plume rise calculations. (Note that MEPSE is another name for a PinG source.)</para>
<para><command>Elevpoint</command> distinguishes PinG sources from non-PinG elevated sources based on emission thresholds, highest day-specific emissions rank compared to other sources, analytical plume rise, and/or stack parameters such as height. <command>Elevpoint</command> flags sources as either elevated or PinG based on instructions given in an input configuration file, the <envar>PELVCONFIG</envar> file. <command>Elevpoint</command> also permits grouping of stacks at the same facility if the stack parameters are similar, within tolerances you specify with the <envar>PELVCONFIG</envar> file; the result is call a <quote>stack group</quote>. For more information on selecting and grouping elevated and PinG sources, refer to <xref linkend="sect_input_pelvconfig" />.</para>
<para><command>Elevpoint</command> can also be used to calculate plume rise using the <quote>cutoff</quote> method. This is the method traditionally used to prepare input files to the air quality models UAM-IV, UAM-V and CAM<subscript>X</subscript>, which require a separate model-ready input file containing emissions for elevated point sources. Below, we refer to this path as the <quote>UAM style</quote> of emissions processing.</para>
<para>For the cutoff method, the <command>Elevpoint</command> program uses the stack parameters of the point sources and estimates the plume rise for each source using a Briggs analytical solution (but not actual gridded meteorology data); the details of this process are given in <xref linkend="sect_programs_elevpoint_briggs" />. <command>Elevpoint</command> then records all of the sources that have an estimated plume rise greater than a specified cutoff as defined in the <envar>PELVCONFIG</envar> file using the <quote>RISE</quote> instruction. Using the <envar>PELVCONFIG</envar> file, this cutoff method can be combined with selection of elevated sources based on stack parameters and/or emissions values.</para>
<para>When emissions values are part of these selection criteria, <command>Elevpoint</command> computes the maximum daily emissions using one or more <envar>PTMP</envar> files. <command>Elevpoint</command> computes the maximum daily value of any pollutant used as a selection criterion across all of the days that you input. You have the option of providing either a list of paths and file names of one or more <envar>PTMP</envar> files, or a single <envar>PTMP</envar> file. The day or days that <command>Elevpoint</command> uses to compute each source’s maximum depends on the time zone in which the source resides, based on the county and the <envar>COSTCY</envar> file setting for the time zone (the time zone is stored in the <envar>PNTS</envar> file output from <command>Smkinven</command>). When using emissions values as a selection criterion, <command>Elevpoint</command> only considers sources that are within the grid domain.</para>