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

GPU docs #2510

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from
Draft

GPU docs #2510

wants to merge 2 commits into from

Conversation

mcabbott
Copy link
Member

@mcabbott mcabbott commented Oct 30, 2024

This re-writes the start of the GPU documentation page. It aims to use simpler examples, and stress that model |> cu just works, before talking about more exotic non-CUDA packages, and the automatic model |> gpu.

Rendered MD: https://github.com/FluxML/Flux.jl/blob/gpu_docs/docs/src/guide/gpu.md

Current docs: http://fluxml.ai/Flux.jl/stable/guide/gpu/

Copy link
Contributor

github-actions bot commented Oct 30, 2024

Once the build has completed, you can preview any updated documentation at this URL: https://fluxml.ai/Flux.jl/previews/PR2510/ in ~20 minutes

In particular, this page: https://fluxml.ai/Flux.jl/previews/PR2510/guide/gpu/

Copy link

codecov bot commented Oct 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 33.20%. Comparing base (32db5d4) to head (d9c03b9).
Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2510   +/-   ##
=======================================
  Coverage   33.20%   33.20%           
=======================================
  Files          31       31           
  Lines        1843     1843           
=======================================
  Hits          612      612           
  Misses       1231     1231           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mcabbott mcabbott added this to the v0.15 milestone Nov 6, 2024
@CarloLucibello CarloLucibello removed this from the v0.15 milestone Nov 16, 2024
@CarloLucibello
Copy link
Member

removing the milestone as this shouldn't be blocking

@mcabbott
Copy link
Member Author

The point is, in part, to think through whatever interface we're adopting by trying to explain it clearly. If it's a mess then 0.15 is when to fix it. That's why it was on the milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants