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

How are the quantization parameters of block_ap passed to the e2e-qp stage?

Open
#29 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the reported load_checkpoint_in_model(...) call and trace how the block_ap checkpoint is handed to the e2e-qp stage. Compare which quantization scales and zero points are expected to be consumed; done means determining whether the "were not used" messages are expected and identifying the relevant checkpoint-loading behavior.

Written by the indexing model from the issue text.

Description

Thank you for your work. I noticed that when loading the model between the two stages, load_checkpoint_in_model(model, checkpoint=model_path, device_map=device_map, offload_state_dict=True), all the scales and zero points were indicated as "were not used." Is this normal?

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.