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 use-case is trommel. The only polars functionality it needs is column selection (pl.select), for which we use dtypes.
In theory we can replace it with duckdv's select_dtypes (or other selection methods). It may be slightly faster, but the important thing is that we shed a lot of dependencies and the methodology may become a portable way to deal with the 'remove metadata -> process data -> append metadata' workflow.
The text was updated successfully, but these errors were encountered:
Implementation note: Converting a duckdb object to numpy is ~20% faster using numpy.array(list(X.fetchnumpy().values())) compared to X.pl().to_numpy().
Surprisingly there is no direct way to go from a duckdb table to a numpy array straight away, only to dictionaries of numpy arrays (per column of course).
The use-case is trommel. The only polars functionality it needs is column selection (pl.select), for which we use dtypes.
In theory we can replace it with duckdv's select_dtypes (or other selection methods). It may be slightly faster, but the important thing is that we shed a lot of dependencies and the methodology may become a portable way to deal with the 'remove metadata -> process data -> append metadata' workflow.
The text was updated successfully, but these errors were encountered: