Expose required init_params
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 124
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Some primitives require the user to provide some init_params, and at the moment the list of these required init_params is only available in the primitive specification.
This can make using a pipeline complicated, as the only way to figure out what arguments needed to create an instance is to read the pipeline JSON, see which primitives the pipeline is using, and then load each all the primitives to see what the required init_params are for each one of them.
This issue is to make an MLPipeline classmethod which allows exploring the required init_params of a pipeline before actually loading it.
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 by locating the MLPipeline class and the code that reads pipeline JSON and primitive specifications. Trace how required init_params are currently discovered during loading, then define the classmethod's result from that information. Done means callers can inspect a pipeline's required init_params before loading its primitives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100