-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[ao][sparsity] Bug Fix: Retain mask and config while replacing data in data sparsifier #82129
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
Conversation
…n data sparsifier Bug: The config and mask were being recreated while replacing data on the data sparsifier. Fix: Introduced an argument `use_old_mask` which when set `True` uses the old mask. If new config is not specified, the data sparsifier by default uses the old config with the new data. Also, added unit tests to check this bug. Test Plan: ```python test/test_ao_sparsity.py TestBaseDataSparsifier``` [ghstack-poisoned]
🔗 Helpful links
✅ No Failures (0 Pending)As of commit f904b70 (more details on the Dr. CI page): Expand to see more💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
…cing data in data sparsifier" Bug: The config and mask were being recreated while replacing data on the data sparsifier. Fix: Introduced an argument `use_old_mask` which when set `True` uses the old mask. If new config is not specified, the data sparsifier by default uses the old config with the new data. Also, added unit tests to check this bug. Test Plan: ```python test/test_ao_sparsity.py TestBaseDataSparsifier``` [ghstack-poisoned]
…cing data in data sparsifier" Bug: The config and mask were being recreated while replacing data on the data sparsifier. Fix: Introduced an argument `use_old_mask` which when set `True` uses the old mask. If new config is not specified, the data sparsifier by default uses the old config with the new data. Also, added unit tests to check this bug. Test Plan: ```python test/test_ao_sparsity.py TestBaseDataSparsifier``` [ghstack-poisoned]
torch/ao/sparsity/_experimental/data_sparsifier/base_data_sparsifier.py
Outdated
Show resolved
Hide resolved
…cing data in data sparsifier" Bug: The config and mask were being recreated while replacing data on the data sparsifier. Fix: Introduced an argument `use_old_mask` which when set `True` uses the old mask. If new config is not specified, the data sparsifier by default uses the old config with the new data. Also, added unit tests to check this bug. Test Plan: ```python test/test_ao_sparsity.py TestBaseDataSparsifier``` [ghstack-poisoned]
…cing data in data sparsifier" Bug: The config and mask were being recreated while replacing data on the data sparsifier. Fix: Introduced an argument `reuse_mask` which when set `True` uses the old mask. If new config is not specified, the data sparsifier by default uses the old config with the new data. Also, added unit tests to check this bug. Test Plan: ```python test/test_ao_sparsity.py TestBaseDataSparsifier``` [ghstack-poisoned]
|
@pytorchbot merge -g |
|
@pytorchbot successfully started a merge job. Check the current status here |
|
Hey @macandro96. |
…data sparsifier (#82129) (#82129) Summary: Bug: The config and mask were being recreated while replacing data on the data sparsifier. Fix: Introduced an argument `reuse_mask` which when set `True` uses the old mask. If new config is not specified, the data sparsifier by default uses the old config with the new data. Also, added unit tests to check this bug. Pull Request resolved: #82129 Approved by: https://github.com/z-a-f Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/7391dec96ab9f52b841973149922ff39ada489ff Test plan from GitHub: ```python test/test_ao_sparsity.py TestBaseDataSparsifier``` Reviewed By: osalpekar Differential Revision: D38226946 Pulled By: macandro96 fbshipit-source-id: 21974cd0e4e53eb860fecd5319c4dea238348657
Stack from ghstack (oldest at bottom):
Bug: The config and mask were being recreated while replacing data on the data sparsifier.
Fix: Introduced an argument
reuse_maskwhich when setTrueuses the old mask. If new config is notspecified, the data sparsifier by default uses the old config with the new data.
Also, added unit tests to check this bug.
Test Plan:
python test/test_ao_sparsity.py TestBaseDataSparsifier