Skip to content

Treat Dask and other libs in the Scientific Libraries lecture? #57

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.

Sign up for GitHub

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

Jump to bottom
Open
jstac opened this issue May 28, 2019 · 8 comments
Open

Treat Dask and other libs in the Scientific Libraries lecture? #57

jstac opened this issue May 28, 2019 · 8 comments

Comments

@jstac
Copy link
Contributor

jstac commented May 28, 2019

Should dask be treated in this lecture: https://lectures.quantecon.org/py/sci_libs.html ?

Any other libraries we're not treating but should at least mention? Jax?

I'm rehashing this question from Slack, where @AakashGfude says: dask is awesome and easy to use. I think we can. It has got a lot of traction as well, with 4.9k stars in github.

@mmcky @shizejin @QBatista @cc7768

Any library we treat needs an application to illustrate it. Thanks in advance for your thoughts!
@jstac jstac changed the title Treate Dask and other libs in the Scientific Libraries lecture? Treat Dask and other libs in the Scientific Libraries lecture? May 30, 2019
@mmcky
Copy link
Contributor

mmcky commented Jun 12, 2019

I would vote for a dask lecture for sure! I think it would be a really fun lecture ... happy to help with this once the new build pathway is up and running etc.

@mmcky
Copy link
Contributor

mmcky commented Jul 19, 2019 •
edited
Loading

Another library to consider would be xarray. I haven't used it much myself but it would be nice to take a closer look as it is becoming a more important foundational library.

http://xarray.pydata.org/en/stable/#

@jstac
Copy link
Contributor Author

jstac commented Jul 19, 2019

Sounds good. We just need use cases, I guess.

@jstac
Copy link
Contributor Author

jstac commented Aug 13, 2019

Perhaps we should drop Cython from this lecture and just recommend that our users stick to Numba.

It's caused execution errors on various machines and it's probably worse on Windows (for our users).

@mmcky
Copy link
Contributor

mmcky commented Aug 13, 2019

hey @jstac I think this is a good idea, particularly given a large number of users are on windows. This is an excellent point and not well tested.

@mmcky
Copy link
Contributor

mmcky commented Sep 9, 2019

This might be useful in the future (as it is currently in active development)

@duncanhobbs
Copy link

Dask is used in this QuantEcon Notes example to compute proximity matrices.

It might be possible to use Dask to import the HS trade data and do some of the dataframe manipulations beforehand (currently done with Pandas) as well.

@jstac
Copy link
Contributor Author

jstac commented Sep 12, 2019

Thanks @duncanhobbs --- this could be a good example.

@Harveyt47 Harveyt47 transferred this issue from QuantEcon/lecture-source-py Apr 23, 2020
@mmcky mmcky transferred this issue from QuantEcon/lecture-python-website Jun 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jstac @mmcky @duncanhobbs