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
{{ message }}
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.
In #62 we introduce tox testing environments for metatensor-core with numpy arrays and with torch tenors. For now in tests/equisolve_tests/numpy/utilities.py we set use_torch to False, so all tests are not run using numpy as array backend. But we probably also want to support torch tensors for modules like Ridge and SparseKRR. Internally everything will be converted to numpy arrays (which we eventually change also at some point).
This would go hand in hand with a renaming of the numpy submodule to something less specific. One could use the term shallow for shallow ML methods like linear and kernel models. Or we split it up into kernel_ridge and linear_model as scikit-learn does it.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In #62 we introduce tox testing environments for metatensor-core with numpy arrays and with torch tenors. For now in
tests/equisolve_tests/numpy/utilities.py
we setuse_torch
to False, so all tests are not run using numpy as array backend. But we probably also want to support torch tensors for modules like Ridge and SparseKRR. Internally everything will be converted to numpy arrays (which we eventually change also at some point).This would go hand in hand with a renaming of the numpy submodule to something less specific. One could use the term
shallow
for shallow ML methods like linear and kernel models. Or we split it up intokernel_ridge
andlinear_model
as scikit-learn does it.The text was updated successfully, but these errors were encountered: