Organization about dask-examples HOT 18 CLOSED

I think that would be a very good start. Are you thinking about migrating notebooks from dask-tutorial or old-dask-example? It might be confusing to a new user to see 3 repos with examples and tutorials(It definitely confused me)

from dask-examples.

I'm not sure, what do you think would be best?

If we did move things from other other repositories we would want to update and clean them up for the expected runtime environment of this repository: https://github.com/dask/dask-examples#contributing

from dask-examples.

I think at a minimum old-dask-example should be retired and the content migrated to dask-examples where applicable. As for the dask-tutorial I'm not sure.

from dask-examples.

I think it'd be great to move over the content that still makes sense. A lot of those notebooks were made a few years ago and may no longer be the best ways of doing things. They also may not be easily runnable, I'm not sure. I'm all in favor of moving things over, I just want to make sure that people actively look at the content they're moving and make judgments on it.

How would you recommend retiring the old repository?

from dask-examples.

Well I think I would go notebook by notebook and migrate over any content that is relevant/useful. Then add DEPRECATED to repo description and at the top of the README. Optionally then if you want then we could remove notebooks from that repo as they are migrated.

from dask-examples.

from dask-examples.

I will get started on this over the weekend then. Once the CI code is merged it should make checking them easy :)

from dask-examples.

@mrocklin from my initial read through and comparison it looks like this repo has most of the same content. The only difference is the sample projects that looked at nyc taxi data or github. I would say we should start over on example products. Thoughts?

from dask-examples.

from dask-examples.

@mrocklin and @mholtzscher what are some of your thoughts on the way HoloViews organized their examples? They have notebooks inside a examples directory with subdirectories.

In addition, how do we feel about using evaluated notebooks with tools like nbsphinx?

from dask-examples.

@mrocklin I meant to say "projects" not "products." :)

@kvn219 I think that is very close to the goal we have discussed so far. I think There will be some notebooks at high level that are the basics and then folders of more advanced notebooks

from dask-examples.

In addition, how do we feel about using evaluated notebooks with tools like nbsphinx?

@kvn219 I can see how that would be valuable. Is there an easy way to roll this into the core dask documentation?

from dask-examples.

I recommend that we have a small number of notebooks at the top level, showing an introduction for each topic like arrays, dataframes, delayed, ML, ..., and also a directory for topics that have many additional notebooks.

@stsievert, you're now actually buidling more notebooks for machine learning. Thoughts on this organization?

from dask-examples.

showing an introduction for each topic ... and also a directory for topics that have many additional notebooks. ... Thoughts on this organization?

That's the organization I've wanted. I've almost done it, but have instead been prefixing with machine-learning- when I've wanted a directory machine-learning/.

from dask-examples.

Though right now it is clear visual separation between extraneous files and examples: all the extra files are in directories, and only the examples are plain files (besides a .travis.yml and README.md).

from dask-examples.

I've hidden all of the extraneous directories in #17

I'm still inclined to group notebooks into directories

from dask-examples.

Is there still things to do here? Should we close it once #41 is merged?

Should we close #13 without merging it?

from dask-examples.

Looks like everything has been done here.

from dask-examples.