Add data_process figure

[hiyuchang]

Description

As the title says.

Checklist

Please check the following items before code is ready to be reviewed.

• Code has passed all tests
• Docstrings have been added/updated in Google Style
• Documentation has been updated
• Code is ready for review

[gemini-code-assist]

Summary of Changes

Hello @hiyuchang, 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 streamlines the visual documentation of data processing and pipeline designs within the project. It replaces multiple older figures with a single, updated, and more comprehensive diagram across the English and Chinese READMEs, as well as the Sphinx documentation. This change aims to provide a clearer and more consistent visual representation of the data flow within Trinity-RFT.

Highlights

• Consolidated Data Pipeline Figures in READMEs: The README.md and README_zh.md files have been updated to replace two separate figures illustrating data processor architecture and high-level data pipeline design with a single, more comprehensive figure. This change also includes updating the image source URLs and summary texts.
• Updated Data Pipeline Figure in Sphinx Documentation: The docs/sphinx_doc/source/main.md file now uses a single, updated figure to represent data pipelines, replacing two older ones. The local image path for this figure has also been updated to reflect the new asset.
• Refined Data Processor Figure in Tutorial Documentation: The docs/sphinx_doc/source/tutorial/example_data_functionalities.md file has had its data processor figure updated with a new image URL, and a redundant style="height: 500px;" attribute has been removed from the image tag.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 data processing figure across several documentation files (README.md, README_zh.md, and Sphinx docs). The change consolidates previous figures into a single, new one, which improves consistency. The changes are generally good. I've added one suggestion to ensure the new, wider image is displayed responsively in the tutorial documentation.