fix: validate final layer in VRAM stage compare#41
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
Make
aten/vram_stage_compare.pyvalidate the requested decoder layer instead of always reading layer 0 weights andO_full_0.Changes:
layer_idxargument tocompare_stageslayer_idxto the lastW_o_<idx>.ptfound in the build directoryW_o,W_gate,W_up, andW_downfor that layerO_full_<layer_idx>from generated ASM commentslayer_idxin the returned result dictThis supports multi-layer native emulator validation where the final-layer VRAM stage comparison is the authoritative check.
Validation
py_compilepassed foraten/vram_stage_compare.pylayer_idx=1O_proj + residual: 100.00% allclose, MSE4.18e-06norm + FFN + residual + final_norm: 100.00% allclose, MSE2.61e-05