Trim WRF domain edges

[nicolejkeeney]

Summary of changes and related issue

WRF domain was trimmed by 10 grid cells for every resolution.

Relevant motivation and context

WRF output needs to be trimmed, because data at the domain edges has weird numerical stuff going on and it takes some time to “relax” onto the domain’s grid.

Per an email conversation with Stefan: we recommend trimming ~10 grid points from the right, left, top, and bottom edges of each domain (d03, d02, and d01). Ideally there will be some investigation for the amount of trimming; this is our best guess right now.

This is what the code does, for 9 km resolution... you can see the untrimmed WRF data (blue) behind the trimmed WRF grid (coolwarm cmap data on top):

WE NEED TO UPDATE THE GUIDANCE BUT I DON'T THINK I'M THE RIGHT PERSON TO DO THAT

How to test

Try retrieving WRF data for the entire domain using climakitae. Make sure it works... and, just review the code using the diff comparison feature.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• None of the above

To-Do

• Unit tests
  • Existing unit tests are passing
  • If relevant, new unit tests are written (required 80% unit test coverage)
• Documentation
  • Intent of all functions included
  • Complex code commented
  • Functions include NumPy style docstrings
• Naming conventions followed
  • Helper functions hidden with _ before the name
• Any notebooks known to utilize the affected functions are still working
• Black formatting has been utilized
• Tagged/notified 2 reviewers for this PR

[vicford]

Tested on monthly 45km data:

• Confirmed that the x, y dimensions were trimmed appropriately
• Confirmed that visualization also showed a trimmed domain

[elehmer]

Works for me as well

[bethem]

lgtm, thanks!