Support Nemotron 3.5 Lightning - #837
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nvidia/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-BF16checkpoint at revisionb3caaabed0263651a17dc1f2d4ce97e794f76c44NemotronHHandlerand already-qualified Nano Mamba-2, MoE, attention, context-parallel, LoRA, export, and native-vLLM paths because Lightning's 52-layer backbone geometry and schedule are identicalmodel.layersLoRA namespace without changing Nano's remote-codebackbone.layerscontractlayers_block_typeschedules and derive a missing scalar depth from that canonical scheduleScope
This is an exact-checkpoint, same-architecture qualification. It does not change attention, FlexAttention, recurrent/Mamba-2, MoE, CP, or serving math. It does not alter train/inference thresholds, throughput floors, timeouts, lifecycle behavior, or compile settings. The throughput entry binds Lightning's exact workload fingerprint to the existing Nemotron-H profile without changing any floor.
Supported here: the BF16 backbone of
NVIDIA-Nemotron-3.5-Lightning-30B-A3B-BF16only. Lightning MTP, FP8/NVFP4 variants, Base/Super/Ultra variants, and multimodal checkpoints are not enabled.Validation
mainThe complete default model-support workflow was intentionally not run for this same-architecture alias qualification. The optional correctness-sensitivity suite was also intentionally not run.