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
This is more of a question rather than an issue, but is there any plan or opinion on supporting Array API compatibility in autograd? Specifically, I'm wondering about the possibility of implementing methods like __array_function__ and __array_ufunc__ for ArrayBox, in a manner similar to the __array_namespace__ discussed in PR #647.
Adding such compatibility would enable autograd to seamlessly interoperate with libraries that follow the Array API standard, such as xarray, and potentially allow differentiating through operations involving those libraries. This would mean that automatic differentiation could potentially "just work" for any library that dispatches to the underlying array implementation.
The text was updated successfully, but these errors were encountered:
Hi @yaugenst-flex, we don't have any plans (and likely not the resources) to work on Array API compatibility but we would be happy about all contributions that extend or improve autograd's usability.
This is more of a question rather than an issue, but is there any plan or opinion on supporting Array API compatibility in autograd? Specifically, I'm wondering about the possibility of implementing methods like
__array_function__
and__array_ufunc__
forArrayBox
, in a manner similar to the__array_namespace__
discussed in PR #647.Adding such compatibility would enable autograd to seamlessly interoperate with libraries that follow the Array API standard, such as xarray, and potentially allow differentiating through operations involving those libraries. This would mean that automatic differentiation could potentially "just work" for any library that dispatches to the underlying array implementation.
The text was updated successfully, but these errors were encountered: