TODO#
Todo
Right now, this uses the ‘rating’ as a count. Actually use counts.
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit-hpf/lenskit/hpf.py:docstring of lenskit.hpf.HPF, line 4.)
Todo
Support for advanced rating situations is not yet supported:
repeated ratings
mixed implicit & explicit feedback
later actions removing earlier ratings
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit/lenskit/data/dataset.py:docstring of lenskit.data.dataset.Dataset, line 8.)
Todo
Support for item and user content or metadata is not yet implemented.
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit/lenskit/data/dataset.py:docstring of lenskit.data.dataset.Dataset, line 15.)
Todo
Aggregate is currently ignored because repeated interactions are not yet supported.
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit/lenskit/data/dataset.py:docstring of lenskit.data.dataset.Dataset.interaction_matrix, line 6.)
Todo
Right now, selection / subsetting only happens on the CPU, and will move data to the CPU for the subsetting operation. There is no reason, in principle, why we cannot subset on GPU. Future revisions may add support for this.
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit/lenskit/data/items.py:docstring of lenskit.data.items.ItemList, line 44.)
Todo
Repeated interactions are not yet supported.
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit/lenskit/data/convert.py:docstring of lenskit.data.convert.from_interactions_df, line 4.)
Todo
Right now, this uses the ‘rating’ as a count. Actually use counts.
(The original entry is located in /home/runner/work/lkpy/lkpy/lenskit-hpf/lenskit/hpf.py:docstring of lenskit.hpf.HPF, line 4.)
Todo
This chapter needs to be rewritten for 2024.1 (in progress).
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/guide/documenting.rst, line 4.)
Todo
Redo some of those types with user & item data, etc.
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/guide/pipeline.rst, line 53.)
Todo
Provide utility functions to make more common wiring operations easy so there is middle ground between “give me a standard pipeline” and “make me do everything myself”.
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/guide/pipeline.rst, line 56.)
Todo
Rethink the “keyword inputs only” constraint in view of the limitation it places on fallback or other compositional components — it’s hard to specify a component that implements fallback logic for an arbitrary number of inputs.
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/guide/pipeline.rst, line 61.)
Todo
Serialization support other than pickle is not yet implemented.
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/guide/pipeline.rst, line 235.)
Todo
Is it clear to write these capabilities as separate protocols, or would it be
better to write a single Component ABC?
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/guide/pipeline.rst, line 301.)
Todo
It would be good to support e.g. safetensors.
(The original entry is located in /home/runner/work/lkpy/lkpy/docs/old/interfaces.rst, line 21.)