Skip to content

Conversation

@macandro96
Copy link

@macandro96 macandro96 commented Jul 25, 2022

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_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

…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]
@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Jul 25, 2022

🔗 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.

Click here to manually regenerate this comment.

…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]
macandro96 added 2 commits July 26, 2022 21:29
…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]
@macandro96
Copy link
Author

@pytorchbot merge -g

@pytorchmergebot
Copy link
Collaborator

@pytorchbot successfully started a merge job. Check the current status here

@github-actions
Copy link
Contributor

Hey @macandro96.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

@macandro96 macandro96 added the topic: bug fixes topic category label Jul 27, 2022
facebook-github-bot pushed a commit that referenced this pull request Jul 28, 2022
…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
@facebook-github-bot facebook-github-bot deleted the gh/macandro96/29/head branch July 31, 2022 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants