Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

environment file for binderized examples #3563

Closed
dcherian opened this issue Nov 22, 2019 · 6 comments · Fixed by #3568
Closed

environment file for binderized examples #3563

dcherian opened this issue Nov 22, 2019 · 6 comments · Fixed by #3568

Comments

@dcherian
Copy link
Contributor

Our examples now have binder links! e.g. https://xarray.pydata.org/en/latest/examples/ERA5-GRIB-example.html

but this is suboptimal because we aren't defining an environment so the only things that get installed are the packages that xarray requires : numpy & pandas. We need to at least add cfgrid, matplotlib, cftime, netCDF4 to get all the examples to work out of the box.

@ocefpaf
Copy link
Contributor

ocefpaf commented Nov 22, 2019

@dcherian it is very experimental but nbrr can probably help you setup the environment.yaml file with a single command.

@scottyhq
Copy link
Contributor

Awesome @dcherian ! I like the approach of defining a binder environment then pulling the examples directory into the binder session with nbgitpuller. There are options for where to store the binder environment config (1) master branch .binder, 2) a new branch called 'binder', or 3) even a separate repo... maybe pydata/xarray-binder-env - see https://github.com/scottyhq/repo2docker-githubci ?

@max-sixty
Copy link
Collaborator

Not in reference to this exact issue, but the binder functionality is really awesome! Well done!

@mrocklin
Copy link
Contributor

You're probably already aware, but https://examples.dask.org and https://github.com/dask/dask-examples might be a nice model to look at.

@dcherian
Copy link
Contributor Author

Thanks all. Now we just need some one to volunteer to do this :)

@jhamman
Copy link
Member

jhamman commented Nov 25, 2019

See #3568 for a basic environment that should do the trick. Going forward, I think it would be nice to split these out into a separate repo. Let's save that for #2378.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants