Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

about the training data format of e2e training

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python

Research direction

Start by locating the e2e training data preparation path and comparing its format with block-ep (PTQ) in the e2e (QAT) process. Check whether system, assistant, and think tokens are intentionally absent; done means documenting the behavior or defining the required format change.

Written by the indexing model from the issue text.

Description

I noticed that in the e2e training data preparing process, it seems that no special tokens like **"system", "assistant" or "think" tokens are included in the e2e data. So you are just using the same data format as block-ep(PTQ) in the e2e(QAT) process? No try for these structural information?

Dominant language
Python
Stars
351
Forks
38
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenGVLab/EfficientQAT

All issues in OpenGVLab/EfficientQAT

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.