Conversation
Summary of ChangesHello @toby-coleman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the flexibility of custom search spaces within the tuning framework. By allowing the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
|
Benchmark comparison for |
There was a problem hiding this comment.
Code Review
This pull request enhances the custom search space functionality by allowing the ProcessSpec to be passed as an optional spec argument to the search space function. This is a valuable feature for creating more dynamic and context-aware tuning configurations. The implementation is solid, involving a necessary refactoring to defer search algorithm initialization until the run method, where the ProcessSpec is available. The accompanying test changes are thorough, including parameterization to cover both old and new custom space function signatures, and a fix for an incorrect parameter name. I have one suggestion to improve the robustness of the search space function resolution.
|
Benchmark comparison for |
|
Benchmark comparison for |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Benchmark comparison for |
Summary
Improve custom search space by allowing the
ProcessSpecto be passed as an optionalspecargument. This allows users to build more general search spaces, which can read e.g. the process/component params.Changes
specargument on custom search space.