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
Got it, thanks. Yeah, I don't know if it's worthwhile to directly map Ibis to_torch to Polars to_torch for performance or other reasons.
gforsyth
added
polars
The polars backend
onboarding
Issues that can be addressed by someone less familiar with ibis
and removed
onboarding
Issues that can be addressed by someone less familiar with ibis
labels
May 10, 2024
Author of the Polars to_torch export here... For the curious, the advantage in a native export path wouldn't be performance (both paths require only a single copy per-array, with no conversion overheads), it would be in avoiding the pyarrow dependency. However, if you've already eaten that import cost then there's no advantage to be had by adding a native path (aside from access to export modes other than "dict").
I see Polars recently added
to_torch
:https://www.linkedin.com/posts/pola-rs_export-your-polars-dataframe-directly-to-activity-7193568311769542656-kqRz
I see Ibis has a
to_torch
API: #6518Is the former supported via the latter?
Code of Conduct
The text was updated successfully, but these errors were encountered: