MLBazaar / MLBazaar/AutoBazaar
Allow user to integrate custom tuners
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Autobazaar currently supports three tuners: gp, gpei, and uniform. It allows users to choose from among them. It is not currently supported to use a different tuner, even if the tuner follows the BTB Tuner API.
Suggested behavior:
- modify
autobazaar.search.PipelineSearcherto take a more flexible inputtuner_type - if
tuner_typeis a string, look up a tuner class inbtb.tuning.tunersby matching on case-insensitive names with or withoutTunersuffix. - if
tuner_typeis a string with the FQ name of a class, then try to import the tuner, confirm it is a subclass of BaseTuner, and then proceed. - else if
tuner_typeis a subclass ofbtb.tuning.tuners.base.BaseTunerthen proceed and instantiate an instance of this tuner - else error
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in autobazaar.search.PipelineSearcher and inspect how its current tuner_type values are handled. Read btb.tuning.tuners and btb.tuning.tuners.base.BaseTuner to understand name lookup, imports, subclass validation, and instantiation. Done means supported names, fully qualified classes, and BaseTuner subclasses work, while invalid inputs error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100