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
it is important to be able to control on which device newly created arrays get placed and where execution happens.
We do mention separate needs for array allocation control and execution control.
When describing the option 3 which this data API adopts, we only talk about allocation control:
Local control via explicit keywords and a method to transfer arrays to another device.
I think it is important to explicitly add that the execution takes place local to the data, a.k.a. "computation follows data" convention.
So I suggest we modify item 3 to say
Local control for data allocation target via explicit keywords, with convention that execution takes place on the same device where all argument arrays are allocated; methods for explicitly transferring data between devices.
The text was updated successfully, but these errors were encountered:
Additionally, the device support document we state that method ary.to_device(device) must be provided, but this method is not listed in the API specs document.
In the document device support we state
We do mention separate needs for array allocation control and execution control.
When describing the option 3 which this data API adopts, we only talk about allocation control:
I think it is important to explicitly add that the execution takes place local to the data, a.k.a. "computation follows data" convention.
So I suggest we modify item 3 to say
The text was updated successfully, but these errors were encountered: