Currently, data being requested through ExtData is automatically regridded to the resolution of the requesting component. This is great, but limits the possibility for (e.g.) calculation of online emissions at a consistent source resolution. We would like to run HEMCO as a gridded component operating on a different grid than (e.g.) GEOS-Chem, so that emissions calculations can be performed at a single, consistent resolution. While we could implement HEMCO as a gridded component on its own grid, there is not currently a standard method to have one gridded component (e.g. GEOS-Chem) request data from another gridded component (e.g. HEMCO) on disparate grids. It would be a huge help if imports/exports could automatically use the existing regridding machinery (including selection of regridding method).
Agreed that this is desirable. I defer to Atanas as to how much work this is in the short-term. Once we go to MAPL 3 we should more easily be able to support NUOPC type functionality such as this.
Currently, data being requested through ExtData is automatically regridded to the resolution of the requesting component. This is great, but limits the possibility for (e.g.) calculation of online emissions at a consistent source resolution. We would like to run HEMCO as a gridded component operating on a different grid than (e.g.) GEOS-Chem, so that emissions calculations can be performed at a single, consistent resolution. While we could implement HEMCO as a gridded component on its own grid, there is not currently a standard method to have one gridded component (e.g. GEOS-Chem) request data from another gridded component (e.g. HEMCO) on disparate grids. It would be a huge help if imports/exports could automatically use the existing regridding machinery (including selection of regridding method).