Skip to content

Conversation

@ZLiao097
Copy link
Contributor

What does this PR do?

Provide an script for DAPO-training qwen2.5-32B on NPU, and update experiment result.

Checklist Before Starting

  • Search for similar PRs. Paste at least one query link here: [recipe] feat: support qwen3-8B/14B DAPO training on ASCEND NPU
  • Format the PR title as [{modules}] {type}: {description} (This will be checked by the CI)
    • {modules} include fsdp, megatron, sglang, vllm, rollout, trainer, ci, training_utils, recipe, hardware, deployment, ray, worker, single_controller, misc, perf, model, algo, env, tool, ckpt, doc, data
    • If this PR involves multiple modules, separate them with , like [megatron, fsdp, doc]
    • {type} is in feat, fix, refactor, chore, test
    • If this PR breaks any API (CLI arguments, config, function signature, etc.), add [BREAKING] to the beginning of the title.
    • Example: [BREAKING][fsdp, megatron] feat: dynamic batching

Test

For changes that can not be tested by CI (e.g., algorithm implementation, new model support), validate by experiment(s) and show results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
image

Response_length/mean Comparison Chart
image

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
image

API and Usage Example

Demonstrate how the API changes if any, and provide usage example(s) if possible.

cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh

Design & Code Changes

Demonstrate the high-level design if this PR is complex, and list the specific changes.

Checklist Before Submitting

Important

Please check all the following items before requesting a review, otherwise the reviewer might deprioritize this PR for review.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a DAPO training script for the Qwen2.5-32B model on Ascend NPUs and updates the documentation accordingly. The changes look good, but I've found a critical shell syntax issue in the new script that will prevent it from running. Please see my comment for the fix.

quoted trainer.logger

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@vermouth1992 vermouth1992 merged commit d2126e7 into volcengine:main Aug 20, 2025
5 checks passed
yellowbee686 pushed a commit to yellowbee686/verl that referenced this pull request Aug 21, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@FightingZhen
Copy link
Collaborator

@ZLiao097 There is a issue #3248 related with this PR, can you have a check?

cczitong123 pushed a commit to cczitong123/verl that referenced this pull request Sep 5, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
DDVD233 pushed a commit to DDVD233/mirl that referenced this pull request Sep 5, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
WncFht pushed a commit to WncFht/verl that referenced this pull request Oct 10, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
techkang pushed a commit to techkang/verl that referenced this pull request Oct 31, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
chenjiaoAngel added a commit to chenjiaoAngel/verl that referenced this pull request Nov 14, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
TimurTaepov pushed a commit to giorgossideris/verl that referenced this pull request Dec 20, 2025
…volcengine#3146)

### What does this PR do?
Provide an script for DAPO-training qwen2.5-32B on NPU, and update
experiment result.

### Checklist Before Starting

- [x] Search for similar PRs. Paste at least one query link here:
[[recipe] feat: support qwen3-8B/14B DAPO training on ASCEND
NPU](volcengine#2836)
- [x] Format the PR title as `[{modules}] {type}: {description}` (This
will be checked by the CI)
- `{modules}` include `fsdp`, `megatron`, `sglang`, `vllm`, `rollout`,
`trainer`, `ci`, `training_utils`, `recipe`, `hardware`, `deployment`,
`ray`, `worker`, `single_controller`, `misc`, `perf`, `model`, `algo`,
`env`, `tool`, `ckpt`, `doc`, `data`
- If this PR involves multiple modules, separate them with `,` like
`[megatron, fsdp, doc]`
  - `{type}` is in `feat`, `fix`, `refactor`, `chore`, `test`
- If this PR breaks any API (CLI arguments, config, function signature,
etc.), add `[BREAKING]` to the beginning of the title.
  - Example: `[BREAKING][fsdp, megatron] feat: dynamic batching`

### Test

> For changes that can not be tested by CI (e.g., algorithm
implementation, new model support), validate by experiment(s) and show
results like training curve plots, evaluation results, etc.

The following are some comparison charts of relevant data from script
testing, where red represents NPU and blue represents GPU.

Critic/rewards/mean Comparison Chart
<img width="1314" height="714" alt="image"
src="https://github.com/user-attachments/assets/3c303100-7106-491b-a6ea-e0bd1926076c"
/>

Response_length/mean Comparison Chart
<img width="1322" height="714" alt="image"
src="https://github.com/user-attachments/assets/9fa01f6f-2774-4b07-a38b-71cb6b5c8359"
/>

Val-core/math_dapo/acc/mean@32 Comparison Chart (Test by aime-2024)
<img width="1320" height="716" alt="image"
src="https://github.com/user-attachments/assets/b6912e3c-89c6-4999-90bb-fa961edc6e4a"
/>


### API and Usage Example

> Demonstrate how the API changes if any, and provide usage example(s)
if possible.

```bash
cd /path/to/verl
bash recipe/dapo/run_dapo_qwen2.5_32b_npu.sh
```

### Design & Code Changes

> Demonstrate the high-level design if this PR is complex, and list the
specific changes.

### Checklist Before Submitting

> [!IMPORTANT]
> Please check all the following items before requesting a review,
otherwise the reviewer might deprioritize this PR for review.

- [x] Read the [Contribute
Guide](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md).
- [x] Apply [pre-commit
checks](https://github.com/volcengine/verl/blob/main/CONTRIBUTING.md#code-linting-and-formatting):
`pre-commit install && pre-commit run --all-files --show-diff-on-failure
--color=always`
- [x] Add / Update [the
documentation](https://github.com/volcengine/verl/tree/main/docs).
- [x] Add unit or end-to-end test(s) to [the CI
workflow](https://github.com/volcengine/verl/tree/main/.github/workflows)
to cover all the code. If not feasible, explain why: ...
- [x] Once your PR is ready for CI, send a message in [the `ci-request`
channel](https://verl-project.slack.com/archives/C091TCESWB1) in [the
`verl` Slack
workspace](https://join.slack.com/t/verl-project/shared_invite/zt-3855yhg8g-CTkqXu~hKojPCmo7k_yXTQ).
(If not accessible, please try [the Feishu group
(飞书群)](https://applink.larkoffice.com/client/chat/chatter/add_by_link?link_token=772jd4f1-cd91-441e-a820-498c6614126a).)

---------

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants