-
Notifications
You must be signed in to change notification settings - Fork 603
Harden DASC analysis and restore boundaries #2394
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
kaix-nv
merged 2 commits into
feature/dasc-state-sparsity-review-contract
from
feature/dasc-state-sparsity-review-api
Sep 11, 2026
+158
−26
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[SUGGESTION] Widening this
exceptto the new base class is the right call for save/restore symmetry, and fail-closed is preserved for the hard cases (_get_gdn_modulesstill raises a plainApplyModeErrorfor "no supported GDN modules" and for unconverted subclasses, so neither is swallowed here). One follow-up on the user-facing guidance:For the newly recoverable case, the advice is wrong.
_DASCDecayParametersUnavailableErrorfires when a supported GDN identity is present butA_log/dt_biasare temporarily unavailable — parameters flattened by a sharding wrapper, or a model not yet materialized off the meta device. The remedy there is to materialize the parameters and re-save/re-validate, not to recalibrate: the policy itself is still valid for this checkpoint, and re-runningcalibrate()on a model whose decay tensors are missing fails with the same error. Concatenating"re-run calibrate() before deployment"onto that message (line 103, and again at line 117) sends users down a dead end.Since both handlers now cover two distinct conditions, consider making the remedy condition-specific, e.g.:
and formatting the warning with
_STALENESS_REMEDIES[type(error)]. The same distinction applies to the guide text added indocs/source/guides/6_sparsity.rst— "export_policy rejects it until recalibration" is accurate for geometry/decay drift, but recalibration is not the fix for temporarily unavailable tensors.