-
Notifications
You must be signed in to change notification settings - Fork 14
feat(zero_shot): enhance evaluation pipeline with rerun-judge and cha… #63
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
base: main
Are you sure you want to change the base?
Conversation
…rt improvements - Add --rerun-judge flag to re-run pairwise evaluation with different judge model - Enhance chart_generator with additional visualization options - Update schema with new configuration options - Improve zero_shot_pipeline with better checkpoint management - Fix minor issue in openai_chat_model
Summary of ChangesHello @XiaoBoAI, 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 upgrades the zero-shot evaluation pipeline by introducing more granular control over the evaluation process and expanding its visualization capabilities. The addition of a dedicated flag for re-running judge evaluations and improvements to incremental data collection streamline the workflow for model comparison. Furthermore, new chart types offer richer insights into model performance, making the evaluation process more efficient and informative. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
The pull request introduces significant enhancements to the zero-shot evaluation pipeline, primarily focusing on improved checkpoint management, incremental evaluation capabilities, and advanced visualization options. The new --rerun-judge flag allows for efficient re-evaluation with different judge models without re-running the entire pipeline. The chart_generator now supports both vertical bar charts and win rate matrix heatmaps, providing more comprehensive visualization of results. The zero_shot_pipeline has been refactored to support incremental collection of responses and pairwise evaluation, making it more robust and efficient for large-scale evaluations. Additionally, a minor fix for Gemini model compatibility in openai_chat_model is included. Overall, these changes greatly improve the usability, efficiency, and analytical depth of the evaluation framework.
| # Load config to get output_dir | ||
| loaded_config = load_config(str(config_path)) | ||
| effective_output_dir = output_dir or loaded_config.output.output_dir |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The configuration is loaded twice: once here to get the output_dir and again inside _run_evaluation. To improve efficiency and avoid redundant operations, consider passing effective_output_dir directly to _run_evaluation and modifying _run_evaluation to accept it, thus removing the need for _run_evaluation to load the config itself.
…rt improvements
OpenJudge Version
[The version of OpenJudge you are working on, e.g.
import openjudge; print(openjudge.__version__)]Description
[Please describe the background, purpose, changes made, and how to test this PR]
Checklist
Please check the following items before code is ready to be reviewed.
pre-commit run --all-filescommand