[Model] NemotronH Support

[danielafrimi]

1. Heterogeneuous FFN support
2. Calculate head_dim - Changed from config.expand * config.hidden_size to config.mamba_num_heads * config.mamba_head_dim
3. Added support for explicit head_dim configuration parameter - Falls back to computed hidden_size // total_num_heads when head_dim is not specified (the models does not force head_dim = hidden_size // total_num_heads

[gemini-code-assist]

Code Review

This pull request adds support for heterogeneous FFN and explicit head_dim for Nemotron-H models. The changes are well-aligned with the description and seem correct. However, I've identified one critical issue where a parameter with a None default value is used in an operation that would cause a TypeError, which could lead to a runtime crash. I've provided a suggestion to make this parameter required, which should resolve the issue.

[honghanhh]

As layer_idx can be None, layer_idx + 1 will fail if it's None, adding a guard for layer_idx and ensure hybrid_override_pattern exists before using them would help.

[danielafrimi]

thanks!
change it that now layer_idx cant be None.
for the config.hybrid_override_pattern we do assume that all nemtoronH will have this configuration.

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[danielafrimi]

CI fails on the a test, listed in CI Failures Dashboard - not cause by my changes

[DarkLight1337]

Can you merge from main to fix Hybrid Models test? Also add a test for your model in there

[DarkLight1337]

Thanks for supporting this model in vLLM!

[gournd]

use vllm-ascend and DeepSeek -V3 -w8a8
(VllmWorker rank=2 pid=55990) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=3 pid=56719) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=0 pid=55435) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=3 pid=56785) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=0 pid=55436) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=1 pid=55699) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=1 pid=55700) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!
(VllmWorker rank=2 pid=55990) WARNING 08-11 11:50:32 [config.py:468] MoE DP setup unable to determine quantization scheme or unsupported quantization type. This model will not run with DP enabled.
(VllmWorker rank=3 pid=56719) WARNING 08-11 11:50:32 [config.py:468] MoE DP setup unable to determine quantization scheme or unsupported quantization type. This model will not run with DP enabled.
(VllmWorker rank=0 pid=55435) WARNING 08-11 11:50:32 [config.py:468] MoE DP setup unable to determine quantization scheme or unsupported quantization type. This model will not run with DP enabled.
(VllmWorker rank=2 pid=55989) INFO 08-11 11:50:32 [quantizer.py:85] Using the vLLM Ascend Quantizer version now!

[DarkLight1337]

Looks like you commented on the wrong PR