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

Location of conv #11

Open
MikeInnes opened this issue Dec 14, 2017 · 0 comments
Open

Location of conv #11

MikeInnes opened this issue Dec 14, 2017 · 0 comments

Comments

@MikeInnes
Copy link
Contributor

MikeInnes commented Dec 14, 2017

Although it's great to have ML-specific functionality held separately from base CuArrays in this package, I'm wondering if we should keep convolutions in CuArrays itself (effectively making it part of the standard library). Image processing is a big use case for GPUs, and it'd be particularly nice if CuArrays and ImageFiltering.jl worked out of the box together.

This wouldn't imply any hard dependency on CUDNN for CuArrays, only the soft dep that we already have (and we could have slower backup kernels when CUDNN isn't available).

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