Brief Instructions/Information For Creating 2016fg/2028fg/PSAT SMAT Input files
--------------------------------------------------------------------------------

1) Make sure the desired model species names are correct in the fortran 'model2smatPM' code and compile for executable.
    - typically between lines 280 and 300, look for the code block beginning with "if(VNAME(V).EQ.'PM25_NO3') then"
    - for the 2016fg and 2028fg non-PSAT runs, EPA wanted to compare SMAT using PM25_OC and PM25_OM
    
2) These 'model2smatPM' fortran programs are already set up for 2016 leapyear base year, but for non-leap base years, 
   the relevant code section is found near the very end of the program
    - look for the two 'nday(2) = ' lines around lines 610-613
    
3) The model species names and leap year on/off are really the only things to check/modify in the fortran program before compiling.

4) The multiple versions of the fortran code for non-psat and bulk are only slightly different, simple unix 'diff' command will show.

5) The PSAT tag versions of the fortran code include slight modifications in order to read in and add the P and S elements of OC.

6) The csh job scripts setup the model, grid cell and other inputs and settings, then calls the fortran executable to make the SMAT input files.
    - However, the 'fg' work required some nuanced csh syntax to setup everything efficiently using the fewest number of scripts.
    
7) The QC programs are examples of SAS jobs to pull out some basic stats/metrics for each PM species to check for number of observations,
   missing values, data ranges, but other statistical methods/programs could do the same thing.
   
8) Lastly, there are 2 other SAS programs provided that were used to make baseline minus tag files in that same SMAT input format.


- Darrell Ensley, GDIT, 04/13/2020
  ensley.darrell@epa.gov