feat: update front page jpg

[shijinpjlab]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @shijinpjlab, I'm Gemini Code Assist¹! 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 primarily focuses on updating image references in the project's README files across different languages, ensuring the correct display of the GUI output image. Additionally, it streamlines the result saving configuration within an example Python script, simplifying how execution results are managed.

Highlights

• Image Format Update: Changed image references in README.md, README_ja.md, and README_zh-CN.md from .png to .jpg for the dingo_gui image, ensuring correct display across all localized READMEs.
• Configuration Simplification: Refactored the result_save configuration in examples/llm_and_rule/only_rule.py to use a single merge: True option, replacing separate bad, good, and raw flags for result saving.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the image format for the GUI output from PNG to JPG in the README files. It also updates an example configuration in only_rule.py to use the merge option for saving results. The change to the example is a bit implicit in its behavior, and I've left a comment with a suggestion to improve its clarity.

[gemini-code-assist]

This change simplifies the configuration, but it might be confusing. By replacing "bad": True, "good": True, "raw": True with just "merge": True, it relies on implicit behavior in the executor where merge: True causes all results to be saved in raw format, regardless of the good and raw flags.

For better clarity in this example, consider adding a comment to explain this behavior.

            "result_save": {
                # When merge is True, all results (good and bad) are saved to a single file in raw format.
                "merge": True,
            }