mmb-carb / esta Goto Github PK

Right now there is a hard-coded mapping from month to season, but users are asking for more flexibility so that seasons can also depend on the region code.

To make this, more complete, mapping it will have to be moved to an input file.

It would be nice to add user functionality for the output file name to add the speciation profile used when creating netCDF output?.
For example, the current default name is:

st_4k.mv.v0220..2013.2013365..e14..ncf.gz
If we used 2013 speciation gsref with vintage 11jan17, it would be nice to be able to keep track of this in the file name to have :

st_4k.mv.v0220..2013.2013365..e14.gsref_13_11jan17.ncf.gz

Upgrade the SMOKE spatial surrogate version to the most recent SMOKE 4.x. The major difference here is the second column should have something more like "06003" as opposed to something like "0SC0060300SC". This will simplify the input information needed for the ESTA model significantly.

What happens if we delete an arbitrary line from the eic_info.py file? Can the program keep running? (Probably not.) So, does ESTA fail with any helpful error message?

Do we want the model to use magical defaults if an EIC is missing? Or do we want it to drop the emissions related to unknown EICs? Should warning messages get thrown to the screen, or should the model fail?

What would be the best possible behaviour?

We are using the CalTrans trucking network as our linehaul spatial surrogate. Are there future years available for this network? If so, we should grab those to make future-year versions of that surrogate.

It would be worth researching.

Users may want DPM in their NetCDF files for toxics studies.

The PMEDS output format (based on the MEDS format) has proven too restrictive. In particular, it does not allow for the California 1km modeling domain. As such, it is time to remove support for the PMEDS format, in favour of a headerless CSV-like format.

Just adding a single loop could make it a lot easier to run a series of ESTA jobs in series.

They would be totally separate ESTA runs. If users want parallel ESTA runs, there will be system-dependent load-balancing issues and they can handle that themselves.

Why do we have this file? can we replace it or create it on the fly?

I think the class name CalvadSmoke4SpatialSurrogateLoader is no longer accurate. This class should probably be renamed to just SmokeSpatialSurrogateLoader.

I believe ESTA should already be able to process toxics. You just need to provide it different GSPRO/GSREF files. BUT, is that the case?

We should try it and find out!

Is there anything to do here? Or will our handling of EMFAC2014 files be fine?

Update the documentation for the two new input CSVs (NOx-by-GAI and season-by-GAI).

The eic_info.py file has a single dictionary with EICs as keys, and three columns of data as values. The question is: do we still need that first column? e.g.

71073411000000: (0, 'vmt', 1.0),     # ('LDA', 'CAT', 'RUNEX')

That first column 0 is a relic of the DTIM link files. However, now it is tied into the CALVAD_VEHICLE types in some strange way. But that is all certainly unnecessary and complicated. So it needs to be removed.

Patch for CALVAD spatial surrogates pending the following updates:

• Estimation of missing gridded VMT values along bay area bridges and along i-10 in Riverside/San Bernardino areas based on neighboring grid cells.
• Estimation of missing gridded VMT values for the local road network based on county median/mean values at given time interval.
• Converting from gridded shapefiles to polyline or “link” level by intersection with primary and local road networks (TIGER).
• Merging of primary and secondary Tiger network with CALVAD data (80/20 split) to form one lumped, time-resolved spatial surrogate.

There are some lingering examples of run configs and code that was original used to test ESTA against DTIM for on-road. These tests are quite old, unsupported, and only partially functioning. It is time to remove them and make the simple examples for new users easier to follow.

Would it be nicer if we had full examples of ESTA run on different grids? Perhaps a SCAQMD and BAAQMD example, with their own surrogates?

Currently, the Heavy-Duty diesel NOx fractions are given by year, but the defaults aren't. It would be better if the defaults also varied by year.

We currently use Calvad for ITN/VMT spatial surrogates. We should try ITN, to support future years and different grids.