Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Difference between standalone implementation and full package #2

Open
albertcthomas opened this issue Nov 12, 2024 · 3 comments
Open

Comments

@albertcthomas
Copy link

albertcthomas commented Nov 12, 2024

If I want to use Tabmini in one of my projects I think I can only use the standalone implementation. Is the full package mostly needed if I want to reproduce the results of the papers and having hyperopt? Or are there other benefits in installing the full package?

@kegl
Copy link

kegl commented Nov 12, 2024

I'm a colleague of Albert. What we'd need is a classical fit/predict API, do you guys think it would be possible?

@Yura52
Copy link
Contributor

Yura52 commented Nov 13, 2024

@albertcthomas the "full package" (i.e. bin, lib etc.) is needed only to reproduce our setup used the paper, with hyperparameter tuning etc. So if you simply want to import TabM without using our "infrastructure", the standalone implementation is recommended: it is the exact full-featured implementation of TabM.

@Yura52
Copy link
Contributor

Yura52 commented Nov 13, 2024

@kegl I don't expect the Scikit-learn API to be implemented within this repository. However, I totally understand the motivation behind the request, and we are currently thinking of how to make the training easier for users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants