-
-
Notifications
You must be signed in to change notification settings - Fork 608
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
Add WIP docstrings to CPU and GPU #1632
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
bors r+ |
1632: Add WIP docstrings to CPU and GPU r=DhairyaLGandhi a=logankilpatrick We could surely use more details, but ideally we would want to document these functions and what they do + usage. Co-authored-by: Logan Kilpatrick <23kilpatrick23@gmail.com> Co-authored-by: Dhairya Gandhi <dhairya@juliacomputing.com>
Canceled. |
bors r- Just wanted to get an opinion on whether to include details about needing a CUDA compatible GPU atm. Also, good to add an example for each, ideally with a simple model. |
Given #1566, I don't think it's necessary to include details about GPU compat for CUDA specifically. |
Would a simple example like: julia> m = Dense(10, 5)
Dense(10, 5)
julia> cpu(m)
Dense(10, 5) work? |
That'd work, i would also show that the types of arrays have changed to a |
I don't have an Nvidia GPU, can you add that example? |
Done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some suggestions to make it clearer and a forward link to @functor
so people aren't confused when they custom layer won't transfer.
Co-authored-by: Kyle Daruwalla <daruwalla.k.public@icloud.com>
Co-authored-by: Kyle Daruwalla <daruwalla.k.public@icloud.com>
I tried to address the comments, please let me know if more needs to be updated! |
bors r+ |
Build succeeded: |
We could surely use more details, but ideally we would want to document these functions and what they do + usage.