add LongContext-ICL-Annotation competition

[ftgreat]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @ftgreat, 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 introduces the foundational structure for a new competition named "LongContext-ICL-Annotation," which aims to challenge participants in automatic data annotation within long context scenarios. The changes establish the necessary directory structure and provide initial documentation, including a detailed list of eight specific tasks designed to test capabilities with extensive contextual information.

Highlights

• New Competition Framework: A new directory, 'LongContext-ICL-Annotation', has been added under 'openseek/competition/', establishing the framework for a new challenge.
• Initial Documentation: Initial README files, both in English and Chinese, have been included to introduce the 'LongContext-ICL-Annotation' competition.
• Competition Tasks Defined: A 'data' subdirectory has been created, containing a 'README.md' that outlines 8 distinct tasks for the competition, each specifying a minimum context length of 30K and 500 test samples.

🧠 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 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 adds the initial files for the 'LongContext-ICL-Annotation' competition. The changes include creating README files for the competition and its data. My review focuses on improving the clarity and completeness of these documentation files. I've suggested adding more details to the main README file to make it more informative for participants. I also found a typo and a missing newline in the data README. Additionally, there appears to be a typo in the filename READMD_zh_cn.md, which should likely be README_zh_cn.md.

[gemini-code-assist]

This README file is very sparse and acts as a placeholder. To provide better context for the competition, please consider adding more details, such as:

• A brief description of the competition's goals.
• Information on how to participate.
• Details about the dataset format.
• The evaluation metrics that will be used.
• A timeline with important dates.

[gemini-code-assist]

There's a typo in the task name 'kernel_genernation'. It should be 'kernel_generation'.

Also, it's a good practice to add a newline at the end of the file to avoid issues with some tools and file concatenations.

Suggested change

	| openseek-8 | kernel_genernation | 30K | 500 |
	| openseek-8 | kernel_generation | 30K | 500 |