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

Feature Request: Modifications to Python Notebooks #6

Open
muntasers opened this issue May 31, 2023 · 0 comments
Open

Feature Request: Modifications to Python Notebooks #6

muntasers opened this issue May 31, 2023 · 0 comments

Comments

@muntasers
Copy link

Following are a list of suggested changes to the Python Nways materials as suggested by Robert Searles and Jonathan Dursi

JIT kernels
• Can we move this before CUDA kernels?
• Maybe add Numba Vectorize as an introduction? the following flow: Vectorize -> JIT -> CuPy CUDA makes more sense than CuPy CUDA -> JIT
• In fact, is the order of cupy then numba the right way to go? Can we flip those sections?

Numba notebook:

Exercise 1
• Again, exercise is too easy; students will just copy and paste. Could we make them change it to float, and multiply? Or some slightly deeper change?

Thread re-use - this comes out of nowhere

Matrix multiply:
• Same idea, could we do a naïve matrix transpose instead?

Numba vectorize/ufuncs
• This seems out of place. It doesn't make sense to me to have this come before Numba CUDA kernels and interrupting the flow between numba cuda kernels and atomics

Atomic
• It would be nice if the atomic example for a reduction built on an earlier example, say calculating average matrix element after the multiplication or something

@muntasers muntasers changed the title Modifications to Python Notebooks Feature Request: Modifications to Python Notebooks May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant