gutmann
commented
7 years ago locality option should be able to specify how many days on either side of the current day should be included (at least for analog options, that gets really difficult with pure_regression)
Many downscaling methods operate independently for each month of the year to help preserve the seasonal cycle.
This can be done in GARD by downscaling separately for each month, but this requires substantial pre-processing of input data (separating monthly data for independent GARD runs and stitching back together in the end)
It is relatively simple to add a “day of the year” variable to the input files, and use that (in any of the analog schemes anyway). To be able to wrap around the year it could be two variables (equivalent to “u” and “v” for wind direction with a unit length). That way days that are far away (in day of year) would have to be very similar for all other variables, while days that are close in day of year would be given more flexibility. It is a little awkward, but might help… It probably will not help the pure regression mode though.
Alternatively it would be nice to add a Day-Of-Year localization option in GARD.
For the pure regression mode this would be tricky, and require GARD to either call downscale_point ~12 (or whatever) times after subsetting the data appropriately each time, then stitching it back internally.
For the analog MODES, it should be possible for GARD to simply have an option (in select_analogs) to take time data and enforce that DoY be within X-days for any analogs selected. This part would be "easy"