Ecosystem section

[TomNicholas]

Intended to fill part of the Ecosystem section of the xarray scipy tutorial, so addressing #116.

Planning to have a short bit of material on each of these topics:

• Flexibility of xarray
• Accessors as a concept
• hvplot accessor
• Rioxarray
• cf-xarray
• pint-xarray
• defining your own accessors
• Wider xarray ecosystem

Currently a work-in-progress.

@dcherian @scottyhq I'm planning to try and write the hvplot, pint-xarray, and possibly cf-xarray sections now, but I'm really not at all familiar with rioxarray (I've never even imported it 😅). I'm happy to present all this content in person on the day, but I think it would be much quicker if one of you guys added the section on rioxarray.

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[scottyhq]

Thanks for doing this @TomNicholas !

I'm happy to present all this content in person on the day, but I think it would be much quicker if one of you guys added the section on rioxarray.

Sounds good. Feel free to leave a blank cell and I'll follow up after this is merged with a tiny example.

[TomNicholas]

I think this is basically ready to merge, just the rioxarray section missing (plus how did you get your exercises to be in drop-down boxes?)

[scottyhq]

plus how did you get your exercises to be in drop-down boxes?

would be good to normalize exercise formatting across notebooks (#88), for now if you want a dropdown on the rendered version you add hide-input or hide-output metadata tags https://jupyterbook.org/en/stable/content/metadata.html

[scottyhq]

looks great @TomNicholas, just need to import xarray as xr at the top! feel free to merge if you're happy with it

[TomNicholas]

Okay great @scottyhq - I've added an import xarray as xr at the top, so I think we should just merge this content now and fix minor formatting gripes later.

[TomNicholas]

Should I be worried about the build-and-deploy test failing?

[scottyhq]

Oh, right, you can see the traceback in the 'Dump build logs' step:

nbclient.exceptions.CellExecutionError: An error occurred while executing the following cell:
[25](https://github.com/xarray-contrib/xarray-tutorial/runs/7256684119?check_suite_focus=true#step:6:26)
------------------
[26](https://github.com/xarray-contrib/xarray-tutorial/runs/7256684119?check_suite_focus=true#step:6:27)
d + t

If you add a raises-exception tag to that cell, jupyterbook knows the error is anticipated and will execute subsequent cells https://jupyterbook.org/en/stable/content/execute.html#dealing-with-code-that-raises-errors

@dcherian what do you think of adding a branch protection rule to require that test to pass before merging? i don't have that admin access it seems

[dcherian]

what do you think of adding a branch protection rule to require that test to pass before merging? i don't have that admin access it seems

Just enabled!

[keewis]

Line #2.    import cf_xarray.units  # must be imported before pint_xarray

the import order is not important anymore with recent versions of pint, so you should probably remove the comment

Reply via ReviewNB

[scottyhq]

sorry @keewis i remember you pointed that out before. i removed the comment in #128