fix: resolve multi-iteration tensor file overwrite and simplify precision checker #104
+637
−444
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
Fix precision checker file accumulation issue during multi-iteration runs and simplify the overall implementation.
Changes
Counter Mechanism Fix
ResetCounters()method to reset tensor counter at iteration boundariesPrecisionCheckEnvwiththread_localstorage for thread safetyResetCounters()at the start of each training step in gpt2/llama3Precision Checker Refactoring
SaveNpy()function with rank subdirectory support[GAS-X] [L-Y] name_idx_stage tensor[i]: dtype=... shape=... min=... max=... mean=... [values] [NaN:X Inf:Y]New Scripts
scripts/precision_check/precision_compare.py- Offline NPY comparison toolscripts/precision_check/run_precision_check_gpt2.sh- GPT2 verification scriptscripts/precision_check/run_precision_check_llama3.sh- LLaMA3 verification scriptDocumentation
docs/precision_checker_guide.mdto reflect current implementationUsage Example
Testing Example
Run verification script: