You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason why Cumo returns 0-dimensional array instead of Ruby numeric object is, to avoid cudaMemcpy from GPU to CPU for performance.
For compatibility between Numo and Cumo, I propose to change behavior of Numo to return 0-dimensional NArray directly without converting it into Ruby numeric object.
The text was updated successfully, but these errors were encountered:
sonots
changed the title
Return 0-dimensional array instead of Ruby numeric object
[PROPOSE} Return 0-dimensional array instead of Ruby numeric object
Jul 7, 2018
sonots
changed the title
[PROPOSE} Return 0-dimensional array instead of Ruby numeric object
[PROPOSE] Return 0-dimensional array instead of Ruby numeric object
Jul 7, 2018
sonots
changed the title
[PROPOSE] Return 0-dimensional array instead of Ruby numeric object
[Propose] Return 0-dimensional array instead of Ruby numeric object
Jul 7, 2018
This is a feedback from Cumo implementation.
https://speakerdeck.com/sonots/fast-numerical-computing-and-deep-learning-in-ruby-with-cumo?slide=42
Numo:
Cumo:
The reason why Cumo returns 0-dimensional array instead of Ruby numeric object is, to avoid cudaMemcpy from GPU to CPU for performance.
For compatibility between Numo and Cumo, I propose to change behavior of Numo to return 0-dimensional NArray directly without converting it into Ruby numeric object.
The text was updated successfully, but these errors were encountered: