Closed ibarraespinosa closed 6 years ago
Can be a god idea, GridEmissions or GridedEmissions !
Currently the wrf_put don't care about what is the input, just send the values directly to a ncdf4 function (which can return errors in some cases). The to_wrf (old wrf_emission) just expand the wrf_put concept to make some writing fast (to use and computationally), but it can be used to a create a simple way to open a vein output and make the emissions (some like the emis-wrf from vein)
I as thinking and EmissionFlux could be better. Gridemissions or GriddedEmissions can be temporally static, as a plane. However, EmissionFlux already has the idea of time because it is a flux.
I think that adding this function as an option in vein::emis_grid could work, but defining the array with its class in here, in eixport. I will test a simple Array, a RasterBrick and a stars object. I want to take out all raster dependencies in VEIN btw
This function should connect with to_wrf to write the wrfchemi
done by vein::GriddedEmissionsArray
.
vein::EmissionsArray
is class of Array with dimensions streets x number of vehicles x hours x days.When working with emissions inputs for air quality models, a required format is an Array with dimensions: LAT x LONG x VERTICAL LEVEL x TIMES.
It would be good create a class that converts
vein::EmissionsArray
and other type of objects into this new class, which could be EmissionsModel or EmissionsFlux in order to accomplish the required dimensions.This class could be SC3 or eventually SC4. It would be a good ideia to take a look into Spatiotemporal tidy arrays for R stars