cucim
cucim copied to clipboard
[DOC] Add link to docs page in README
Would be helpful for people getting started to have a link to the docs from the README
cc @jlefman @gigony @quasiben
Thanks @jakirkham for creating this issue!
Also would be useful to add some links for using CuPy, such as:
- Some examples of how to do asynchronous transfers (async memcpy).
- There needs to be more guidance or links on how do you read multiple files and stream that data to be processed as you're reading it. The kind of workflow that comes up over and over again.
- Basics of CuPy — CuPy 10.0.0 documentation
- Performance Best Practices — CuPy 10.0.0 documentation
- Memory Management — CuPy 10.0.0 documentation
Yeah we need to think a bit about what lives in the docs here vs. in CuPy. Not sure what the right answer is.
Perhaps a good next step would be a corresponding issue raised with CuPy highlighting parts of the documentation or questions that came up when using CuPy that were not otherwise clear. Having this perspective (particularly from new users) is incredibly helpful.
The fact that cupy.asarray
copies asynchronously is certainly one. While several of us were pretty sure this was the case, the exact text in the CuPy docs saying this was hard to find. Maybe this should live as a note under cupy.asarray
. That said, offline we did find this text in the docs, which helped clarify this particular point:
In CuPy, all CUDA operations such as data transfer (see the Data Transfer section) and kernel launches are enqueued onto the current stream, and the queued tasks on the same stream will be executed in serial (but asynchronously with respect to the host).
Another idea that came up in discussion was having a notebook covering these things. We do have this notebook. Perhaps we could add a comment there.
This was done in PR: https://github.com/rapidsai/cucim/pull/315