Diana Gergel

@tbohn that one didn't address this - because that PR was for gridcell-averaged albedo - so spatially rather than temporally averaged

For additional reference, here are timing tables from the RI hourly and RBR 5 day runs: RI hourly: ```------------------------------ VIC TIMING PROFILE ------------------------------ Date : Mon Aug 28 15:59:00 2017...

@bartnijssen we generate these with VIC. @jhamman noticed that there are some missing timers in `cesm_interface_c.c`, which is likely the cause of the zeros. Here is a comparable timing table...

Yes, just double checked that that run had frozen soils, `CLOSE_ENERGY`, and `FULL_ENERGY` all set to `True`. And 50 nodes. But, it was running 3-hourly, not hourly as the RI...

@bartnijssen I don't think that the culprit is reading from/to a statefile, since we fixed exact restarts a while back in the image driver. I think what we're dealing with...

@jhamman a question from the criteria you listed: would `xESMF` fall under the category of adding too many dependencies, or would you be open to it being used? The spatial...

@jhamman fair enough. By adding xESMF to the doc build, do you mean a recipe for using xESMF as an intermediate step external to the workflow, or something beyond that?...

@jhamman what I had meant in my second option was that I was directly using source code from xesmf to apply regridding weights on dask workers, as I'd had trouble...

Circling back on this - what I have in mind is a recipe like this: 1. compute multi-decade daily climatologies of ERA-5 at obs-res and coarsen it to model-res ++...

I've been putting some thought into how best to implement QDM in scikit-downscale - which I'm hoping to do over the next few weeks - and it would be great...