Why does the zero-cost predictor not integrate with model search space module
- Dominant language
- Python
- Stars
- 595
- Forks
- 133
- PR merge metrics
- No merged PRs in 30d
Description
In file `NASLib/tree/Develop/naslib/predictors/zerocost_v1.py`, it use the search space defined in `NASLib/tree/Develop/naslib/predictors/utils/models`. It basically defines some architectures of nasbench101 and nasbench201.
However, there is already a module called `search_space.` including many search spaces, and they are well-structured,
Why the `zerocost_v1` don't use the model defined in `search_space`?
Contributor guide
Research direction
Compare NASLib/tree/Develop/naslib/predictors/zerocost_v1.py and the models under NASLib/tree/Develop/naslib/predictors/utils/models with the existing search_space module. First determine whether zerocost_v1 should support the shared search-space interfaces, then define the expected integration scope and validation criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100